Short answer: Drop the "Trafft → List Appointments" 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 |
|---|---|---|---|
Page page | number | Optional | — |
Per Page per_page | number | Optional | — |
From Date from_date | string | Optional | Filter appointments starting from this date (YYYY-MM-DD). |
To Date to_date | string | Optional | 2026-05-31 |
{"page": "{{trigger.page}}","per_page": "{{trigger.per_page}}","from_date": "2026-05-01","to_date": "2026-05-31"}
{"data": [{"id": 123,"service": {"name": "Consultation"},"customer": {"email": "x@y.com"},"starts_at": "2026-05-15T10: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.