Short answer: Drop the "HeySummit → Register HeySummit Attendee" 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 |
|---|---|---|---|
Event ID event_id | string | Required | The Event ID assigned by Heysummit. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Email email | string | Required | The email address. Used as the recipient or identifier depending on context. |
First Name first_name | string | Required | Contact's first (given) name. |
Last Name last_name | string | Optional | Contact's last (family) name. |
{"event_id": "{{trigger.event_id}}","email": "e.g. user@example.com","first_name": "e.g. Jane","last_name": "e.g. Doe"}
{"id": 456,"email": "user@example.com","first_name": "Jane"}
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.