When money moves, something happens.
A trigger, your steps, branches and loops on one canvas, over the bank data BankSync already syncs. Alert when a balance drops, post failed deliveries to a table, send a digest after each run. Dry-run it first; every run is audited.
Nightly order syncactiveAnything that happens to your money can start a run.
Triggers carry ids, counts and timestamps — never amounts or free text — so a run starts fast and your data stays where it is.
New transactions
A poll over the cached rows BankSync already has. Never a bank refresh.
Balance threshold
A balance crosses a line you set, up or down.
Feed events
A run completed or failed, a destination refused rows, an enrichment applied.
Bank events
A connection needs signing in again, a consent is expiring, a bank was removed.
Table events
A row created, updated, restored, or matching a view you choose.
Schedule, webhook, by hand
A cron, a signed webhook, a Run now, or another automation calling this one.
Steps that read, decide, write and tell someone.
Each step is a card on the canvas with its own settings, retries and error route.
Branch and loop
Paid or refunded? For each row? Match first, fall back, carry on.
AI steps
Summarise, classify, extract, draft or validate — on credits you control.
Read and write tables
Query, insert, update, delete and restore rows; add a message to a row.
Read your data
Banks, balances, transactions, enrichments, dashboards and widget data, as the app shows them.
Notify the workspace
An in-app notification to everyone, or to owners and admins only.
Run a feed
Kick off a sync and wait for its counts before the next step.
Templates for the asks everyone has.
Each template names what starts it and what it does, so you check it before anything runs.
Start from a template6 of 16 templatesFrom template to audited run
- 1
Start from a template or a blank canvas
Sixteen templates cover the common asks. Each names its trigger and its steps before you add it.
- 2
Wire the steps on the canvas
Drag a step in, bind it to a connection or a table, and draw the wire. The builder validates as you go.
BranchLoopAI stepTable writeNotify - 3
Dry-run, then publish
Test with sample data, publish an immutable revision, approve the grant it runs under. Every run lands in the history.
Dry runRevision 7Audited
Run historyno payloadsSafe to hand your books to.
Dry-run first
Test with sample data: nothing leaves BankSync until you publish.
Immutable revisions
Publishing creates a content-hashed revision. Rollback is one click, by a person.
Every run audited
What ran, what each step did, who approved what. Payloads are never kept in history.
Approvals for the risky bits
Bulk deletes above a threshold wait for a member to decide.
“Email me if software spend jumps 20%.”
Claude, ChatGPT or Cursor can create, dry-run and edit automations through the MCP server, the REST API and the CLI. Approving what they build stays with you.
Frequently asked questions
What is a BankSync automation?
A small program you draw instead of write: one trigger (a schedule, a webhook, a bank or feed event, a table change, a poll over your synced rows), then steps that branch, loop, read your data, write to tables, call AI or notify the workspace. It runs under a grant a workspace member approved, and every run is recorded.
Can an automation move money or change my bank?
No. Automations read the data BankSync has already synced and act inside your workspace: tables, dashboards, feeds, notifications. There is no step that moves money or talks to your bank beyond the read-only connection you already approved.
Which notifications can an automation send?
An in-app notification to the whole workspace or to owners and admins, capped at 50 a day by default. A feed converted into an automation can also email its recipients after a run. Slack and SMS are not available yet.
What happens when a step fails?
You decide per step: retry on named errors with a backoff, route the error to another branch, or stop the run with a titled reason. The run history shows each step’s status, attempts and failed item count — never the payload.
Can my AI agent build automations for me?
Yes. The MCP server, REST API and CLI expose create_automation, dry_run_automation, edit_automation and friends. Approving the grant, deciding an approval, rolling back and re-running stay with a signed-in member.
Who can use automations today?
Automations are in early access. They are on for every workspace in staging and for selected production workspaces while we finish the rollout. Ask from inside the app or contact us to join.
Let the boring part run itself.
Connect a bank, pick a template, dry-run it on sample data. Automations are in early access; ask from inside the app to join.