The work gets discussed in a channel and then done somewhere else. Zero closes that gap: ask in the thread, and it reaches the tools the answer actually lives in.
Connecting a service is an approval, not a key handover — credentials stay outside the place the agent runs.
Install it in Slack or Microsoft Teams and it joins the channels you invite it to. Nothing changes about how your team already communicates.
Mention Zero where the question came up. The answer, the draft, or the report lands in the same thread, with the context everyone can already see.
Approve the services it may reach — mail, docs, code, CRM — one connector and one permission at a time.
Scheduled work can post its result into the channel that cares about it, so the update arrives without anyone chasing it.
Over a hundred services are supported. These are the ones teams wire up first.
Mention Zero in a channel or DM it directly. Threads keep their context, and automations can post results where the team is watching.
The same assistant in the Microsoft stack — conversations and thread replies, for teams that live in Teams rather than Slack.
Read a thread, prepare a reply as a draft, and pull the week's meetings into a brief. Sending stays a human decision.
Notion, Google Docs, Sheets, and Drive, so the output lands in the document the team already reads.
GitHub and Linear for the work that starts as an issue and ends as a pull request.
HubSpot, Stripe, and the rest of the operational stack, for the record keeping that follows every conversation.
No. It sees the channels it is invited to and the messages that mention it. It is a participant in the conversations you bring it into, not a listener on the workspace.
No, and you should not use one. Each member connects their own account, so what Zero can reach on your behalf matches what you can reach yourself.
Outside the environment the agent runs in. Requests are made on your behalf through an approved connection, so the agent never holds the token itself.
Most services with an API can be added as a connector. If yours is missing, tell support what you need and we will look at adding it.
Yes. A scheduled workflow can deliver its result straight into the Slack or Teams conversation that should see it.
Zero also covers workflows and automation, generative services, and team collaboration. See the built-in web services it calls without an API key of your own, the models you can switch between, and pricing for what each plan includes.
Ask where the work is discussed and let the answer come back in the thread.