Early access

Code a Week of Brex Expenses

For finance teams buried in card swipes. DuckyHelper learns Brex's web API once, reads the week's transactions, applies your coding rules, writes them to the ledger sheet, and puts anything unusual in a review tab.

YOU SAY

“Code this week's Brex transactions with our GL rules, add them to the Expense Ledger sheet and flag anything odd.”

Press fn (Ctrl+Shift+Space on Windows and Linux) and ask out loud.

DUCKYHELPER DOES

01
Turn Brex and Google Sheets into APIs it can callIt watches each site's own requests once and saves them as actions. Kept on your device.listTransactions(range)appendRows(sheet, rows)
02
Pull the week's transactions
03
Apply GL codes from your rules
04
Add them to the ledger sheet
05
Put new vendors and odd amounts in a review tab

You getCoded before Friday. The ledger is current and only the real questions need you. Next week it's one call.

Code a Week of Brex Expenses

A run, drawn from this page · early access on Mac

WHERE IT ASKS FIRST

Nothing to send, so it runs straight through.

Nothing in this job sends a message or pays for anything, so it works through to the end and tells you when it's done. If a step ever would, it's built to stop and ask you first.

If it hits a sign-in, you sign in yourself. It's built not to type your passwords or card numbers.

Sign in to Brex to keep going

DuckyHelper is built not to type your passwords or card numbers. Sign in yourself, then it picks up where it stopped.

MAKE IT ALWAYS ON

Do it once. Then let it repeat.

When it's done, it offers to keep doing it: every Monday at 9:00 AM. Each run goes through the API it learned the first time, so it's quick, and it's still built to ask before it sends or pays.

Always-on automations are in early access on Mac.

Make this automatic?Schedule

Code a Week of Brex Expenses

WhenEvery Monday at 9:00 AM

DoesDuckyHelper reads the week's Brex transactions, applies your GL codes, adds them to the ledger and flags anything odd.

ThenTells you when it's done

FAQ

Before you ask it.

What do I say?

Press fn (Ctrl+Shift+Space on Windows and Linux) and ask out loud, in your own words, like "Code this week's Brex transactions with our GL rules, add them to the Expense Ledger sheet and flag anything odd."

Why is the second time faster?

The first time, it writes small JavaScript tools for Brex and Google Sheets and builds an API from each site's own buttons, forms and requests. After that it calls them directly, so the job runs in one go instead of click by click. It costs less and breaks less.

Will it send anything without me?

It's built to ask first before it sends a message or pays for anything, and to wait for your yes. It may not recognize every send or payment, so keep an eye on tasks that involve messages or money. It's built not to type your passwords or card numbers: you sign in yourself, and it picks up from there.

Why not just do it by hand?

Every transaction needs a code, and the odd ones take the longest to spot.

Can it keep doing this on its own?

Yes. When it's done it offers to make it automatic (every Monday at 9:00 AM). Each run goes the same way and is still built to ask before it sends or pays.

Can I use this today?

Doing jobs in your apps is in early access on Mac. Talking to DuckyHelper, and having it see your screen and draw on it, works today on Mac, Windows and Linux.

MORE JOBS LIKE THIS

Every use case →