Short answer: Drop the "Freshsales → Create Freshsales Contact" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
First Name first_name | string | Required | First Name. e.g. "John" |
Last Name last_name | string | Required | Last Name. e.g. "Doe" |
Email email | string | Required | Primary email address |
Mobile Number mobile_number | string | Optional | Mobile Number. e.g. "+15551234567" |
Work Phone work_number | string | Optional | Work Phone. e.g. "+15559876543" |
Job Title job_title | string | Optional | Job Title. Example: VP of Engineering |
Company Name company_name | string | Optional | Company Name. Example: Acme Inc |
Lead Source medium | string | Optional | How this contact was acquired |
{"first_name": "John","last_name": "Doe","email": "user@example.com","mobile_number": "+15551234567","work_number": "+15559876543"}
{"contact": {"id": 1,"email": "john@example.com","last_name": "Doe","first_name": "John"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.