Resources · Make integration

HeySummit Make integrationAutomate HeySummit with Make.

Can Make react the moment someone registers for your HeySummit event? Yes. The HeySummit Make integration gives you 9 modules: 2 instant triggers and 7 actions. This guide walks event organizers through the connection, a first scenario and each module.

Try the HeySummit integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the HeySummit Make integration do for your events?

The HeySummit Make integration links your HeySummit account to Make, a no-code tool where you build a scenario: an automation made of connected steps. Each step is a module. HeySummit modules can start a scenario when someone registers, add attendees for you, or look up an event, a talk or an attendee so other apps get the details.

Every new registrant lands in your CRM. Watch new attendees fires as soon as someone signs up for an event, and Get an event adds the event details, so your sales team knows which summit the lead came from.

Speakers hear about their audience. Watch new talk signups reacts to each registration for a talk. Pair it with Get a talk and post the session details in your team chat or a shared sheet.

Registrations from elsewhere become attendees. When people sign up through a form or a partner list in another app, Create an attendee registers them in HeySummit, with no copy and paste.

What the app does not offer: no search module, and no module that updates or deletes an attendee. For other parts of the HeySummit API, Make an API call reuses your connection. The same app may also have an n8n node; the n8n vs Make comparison helps you weigh both. New to the editor? The Make training covers the basics, and Make pricing explains how operations (one run of one module, what your plan counts) add up.

Connect

How do you connect HeySummit to Make?

  1. 01

    Copy your API key

    In HeySummit, open Event Setup, then API Settings, and copy the API key shown on screen. You need an active HeySummit account for this, since the key is what lets Make act on your events.

  2. 02

    Add a HeySummit module

    In your Make scenario, add any HeySummit module and click Create a connection. A connection is your HeySummit account linked to Make once, then reused by every HeySummit module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when several people share the workspace. Paste the API key you copied, or follow the on-screen instructions, and save.

First scenario

Your first scenario: turn form signups into HeySummit attendees

GoalWhen a registration arrives in your form tool, Make creates the matching attendee in HeySummit.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. It belongs to the app where your registrations arrive, here a form tool.

  2. 02

    Pick the form trigger

    Search the form app by name, choose its trigger for new submissions and connect that account. Each submission becomes a bundle, one item that travels from one module to the next.

  3. 03

    Add Create an attendee

    Click the + on the right of the first module, search HeySummit and pick Create an attendee. Link your account with Create a connection, then fill each field by mapping data from the form.

  4. 04

    Test with Run once

    Send one test submission, then click Run once. Read the bundles each module received and check that the new attendee now appears in HeySummit.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default. Keep it or choose another interval your plan allows, then switch the scenario on.

Triggers

What starts a HeySummit scenario?

2 modules start a scenario when something happens in HeySummit. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by HeySummit as soon as it happens.

HeySummit1Watch new attendees

Watch new attendees

Instant trigger

In Make“Triggers when a new attendee registers for your event.”

You get a scenario that starts the moment a person registers for one of your HeySummit events, with that attendee passed along as a bundle. It is the natural entry point for welcome emails, CRM updates or a shared guest list.

How it fires
instant. HeySummit calls Make through a webhook as soon as the registration happens.
When to use it
you want every event registrant copied into your CRM or newsletter tool without exporting lists by hand.
Watch out
Make asks you to click Create a webhook before Create a connection, so follow that order when you add it.
HeySummit2Watch new talk signups

Watch new talk signups

Instant trigger

In Make“Triggers when a new registration for a talk is made.”

Each new registration for a talk reaches your scenario on its own, which matters when your summit runs several sessions and each speaker cares about their own audience.

How it fires
instant. HeySummit calls Make through a webhook the moment someone signs up for a talk.
When to use it
pick it over Watch new attendees when the talk, not the event as a whole, drives the follow-up, such as alerting a speaker or filling a per-session sheet.
Watch out
if you run both triggers in separate scenarios, decide which one sends each message so nobody gets the same note twice.
Modules

What can HeySummit do inside a scenario?

HeySummit gives you 7 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

HeySummit1

Create an attendee

Action

In Make“Creates a new attendee for a specified event.”

People who signed up somewhere else end up on the official guest list: this module adds a new attendee to the HeySummit event you choose.

When to use it
registrations reach you through a form, a partner spreadsheet or a CRM, and you want each one registered in HeySummit without retyping.
Watch out
every run adds an attendee, so test with Run once on a single entry before switching the scenario on.
HeySummit2

Get an attendee

Action

In Make“Returns information about a specific attendee for an event.”

Your scenario gets the full HeySummit record of one attendee of an event, which gives later modules more to work with than a name alone.

When to use it
the scenario already knows who the person is, from a trigger or a sheet, and you need their HeySummit details before writing them to your CRM.
Watch out
it targets a single attendee, and the HeySummit app offers no search module to pull a list.
HeySummit3

Get an event

Action

In Make“Returns information about a specific event by its ID.”

A message or a report can name the right summit: this module returns what HeySummit holds about one event, found by its ID.

When to use it
right after Watch new attendees, to add the event details to the lead you pass to sales or to your newsletter tool.
Watch out
map the event ID from an earlier module instead of typing it, or the scenario will read the same event on every run.
HeySummit4

Get a talk

Action

In Make“Returns information about a specific talk for an event.”

Speaker alerts and session recaps get their substance here, since the module hands your scenario the details of one talk from an event.

When to use it
after Watch new talk signups, to include the talk information in the note you send to the speaker or the moderator.
Watch out
it reads one talk only, so pair it with a module that tells it which talk to fetch.
HeySummit5

Make an API call

Action

In Make“Sends a custom API call to HeySummit. You can use this to call endpoints that aren’t covered by existing modules.”

The rest of the HeySummit API opens up to your scenario, through the connection you already set up, whenever the other actions fall short.

When to use it
you need an endpoint that none of the listed HeySummit modules covers.
Watch out
you build the request yourself, so this module suits someone comfortable reading an API reference rather than a first-time Make user.
HeySummit6

Archive an Event (deprecated)

ActionIn the docs only

Older scenarios can keep archiving a HeySummit event with this module, but Make labels it deprecated, so treat it as legacy rather than a building block for new work.

When to use it
only when you maintain an existing scenario that already relies on it.
Watch out
for a new build, check whether Make an API call covers the same need, and plan to move off this module.
HeySummit7

Get a Ticket (deprecated)

ActionIn the docs only

A scenario built earlier can still read a HeySummit ticket through this module, although Make flags it as deprecated and publishes no description of it.

When to use it
in an existing scenario that still calls it and that you simply need to keep running.
Watch out
nothing official says what it returns, so click Run once and read the bundle before mapping anything from it.
Need help

Need help automating HeySummit with Make?

A person reads every message.

FAQ

HeySummit and Make: common questions

01Is the HeySummit Make integration free?
Yes, on the Make side. HeySummit is a standard app, so its 9 modules work on the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops a run after 5 minutes and handles files up to 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in operations, one execution of one module on one bundle. Your HeySummit subscription is separate: you still need an active account and an API key.
02What do you need to connect HeySummit to Make?
An active HeySummit account and its API key. In HeySummit, go to Event Setup, then API Settings, and copy the key displayed there. Back in Make, add a HeySummit module, click Create a connection, give the connection a name if you like, and paste the key. If the first module you add is an instant trigger, Make asks you to click Create a webhook before Create a connection. After that, every HeySummit module can reuse the same connection, so the setup happens once for that account.
03Do HeySummit triggers in Make fire in real time?
Yes. Both HeySummit triggers, Watch new attendees and Watch new talk signups, are instant: HeySummit calls Make through a webhook as soon as a registration happens, and the scenario starts right away. A scheduled trigger works differently, since Make checks the app at the interval set on the scenario, every 15 minutes by default. The HeySummit app has no scheduled trigger. In the editor, you spot an instant trigger by the lightning badge on the module. To test one, click Run once, then register a test attendee in HeySummit and read the bundle that arrives.
04What if a HeySummit module is missing in Make?
Use Make an API call. It sends a custom request to the HeySummit API with the connection you already have, so it reaches endpoints the listed modules leave out. Those modules create an attendee and read an attendee, an event or a talk; none updates or deletes a record, and there is no search module. Two older modules, Archive an Event and Get a Ticket, carry a deprecated label, so avoid basing new scenarios on them. For questions about the HeySummit API itself, the HeySummit team is the right contact.
05Should you use Make or n8n for HeySummit?
It depends on what your scenario needs. In Make, HeySummit comes with 9 ready modules, 2 of them instant triggers, and runs on the Free plan as a standard app, so you can test a real scenario before paying for anything. n8n often has a node for the same app, but this page does not cover whether one exists for HeySummit or what it includes. Compare the module lists against your use case, and pick the tool that covers it without workarounds and whose way of counting usage fits your volume.
Same platform

Other docs you might need on this stack.

Browse all integrations