Resources · Make integration

cobra Event Make integrationAutomate cobra Event with Make.

Can Make react to what happens in cobra Event? Yes. The cobra Event Make integration gives you 20 modules: 11 triggers that watch bookings, tickets and events, and 9 actions. This guide is for event teams who want fewer manual steps, from the connection to a first live scenario.

Try the cobra Event integration on MakeSee the 20 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the cobra Event Make integration do for you?

The cobra Event Make integration links your cobra Event account to Make, a no-code tool where you build a scenario: the automation itself, made of modules placed one after the other. Once linked, Make can spot new bookings, cancellations and event changes in cobra Event, then hand them to your other tools or act back on a booking.

Your booking list, copied where your team works. Start from Watch New Booking, add Get a Booking to read that booking, and send what you need to the spreadsheet or CRM your sales team already opens. Nobody retypes a registration again.

Payments that close themselves. When your payment tool records money for a booking, Update a Payment Status marks it in cobra Event, and Set an Invoice Number of an External Booking stores the invoice reference next to it. Your finance colleague stops chasing two screens.

Cancellations nobody misses. Watch Cancelled Booking and Watch Cancelled Tickets pick up every withdrawal, so the person who manages seats or catering hears about it on the channel of their choice.

Know the limit before you build: Make's own documentation for cobra Event is thin, and none of the 20 modules comes with an official description. Test each one with Run once and look at what it returns before you map anything. If something breaks later, the Make troubleshooting guide covers the usual suspects.

New to the editor? The Make training starts from zero. Still weighing your options, the n8n vs Make comparison puts both tools side by side.

Connect

How do you connect cobra Event to Make?

  1. 01

    Add a cobra Event module

    In your scenario, click the +, type cobra Event and pick any of its modules. Make then asks for a connection, meaning your cobra Event account linked to Make once and reused by every cobra Event module. Click Create a connection.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later, handy if you manage several cobra Event accounts. Then follow the window: either you approve Make on the cobra Event page, or you paste the key that cobra Event gives you.

  3. 03

    Save and check the fields

    Click Save. Back in the module, Make can now read your cobra Event account and offer the objects it finds, so you pick from a list instead of typing IDs by hand.

First scenario

Your first scenario with cobra Event

GoalWhen your payment tool records a payment, Make updates the payment status of the matching booking in cobra Event.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. That first module decides when everything starts.

  2. 02

    Start from your payment tool

    Search for the app where payments land and pick its module that watches new payments. Link that account with Create a connection, just as you will do for cobra Event.

  3. 03

    Add Update a Payment Status

    Click the + on the right, search cobra Event and choose Update a Payment Status. Connect your cobra Event account, then map the data from the payment module that points to the right booking.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundle each module received, a bundle being one item passed along, here one payment. Open the booking in cobra Event and check the status.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set how often Make checks for payments. A new scenario runs every 15 minutes by default. Switch the scenario on and it keeps working without you.

Triggers

Which cobra Event triggers can start a scenario?

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

cobra Event1Watch Booked Tickets

Watch Booked Tickets

triggerIn the docs only

Going by its name, this trigger starts your scenario when tickets get booked in cobra Event, so every seat sold can reach your other tools without a manual export.

How it fires
scheduled. Make checks cobra Event on the scenario's schedule, the clock badge on the module.
When to use it
you count tickets rather than bookings, for example to share each sale with the person who prepares badges.
Watch out
the doc says nothing about what this module returns, so click Run once and read a real bundle before mapping.
cobra Event2Watch Cancelled Tickets

Watch Cancelled Tickets

triggerIn the docs only

This one reacts to tickets being cancelled, as its name tells you. The seat that just freed up becomes information your team gets on the next run instead of discovering it on the day.

How it fires
scheduled. Make asks cobra Event for changes at the pace you set on the scenario.
When to use it
a waiting list exists and someone has to offer the free seat, or catering numbers must drop.
Watch out
a ticket and a booking are not the same thing, so pick Watch Cancelled Booking if the whole booking is what you follow.
cobra Event3Watch Created Booking

Watch Created Booking

triggerIn the docs only

Need a scenario that starts from every booking created in cobra Event? The name of this trigger points there: it picks up newly created bookings and passes each one along as a bundle.

How it fires
scheduled. On each run of the scenario, Make looks for bookings created since the last check.
When to use it
you want to copy each fresh booking into a CRM or a spreadsheet the sales team reads.
Watch out
Watch New Booking sounds very close; run both once on the same account and keep the one whose bundles fit your need.
cobra Event4Watch Created Event

Watch Created Event

triggerIn the docs only

Every event your team sets up in cobra Event can open a scenario here, which saves you from announcing it by hand in each tool. The name says it watches event creation; the doc adds nothing more.

How it fires
scheduled. Make polls cobra Event on the schedule of the scenario.
When to use it
a new event should appear in a shared planning sheet or trigger a message to the marketing team.
Watch out
each event found counts as one operation, meaning one execution of the module that Make deducts from your plan.
cobra Event5Watch Deleted Bookings

Watch Deleted Bookings

triggerIn the docs only

Deleted bookings leave no trace in your other tools unless something tells them. Judging by its name, this trigger is that something: it spots bookings removed from cobra Event and starts the scenario for each one.

How it fires
scheduled. Make checks for deletions at the interval of the scenario.
When to use it
your CRM or sheet holds a copy of each booking and has to stay clean when one disappears.
Watch out
once a booking is gone, a later Get a Booking on it is unlikely to help, so test with Run once what the bundle still carries.
cobra Event6Watch Deleted Events

Watch Deleted Events

triggerIn the docs only

Removing an event in cobra Event can ripple into calendars, pages and sheets. This trigger, if its name holds, catches those deletions so the scenario can tidy up the rest for you.

How it fires
scheduled. Make queries cobra Event on the rhythm you give the scenario, not the second it happens.
When to use it
a shared planning or a public list has to lose the event once it leaves cobra Event.
Watch out
start with Run once on a test event, since the doc does not say which details stay available after a deletion.
cobra Event7Watch New Attendance Records

Watch New Attendance Records

triggerIn the docs only

Who actually showed up? According to its name, this trigger picks up new attendance records in cobra Event, which turns check-ins into data your follow-up tools can use.

How it fires
scheduled. Make asks cobra Event for new records each time the scenario runs.
When to use it
attendees and no-shows should get different follow-up messages after the event, or a certificate list has to be built.
Watch out
the doc does not describe a record, so read one real bundle before deciding which data to send on.
cobra Event8Watch Updated Event

Watch Updated Event

triggerIn the docs only

A date that moves or a venue that changes can be passed on automatically with this trigger, which, as the name suggests, follows edits made to events in cobra Event.

How it fires
scheduled. Make checks for updated events on the scenario's own schedule.
When to use it
the details shown in another tool, such as a planning sheet or a team channel, must stay identical to cobra Event.
Watch out
if the same scenario also edits that event somewhere cobra Event reads from, keep an eye on it so your updates do not keep restarting it.
cobra Event9Watch Cancelled Booking

Watch Cancelled Booking

triggerIn the docs only

When a whole booking gets cancelled, this trigger lets the scenario react, going by its name. You get one clear signal per cancellation instead of scanning the booking list.

How it fires
scheduled. Make looks for cancelled bookings every time the scenario runs.
When to use it
finance must stop a payment follow-up, or the organizer wants a message in the team channel with the booking name.
Watch out
a cancelled booking is not a deleted one; if your team deletes instead of cancelling, Watch Deleted Bookings is the trigger to test.
cobra Event10Watch New Booking

Watch New Booking

triggerIn the docs only

This is the natural starting point for most cobra Event scenarios: judging by its name, it hands each new booking to the next module, ready to be copied, enriched or announced.

How it fires
scheduled. Make checks cobra Event for new bookings on the schedule of the scenario, 15 minutes at the shortest on the Free plan.
When to use it
a welcome email, a CRM contact or a row in a shared sheet should follow every registration.
Watch out
pair it with Get a Booking only if the bundle from Run once lacks something you need.
cobra Event11Watch Updated Booking

Watch Updated Booking

triggerIn the docs only

Changes to an existing booking, such as a new attendee name or another option, can reach your other tools through this trigger, which follows booking edits if its name is to be trusted.

How it fires
scheduled. Make asks cobra Event for edited bookings each time the scenario runs.
When to use it
the copy of each booking in your CRM has to follow what happens in cobra Event.
Watch out
Update a Payment Status in the same scenario would edit the booking again, which may wake this trigger up on the next run.
Modules

What can Make do in cobra Event?

cobra Event gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

cobra Event1

Delete a Booking

ActionIn the docs only

Removes a booking from cobra Event for you, so duplicates or test entries stop cluttering the list without anyone clicking through them.

When to use it
a test run created fake bookings, or another tool confirms a registration was a duplicate.
Watch out
a deletion does not come back; try it with Run once on a booking you made for testing.
cobra Event2

Delete an Event

ActionIn the docs only

Takes an event out of cobra Event from inside a scenario, handy when the decision to drop it is made elsewhere, in a project tool or a shared sheet.

When to use it
your planning sheet is the one people trust, so a row marked as dropped should clean cobra Event as well, without a second pass by hand.
Watch out
nothing undoes it, and any bookings tied to that event deserve a check before you let a scenario do this.
cobra Event3

Get a Booking

ActionIn the docs only

Reads one booking you already know, so the next modules work with its details instead of what a trigger happened to pass along.

When to use it
another app gives you a booking reference and you need the rest before writing to your CRM.
Watch out
it reads one booking only, the one you point to; it is not a search across all of them.
cobra Event4

Get a Tenant

ActionIn the docs only

Fetches the tenant, which in cobra Event appears to be the account your events live in. The doc gives no definition, so see this module as a way to read account-level details.

When to use it
you run several cobra Event accounts and a report must say which one each record came from.
Watch out
run it once and look at the bundle before building on it, since nothing official says what it returns.
cobra Event5

Get a Ticket

ActionIn the docs only

Brings back a single ticket, useful when the rest of your scenario needs more than the reference a trigger or another tool gave you.

When to use it
after Watch Booked Tickets, a badge printing tool or a message template needs the ticket itself.
Watch out
each call costs one operation; skip it when the trigger bundle already holds what you use.
cobra Event6

Get an Event

ActionIn the docs only

Reads one event from cobra Event so you can show its details in another tool, for example a title or a date in a confirmation message.

When to use it
a booking arrives and your email needs the details of the event it belongs to.
Watch out
you need the event reference first, so place it after a module that provides it and check the mapping with Run once.
cobra Event7

Make an API Call

ActionIn the docs only

Covers what the listed modules leave out: it calls any endpoint of the cobra Event API from your scenario, reusing the connection you already made.

When to use it
you need an object or an action no listed module offers, and your cobra Event contact can point you to the right endpoint.
Watch out
you are working directly with the API here, so keep the cobra Event API reference open while you fill it in.
cobra Event8

Set an Invoice Number of an External Booking

ActionIn the docs only

Writes an invoice number onto an external booking in cobra Event, which keeps the link between the booking and the invoice issued by your accounting tool.

When to use it
invoices are created outside cobra Event and finance wants to find each one from the booking.
Watch out
the name targets external bookings; the doc does not say what makes a booking external, so test on one real case first.
cobra Event9

Update a Payment Status

ActionIn the docs only

Changes the payment status in cobra Event without anyone opening it, so the organizer sees at a glance who has paid.

When to use it
your payment provider or bank tool confirms a payment and cobra Event should reflect it.
Watch out
the doc lists no accepted values, so try the status on a test booking with Run once and check the result in cobra Event.
Need help

Need help automating cobra Event with Make?

A person reads every message.

FAQ

Common questions about cobra Event and Make

01Is the cobra Event Make integration free?
Yes, cobra Event is a standard app in Make, so it works from the Free plan. That plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes per execution, files up to 5 MB and 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 count usage in credits each month. Your cobra Event subscription is a separate matter that Make does not handle.
02What do you need to connect cobra Event to Make?
A cobra Event account and a Make account are enough to start. Make's documentation lists no other prerequisite and no official connection steps for cobra Event, so the usual Make path applies: add a cobra Event module, click Create a connection, give it a name if you want, then approve Make on the cobra Event page or paste the key cobra Event provides, and save. The same connection then serves all 20 modules.
03Do cobra Event triggers in Make fire in real time?
No. Make's documentation lists the 11 cobra Event triggers without giving their type; their Watch names point to scheduled triggers: Make checks cobra Event on the scenario's schedule, shown by the clock badge on the module. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans go down to 1 minute. An instant trigger, the kind an app calls through a webhook as soon as something happens, does not appear in that list. Check the badge in the editor.
04What if the cobra Event module you need is missing?
Use Make an API Call. When an app has this module, as cobra Event does, you can call any endpoint of its API from the scenario with the connection you already set up. Be aware that Make's documentation for cobra Event is limited and describes none of the modules, so the cobra Event API reference and a test with Run once become your main guides. The Make troubleshooting guide helps when a call fails.
05Make or n8n for cobra Event, which should you pick?
It depends on the tool your team already runs. On Make, cobra Event comes with 20 ready modules, 11 scheduled triggers and 9 actions, plus Make an API Call for anything else, all usable from the Free plan. Plenty of apps also have an n8n node, so check whether cobra Event does before deciding. This page does not rank the two tools, and the comparison page linked above lays them side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations