Short answer: Drop the "RingCentral → RingCentral Call Completed" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in RingCentral, 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": "+15559876543","from": "+15551234567","status": "Disconnected","direction": "Inbound","session_id": "s-1"}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| to | string | "+15559876543" |
| from | string | "+15551234567" |
| status | string | "Disconnected" |
| direction | string | "Inbound" |
| session_id | string | "s-1" |
One trigger. 6+ downstream actions. Zero glue.