Corymbus Zapier integrationAutomate Corymbus with Zapier.
The Corymbus Zapier integration gives you 6 operations: 2 triggers, 3 actions and 1 search. Enough to turn each new contact into a deal, file company accounts without retyping, and react to activity logged in your CRM, from the free plan up.
Verified Trustpilot reviews · AI, automation & growth agency
What the Corymbus Zapier integration does for you
Corymbus is a CRM aimed at freelancers and small businesses, with sales and marketing kept deliberately simple. Linked to Zapier, it reports new contacts and new activities, and it can create accounts, contacts and opportunities or look an account up, so nobody copies data between screens.
A deal for every new lead. New Contact starts the Zap and Create Opportunity opens the matching deal, so no prospect sits in the CRM without a next step attached.
Deals tied to the right company. Find Account fetches the company that already exists before the opportunity is created, instead of leaving you to match them by hand later.
Activity that gets a follow-up. New Activity fires on each activity created in Corymbus, and a filter keeps only the ones that deserve an opportunity.
What Zapier does not do here: no trigger for a new account or a new opportunity, no action to update or delete a record, and the only search looks for accounts, not contacts. Plan around those gaps before building, because no setting in the editor adds them back.
Comparing platforms? The Corymbus Make integration covers the same CRM on Make, and our Zapier agency can build the Zap if you would rather hand it over.
Zapier vocabulary in one minute
Seven or eight words carry the whole page. Read them once and the rest of the page reads like plain English.
- Zap
- The automation you build on Zapier: one trigger that starts it, then one or more actions that run every time that event happens.
- Trigger
- The event in an app that sets the Zap off. Once the Zap is published, Zapier sits and waits for that event to come up.
- Action
- The step that does the work after the start: it creates, sends or writes something in an app on your behalf.
- Task
- Zapier's billing unit. One task is one action that completed successfully, and your plan is sized as a count of those.
- Polling vs instant
- Polling: Zapier asks the app for new items on a timer. Instant: the app calls Zapier itself the moment something happens.
- Filter
- A step that lets the Zap carry on only when the incoming item meets a condition you set, and stops it otherwise.
- Connection
- Your Corymbus account linked to Zapier once, then reused by every step of every Zap that works with Corymbus.
- Search step
- A step that looks up something already stored in an app, so the steps after it can use what it found.
What a Corymbus Zap really costs
Short version: the trigger is free, every successful action is billed, and the free plan stops at two steps.
- Triggernever billed
- Successful action1 task each
- Free plan100 tasks a month, two-step Zaps
- Premium appno
Zapier counts in tasks. Looking for new data never costs anything, and an action that fails is not billed. Each action that succeeds counts on its own, so a Zap with three actions uses three tasks per run. The free plan gives you 100 tasks a month and Zaps of exactly two steps. Add a second action, a filter or a search step and the Zap turns multi-step, which needs a paid plan. Corymbus is not a premium app: it works from the free plan. The plan also sets how often a polling trigger checks for new items, and that check is free.
Connect Corymbus to Zapier in three steps
- 01
Open Apps and start a connection
In your Zapier account, go to the Apps page and click + Add connection. Type Corymbus in the search box of the dialog and pick it from the list of results.
- 02
Sign in to Corymbus
Click Add connection. A new tab opens on the Corymbus side: log in with the account the Zap should work with. You need an account there, plus read or write access to anything you do not own yourself.
- 03
Grant access, once
Approve the access Zapier asks for. That connection is now reusable: every Corymbus step in every Zap picks it up, so you link the account once rather than once per Zap.
Your first Corymbus Zap: contact in, deal out
GoalEvery new Corymbus contact gets its company looked up and an opportunity opened on it.
- 01
Build: pick the trigger
In the Build phase, choose Corymbus as the trigger app and New Contact as the event, then select the connection you made earlier.
- 02
Test it on a real contact
Run the trigger test. Zapier brings back the three most recent contacts of your account, so you pick a real one and map the next steps on actual values rather than blanks.
- 03
Add Find Account
Add the search as step two and fill its search field from the contact data the test returned. A search makes the Zap multi-step, so this one needs a paid plan.
- 04
Open the opportunity
Add Create Opportunity and map into it the account found at step two plus the contact details you care about. Leave out anything your sales process never reads.
- 05
Test, then Publish
Use Test on each step and check the opportunity in Corymbus. Then click Publish: from now on Zapier looks for new contacts on your plan's schedule.
Corymbus triggers: what starts a Zap
2 events start a Zap when something happens in Corymbus. Zapier checks for them at the interval your plan allows.
New Activity
Polling triggerIn Zapier“Triggers when a new activity is created.”
Each time someone on your team creates an activity in Corymbus, this trigger hands it to Zapier so the rest of the Zap can act on it.
New Contact
Polling triggerIn Zapier“Triggers when a new contact is created.”
A fresh contact landing in Corymbus, typed in by you or added by a colleague, is what sets this one off.
Corymbus actions: what the Zap can do
Corymbus gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Account
ActionIn Zapier“Creates an Account”
Opens a company record in Corymbus. The account Name is the one field it insists on, so it works even when you know little else about the company.
Create Contact
ActionIn Zapier“Creates a Contact”
Adds a person to your Corymbus contacts from the data of an earlier step, so the record exists without anyone typing it.
Create Opportunity
ActionIn Zapier“Creates an Opportunity”
Records a new opportunity in Corymbus, giving the potential sale its own line to follow up on.
The Corymbus search and its three settings
1 search step looks for data that already exists in Corymbus, so a later step can use it.
A search step looks something up instead of creating it. Searches sit at the bottom of the Action event list, under SEARCH, and some action fields offer + Add search step to slot one in before the current step.
Find Account
SearchIn Zapier“Finds an Account”
Looks up a company that already exists in Corymbus and passes its record to the steps that follow.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that comes back empty stops the run there and the steps that needed it are skipped. Switched on, the Zap carries on without the account.
- Create X if it doesn't exist yet?This is the box that turns a search into find-or-create. Corymbus offers no such variant: Find Account only finds, and creating a missing account stays a separate Create Account step.
- If multiple search results are found?When several accounts match, the Zap keeps the first one by default. You can also stop the run, or hand every match on at once.
When a Corymbus Zap breaks
Zapier attaches no help article to Corymbus, so the traps are the general ones, applied to a CRM.
One thing to keep in mind first: a polling trigger remembers what it has already returned, so the same contact never starts the Zap twice. The four cases below are where things actually go wrong. When a run fails anyway, start with our Zapier troubleshooting guide.
Old contacts are never picked up
The Zap only reacts to contacts and activities created after you publish it. Everything already in Corymbus stays put, and moving that backlog is a separate job.Create Contact feeding New Contact
A Zap whose action creates contacts in the very account its New Contact trigger watches sets itself off again and again, and burns through your tasks.A bulk import gets held back
Import a big contact list in one go and the trigger may return a huge batch at once. Zapier's flood protection can hold it back instead of running every item.Account Name left blank
Create Account needs a Name. If the value you map can arrive empty, the action fails: not billed, but no account is created either.
Need help automating Corymbus with Zapier?
A person reads every message.
