Short answer: Drop the "Freshsales → Freshsales Contact Updated" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Freshsales, not on a polling schedule.
Drop it on the canvas. Configure a couple of fields. Publish.
You don’t need to read this. Tiny Command auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.
{"contact": {"id": 3001,"city": "San Francisco","email": "sarah.chen@example.com","state": "CA","address": "456 Mission St, San Francisco, CA 94105","company": {"id": 501,"name": "Acme Corp"},"country": "US","owner_id": 100,"job_title": "VP of Operations","last_name": "Chen","created_at": "2026-03-10T14:30:00Z","department": "Operations","first_name": "Sarah","updated_at": "2026-04-23T11:45:00Z","work_number": "+14155551234","mobile_number": "+14155557890","lead_source_id": 2}}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| contact | object | { … } |
| contact.id | number | 3001 |
| contact.city | string | "San Francisco" |
| contact.email | string | "sarah.chen@example.com" |
| contact.state | string | "CA" |
| contact.address | string | "456 Mission St, San Francisco, CA 94105" |
| contact.company | object | { … } |
| contact.company.id | number | 501 |
| contact.company.name | string | "Acme Corp" |
One trigger. 12+ downstream actions. Zero glue.