Resources · Zapier integration

HeySummit Zapier integrationAutomate HeySummit with Zapier.

The HeySummit Zapier integration listens to your online summit and passes the news on. It offers 4 triggers, 0 actions and 0 searches: registrations, talk sign-ups, speaker submissions and ticket sales start a Zap, and another app does the work.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the HeySummit Zapier integration is for

HeySummit runs online summits: speakers, talks, registrations, tickets. The Zapier integration is a one-way bridge out of it. Something happens in your event, HeySummit tells Zapier, and Zapier runs a step in another tool. Nothing flows back in, because Zapier offers no action that writes into HeySummit.

Three results people build with it, each tied to a real trigger.

A sales feed for the team. Ticket Purchased fires on every ticket bought, so a buyer can land in your CRM or a team chat without anyone exporting a list. Handy on launch day, when sales come in bursts.

A review queue for speaker pitches. New Talk Submission fires once a pitch is ready for review. Turn it into a card on a board and your program committee sees each proposal the moment it lands, not at the end of the call for papers.

Per-talk audience lists. New Talk Attendee fires for each talk a person signs up to. Push those into a sheet and every speaker gets a clean list of who chose their session. New Attendee is the wider net: one run per registration to the event itself.

Now the limits, plainly. Zapier cannot create a talk, add a speaker, register someone or issue a ticket in HeySummit. There is no search step either, so a Zap cannot look up an existing attendee. If your process needs to write into HeySummit, this integration will not do it.

For a broader take on the tool itself, read the Zapier review. If you are still weighing another platform, the HeySummit Make integration page and Make vs Zapier are the next stops.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain English.

Zap
The automation you build on Zapier: one starting event, then one or more steps that run each time that event happens.
Trigger
The event that starts a Zap, here a sale, a registration or a speaker pitch in HeySummit. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you, always in another app for HeySummit.
Task
The unit Zapier bills. One action that completes successfully counts as one task, and your plan caps how many you get each month.
Instant trigger
A trigger the app reports itself: it calls Zapier the moment the event happens. All four HeySummit triggers work this way.
Polling trigger
The other kind: Zapier checks the app on a timer for new items. HeySummit has none, so the timer never applies to this app.
Filter
A step that lets the Zap continue only when what arrived matches a condition you set, and stops it quietly otherwise.
Cost

What a HeySummit Zap really costs

Good news first: HeySummit is not a premium app, so it works on the free Zapier plan.

  • TriggerFree, never counted
  • Successful action1 task each
  • Free plan100 tasks a month, 2-step Zaps
  • Premium appNo, free plan works

The trigger never costs a task. A registration arriving from HeySummit is free; only the action that follows in your other app is billed, and only when it succeeds. A failed action is not counted. The free plan gives 100 tasks a month and builds two-step Zaps: one trigger, one action. Add a filter or a second action and the Zap becomes a multi-step Zap, which needs a paid plan. Since all four triggers are instant, the 15-minute check of the free plan does not slow them down.

Connect

Connect HeySummit to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. A connection is your HeySummit account linked once, then reused by every Zap that needs it.

  2. 02

    Pick HeySummit

    Type HeySummit in the search box of the dialog, select it, then click Add connection. Have a HeySummit account ready, with access to the event you want to watch.

  3. 03

    Sign in and allow access

    Log in to HeySummit in the tab that opens and grant Zapier access to the account. Back in Zapier, the connection shows up in your list, ready for any trigger.

First Zap

Your first Zap: ticket buyers into HubSpot and Slack

GoalEvery ticket sale lands in HubSpot as a contact, and the sales team gets a Slack message about it.

  1. 01

    Create the Zap

    Start a new Zap and pick HeySummit as the app that starts it, with Ticket Purchased as the event. Choose the connection you added earlier.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent sales from your account, so you can pick a real one and see which values it carries before mapping anything.

  3. 03

    Add HubSpot

    Add HubSpot with Create or Update Contact, then map the buyer values you saw in the test into the contact fields. Test the step once.

  4. 04

    Add Slack

    Add Slack, pick the channel your sales team reads and write a short message from the same values. Test it once and check what came back.

  5. 05

    Publish

    Click Publish to switch it on. With two actions this is a multi-step Zap, so it needs a paid plan and costs two tasks for each sale.

Triggers

The 4 HeySummit triggers, one by one

4 events start a Zap when something happens in HeySummit, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Attendee

Instant trigger

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

Starts your Zap each time someone signs up for your HeySummit event as a whole. You get one run per person, whatever talks they pick later, which makes it the right base for a contact list or a welcome sequence in your email tool.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want every new registrant added once to your newsletter tool, tagged with the event name, so the follow-up emails go out from there.
Watch out
ticket purchases have their own trigger, so a Zap meant for buyers only should start from Ticket Purchased instead of filtering here.
2

New Talk Attendee

Instant trigger

In Zapier“Triggers when a new attendee registers for a Talk within your HeySummit Event. A Zap is sent for each Talk they register for.”

Fires when a person registers for a specific talk inside your event. HeySummit sends one run per talk, so someone who picks five sessions sets off five runs, each carrying that talk. It is the granular view, session by session.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
each speaker wants a row per attendee of their own session in a shared sheet, to prepare questions or send slides afterwards.
Watch out
every one of those runs bills its action, so a busy summit can eat a free plan's 100 tasks far faster than the registration count suggests.
3

New Talk Submission

Instant trigger

In Zapier“Triggers when a new talk submission is ready for review in your HeySummit event.”

Kicks off when a speaker proposal is ready for review in your event. This is the one for the organizing side rather than the audience: it turns each pitch into a piece of work for whoever chooses the program.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your selection committee works from a project board, and you want every incoming pitch to appear there as a card, without anyone copying it across by hand.
Watch out
the Zap cannot accept or reject the talk back in HeySummit, since the integration offers no action, so the decision itself still happens in HeySummit.
4

Ticket Purchased

Instant trigger

In Zapier“Triggers when an attendee purchased a ticket on your HeySummit event.”

Runs when an attendee buys a ticket for your HeySummit event. Of the four, this is the sales signal: a ticket bought, not just a registration, which is what sales and finance usually want to hear about.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
on launch day, your team wants a chat message per sale to watch the early-bird wave in real numbers instead of refreshing a dashboard.
Watch out
the ticket values available for a filter are the ones you see when you test the trigger, so run that test before writing any condition.
When it breaks

When a HeySummit Zap breaks

Zapier attaches no help article to HeySummit and no app-specific limit is documented. What goes wrong comes from Zapier itself, and from how the triggers count.

Four cases come up again and again. In each of them the Zap does less, or costs more, than you expected.

  • Past registrations never arrive

    A Zap only sees what happens after you publish it. The attendees already in your event stay out, and moving that backlog is a separate job, such as an export.
  • One person, many runs

    New Talk Attendee fires once per talk chosen. An attendee who books six sessions triggers six runs, and each successful action counts as a task.
  • A launch-day burst is held back

    When a trigger suddenly sends a huge batch, Zapier's flood protection can hold the runs back rather than fire them all at once. Expect it after a big promo.
  • The filter silently blocks everything

    Filter rules are typed. A text rule on a number, or a number rule on text, never passes, and the Zap stops without doing anything at all.
Need help

Need help automating HeySummit with Zapier?

A person reads every message.

FAQ

HeySummit Zapier integration: common questions

01Is the HeySummit Zapier integration free?
Yes, it works on the free Zapier plan, because HeySummit is not a premium app. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps: one trigger and one action. That is enough to send every ticket buyer to a CRM or every registrant to a mailing list. As soon as you add a filter or a second action, the Zap becomes multi-step and needs a paid plan. No price is quoted here, since plan grids change often; check the Zapier pricing page before choosing.
02How many tasks does a HeySummit Zap use?
The HeySummit trigger itself uses none. Only the action that follows, in your other app, is counted, and only when it succeeds; a failed action is not billed. A Zap with one action costs one task per run, a Zap with two actions costs two. The catch is the run count: New Talk Attendee fires once for every talk a person joins, so one attendee picking four sessions means four runs. Estimate your volume from talk sign-ups, not from the number of people registered, before you settle on a plan.
03Do HeySummit triggers work in real time?
Yes. All four HeySummit triggers are instant: HeySummit calls Zapier the moment a registration, a talk sign-up, a submission or a sale happens, and the Zap starts straight away. This holds on every plan, including the free one. The 15-minute check interval of the free plan only concerns polling triggers, where Zapier asks the app for news on a timer, and HeySummit has none. In the editor, a Zap built on an instant trigger shows a lightning bolt, which is a quick way to confirm it.
04What does it take to connect a HeySummit account?
A HeySummit account with access to the event you want to watch, and a Zapier account. From the Apps page in Zapier, click + Add connection, search for HeySummit, then click Add connection. A tab opens where you sign in to HeySummit and grant Zapier access. Once that is done, the connection is saved and reused by every Zap that starts from HeySummit, so you only do it once. If you watch an event someone else owns, make sure your account can actually see it first.
05Why does one HeySummit attendee start a Zap several times?
Because New Talk Attendee sends one run per talk, not one per person. HeySummit states it plainly: a run goes out for each talk the attendee registers for. If you only want one run per person, start the Zap from New Attendee instead, which fires once per registration to the event. Keep New Talk Attendee for jobs that really are per session, like building each speaker's attendee list. Mixing them up is the most common reason a HeySummit Zap burns through its monthly tasks early.
06What if the HeySummit operation you want is missing?
Then Zapier cannot do it for this app today. The integration offers four triggers and nothing else: no action to create a talk, register someone or issue a ticket, and no search step to look up an attendee. If your process needs to write into HeySummit, Zapier is the wrong route for that part. What still works is the outgoing direction: anything that starts from a sign-up, a submission or a sale in HeySummit can be pushed to the many other apps Zapier connects, where the real work happens.
07Zapier, Make or n8n for HeySummit?
Choose by criteria rather than by brand. On Zapier, HeySummit offers four instant triggers and no action, so it fits when your need is to react to events in your summit and act in another tool. It works on the free plan for two-step Zaps, and the task count grows with talk sign-ups. If you need to create or update records inside HeySummit, check what each other platform offers for this app before deciding, because Zapier does not cover that direction. Compare billing models against your expected volume.