Short answer: You can update freshsales contact in Freshsales by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Freshsales Update Freshsales Contact action to a workflow, map its 7 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Contact ID contact_id | string | Required | The numeric ID of the contact to update |
First Name first_name | string | Optional | Contact's first (given) name. |
Last Name last_name | string | Optional | Contact's last (family) name. |
Email email | string | Optional | Email. e.g. "user@example.com" |
Mobile Number mobile_number | string | Optional | Mobile Number. e.g. "+15551234567" |
Job Title job_title | string | Optional | Job Title. Example: VP of Engineering |
Company Name company_name | string | Optional | Company Name. Example: Acme Inc |
{"contact_id": "e.g. 12345","first_name": "e.g. Jane","last_name": "e.g. Doe","email": "user@example.com","mobile_number": "+15551234567"}
{"contact": {"id": 12345,"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.