Connected Apps & Integrations

Connected Apps (Work menu) and Integrations (Configuration menu) both link WorkBOS to outside tools, but in opposite directions. Connected Apps is a one-click, authorize-once connection that lets your Chief of Staff READ and cite what is in your other apps. Integrations SENDS your data out or automates it. If you just want to authorize an app and go, that is Connected Apps.

• Connected Apps (inbound / read-lane): click Connect, authorize in the app, done, no webhook URLs or API keys to paste. Slack, Gmail and Google Drive are all live. Chief can then search and cite that content and deep-link back to it. Google Calendar is NOT a Connected App: it was listed as one until v1.168.0 and every attempt to connect it was refused by the server, so the entry was removed rather than left to disappoint you.
• Scope per connection: choose “Only me” to index it privately (nobody else, not even an admin, can recall it through Chief) or let an admin share it with the whole team.
• Security is end-to-end: connecting requires the Connected Apps create permission (Users ▸ Roles), every account is fenced to your workspace by row-level security, and OAuth tokens are stored server-side and never shown back. One OAuth app per provider is held by the platform; every workspace connects its OWN account through it, isolated from all others.
• Integrations (outbound / automate): the catalogue is sorted by HOW a thing connects, and each entry says which. Built-in modules of ours; one-click Connected Apps; event webhooks that POST to Slack, Discord, Teams or any endpoint in that product’s own message format; inbound bridges others POST into (GoHighLevel, our REST API); providers you bring your own account for and we call directly (Twilio, Telnyx, Plivo, Resend, SMTP, Gmail, Stripe, LiveKit, LinkedIn); assistants over MCP; guided CSV migrations; and, listed plainly rather than dressed up, the ones we have NOT built an adapter for, which you wire yourself with an API key.
• The counter at the top is three numbers, not one. Before v1.168.0 it printed the length of the list under the word “live”, which counted a Zapier recipe and a CSV export the same as a working webhook. If a tile claims we built something, there is a file in the codebase that implements it and a test that reads that file, so the page cannot get ahead of the product again.