What could this do for me?
"What can Faber already do about invoices?"
Uses browse_task_catalog, which works before you have a Faber account at all.
Connect Faber
Set it up in the chat you already had.
Connect Faber to Claude or ChatGPT and say "I want this to keep happening". The assistant already has the mail, the sheet and the wording in front of it, so it can set the task up, show you a preview, and hand it to Faber to run from then on.
Why in a chat
The assistant just did the work.
It has seen the real mail, the real sheet, and the way you write.
That is a better description of the task than anything you would type into a setup form.
Faber adds the part a chat cannot do: running on Monday when nobody is in the chat.
Schedules, triggers, approval holds and a record of every run.
Try these
Three things to say, once Faber is connected.
Turn this into a task
"That reply you just drafted - I write one like it every morning. Set it up in Faber to run at 8am and show me a preview."
Uses create_task, then get_build_stateand run_task for the preview.
Catch me up
"What is waiting on me in Faber?"
Uses what_needs_attention, then get_runto read back anything a run is holding.
What it can do
Reading, and acting.
Without a Faber account, an assistant can browse the task catalog and nothing else. That is enough to answer "what could this do for me", which is the question worth answering before anyone signs up.
Once you connect your account, it can do everything: read your tasks and runs, build one, run one, approve held messages, arm and disarm automations. Every assistant gets the same tools - there is no short list of favoured ones. What decides it is your account and your yes on the consent screen, not who made the assistant.
Some things are not reachable at all, by any assistant: deleting your account, deleting a task, anything to do with billing, and reading a stored key. No part of Faber returns a stored secret to anybody, including you.
Approvals
Sending is still your call.
A preview run discards every write, so you can see what it would do before anything happens.
When a live run reaches something you flagged, it stops and holds it.
An assistant may only pass on a yes you gave it. It is told not to decide on its own reading of the output.
Every approval, arming and stored key records which assistant carried it, so you can check later.
An assistant can start a limited number of runs a day on your behalf. Runs you start in Faber are not counted.
Every assistant gets the same tools. What decides what one can do is your account and the yes you gave it, not who made it.
Connecting accounts
Faber needs its own connections.
Connecting Gmail to Claude does not connect it to Faber. Faber runs on Monday when the chat is closed, so it holds its own grant.
That is one browser click, not one per task: ask the assistant to connect an account and it hands you a link. Open it whenever. The task waits for you rather than the other way round, and every later task reuses the same connection.
Add Faber to your assistant.
You need a Faber account. Connect it once in your assistant's connector settings and the tools appear in every chat.