Short answer: Drop the "Trafft → Create Appointment" 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 |
|---|---|---|---|
Service ID service_id | string | Required | The Service ID assigned by Trafft. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Employee ID employee_id | string | Required | — |
Customer Email customer_email | string | Required | The email address. Used as the recipient or identifier depending on context. |
Customer First Name customer_first_name | string | Required | — |
Customer Last Name customer_last_name | string | Optional | — |
Start (ISO) starts_at | string | Required | 2026-05-15T10:00:00Z |
{"service_id": "{{trigger.service_id}}","employee_id": "{{trigger.employee_id}}","customer_email": "e.g. user@example.com","customer_first_name": "{{trigger.customer_first_name}}","customer_last_name": "{{trigger.customer_last_name}}"}
{"id": 123,"status": "approved","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.