Short answer: Drop the "Freshdesk → Create 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 |
|---|---|---|---|
Name name | string | Required | Name. e.g. "John Doe" |
Email email | string | Required | Email. e.g. "user@example.com" |
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 |
Company ID company_id | string | Optional | Freshdesk company ID to associate |
{"name": "John Doe","email": "user@example.com","phone": "e.g. +14155551234","mobile": "e.g. +14155551234","job_title": "{{trigger.job_title}}"}
{"id": 1001,"name": "John Doe","email": "user@example.com","active": true}
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.