ActionFreshsalesUpdated September 2026
How do I add a Freshsales contact?
Short answer: You can create freshsales contact in Freshsales by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Freshsales Create Freshsales Contact action to a workflow, map its 8 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
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 |
Sample request
{"first_name": "John","last_name": "Doe","email": "user@example.com","mobile_number": "+15551234567","work_number": "+15559876543"}
Returns
{"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.
Triggered by
Apps that pair well as the trigger for Create Freshsales Contact.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Create Freshsales Contact.
What does the Create Freshsales Contact action do in Freshsales?
Creates a new contact with email (dedupe), name, custom fields, and optional account association. The base hook for "form submission → push to Freshsales" sync workflows.
What inputs does Create Freshsales Contact require?
Required: First Name, Last Name, Email. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Freshsales returns an error?
The run history shows the failed step with its input and the error message Freshsales returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Create Freshsales Contact support batch operations?
Run Create Freshsales Contact inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Freshsales's rate limits.
More actions
Other Freshsales actions.
Action
Create Freshsales Account
Creates a company/account record. Useful for "new B2B prospect → account record before contact" workflow patterns.
ActionCreate Freshsales Deal
Creates a deal with name, amount, pipeline, stage, contact. For "qualified lead → auto-create deal in the AE's pipeline" workflows.
ActionDelete Freshsales Contact
Hard-deletes a contact. For GDPR right-to-erasure workflows; for soft removal use a custom "deleted" tag or status field.
ActionDelete Freshsales Deal
Removes a deal from the pipeline. For "duplicate deal cleanup" or "lost deal archiving" maintenance workflows.
ActionGet Freshsales Contact
Returns a contact by ID with all standard and custom fields plus related deals and activities. The standard lookup before update workflows.
ActionGet Freshsales Deal
Returns a deal by ID with value, stage, contacts, activities. The lookup for forecast workflows or for cross-system reporting.