Short answer: Drop the "TidyCal → List Bookings" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Start After (ISO) starts_at | string | Optional | 2026-05-01T00:00:00Z |
End Before (ISO) ends_at | string | Optional | — |
{"starts_at": "2026-05-01T00:00:00Z","ends_at": "{{trigger.ends_at}}"}
{"data": [{"id": 1,"contact": {"name": "Jane Doe","email": "jane@x.com"},"ends_at": "2026-05-11T11:00:00Z","starts_at": "2026-05-11T10:00:00Z"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.