Short answer: Drop the "Freshdesk → Update 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 |
|---|---|---|---|
Contact ID contact_id | string | Required | The Contact ID assigned by Freshdesk. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Name name | string | Optional | Name |
Email email | string | Optional | The email address. Used as the recipient or identifier depending on context. |
Phone phone | string | Optional | Phone number in E.164 format (with country code, no spaces). |
Mobile mobile | string | Optional | Phone number in E.164 format (with country code, no spaces). |
Job Title job_title | string | Optional | Job Title |
{"contact_id": "{{trigger.contact_id}}","name": "{{trigger.name}}","email": "e.g. user@example.com","phone": "e.g. +14155551234","mobile": "e.g. +14155551234"}
{"id": 1001,"name": "John Doe Updated","email": "john@example.com"}
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.