HActionHeySummitUpdated September 2026

How do I register an attendee in HeySummit?

Short answer: You can register heysummit attendee in HeySummit by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the HeySummit Register HeySummit Attendee action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Inputs

The fields this action accepts.

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.

Sample request

{
  "event_id": "{{trigger.event_id}}",
  "email": "e.g. user@example.com",
  "first_name": "e.g. Jane",
  "last_name": "e.g. Doe"
}

Returns

{
  "id": 456,
  "email": "user@example.com",
  "first_name": "Jane"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Register HeySummit Attendee.

Any of these apps can fire this action as part of a workflow.

Google Sheets → HeySummit

2 Google Sheets triggers

HubSpot → HeySummit

18 HubSpot triggers

FAQ

Questions about Register HeySummit Attendee.

What does the Register HeySummit Attendee action do in HeySummit?

Programmatically registers someone for a summit with optional source attribution. For "partner promo brought this lead → auto-register with the partner's attribution code" workflows.

What inputs does Register HeySummit Attendee require?

Required: Event ID, Email, First Name. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if HeySummit returns an error?

The run history shows the failed step with its input and the error message HeySummit returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Register HeySummit Attendee support batch operations?

Run Register HeySummit Attendee inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within HeySummit's rate limits.

More actions

Other HeySummit actions.

Action

List HeySummit Attendees

Paginated registrations for a specific summit event. For "all attendees → sync to CRM" or "no-shows → send replay link" post-event workflows.

Action

List HeySummit Events

Returns every event/summit on the account with status, dates, attendee counts. For inventorying summit catalog and for resolving event IDs at workflow setup.