- Home
- Resources
- Integrations
- Mercury Connect
Mercury Connect Zapier integrationAutomate Mercury Connect with Zapier.
The Mercury Connect Zapier integration counts 7 triggers, 5 actions and 2 searches. People and opportunities move both ways between the CRM and your other tools, and all 7 triggers are instant, so a Zap starts as soon as a record is created, updated or deleted.
Verified Trustpilot reviews · AI, automation & growth agency
What the Mercury Connect Zapier integration is for
Mercury Connect is a CRM for tracking people and opportunities, with loan calculations, product comparison and compliance on top. Through Zapier, it starts a Zap (an automation on Zapier: one trigger, then one or more actions that run every time the trigger event happens) when a record changes, and other apps can create or update its records.
Three results come up most. A heads-up on new business: New Opportunity posts each new opportunity in your team chat, so nobody has to refresh the CRM to see it. Web enquiries that land in the right place: a form answer goes through Find a Person, with its find-or-create option, then Create Opportunity and Attach a Person to an Opportunity link the two. Cleaner contact data: when your email tool reports a bounce, Update a Person sets Email Bounced, and Mercury Connect flags that address in red.
Now what Zapier does not do here. There is no action to delete a person or an opportunity, even though deletions can start a Zap. Updates need an ID: Update a Person wants the Person Id and Update an Opportunity the Opportunity Id, so a search goes first. And on the trigger side, each person trigger asks for a Contact Type and each opportunity trigger for an Opportunity Type.
For more, see our Make vs Zapier comparison or our Zapier agency page, and check whether any other tool connects to Mercury Connect at all.
Zapier words used on this page
Eight terms, explained once in plain English, then used as is.
- Zap
- An automation built on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event that starts a Zap, such as a new person or an opportunity status change in Mercury Connect.
- Action
- What the Zap does once started: the step that writes, sends or moves something, like creating an opportunity.
- Task
- The unit Zapier bills. Each action your Zap completes successfully counts as one task on your plan.
- Instant vs polling
- An instant trigger is reported by the app the moment it happens; a polling one is checked on a timer. Mercury Connect's are instant.
- Filter
- A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
- Search step
- A step that looks up something already in an app, such as a person, so the next steps can use what it found.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter, a search or a second action makes it one, and it then needs a paid plan.
What it really costs
Mercury Connect is not a premium app, so it works on the free plan. Its triggers cost nothing: only actions that complete are billed.
- TriggerNo task
- Successful action1 task each
- Free plan100 tasks a month, two-step Zaps
- Premium appNo
Each action that succeeds counts as one task, and a failed one does not. A three-action Zap uses three times what a one-action Zap does, so the enquiry flow above, with an opportunity and an attachment, costs two tasks per form answer on top of any other action. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps; a search or a filter makes the Zap multi-step and paid. The interval grid below is for polling triggers and does not apply to the 7 Mercury Connect triggers, which are all instant.
Connect Mercury Connect to Zapier in 3 steps
- 01
Open your connections
In your Zapier account, open the Apps page and click + Add connection. You need a Mercury Connect account, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 02
Pick Mercury Connect
Search for Mercury Connect in the dialog that opens, select it in the results, then click Add connection. A new tab opens so you can sign in on the CRM side.
- 03
Sign in and grant access
Sign in to Mercury Connect in that tab and grant Zapier access to the account. From then on, every Zap using Mercury Connect reuses that same connection, with nothing to redo.
Your first Zap: tell the team when an opportunity moves
GoalWhen an opportunity's status changes in Mercury Connect and the change meets your condition, your team chat gets a message.
- 01
Set the trigger
Start a Zap, choose Mercury Connect as the app and Opportunity Status Updated as the event, select your connection, then pick the Opportunity Type to watch.
- 02
Test it
Run the test. Zapier brings back the three most recent items of the connected account, so you map fields from a real opportunity rather than a guess.
- 03
Add the filter
Click the plus icon, add Filter, then set the field to look at, the rule and the value. Use a text rule on text; the wrong rule type means the filter never passes.
- 04
Add the message
Add your team chat as the action, choose its step for sending a message and write it from the opportunity fields of the test. Check at the test what each field holds.
- 05
Test and publish
Test each step once and read what came back, then click Publish. The filter makes this a multi-step Zap, so it needs a paid plan.
Mercury Connect triggers
7 events start a Zap when something happens in Mercury Connect, and 7 of them are instant: the app calls Zapier straight away, whatever your plan.
Deleted Opportunity
Instant triggerIn Zapier“Triggers when an opportunity is deleted.”
Fires when an opportunity is deleted. Since no Zapier action deletes anything in Mercury Connect, this is how a deletion made in the CRM reaches your other tools.
Deleted Person
Instant triggerIn Zapier“Triggers when a person is deleted.”
Starts the Zap when a person is deleted from Mercury Connect. It lets you clean up the copies of that person held elsewhere, in a mailing list or a contact sheet.
New Opportunity
Instant triggerIn Zapier“Triggers when an opportunity is created.”
Fires on every opportunity created in Mercury Connect. It is the natural start for alerts, task creation or a copy of the pipeline in a spreadsheet.
New Person
Instant triggerIn Zapier“Triggers when a person is created.”
Reacts when a person is created in the CRM. Whoever added them, the record can then be copied to the tools where you write to people or plan follow-ups.
Opportunity Status Updated
Instant triggerIn Zapier“Triggers when the opportunity status is updated.”
Goes off when an opportunity's status is updated. It follows progress through your pipeline rather than every edit you could watch with Updated Opportunity.
Updated Opportunity
Instant triggerIn Zapier“Triggers when an opportunity is updated.”
Fires whenever an opportunity is updated. Broader than the status trigger, it suits copies that must follow every change, like a pipeline sheet.
Updated Person
Instant triggerIn Zapier“Triggers when a person is updated.”
Watches people's records for edits: it runs whenever a person is updated. Changes made in the CRM can then flow out to the other tools that hold the same person; the test shows which details come with them.
Mercury Connect actions
Mercury Connect gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Person
ActionIn Zapier“Creates a new person.”
Adds a person to Mercury Connect from an email and a first name, both required. Optional switches cover the default mailing address, No Email Marketing, Mark as Private and Email Bounced.
Update a Person
ActionIn Zapier“Updates an existing person.”
Changes an existing person from their Person Id. Among the optional fields, Email Bounced makes Mercury Connect flag the address in red, and Add to DMH is available here.
Create Opportunity
ActionIn Zapier“Creates a new opportunity.”
Opens a new opportunity, with only its name required. Optional fields include Settlement Date Confirmed? and Security.
Attach a Person to an Opportunity
ActionIn Zapier“Attaches an existing person to an opportunity.”
Links an existing person to an opportunity with a relationship. Person Id, Opportunity Id and Relationship are all required.
Update an Opportunity
ActionIn Zapier“Updates an existing opportunity.”
Edits an opportunity from its Opportunity Id, including Settlement Date Confirmed? and Security.
Mercury Connect searches
2 search steps look for data that already exists in Mercury Connect, so a later step can use it.
A search step looks something up in Mercury Connect and hands it to the next steps. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the lookup does not return exactly one item.
Find a Person
SearchFind or createIn Zapier“Search for a person based on various criteria.”
Looks a person up from various criteria and hands what it found to later steps, which is how they get a Person Id; check it at the test. The editor also lists Find or create person: the same search with the create box ticked, not a separate operation.
Find an Opportunity
SearchFind or createIn Zapier“Search for an opportunity based on various criteria.”
Finds an opportunity from its name, which is required, plus other criteria. Find or create opportunity, shown in the editor, is this same search with creation switched on.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking it turns the search into a find-or-create: it stops offering the setting above and asks for the fields needed to create the missing item. Both Mercury Connect searches offer it.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks
Zapier lists no help article and no rate limit for Mercury Connect. The problems worth knowing come from how the triggers and actions fit together, and from Zapier itself.
Four cases, each tied to how the steps fit together. If a Zap still misbehaves once they are ruled out, see our Zapier troubleshooting guide.
The Zap keeps restarting
A Zap that writes where its own trigger watches can set itself off again and again. Each extra run of an action burns a task, so test any Zap that writes back into Mercury Connect.Duplicate people appear
Create Person adds a new person. Put Find a Person first, or tick its find-or-create option, and check at the test.Old records are not sent
A Zap only reacts to what happens after it is switched on. People and opportunities created earlier are not picked up; moving them is a separate job.A large batch is held back
If a trigger suddenly sends a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those items back instead of running them all.
Need help automating Mercury Connect with Zapier?
A person reads every message.



