HActionHeySummitUpdated September 2026

How do I list HeySummit attendees?

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

List HeySummit Attendees in HeySummit — start free All 3 HeySummit actions

List HeySummit Attendees in HeySummit — start free

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.
Page Size page_size	number	Optional	–

Sample request

{
  "event_id": "123",
  "page_size": "{{trigger.page_size}}"
}

Returns

{
  "results": [
    {
      "id": 456,
      "email": "attendee@example.com",
      "first_name": "Jane",
      "registered_at": "2026-05-01T12:00:00Z"
    }
  ]
}

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

Triggered by

Apps that pair well as the trigger for List HeySummit Attendees.

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 List HeySummit Attendees.

What does the List HeySummit Attendees action do in HeySummit?

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

What inputs does List HeySummit Attendees require?

Required: Event ID. 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 List HeySummit Attendees support batch operations?

Run List HeySummit Attendees 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 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.

Action

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.

List HeySummit Attendees in HeySummit — start free