Roles and accounts
Add and change roles, and manage your connected Google accounts.
Last verified 2026-10-07
In the web app
Roles
Add a role on the Roles page with a name of up to 40 characters and a colour.
A new role starts with every kind of email as an update; change that in the roles table or on the role's own page.
Renaming or recolouring a role keeps its email settings.
A role does not need an account; a role that no account and no routing rule feeds shows Agent-only: receives no mail.
On a role's page, Where this role's tasks live chooses zonask (the default) or a Google Tasks list from a connected account with Tasks permission. New tasks of this role go to the chosen list. Tasks you already have stay where they are. If Google deletes the list, zonask returns the role to zonask and shows one notice.
Routing rules
One mailbox can feed several roles: under Routing rules on the Roles page, choose a role, what the rule matches (Recipient alias, Gmail label or Sender domain) and a value, then press Add rule.
A new email takes the role of the first rule in your list that matches it; without a match it takes its account's role.
Move up, Move down and Remove change your list; every change applies to new emails only.
You can have at most 50 routing rules.
Preview lists up to 20 recent emails the rule would have matched, from what zonask already stored, without reading your mailbox again.
Connected accounts
Setup, Accounts opens the one list of your connected Google accounts; add more with Add a Google account, one at a time.
The address you sign in to zonask with is not one of these accounts: the list holds the mailboxes and calendars zonask reads, and the page names your sign-in address above it.
Each account shows its role and its status: Connected, Choose a role, Reconnect needed or Error.
Choose an account's role in its picker; it saves at once.
Next to the role, Calendar use says how zonask treats the account's calendar: My calendar, Show only or Not used; see Inbox and calendar.
Sync now reads your accounts right away, at most once a minute.
Disconnect asks again, then revokes zonask's access at Google and deletes the stored token.
When Google rejects an account's access, the account shows Reconnect needed with Reconnect.
When your company blocks zonask
If your company's Google Workspace blocks zonask, Google's answer brings you to Ask your IT to allow zonask; you also reach it from the accounts page with Your company blocks zonask? Ask your IT for approval.
Enter your work email there, and zonask prepares a request your IT can approve; zonask itself sends no email.
Your connected accounts takes you back to the list.
Second brain
Setup, Second brain connects one notes vault that runs as a remote MCP server, such as an Obsidian vault served by a Vault MCP.
Enter the server's https address and press Connect: zonask finds the server's sign-in, opens its page, and you sign in there.
zonask asks for the narrowest access the server lists for a second brain, and zonask itself only searches your notes and adds new ones.
zonask keeps only an encrypted sign-in it renews by itself, and the page then shows Signed in with OAuth. and the status.
When the server no longer accepts that sign-in, the page shows Reconnect needed with Reconnect, and you get one notice.
For a server without sign-in, open Use an API key instead, paste the token the server gives zonask and press Connect with API key.
Disconnect deletes zonask's stored sign-in or key; to end the sign-in on the server as well, remove zonask from the apps the server's sign-in lists.
In Claude or ChatGPT
list_roles, show_role and list_accounts show your roles and accounts; save_role and set_account_role change them after your confirm.
list_task_lists shows the lists in one connected Google account. save_role can choose one as a role's task home after your confirm. For example, ask “Put new Private tasks in my Google Tasks list Home.”
set_calendar_use changes an account's calendar use after your confirm.
list_roles and show_role also show each role's routing rules and whether it is agent-only; save_role adds, moves or removes routing rules after your confirm and previews the emails each new rule would have matched.
sync_now reads your accounts now, like Sync now.
Connecting and disconnecting accounts happen only in the browser.