Letting your assistant read another app is not the same job as sending your data out to one. Most catalogues blur the two. This one sorts by how a thing actually connects, and says so on every tile.
Included on every plan, free included
One-click, authorize-once OAuth. Slack, Gmail and Google Drive are live. Your AI chief of staff can then search and cite what is in them and link straight back to the original. No webhook URLs and no API keys to paste.
Choose Only me and it is indexed privately: nobody else, not even an admin, can recall it through Chief. Or let an admin share it with the whole team.
Event webhooks POST to Slack, Discord, Teams or any endpoint, in that product’s own message format. Inbound bridges accept posts from other tools. There is a GoHighLevel bridge so you can run both without double entry.
A key you issue is READ ONLY by default. You choose read-only or read-and-write when you create it, and you can change an existing key between the two at any time without reissuing it, so a dashboard keeps working while losing the ability to write.
Point Claude, ChatGPT or Cursor at your workspace and they read it through the same row-level security and role rules a person gets, with a key you can revoke and a workspace-wide kill switch for writes.
The catalogue used to print the length of the list under the word "live", which counted a Zapier recipe the same as a working webhook. Now every tile says how it connects, and if a tile claims we built something there is a file in the codebase that implements it and a test that proves it.
The part you would otherwise find out in week three. If one of these is central to how you work, raise it before you buy rather than after.
Direction. Connected Apps is inbound: a one-click OAuth connection that lets Chief READ and cite what is in your other tools. Integrations is outbound: sending your data out or automating it. If you want to authorize an app and go, that is Connected Apps.
Yes. WorkBOS is itself an MCP server, so Claude, ChatGPT or Cursor can read your workspace through the same permissions a person has, with a key the workspace issues and can revoke. Included from Pro upwards, with a kill switch for writes.
A key is read-only by default, and you can flip an existing key between read-only and read-and-write without reissuing it. Keys are stored encrypted server-side and the page shows status, never the value. Per-key rate limits apply.
Yes, through the webhook action on any automation: it POSTs the rule, event and trigger data to any URL you choose. We do not maintain a native Zapier app, and the catalogue says so rather than showing a logo.
The full product documentation for this module is at /docs#connectors.
Free for up to 5 seats, no card required. Every module is in the same workspace, so nothing needs connecting to anything.