Short answer: Drop the "PayPal → PayPal Subscription Created" trigger on your workflow canvas, add filters if you want them, and publish. It fires within seconds of the event in PayPal, 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.
{"id": "sub_123","status": "ACTIVE","plan_id": "plan_456","start_time": "2026-04-11T10:00:00Z","subscriber": {"name": {"surname": "Doe","given_name": "John"},"email_address": "user@example.com"}}
Every field below can be referenced by name in any action or filter that comes after this trigger.
| Field | Type | Example |
|---|---|---|
| id | string | "sub_123" |
| status | string | "ACTIVE" |
| plan_id | string | "plan_456" |
| start_time | string | "2026-04-11T10:00:00Z" |
| subscriber | object | { … } |
| subscriber.name | object | { … } |
| subscriber.name.surname | string | "Doe" |
| subscriber.name.given_name | string | "John" |
| subscriber.email_address | string | "user@example.com" |
One trigger. 4+ downstream actions. Zero glue.