Short answer: Drop the "ActiveCampaign → Deal Created" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in ActiveCampaign, 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.
{"value": "1.00","org_id": "0","status": "0","deal_id": "20","currency": "usd","org_name": "","owner_id": "1","stage_id": "1","contact_id": "31","created_at": "2026-04-11T10:00:00Z","deal_title": "TC test deal","event_type": "deal_add","owner_name": "TinyCommand","occurred_at": "2026-04-11T10:00:00Z","pipeline_id": "1","stage_title": "To Contact","contact_name": "TC","initiated_by": "api","contact_email": "tc@example.com","pipeline_title": "new deal test"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| value | string | "1.00" |
| org_id | string | "0" |
| status | string | "0" |
| deal_id | string | "20" |
| currency | string | "usd" |
| org_name | string | "" |
| owner_id | string | "1" |
| stage_id | string | "1" |
| contact_id | string | "31" |
| created_at | string | "2026-04-11T10:00:00Z" |
| deal_title | string | "TC test deal" |
| event_type | string | "deal_add" |
| owner_name | string | "TinyCommand" |
| occurred_at | string | "2026-04-11T10:00:00Z" |
| pipeline_id | string | "1" |
| stage_title | string | "To Contact" |
| contact_name | string | "TC" |
| initiated_by | string | "api" |
| contact_email | string | "tc@example.com" |
| pipeline_title | string | "new deal test" |
One trigger. 11+ downstream actions. Zero glue.