Every 15 minutes

Post every Mercury transaction to Slack

Deposits and payments appear in your channel within about 15 minutes, each one posted once.

Runs: Every 15 minutes
Apps: Mercury
AI: Not needed
Access: read-only token

Send this to your assistant

Create a ClickRuntime automation: every 15 minutes, check Mercury for new transactions on all my accounts and post the counterparty, amount and direction to #bank in Slack.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Every incoming and outgoing transaction on a business account tells a story: a customer paid, a subscription renewed, someone spent on a company card. Most owners see these only in a monthly statement, where an unfamiliar $480 charge from three weeks ago is hard to challenge and a payment that has not arrived is hard to chase. Small fraud and billing errors are easiest to fix on the day they happen.

Every 15 minutes, ClickRuntime lists the transactions on your Mercury account since the last check, skips ones it has already posted, and sends each new one to Slack. The message shows the amount, direction and counterparty, so the whole team can follow the account.

It is a good fit for owners who want to see their cash move and for finance teams that reconcile daily.

What you get out of it

Unexpected charges are caught early
A charge you do not recognize is much easier to dispute within a day than a month. Seeing it in Slack gives you time to ask who made it and cancel if needed.
Customer payments are confirmed quickly
When a client says they paid, you can check the channel instead of logging into the bank. You can ship the order or start the work without waiting for a manual confirmation.
Reconciliation becomes lighter
Because each transaction is posted when it happens, your bookkeeper can match them as they appear. That avoids a month-end pile of unmatched lines. Matching is quicker when each line is fresh.
The team understands cash flow
Seeing money come in and go out builds a feel for the business that a dashboard does not. Managers learn which customers pay quickly and which expenses recur. That context helps when planning hiring and purchases.
Each item appears once
Remembering what has been posted avoids repeats, so the channel stays clear even if a run is delayed. You can rely on it as a complete record. Nothing slips through unnoticed or shows up twice.
A second pair of eyes on spending
When several people can see card activity as it happens, odd purchases get questioned quickly. Honest mistakes and genuine fraud are both caught while they are small and easy to reverse.

How it works

What happens, step by step

Every 15 minutes, ClickRuntime checks each of your Mercury accounts for recent transactions.
It skips any transaction it has already posted, so each one appears only once.
Each new deposit or payment appears in your #bank Slack channel with the direction, amount, counterparty and account.

Before it runs live

Connect Mercury

What you get

RunsEvery 15 minutes

Post every Mercury transaction to Slacktoday, 9:00Succeeded

Slack · #bank⬇ in $12,500.00 · Acme Corp (Mercury Checking ••4321)

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Mercury steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

new_transaction_alert.pyexample

from clickruntime import on_trigger, credentials, http, state, notify, report_fetched

API = "https://api.mercury.com/api/v1"

@on_trigger
def run(event):
    h = {"Authorization": f"Bearer {credentials.secret('MERCURY_TOKEN')}"}
    seen = set(state.get("seen") or [])
    fresh, recent = [], []
    for acct in http.get(f"{API}/accounts", headers=h).json()["accounts"]:
        txs = http.get(f"{API}/account/{acct['id']}/transactions", headers=h, params={"limit": 50}).json()["transactions"]
        recent += [t["id"] for t in txs]
        fresh += [(acct["name"], t) for t in txs if t["id"] not in seen]
    report_fetched(len(fresh))
    if not fresh:
        return {"new": 0}
    for name, t in fresh:
        direction = "⬇ in" if t["amount"] > 0 else "⬆ out"
        notify.slack(f"{direction} ${abs(t['amount']):,.2f} · {t['counterpartyName']} ({name})", channel="#bank")
    state.set("seen", recent)
    return {"new": len(fresh)}

FAQ

Common questions

Does it include pending transactions?

It reports the transactions Mercury lists on the account. Pending ones may appear first, and whether you also see them again after they settle depends on how the status is handled, so check a sample after setup.

Can I limit it to large transactions?

Yes. A minimum amount can be added so that only transactions above, say, $1,000 reach Slack. This helps if your account has a lot of small card purchases that would otherwise flood the channel. Smaller ones then stay out of the channel.

Is it safe to share transaction details in Slack?

The message contains whatever fields you choose to include. If the channel has many members, you can leave out account numbers and show only amount and counterparty, or send alerts to a private channel. A private channel keeps the audience small.

What permissions does it need?

read-only token. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it checks. Checks that find nothing new and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Hourly