Chase overdue invoices
A billing teammate, triggered on an interval, in 4 steps across 2 granted connections. Installing copies it into your workspace as an ordinary job you can edit.
Install it
Installing copies revision 1 into your workspace as an ordinary job, schedule and procedure. You can edit every part of it afterwards; the recipe is a starting point, not a product you rent.
The demo runs on fictional data. Nothing in it can reach a real inbox.
What it does
One job, several apps, no one clicking through it
It runs unattended for as long as the work takes — minutes or hours — and carries the work across the connected apps you granted. If a model account hits its limit, the job continues from its last checkpoint on the next account you authorised: the SAME job, not a restart, so nothing already done is repeated. It stays traceable the whole time through its thread and its place on the board.
Steps, in order
- 01load_invoices
- 02select_overdue
- 03draft_reminder
- 04request_approvalApproval point
What it needs
2 grants, and the scope each one gets
Installing does not grant anything. Each requirement below is something you approve for this teammate, at the scope shown, and can revoke without touching the rest.
payments_read
- Scope
- read-only
email_write
- Scope
- write · approval-gated
A teammate also needs somewhere to think: one of your AI accounts, chosen per teammate. See what each capability family can do →
Inputs
What the install asks you, once
Installing creates the job, the schedule and your own editable copy of the procedure, then stops. Nothing runs until you have answered all three, and every later change is recorded as an edit to your copy — the published recipe is untouched.
- 01
Which teammate runs it
The recipe names a role; you choose the teammate. That teammate's model accounts, caps and grants are what the job actually runs under.
- 02
Which accounts it may touch
Each requirement above becomes a grant you make explicitly, at read-only or read-write, on the resources you select. No grant means no access.
- 03
Whether the schedule starts on
You can install it paused, run it once by hand to watch it, then turn the schedule on when you are satisfied with what it did.
Schedule
On an interval
every 360 min
- Kind
- interval
- Timezone
- Your workspace's
- If a run is missed
- Catch up once, then skip
- Notification
- Only when it needs you
You can pause it, run it once now, or change it to a different hour without touching the procedure. A paused schedule stops new runs; a run already in flight finishes at a checkpoint.
The procedure
4 steps, and you can edit any of them
This is the recipe's skill, written out. Reorder it, delete a step, add a check, or mark a point where it must ask you — it is an editable, replayable procedure, not a locked macro. You can also add a step by DEMONSTRATING it: take control of the teammate's browser and do it once while the recorder watches, and the clicks, the navigation and the values you typed become new steps. Capture pauses before any sign-in and the credential is taken from the vault at run time instead, so a password or a one-time code never becomes part of a procedure. There is no setting that turns that off.
- 01
load_invoices
Step - 02
select_overdue
Step - 03
draft_reminder
Step - 04Not editable away
request_approval
Approval point
What it will ask you
The exact thing, not a summary
- An approval shows the exact act: the recipient, the subject, the full body, the amount and currency, the account it would be sent or paid from, the resource it would change, and when the request expires.
- It authorises that one revision only. Editing the draft — recipient, body, amount, account or resource — voids the approval and raises a fresh request showing what changed.
- Limits and daily caps are rechecked at the moment of execution, not at the moment you said yes. Several outbound acts in one run mean several approvals, never one.
What it leaves behind
A receipt per call, reads included
- Every call this recipe makes into a connected account writes a receipt: the account, the resource, the record, the time, the outcome and a redacted diff of what changed.
- A denied call is a receipt too. A step whose grant is missing is skipped with the reason recorded, and the run continues rather than failing silently.
- A vault read is a receipt naming which secret, which teammate and which job. The value itself is never rendered, in the receipt or anywhere else.
Put this one to work
Installing creates the job, the schedule and your own editable copy of the procedure, then stops and asks which teammate runs it and which accounts it may touch. Nothing runs until you have answered both.
It's a snapshotA later revision of this recipe never changes what you installed.
It grants nothingConnections and scopes are separate decisions you make afterwards.
It's yours to changeEdit the steps, the schedule and the wording; it stops being a recipe the moment it lands.