Resources · Make integration

Corymbus Make integrationAutomate Corymbus with Make.

Can your CRM stop asking you to copy the same contact twice? The Corymbus Make integration gives you 16 modules: 3 scheduled triggers, 9 actions and 4 searches. This page is for sales and ops people who know Corymbus but are new to Make, and it walks you from the connection to a first working scenario.

Try the Corymbus integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Corymbus Make integration let you automate?

The Corymbus Make integration links your Corymbus account to Make, a no-code tool where you build a scenario, meaning an automation made of modules placed one after the other. Each module is one brick: a trigger that starts things, an action that writes to Corymbus, or a search that reads from it.

Follow up every new contact without a reminder. Watch New Contacts picks up the people added to Corymbus, and Create an Activity logs the first touchpoint on each one, so nobody lands in the CRM without a next step.

Keep deals moving when a customer answers. Search Opportunities finds the deal tied to a customer, then Update an Opportunity changes it from the data another app sends, such as a signed form or a paid invoice.

Feed your other tools with fresh accounts. Watch New Accounts spots each company added to Corymbus and passes it to the next module, for instance a message to your team channel or a row in a spreadsheet.

Know the limit before you start: Make's own documentation for Corymbus is thin and gives no field list, no connection guide and no troubleshooting notes. Test each module with Run once before trusting it. If a module you need is missing, Make an API Call reaches the rest of the Corymbus API. Weighing Make against another tool? The n8n vs Make comparison lays out the criteria, and the Make pricing page explains how operations are counted. Stuck on an error? See Make troubleshooting.

Connect

How do you connect your Corymbus account to Make?

  1. 01

    Add a Corymbus module

    In a new scenario, click the + and search for Corymbus, then pick any of its modules. Make asks for a connection, which is your Corymbus account linked to Make once and reused by every Corymbus module afterwards. Click Create a connection.

  2. 02

    Name the connection

    Naming it is optional, but a clear name such as your team or workspace helps when you later hold two Corymbus accounts in Make and have to pick the right one from a dropdown.

  3. 03

    Authorize and save

    Depending on what the window shows, either approve Make on the Corymbus page that opens or paste the key Corymbus gives you. Then click Save. The module now lists what it can read from your account.

First scenario

Build your first scenario with Corymbus

GoalWhen a new contact appears in Corymbus, Make logs a first activity on that contact.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the editor. This first slot is where the trigger goes.

  2. 02

    Add Watch New Contacts

    Search for Corymbus, choose Watch New Contacts and create the connection. Fill the fields Make shows; once connected, it lists the Corymbus data it can read.

  3. 03

    Add Create an Activity

    Click the + on the right of the trigger and add Create an Activity. Map the contact coming from the trigger into the activity, so each bundle (one new contact) gets its own entry.

  4. 04

    Test with Run once

    Add a test contact in Corymbus, then click Run once. Open the bubbles above each module to read the bundles they received and check the activity landed on the right person.

  5. 05

    Schedule and switch on

    Click the clock on the first module. A new scenario checks every 15 minutes by default, which is also the shortest gap on the Free plan. Set it, then switch the scenario on.

Triggers

What can start a Corymbus scenario?

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

Corymbus1Watch New Accounts

Watch New Accounts

triggerIn the docs only

Hands each account newly added to Corymbus to your scenario, one bundle per account, so the next modules can act on it without anyone exporting a list.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and the module carries the clock badge.
When to use it
when a freshly signed company should reach another tool, like a shared sheet or a team message, once it exists in the CRM, without anyone copying it.
Watch out
Make lists this module in its documentation without a description, and its type comes from its name. Run it once on a test account to see exactly what it returns.
Corymbus2Watch New Activities

Watch New Activities

triggerIn the docs only

Brings every new activity logged in Corymbus into Make, which lets you react to the work your team records rather than to the records themselves.

How it fires
scheduled. Make checks the app on the scenario's schedule, so an activity waits until the next check before your scenario sees it.
When to use it
to copy call notes or meetings into a reporting sheet, or to alert a manager when a rep logs a touchpoint on a key account.
Watch out
each activity is one bundle, and every later module spends one operation on it. A busy sales team can use up a plan faster than expected.
Corymbus3Watch New Contacts

Watch New Contacts

triggerIn the docs only

Picks up each person added to Corymbus and starts your scenario with their record, the natural entry point for onboarding and follow-up flows.

How it fires
scheduled. Make checks the app on the scenario's schedule; it does not react the moment the contact is saved.
When to use it
to log a first activity, to push the person to your email tool, or to warn the account owner that someone new joined a company they follow.
Watch out
the name speaks of new contacts only. Do not count on it to catch edits to existing ones; test that case with Run once if you need it.
Modules

What can Make do in Corymbus?

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

Corymbus1

Create a Contact

ActionIn the docs only

Adds a person to Corymbus from data that arrives elsewhere, so a form entry or an email signup turns into a CRM contact without typing.

When to use it
right after a lead fills a form in another app and you want sales to see them in Corymbus.
Watch out
it creates a new record every time it runs. Put Search Contacts in front of it if the same person might arrive twice.
Corymbus2

Create an Account

ActionIn the docs only

Opens a new account in Corymbus from another source, which keeps the company side of your CRM in step with your billing or signup tool.

When to use it
when a new customer pays a first invoice and the company should exist in the CRM before sales calls them.
Watch out
List Accounts can check first whether the company is already there, which avoids two accounts for one client.
Corymbus3

Create an Activity

ActionIn the docs only

Records an activity in Corymbus, a trace of what happened with a customer, written by the scenario rather than by a rep at the end of the day.

When to use it
after a meeting is booked in a calendar app or a support ticket closes, so the history of the client stays complete in one place.
Watch out
map the right contact or account into it, otherwise the entry lands without the link that makes it useful.
Corymbus4

Create an Opportunity

ActionIn the docs only

Starts a deal in Corymbus automatically, so a qualified request becomes a line in your pipeline the moment it qualifies.

When to use it
when a quote request or a demo booking arrives through another tool and should become a deal for the sales team to own.
Watch out
each run adds one more opportunity. Search Opportunities first when a customer may ask twice for the same thing.
Corymbus5

List Accounts

SearchIn the docs only

Returns the accounts of your Corymbus workspace so the rest of the scenario can loop over them, one bundle per account.

When to use it
to sync your company list into a sheet, or to check whether an account already exists before creating one.
Watch out
a long list means many bundles, and every module placed after it spends one operation per bundle. Filter right after it to keep the count down.
Corymbus6

Make an API Call

ActionIn the docs only

Calls any endpoint of the Corymbus API with the connection you already set up, which covers whatever the ready-made modules leave out.

When to use it
when none of the other 15 modules offers the record type or operation you need.
Watch out
you write the request yourself, so you need the Corymbus API documentation at hand; Make gives no guide for it.
Corymbus7

Search Activities

SearchIn the docs only

Looks up activities already logged in Corymbus and sends back what matches, which tells the scenario whether something was done before it acts.

When to use it
to check if a follow-up call is already on record before logging a new one, or to pull the history of a client into a report.
Watch out
a search can return zero, one or several bundles. Plan for the empty case, or the modules after it simply will not run.
Corymbus8

Search Contacts

SearchIn the docs only

Finds people already stored in Corymbus, the step that stops your scenarios from filling the CRM with duplicates.

When to use it
before Create a Contact, to decide whether to update the person you found or to add a new one.
Watch out
two contacts can match the same search. Add a filter after it so only the right one moves on to Update a Contact.
Corymbus9

Search Opportunities

SearchIn the docs only

Retrieves the deals that match what you look for in Corymbus, so a later module can update the right one instead of guessing.

When to use it
when a signed contract or a payment arrives in another app and you need the matching deal to move it forward.
Watch out
when nothing matches, the search returns no bundle and the rest of the scenario stops there for that run.
Corymbus10

Update a Contact

ActionIn the docs only

Changes an existing person in Corymbus with fresh data, so a new job title or phone number reaches the CRM without anyone editing it by hand.

When to use it
after Search Contacts finds the person, when another app holds the more recent details.
Watch out
it needs a contact that already exists. Map the one returned by the search, not a value typed once for testing.
Corymbus11

Update an Account

ActionIn the docs only

Edits a company already in Corymbus, keeping its record in line with what your billing or support tools know about it.

When to use it
when a customer changes plan or address in another system and the CRM should reflect it for the sales team.
Watch out
pick the account from List Accounts or from a trigger first; an update never creates a missing record.
Corymbus12

Update an Activity

ActionIn the docs only

Rewrites an activity already logged in Corymbus, useful when the outcome of a task is known only after it was created.

When to use it
once a meeting logged earlier actually happens and your calendar or call tool knows how it went.
Watch out
Search Activities usually comes first, because the update has to target one specific activity.
Corymbus13

Update an Opportunity

ActionIn the docs only

Moves a deal forward in Corymbus from an outside event, so your pipeline reflects signatures and payments without a manual status change.

When to use it
when an e-signature tool reports a signed quote and the matching deal should change right away in the CRM.
Watch out
pair it with Search Opportunities; updating the wrong deal is easy to do and harder to notice.
Need help

Need help automating Corymbus with Make?

A person reads every message.

FAQ

Corymbus and Make: common questions

01Is the Corymbus Make integration free?
Yes, Corymbus is a standard app in Make, so you can use it on the Free plan. That plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in credits per month. Any Corymbus subscription of your own is a separate matter that this page does not cover.
02What do you need to connect Corymbus to Make?
A Corymbus account and a Make account. Make's documentation lists no prerequisites for Corymbus and gives no app-specific steps, so the generic flow applies: add a Corymbus module, click Create a connection, optionally name it, authorize Make on the Corymbus page or paste the key Corymbus provides, then click Save. The connection is then reused by all 16 modules. If authorization fails, ask your Corymbus admin what access your user holds, then create the connection again.
03Does the Corymbus trigger in Make react in real time?
No. The three Corymbus triggers are scheduled: Make checks Corymbus on the scenario's schedule, every 15 minutes by default, and never faster than every 15 minutes on the Free plan. Paid plans allow a check every minute. A new contact, account or activity therefore reaches the scenario at the next check, not the moment it is saved. None of the three is an instant trigger. If you need a faster reaction, lower the interval on a paid plan, or use Run once while you build.
04What if a Corymbus module is missing in Make?
Use Make an API Call. It calls any endpoint of the Corymbus API with the connection you already created, so a record type or operation absent from the 15 other modules stays within reach. Keep in mind that Make says its Corymbus documentation is limited, for lack of public information on the app, so you will rely on the Corymbus API documentation and on tests with Run once. Whatever you call this way uses the same connection and counts as operations like any other module.
05Should you use Make or n8n for Corymbus?
It depends on the tool your team already works in. Make offers Corymbus 16 ready modules, three scheduled triggers and an API call module for the rest, on the Free plan as well. Corymbus may also have an n8n node; compare the two on the modules you actually need and on how each counts runs, not on reputation. The comparison page linked above lays out those criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations