Collects as they arrive, acts daily

Get a weekly log of completed transfers

Every Monday you get last week's settled Brex transfers in one list, money in and money out.

Runs: Collects as they arrive, acts daily
Apps: Brex
AI: Not needed
Access: transfers read

Send this to your assistant

Create a ClickRuntime automation: keep track of every Brex transfer that's processed, and every Monday at 9am email me last week's list with date, counterparty, direction and amount.

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

Month-end reconciliation is easier when every transfer has been written down somewhere as it happened. With Brex, incoming and outgoing transfers are in the dashboard, but reviewing them means filtering by date and exporting a list. A bookkeeper who needs last week's wires and ACH payments in one place will usually ask for a spreadsheet, and the finance lead forgets until the books are already late.

As Brex processes each transfer, a TRANSFER_PROCESSED event arrives at ClickRuntime and is stored in state. Nothing is sent until the end of the week, when the list is emailed to you in one message and cleared for the following week. It gives you a complete weekly ledger of money in and out of the account.

It is a fit for bookkeepers and finance leads who review transfers in batches rather than one at a time.

What you get out of it

Bookkeeping gets a ready weekly list
The bookkeeper receives every processed transfer in one email, so there is nothing to export or request. Entries are matched against invoices and bank lines the same week they happened.
Nothing is missed during busy weeks
Events are stored as they arrive, so a transfer that happens late on a Friday still appears in that week's list. The log is complete even when nobody was watching the account.
Reconciliation errors are found sooner
Comparing a weekly list against expected payments quickly shows a transfer that should have occurred and did not, or one nobody recognizes. Catching that within a week keeps the unexplained items small.
One message instead of many notifications
Collecting the events and sending them together avoids constant pings for routine movements. Attention is saved for the failure alerts, which are the ones that need an immediate response. Collecting events this way means a late-week transfer still lands in the right report.
A durable record of cash movement
The emails build a dated history of incoming and outgoing transfers that can be searched later. When a question comes up about a payment from months ago, the answer is a mailbox search away. Auditors and new team members benefit from the same tidy trail.

How it works

What happens, step by step

Each time a Brex transfer settles, ClickRuntime records its date, description, payment type and amount.
Every Monday at 9am it sends you one email listing last week's settled transfers, money in and money out.
The list is then cleared for the new week.

Before it runs live

Connect Brex
Paste your automation's link into the other app's webhook settings

What you get

RunsCollects as they arrive, acts daily

Get a weekly log of completed transferstoday, 9:00Succeeded

Email · Brex transfersBrex transfers last week (6) 2026-10-13 Northwind Payroll ACH $24,800.00

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

processed_transfer_log.pyexample

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

@on_event
def handle(event):
    body = event.json or {}
    if body.get("event_type") != "TRANSFER_PROCESSED":
        return {"skipped": True}
    t = http.get(f"https://platform.brexapis.com/v1/transfers/{body['transfer_id']}",
                 headers={"Authorization": f"Bearer {credentials.secret('BREX_TOKEN')}"}).json()
    log = state.get("week") or []
    log.append([t.get("process_date") or event.received_at[:10], t.get("description") or "", t.get("payment_type", ""),
                t["amount"]["amount"] / 100])
    state.set("week", log)
    return {"stored": t["id"]}

@on_trigger
def run(event):  # Monday 9am
    log = state.get("week") or []
    lines = [f"{d}  {who}  {kind}  ${amt:,.2f}" for d, who, kind, amt in sorted(log)]
    notify.email_me(f"Brex transfers last week ({len(log)})", "\n".join(lines) or "No transfers processed.")
    state.delete("week")
    return {"transfers": len(log)}

FAQ

Common questions

Which transfers are included in the weekly list?

Those for which Brex sends a TRANSFER_PROCESSED event during the week, covering both incoming and outgoing transfers. Failed or pending transfers have different event types and are not part of this list unless you add them.

What happens to the list after it is sent?

The stored events are cleared after the email goes out, so each transfer appears in exactly one weekly report. Starting fresh each week keeps the emails a manageable size and prevents the same transfer being reconciled twice.

Can I get the list daily instead of weekly?

Yes. The collection method is the same, and only the sending schedule changes. A daily list suits teams with high transfer volume. Ask your AI assistant to switch the schedule and review the change before approving it.

What permissions does it need?

transfers read. 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.

The moment it happens