Resources · Make integration

BigMarker Make integrationAutomate BigMarker with Make.

What if every webinar signup landed where your team needs it, without a copy-paste? The BigMarker Make integration gives you 23 modules: one instant trigger, 13 actions and 9 searches. This page shows how to link your account and build a first working scenario.

Try the BigMarker integration on MakeSee the 23 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the BigMarker Make integration do for your webinars?

The BigMarker Make integration links your BigMarker account to Make, a tool where you build scenarios: automations made of modules, each module being one brick such as a trigger, an action or a search. BigMarker then talks to your other apps, and nobody has to export a registrant list by hand.

Signups that follow up on their own. Watch Conference Registrants fires as soon as someone registers for a conference. From there, Add a Channel Subscriber puts that person on your channel, so the next event you announce reaches them too.

Events created from your planning tool. A marketer who plans sessions elsewhere can feed Create a Conference and Add a Presenter to a Conference, then fix a changed title later with Update a Conference. The webinar exists in BigMarker before anyone opens it.

Attendance you can actually use. After a session, List a Conference's Attendees returns who showed up, one bundle (one item passed to the next module) per person, ready to go to a sheet or a CRM. Compare it with List a Conference's Registrants to spot the no-shows.

BigMarker has no scheduled trigger in Make, only the instant one, and the documentation is short: it lists modules without limits. When a listed module does not cover a need, Make an API Call reaches the rest of the API. The same app often has an n8n node too; the n8n vs Make comparison helps you choose, and the Make pricing page explains what the plans include.

Connect

How do you connect your BigMarker account to Make?

  1. 01

    Copy your API key in BigMarker

    BigMarker signs in with an API key, so grab it first. Open your user settings page in BigMarker, go to the API Keys section and copy the key shown on screen. You need an active BigMarker account for this.

  2. 02

    Add a BigMarker module in Make

    In your scenario, add any BigMarker module and click Create a connection. A connection is your BigMarker account linked to Make once, then reused by every BigMarker module. The Connection name field is optional; a clear name helps if you run several accounts.

  3. 03

    Paste the key and save

    Paste the API key you copied into the connection window, or follow the instructions Make shows, and save. Make can now read your channels and conferences, and every other BigMarker module in the scenario picks the same connection from a list.

First scenario

Your first scenario: turn each registrant into a channel subscriber

GoalWhen someone registers for a conference in BigMarker, Make adds that person as a subscriber to your channel.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. That empty circle is where the first module, the one that starts everything, will sit.

  2. 02

    Add the registration trigger

    Search for BigMarker and pick Watch Conference Registrants. Click Create a webhook, then Create a connection with your API key. The lightning badge tells you BigMarker will call Make on its own.

  3. 03

    Add the subscriber action

    Click the + on the right of the trigger and choose Add a Channel Subscriber. Pick your channel from the list Make shows, then map the registrant's details from the trigger into the fields.

  4. 04

    Test with Run once

    Click Run once, then register to one of your conferences with a test address. Open each module's bubble to read the bundle it received: the new registrant, then the subscriber created.

  5. 05

    Switch the scenario on

    Turn the scenario on. Because the trigger is instant, BigMarker calls Make through the webhook as each signup happens, and every run of each module counts as one operation on your plan.

Triggers

What starts a BigMarker scenario?

1 module starts a scenario when something happens in BigMarker. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by BigMarker as soon as it happens.

BigMarker1Watch Conference Registrants

Watch Conference Registrants

Instant trigger

In Make“Watches new conference registrations.”

This trigger starts your scenario each time a person registers for one of your conferences, and hands the following modules one bundle per new registrant. It is the entry point for anything that should happen right after a signup.

How it fires
instant. BigMarker calls Make through a webhook as soon as the registration happens, so there is no polling interval to set.
When to use it
you want a sales rep, a CRM or your channel list to know about a registrant without waiting for an export after the event.
Watch out
create the webhook before the connection, as the setup asks; a scenario left switched off receives nothing.
Modules

What can Make do in BigMarker?

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

BigMarker1

Add a Channel Subscriber

Action

In Make“Adds a subscriber to a channel.”

Puts a person on one of your BigMarker channels, so the events you publish there reach them. It is the simplest way to grow an audience from contacts that already live in another tool.

When to use it
a lead fills a form on your site and should hear about upcoming webinars.
Watch out
pick the channel from the list rather than typing it, to avoid adding people to the wrong one.
BigMarker2

Add a Presenter to a Conference

Action

In Make“Adds a presenter to a conference.”

Attaches a speaker to an existing conference, so the guest appears on the event without anyone editing it in BigMarker. Pair it with Create a Conference when a whole session is built from outside data.

When to use it
a speaker confirms through your booking form and must show on the event page.
Watch out
the conference has to exist first, so place this module after the one that creates or finds it.
BigMarker3

Create a Conference

Action

In Make“Creates a new conference and adds it to a channel.”

Creates a new conference and files it inside one of your channels. Your webinar schedule can then start from a planning sheet or a project tool instead of the BigMarker dashboard.

When to use it
a content team validates a topic in its planning tool and wants the event ready right away.
Watch out
run it once with a test channel first, since every run adds a real event your audience may see.
BigMarker4

Delete a Channel Subscriber

Action

In Make“Deletes a subscriber from a channel.”

Removes a subscriber from a channel, which keeps your audience list in line with the opt-outs recorded in your other tools. Nobody has to hunt for the contact by hand.

When to use it
a contact unsubscribes in your email tool and should stop hearing about your events.
Watch out
a deletion does not come back; test on a dummy subscriber before mapping real people.
BigMarker5

Delete a Conference

Action

In Make“Deletes a conference from a channel.”

Removes a conference from its channel for good. It lets a cancellation decided elsewhere clean up BigMarker automatically, instead of leaving a dead event online.

When to use it
a session is cancelled in your planning tool and must disappear from the channel page too.
Watch out
there is no undo, so put a filter before it and check with Run once which conference it receives.
BigMarker6

Delete a Conference Presenter

Action

In Make“Deletes a conference presenter.”

Takes a speaker off a conference while the event itself stays in place. The page then shows only the people who will actually be on stage.

When to use it
a guest pulls out and your speaker tracker marks them as cancelled.
Watch out
if the goal is only to fix a name or a bio, Update a Conference Presenter keeps the speaker and changes the details instead.
BigMarker7

Get a Channel

Action

In Make“Retrieves a channel.”

Fetches the details of one channel you already know, as a single bundle. Later modules can then reuse its information without you retyping it in each field.

When to use it
a scenario needs the channel's details before creating an event or writing a report.
Watch out
it reads one channel only; to go through all of them, List Channels is the right module.
BigMarker8

Get a Conference

Action

In Make“Retrieves information about a conference.”

Reads the information of one conference and passes it on as one bundle. It is useful when a trigger or a sheet gives you an event reference but not the rest of its details.

When to use it
a registrant arrives and your follow-up email should mention the event it belongs to.
Watch out
it needs a conference you can identify; without one, start with Search Conferences.
BigMarker9

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the BigMarker API from your scenario, using the same connection as the other modules. It covers what the listed modules leave out, without a separate login.

When to use it
the action you need exists in BigMarker but no module in this list handles it.
Watch out
you write the request yourself, so keep the BigMarker API documentation open and test with Run once.
BigMarker10

Register a User to a Conference

Action

In Make“Registers a person to an existing conference.”

Signs a person up for an existing conference from data held in another tool. Your own forms, CRM or checkout can then feed BigMarker directly.

When to use it
a customer buys a training package and should be registered to the matching session.
Watch out
if the same scenario also starts from Watch Conference Registrants, each registration would call it again; keep the two in separate flows.
BigMarker11

Unregister a User from a Conference

Action

In Make“Unregisters a user from an existing conference.”

Cancels a person's registration to a conference, so your attendee numbers match reality before the session starts. The rest of the event stays untouched.

When to use it
a refund or a cancellation request lands in your billing or support tool.
Watch out
map the right person and the right conference; a wrong match removes someone who still plans to join.
BigMarker12

Update a Conference

Action

In Make“Updates a conference.”

Changes an existing conference, so a correction made in your planning tool reaches BigMarker without a second round of editing. Nobody has to open the event page to retype the change.

When to use it
the title or description of a webinar changes after validation and the page must follow.
Watch out
map only the fields you intend to change, and check the result with Get a Conference during the test.
BigMarker13

Update a Conference Presenter

Action

In Make“Updates the presenter of a conference.”

Edits the details of a speaker already attached to a conference. The presenter stays on the event, only the information you map is replaced.

When to use it
a guest sends a new job title or bio and your speaker sheet is updated first.
Watch out
this module assumes the presenter already exists on the event; for a new guest, Add a Presenter to a Conference is the one.
BigMarker14

List a Channel's Conferences

Search

In Make“Retrieves conferences from a channel.”

Returns the conferences of one channel, one bundle per event. You get a clean inventory of a single brand or series without mixing in the others.

When to use it
a team runs several channels and wants a sheet of only its own events.
Watch out
the result can be empty or long; the modules after it run once per conference, and each run costs an operation.
BigMarker15

List a Channel's Subscribers

Search

In Make“Retrieves all channel subscribers.”

Retrieves every subscriber of a channel, one bundle each. It turns your BigMarker audience into data you can copy to a CRM, a newsletter tool or a sheet.

When to use it
marketing wants to compare the channel audience with its email list.
Watch out
a large channel produces many bundles, and each module placed after it runs for every one of them.
BigMarker16

List a Conference's Attendees

Search

In Make“Retrieves attendees of a specific conference.”

Returns the people who actually attended a given conference. That is the list that matters for follow-up, since it separates viewers from people who only signed up.

When to use it
after a webinar, sales wants to call the people who stayed for the demo.
Watch out
it returns one bundle per attendee, so every module after it runs as many times as there were people.
BigMarker17

List a Conference's Registrants

Search

In Make“Retrieves all registrants of a specific conference.”

Pulls every registrant of one conference at once, including the people who signed up before your scenario existed. It fills the gap the instant trigger leaves on older signups.

When to use it
you connect BigMarker to a CRM and want to import the registrants already there.
Watch out
run it again later and you get the same people; add a check in the next module to avoid duplicates.
BigMarker18

List a Presenter's Conferences

Search

In Make“Retrieves all the conferences of a presenter.”

Finds every conference a given presenter is linked to. It answers the question "where does this speaker appear?" without opening each event one by one.

When to use it
a speaker leaves the company and you need to review all their sessions.
Watch out
the modules that follow run once per conference found, so a busy presenter means more operations.
BigMarker19

List Channels

Search

In Make“Retrieves all channels.”

Retrieves all the channels of your account, one bundle per channel. It is a handy starting point when a scenario should loop over each brand or series you run.

When to use it
you build a report that covers every channel and feed it to List a Channel's Conferences.
Watch out
for one channel you already know, Get a Channel does the job with a single bundle.
BigMarker20

List Future Conferences

Search

In Make“Retrieves all future conferences from all of your channels.”

Returns the upcoming conferences from all your channels in one pass. Past events stay out, so the output is your agenda and nothing else.

When to use it
a shared calendar or an intranet page should show the next webinars your company hosts.
Watch out
it covers every channel; if only one series matters, List a Channel's Conferences gives a narrower result.
BigMarker21

Search Conferences

Search

In Make“Searches for conferences from all of your channels.”

Looks for conferences across all of your channels and returns those that match. It helps when you know roughly which event you want but not its exact reference.

When to use it
a form mentions an event by topic and the scenario has to find the matching conference before registering someone.
Watch out
a search may return zero, one or several bundles; add a filter so the next module works on the right one.
BigMarker22

Search Recurring Conferences

Search

In Make“Searches for the child conferences of a recurring conference.”

Finds the child sessions of a recurring conference, meaning each occurrence of a series. You can then act on one specific date instead of the whole series.

When to use it
an onboarding webinar repeats and new customers must land in the next occurrence.
Watch out
start from the parent conference; results come back as several bundles, one per occurrence.
Need help

Need help automating BigMarker with Make?

A person reads every message.

FAQ

Questions about the BigMarker Make integration

01Is the BigMarker Make integration free?
Yes, on the Make side. BigMarker is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run. You still need an active BigMarker account, whose own subscription is separate.
02What do you need to connect BigMarker to Make?
An active BigMarker account and its API key. In BigMarker, open your user settings page, go to the API Keys section and copy the key displayed. In Make, add a BigMarker module, click Create a connection, give it a name if you like and paste the key. For the instant trigger Watch Conference Registrants, click Create a webhook first, then create the connection from there. The connection is then reused by every BigMarker module of your scenarios.
03Does the BigMarker trigger react in real time?
Yes. Watch Conference Registrants is an instant trigger: BigMarker calls Make through a webhook as soon as someone registers, so the scenario starts without waiting for a schedule. It is the only trigger this app has in Make. For anything else, such as a list of attendees after an event, start the scenario on a schedule and use a search module like List a Conference's Attendees. A new scenario is set to run every 15 minutes by default.
04What if a BigMarker module you need is missing in Make?
Use Make an API Call. This module reaches any endpoint of the BigMarker API with the same connection as the other modules, so you are not limited to the 13 actions and 9 searches in the list. You write the request yourself, so keep the BigMarker API documentation at hand. The Make documentation for this app lists modules but gives no specific limits, and it warns that its content may contain mistakes, so check anything important with BigMarker directly.
05Should you use Make or n8n for BigMarker?
It depends on what your team already uses. On Make, BigMarker comes with 23 modules, an instant registrant trigger and Make an API Call for the rest, all usable from the Free plan. The same app often has an n8n node as well. The fair way to decide is to check which tool your team knows, whether the module you need exists on each side, and how each counts usage. Neither tool is ranked above the other here.
Same platform

Other docs you might need on this stack.

Browse all integrations