Apps
Apps your worker uses.
ZeroTwo connects to the systems where work already happens. Instead of asking you to copy context into chat, the worker uses approved apps to read, write, search, and deliver.
Gmail & Calendar
Gmail, Google Calendar, Outlook, Teams
Meeting briefs, email follow-ups, inbox triage, scheduling prep
Drive & Docs
Google Drive, Docs, Sheets, Slides, Dropbox, Box
Find files, summarize documents, produce reports and spreadsheets
GitHub & Dev Tools
GitHub, Linear, Postman, Supabase, Vercel, Datadog
Bug triage, code review, issue creation, release notes, incident briefs
Slack & Communication
Slack, Teams, Zoom, Gmail, Discord
Channel digests, action item extraction, stakeholder updates
Notion & Databases
Notion, Airtable, Postgres, Snowflake, BigQuery
Knowledge base updates, analysis, QA checks, structured exports
Finance & CRM
Stripe, Salesforce, HubSpot, Ramp, QuickBooks
Revenue reports, pipeline briefs, reconciliation, renewal risk reviews
How ZeroTwo uses a connected app
Connecting an app is not the same as handing a chatbot your inbox. Each connection grants a specific set of actions in that app, and every action with a consequence — sending, writing, deleting, changing a record — stops for your approval before it runs.
Reading context instead of asking you to paste it
Most of the work in a normal AI task is assembling context: finding the thread, exporting the report, copying the ticket in. A connected app removes that step. Asking for a brief on tomorrow’s meeting means the agent reads the calendar entry, finds the recent thread with those attendees, pulls the account record, and opens the relevant documents — then writes the brief. Nothing was pasted, and nothing was left out because you forgot it existed.
Writing back, behind an approval gate
Output usually has to land somewhere: a draft in the mail client, rows appended to a sheet, an issue opened, a page updated, a message posted to a channel. ZeroTwo composes the change and shows it to you before committing it. Approving is one step, and editing the draft first is the normal case rather than the exception.
Combining apps in a single task
The categories above matter less than the combinations between them. A pipeline review reads the CRM, the calendar, and the mailbox. A release note reads the repository and the issue tracker, then posts to chat. A month-end pass reads the payment processor and the accounting system and writes to a spreadsheet. Real work crosses systems; a single-app assistant leaves you to be the integration layer.
Permissions and scope
You connect the apps you want and nothing else, and any of them can be disconnected later. Access follows the account you authorize with, so the agent never sees more than that account does — a shared folder you cannot open is not readable by the agent either. Approval gates sit on top of that, so read access and write access are separate decisions.
Limits worth knowing
A connection can only do what the app’s own API exposes, so anything the vendor does not offer programmatically is out of reach, and the same rate limits that apply to any other client apply here. Very large exports are usually better handed over as a file than pulled live. If a token expires, the run stops and asks you to reconnect rather than quietly returning stale data.