{"id":"d4053153-bd1c-4c0c-92eb-5a8d8421dd34","slug":"workers-integrations","category_slug":"workers","order_index":104,"published":true,"created_at":"2026-06-19T14:40:42.572Z","related_slugs":"[\"behaviour-studio\",\"connect-integration\",\"worker-microsoft-google-account\"]","title_fr":"Connecter ton Worker à des outils : les intégrations","title_en":"Connecting your Worker to tools: integrations","content_en":"\n\n<blockquote>\n<p><strong>The key idea:</strong> an integration is like handing your Worker a <strong>keyring</strong>. Once it has the key, it knows how to open the right door (via the <em>discover</em> mechanism — see the Behavior Studio article).</p>\n</blockquote>\n\n<h2>Where it happens</h2>\n<ul>\n<li>Open the Worker's page → <strong>Integrations</strong> tab</li>\n<li>There you'll find the <strong>catalog</strong> (everything available, grouped by category) and your <strong>active connections</strong></li>\n</ul>\n<figure class=\"screenshot\"><img src=\"/images/worker_integrations_catalog.png\" alt=\"Worker Connectors tab: Connectors, Custom, API &amp; MCP, Computer, Public tabs; Communication, Marketing &amp; Sales, Dev &amp; Project, Design &amp; Docs, Data, Analytics, Finance, Social networks, HR &amp; Recruiting category filters; Essentials (Gmail, GitHub, Outlook, Slack, LinkedIn, Microsoft Teams), then More connectors\"><figcaption>Worker Connectors tab: Connectors, Custom, API &amp; MCP, Computer, Public tabs; Communication, Marketing &amp; Sales, Dev &amp; Project, Design &amp; Docs, Data, Analytics, Finance, Social networks, HR &amp; Recruiting category filters; Essentials (Gmail, GitHub, Outlook, Slack, LinkedIn, Microsoft Teams), then More connectors</figcaption></figure><h3>The categories</h3>\n<p>Integrations are sorted into broad families:</p>\n<table>\n<thead>\n<tr>\n<th>Category</th>\n<th>Examples</th>\n</tr>\n</thead>\n<tbody><tr>\n<td><strong>Communication</strong></td>\n<td>Slack, Gmail, Outlook, Microsoft Teams, Google Calendar</td>\n</tr>\n<tr>\n<td><strong>Social networks</strong></td>\n<td>LinkedIn, Instagram, X</td>\n</tr>\n<tr>\n<td><strong>Marketing &amp; Sales</strong></td>\n<td>HubSpot, Salesforce, Apollo, Lemlist, Hunter, ZoomInfo, <strong>Pega</strong>, Affinity</td>\n</tr>\n<tr>\n<td><strong>Dev &amp; Project</strong></td>\n<td>GitHub, Linear, Jira/Confluence, Monday</td>\n</tr>\n<tr>\n<td><strong>Design &amp; Drive</strong></td>\n<td>Notion, SharePoint, Box, Canva, DocuSign</td>\n</tr>\n<tr>\n<td><strong>Finance</strong></td>\n<td>Stripe, Qonto, Pennylane, Shopify</td>\n</tr>\n<tr>\n<td><strong>Analytics</strong></td>\n<td>PostHog, Grafana</td>\n</tr>\n<tr>\n<td><strong>Data</strong></td>\n<td>Google Drive, Pappers, Data.gouv…</td>\n</tr>\n</tbody></table>\n\n<h2>The different ways to connect</h2>\n<p>Not all integrations connect the same way. Here are the main cases, from a user's point of view:</p>\n<h3>a) OAuth (the most common)</h3>\n<p>Click <strong>Connect</strong> to open the connector window (for example, Slack). Choose <strong>Sign in as Karen</strong> to connect on behalf of the Worker, or <strong>Use my own account instead</strong> to connect with your own account. No key to copy.\n<em>Examples: Slack, Gmail, Notion, Linear, Stripe, LinkedIn, GitHub…</em></p>\n<figure class=\"screenshot\"><img src=\"/docs_workers/worker_integration_oauth_connect.png\" alt=\"Slack connector window: Your AI team’s communication hub; Its own Slack member: people DM it or mention it, and it answers as Karen; Sign in as Karen button and Use my own account instead link\"><figcaption>Slack connector window: Your AI team’s communication hub; Its own Slack member: people DM it or mention it, and it answers as Karen; Sign in as Karen button and Use my own account instead link</figcaption></figure><p><em>Slack example: “Its own Slack member: people DM it or mention it, and it answers as Karen.” Select “Sign in as Karen” to connect as the Worker, or “Use my own account instead” to connect with your own account.</em></p>\n<h3>b) API key</h3>\n<p>You click <strong>Connect</strong>, a dialog asks you to <strong>paste an API key</strong> generated at the provider.\n<em>Examples: Apollo, Hunter, Grafana, PostHog, Pappers…</em></p>\n<blockquote>\n<p> <strong>No validation at entry.</strong> The key is stored as-is; its validity is only tested <strong>when the Worker uses it</strong>. A \"connected\" card can therefore hide an invalid key — test it by asking the Worker to perform an action.</p>\n</blockquote>\n<h3>c) OAuth \"BYOK\" (Bring Your Own Key)</h3>\n<p>The service runs on <strong>your instance</strong> or requires <strong>your own OAuth application</strong>. You additionally provide an <strong>instance URL</strong> and/or a <strong>Client ID + Client Secret</strong>.\n<em>Examples: <strong>Pega</strong> (instance URL + client id/secret), Salesforce, Affinity, DocuSign.</em> → see the dedicated <em>Integrating Pega</em> article.</p>\n<h3>d) Special cases</h3>\n<ul>\n<li><strong>Phone</strong> (Telegram in personal-account mode): number + SMS code.</li>\n<li><strong>No credentials</strong> (Excalidraw, Data.gouv): a simple switch, nothing to connect.</li>\n</ul>\n\n<h2>Connect, enable, disconnect</h2>\n<h3>The toggle (active/inactive)</h3>\n<p>Once connected, each integration has a <strong>toggle</strong>:</p>\n<ul>\n<li><strong>On</strong> → the Worker can use it</li>\n<li><strong>Off</strong> → the connection is <strong>kept</strong> but the Worker no longer uses it (soft disable)</li>\n</ul>\n<h3>The masked key</h3>\n<p>For API keys, only the first and last characters stay visible (e.g. <code>sk_abc123…xyz</code>).</p>\n<h3>Disconnect</h3>\n<p>The trash icon <strong>permanently</strong> deletes the credentials. The card goes back to \"Not authorized\".</p>\n\n<h2>Personal or shared by the team?</h2>\n<ul>\n<li><strong>Personal credentials (default)</strong>: each user connects their own account. Your HubSpot connection is not your colleague's.</li>\n<li><strong>Organization-level credentials</strong>: an admin configures a shared application (Client ID/Secret) that the whole organization reuses. This is what enables team \"BYOK\", sometimes restricted to specific teams.</li>\n</ul>\n<blockquote>\n<p><strong>Who can connect?</strong> Changes go through the Worker's <strong>manager</strong>. Organization credentials are managed in the admin space.</p>\n</blockquote>\n\n<h2>The classic pitfalls</h2>\n<ol class=\"steps\">\n<li><p><strong>\"I can't see the integration.\"</strong>\nSome integrations exist but are <strong>not listed in the catalog</strong> (intentionally hidden or not yet published — this is the case for Telegram, WhatsApp, or brand-new integrations). If an integration is defined but missing from the catalog, it won't appear until the catalog is updated.</p>\n</li>\n<li><p><strong>\"It says connected but it doesn't work.\"</strong>\nFor <strong>API keys</strong>, there's no validation at entry: a wrong key goes unnoticed until first use. Also check that the <strong>toggle is on</strong>.</p>\n</li>\n<li><p><strong>\"OAuth fails (redirect_uri mismatch).\"</strong>\nIn BYOK mode, your OAuth application must declare <strong>exactly</strong> the right redirect URL. A mistyped URL makes the connection fail.</p>\n</li>\n<li><p><strong>\"It asks me for an instance URL.\"</strong>\nMulti-instance services (Salesforce, <strong>Pega</strong>…) need your <strong>instance origin</strong> (e.g. <code>https://acme.pega.com</code>). A typo fails silently.</p>\n</li>\n<li><p><strong>\"Paid plan required.\"</strong>\nSome services restrict API access to their paid tiers (e.g. Apollo). Without a suitable plan, the key will be rejected at use time.</p>\n</li>\n</ol>\n\n<h2>What's next?</h2>\n<p>Once the integration is <strong>active</strong>, you have nothing else to do: when a task requires it, the Worker <strong>activates</strong> the integration on the fly (the <em>discover</em> mechanism) and calls the right tools. → see the <strong>Skills, Behavior Studio &amp; Discover</strong> article.</p>","tags_fr":null,"tags_en":null,"intro_fr":"Une intégration branche ton Worker à un service tiers (Slack, HubSpot, GitHub, Pega…) pour qu'il puisse y lire et y agir.","intro_en":"An integration connects your Worker to a third-party service (Slack, HubSpot, GitHub, Pega…) so it can read and act there.","prerequisites_fr":null,"prerequisites_en":null}