Resources · Zapier integration

Mercury Zapier integrationAutomate Mercury with Zapier.

The Mercury Zapier integration gives you 6 triggers, 0 actions and 0 searches. Every one is instant: Mercury tells Zapier when a transaction appears, settles, fails, is cancelled or changes, and when an account balance moves. Zapier cannot write anything back into Mercury.

See the 6 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Mercury Zapier integration does

Mercury is an online financial platform that startups use to manage their money. On Zapier it is a source of events: it starts a Zap (an automation on Zapier: one trigger, then one or more actions that run every time the trigger event happens) whenever something happens on your accounts, and other apps take it from there.

Three results people build first. Spending alerts: New Transaction posts each new movement in your team chat, so card spend is visible to the people who care. A bookkeeping sheet that only holds final figures: Settled Transaction adds a row once a transaction has settled, which keeps pending amounts out of your numbers. A follow-up on what went wrong: Failed Transaction creates a task in your task manager for each payment that did not go through.

The detail that changes how you build: New Transaction fires before the transaction settles, and Transaction Update fires on every change, including a revised amount after settlement, as with a tip added later. Pick the trigger that matches the moment you care about.

Now what Zapier does not do here. Mercury offers no action and no search on Zapier: a Zap cannot move money, create anything in Mercury or look a transaction up. Data only flows out. For more, see our Zapier review or our Zapier training page.

Vocabulary

Zapier words used on this page

Seven 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 the Zap. With Mercury, that is a transaction event or a balance change on your accounts.
Action
What the Zap does once started: the step that writes, sends or moves something in another app. Mercury has none.
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. All Mercury triggers are instant.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A filter or a second action makes it one, and it then needs a paid plan.
Cost

What it really costs

Mercury is not a premium app, so its triggers work on the free plan. A trigger never costs a task, however many transactions come through.

  • TriggerNo task
  • Successful action1 task each
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

Only the actions in your other apps are billed: each one that succeeds counts as a task, and one that fails does not. A Zap with three actions uses three times what a one-action Zap does. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps; a filter on the amount makes the Zap multi-step, which needs a paid plan. The grid below is how often Zapier checks polling triggers. It does not apply to the 6 Mercury triggers, which are all instant.

Connect

Connect Mercury to Zapier in 3 steps

  1. 01

    Open your connections

    In your Zapier account, open the Apps page and click + Add connection. You need a Mercury account, plus read or write access on anything you do not own yourself and want the Zap to touch.

  2. 02

    Pick Mercury

    Search for Mercury 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 Mercury side.

  3. 03

    Sign in and grant access

    Sign in to Mercury in that tab and grant Zapier access to the account. From then on, every Mercury Zap you build reuses that same connection, with nothing to redo.

First Zap

Your first Zap: an alert for transactions that matter

GoalWhen a new Mercury transaction meets the condition you set, your team chat gets a message about it.

  1. 01

    Set the trigger

    Start a new Zap, choose Mercury as the app and New Transaction as the event, then select your Mercury connection. Decide whether credit accounts should be included too.

  2. 02

    Test on real data

    Run the test. Zapier brings back the three most recent items of the connected account, so you map fields from a real transaction rather than a guess.

  3. 03

    Add the filter

    Click the plus icon, add Filter, then set the field to look at, the rule and the value. Use a number rule for an amount; a text rule on a number never passes.

  4. 04

    Add the message

    Add your team chat as the action, pick its step for sending a message and write it with the fields from the test. Check at the test what each field really holds.

  5. 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.

Triggers

Mercury triggers

6 events start a Zap when something happens in Mercury, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Checking/Savings Account Balance Update

Instant trigger

In Zapier“Triggers when an account's balance changes.”

Fires each time the balance of a checking or savings account changes. Instead of a transaction, you get the account's new position, which is what a cash watch needs.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you want a message when the balance crosses a level you set, using a filter on the balance.
Watch out
check at the test what a balance update carries, and let a filter keep only the runs worth acting on.
2

Cancelled Transaction

Instant trigger

In Zapier“Triggers when a transaction is cancelled.”

Starts the Zap when a transaction is cancelled. It is the counterpart to New Transaction: whatever you logged or announced when the transaction appeared can be corrected here.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a spending alert went out earlier and the team should know the charge will not happen after all.
Watch out
run the test to see which details a cancelled transaction carries before mapping them anywhere.
3

Failed Transaction

Instant trigger

In Zapier“Triggers when a transaction fails.”

Reacts when a transaction fails. A failed payment is the kind of event that should never sit unnoticed in a dashboard, and this trigger pushes it to wherever someone will act on it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
each failure should create a task for the person who handles payments.
Watch out
a Zap only sees failures that happen after it is switched on; earlier ones stay in Mercury.
4

New Transaction

Instant trigger

In Zapier“Triggers when a new transaction is created on any bank account (eg. Checking or Savings). Optionally, can also include any Credit account (eg. Physical/Virtual Credit or Debit). This trigger fires before the transaction settles.”

Fires when a new transaction is created on any bank account, checking or savings, and can optionally include credit accounts such as physical or virtual cards. It fires before the transaction settles.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
speed matters more than the final figure, as with a spending alert.
Watch out
the amount may not be final yet; use Settled Transaction for anything that needs the final amount.
5

Settled Transaction

Instant trigger

In Zapier“Triggers when a transaction settles.”

Goes off when a transaction settles. By then the transaction is done, so this is the trigger to use when the record you write should not have to be corrected later.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
feeding a bookkeeping spreadsheet or an accounting tool with final transactions only.
Watch out
an amount can still be revised after settlement, as with a tip; Transaction Update is the trigger that sees those revisions.
6

Transaction Update

Instant trigger

In Zapier“Triggers when a transaction changes status. This will trigger on any update to a transaction, including revisions to the amount following settlement, such as in the case of tips for service staff.”

Fires whenever a transaction changes status, and on any other update to it, including a revised amount after settlement, such as a tip added for service staff.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you keep one row per transaction and want it to follow every change.
Watch out
one transaction can start this Zap several times, and each run's actions count as tasks.
When it breaks

When it breaks

Zapier lists no help article and no rate limit for Mercury. What goes wrong comes from the way the triggers behave and from how Zapier works.

Four cases are worth knowing before you switch a Zap on. Each one looks like a number that seems wrong or a row that seems missing, and each comes from how the triggers behave. If a Zap still misbehaves once these are ruled out, see our Zapier troubleshooting guide.

  • The amount in the sheet is wrong

    New Transaction fires before settlement, so the figure it sends may not be final. Build records that must match on Settled Transaction instead.

  • One transaction, several runs

    Transaction Update fires on every change, including revised amounts after settlement. Each run's actions cost tasks, so plan for several runs per transaction.

  • Past transactions are missing

    A Zap only reacts to what happens after it is switched on. Transactions from before are never sent; filling them in is a separate job.

  • A large batch is held back

    If a trigger suddenly sends a huge batch, Zapier's flood protection can hold those items back instead of running them all at once.
Need help

Need help automating Mercury with Zapier?

A person reads every message.

FAQ

Mercury Zapier integration: questions

01Is the Mercury Zapier integration free?
Yes. Mercury is not a premium app, so all six triggers work on the free Zapier plan. That plan includes 100 tasks a month and unlimited Zaps, but every Zap stops at two steps: one trigger and one action. Posting each new transaction to your team chat fits. Posting only the transactions above a threshold does not, because the filter adds a step and makes a multi-step Zap, which needs a paid plan. The upside: Mercury's triggers are instant, so the free plan's polling interval never delays them.
02How many tasks does a Mercury Zap use?
The Mercury side costs nothing: a trigger never uses a task. What counts is each action in your other apps that completes successfully, one task each, while an action that fails is not counted. So a Zap that writes every settled transaction to a spreadsheet uses one task per transaction. Watch Transaction Update: it fires on every change to a transaction, and every run that reaches an action costs a task. A few apps and actions take more than one task when they complete.
03Is Mercury on Zapier real time?
Yes. All six Mercury triggers are instant: Mercury tells Zapier the moment a transaction is created, settles, fails, is cancelled or changes, or when a balance moves, and the Zap starts right away whatever your plan. The polling interval of the Zapier plans does not apply to them. In the editor, a Zap built on an instant trigger shows a lightning bolt. Keep in mind that instant does not mean final: New Transaction fires before settlement.
04What do you need to connect a Mercury account?
A Mercury account, plus read or write access on anything you do not own yourself and want the Zap to touch. From the Apps page of your Zapier account, click + Add connection, search for Mercury, click Add connection, sign in on the tab that opens and grant Zapier access. The connection is then reused by every Zap that starts on Mercury, so there is nothing to redo per Zap. When you first test a Mercury trigger, Zapier brings back the three most recent items of the connected account.
05Which Mercury trigger should feed a bookkeeping sheet?
Settled Transaction, when the sheet needs final figures. New Transaction fires before the transaction settles, so its amount may still move. Settled Transaction waits for settlement, which keeps pending amounts out of your records. If amounts can be revised even after settlement, as with a tip, Transaction Update sees those changes too, but it can fire several times per transaction, so it suits a sheet that updates one row rather than one that adds a row per run.
06What if the Mercury operation you need is missing?
Then Zapier cannot do it with Mercury today. The Mercury page on zapier.com shows the current list of operations, which at the time of writing is six triggers and no action or search. So a Zap cannot create a transaction, move money or look one up in Mercury. The Zap editor cannot add an operation either. If your process needs that, do the step in Mercury itself, or check whether another automation tool connects to Mercury with the operation in question.
07Zapier, Make or n8n for Mercury?
Use criteria rather than a ranking. Coverage: on Zapier, Mercury brings six instant triggers and nothing else, so it suits flows that react to your accounts; check whether Make or n8n connect to Mercury and with which operations. Shape: on Zapier, a filter on the amount already makes a multi-step Zap on a paid plan. Volume: busy accounts mean many runs, and each successful action is a task. Speed is not the question on Zapier here, since every Mercury trigger is instant.
Same platform

Other docs you might need on this stack.

Browse all integrations