Short answer: Drop the "Salesloft → Salesloft Call Logged" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in Salesloft, 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.
{"to": "+15551234567","notes": "Booked demo for Friday","call_id": 999888,"user_id": 12345,"duration": 180,"person_id": 1234567,"sentiment": "Positive","created_at": "2026-04-11T10:00:00.000Z","disposition": "Connected"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| to | string | "+15551234567" |
| notes | string | "Booked demo for Friday" |
| call_id | number | 999888 |
| user_id | number | 12345 |
| duration | number | 180 |
| person_id | number | 1234567 |
| sentiment | string | "Positive" |
| created_at | string | "2026-04-11T10:00:00.000Z" |
| disposition | string | "Connected" |
One trigger. 6+ downstream actions. Zero glue.