Integrations
Threada connects to the systems your team already uses. Integrations fall into three categories:
- Channels — sources that produce WorkItems.
- Knowledge sources — systems whose content is indexed for RAG.
- Actions — systems Threada can write to or call as part of a pack workflow.
Most integrations span more than one category — Salesforce can be a knowledge source and an action target, for example.
Marketplace packaging is tracked separately from runtime capability. A connector
can be [live] for tenant-scoped runtime use before it is ready for public app
store review. Slack Marketplace launch scope, copy, and acceptance criteria live
in Slack Marketplace, the public setup and support
guide lives in Slack setup and support, the submission
control sheet lives in Slack Marketplace submission pack,
Zapier setup and support lives in Zapier setup and support,
Zapier public integration scope lives in
Zapier Public Integration,
Microsoft Teams setup and support lives in
Microsoft Teams setup and support,
Microsoft Teams Store scope lives in
Microsoft Teams Store,
Google Workspace setup and support lives in
Google Workspace setup and support,
Google Workspace Marketplace scope lives in
Google Workspace Marketplace,
Atlassian setup and support lives in
Atlassian setup and support,
Atlassian Marketplace scope lives in
Atlassian Marketplace,
Zendesk setup and support lives in
Zendesk setup and support,
Zendesk Marketplace scope lives in
Zendesk Marketplace,
HubSpot setup and support lives in
HubSpot setup and support,
HubSpot App Marketplace scope lives in
HubSpot App Marketplace,
Salesforce setup and support lives in
Salesforce setup and support,
Salesforce AppExchange scope lives in
Salesforce AppExchange,
ServiceNow setup and support lives in
ServiceNow setup and support,
ServiceNow Store scope lives in
ServiceNow Store,
Shopify App Store scope lives in
Shopify App Store,
Freshworks Marketplace for Freshdesk scope lives in
Freshworks Marketplace for Freshdesk,
GitHub Marketplace scope lives in
GitHub Marketplace,
runtime-bound OAuth install architecture for GitHub, Atlassian/Jira, Notion,
Asana, monday.com, Intercom, HubSpot, Salesforce, and Zendesk lives in
Marketplace OAuth installs,
second-wave marketplace setup and support lives in
Marketplace follow-on setup and support,
and the broader marketplace rollout sequence lives in
Integration Store Launch and
Marketplace distribution program.
Status labels
- [live] — executable through the current public API, runtime webhook, or governed action payload.
- [planned] — product direction or packaged connector work that should not be treated as generally available.
- [custom] — available through Custom HTTP, Workato, webhooks, or implementation-specific connector work.
Messaging and channels
| Integration | Status | Channel | Actions |
|---|---|---|---|
| Web intake | [live] | Create WorkItems from web forms and embedded intake via web/public API paths. | N/A |
| Public API | [live] | Create, list, update, and message WorkItems. | Create governed action proposals and read action records; direct side-effecting execution remains MCP/A2A or first-party Work/Studio governed execution. |
| Slack | [live] channel, admin credential install, and governed post-message action; [planned] public Marketplace approval and broader packaged actions | Runtime webhook/channel intake. | Governed channel post action proposals are live for tenant integrations with a Slack bot-token secret and recorded chat:write scope evidence. Authenticated tenant admins can install a Slack bot token through POST /api/v1/integrations/slack/directory-install, which writes the token to Secret Manager and upserts a runtime-bound Slack integration with the slack_post_message allowlist. Slack Marketplace v1 remains command-intake only until the submitted app, scopes, OAuth token storage/revocation, and reviewer smoke evidence support post-message claims. DMs, channel management, history/export, file access, and bulk operations remain planned. |
| Microsoft Teams | [live] runtime app intake, relay channel, and Studio runtime config; [planned] public Teams Store approval | Runtime webhook/channel intake for Bot Framework Teams app messages, message-extension WorkItem creation, and custom relay-style use. | Studio exposes the public setup handoff at https://studio.threada.ai/integrations/teams/install, backed by the teams console-shell runtime integration kind and INTEGRATION_TYPE_MICROSOFT_TEAMS; a private Teams app package scaffold exists at packages/teams-store-app; public Teams setup/support is tracked in Microsoft Teams setup and support, and public Store app scope is tracked in Microsoft Teams Store. |
| Google Chat | [live] tenant-bound Google Chat-to-WorkItem intake and Studio runtime config; [planned] public Google Workspace Marketplace approval | Runtime webhook/channel intake. | The Google Workspace runtime catalog, BFF webhook route, and runtime automation service support Google Chat channel-message intake. Studio exposes the public setup handoff at https://studio.threada.ai/integrations/google-workspace/install, backed by the google_workspace console-shell runtime integration kind and INTEGRATION_TYPE_GOOGLE_WORKSPACE; a private Google Workspace Marketplace configuration scaffold exists at packages/google-workspace-marketplace-app; public Google Workspace setup/support is tracked in Google Workspace setup and support, and public Marketplace scope is tracked in Google Workspace Marketplace. |
| Email (Gmail) | [live] channel and draft action; [planned] Gmail/Workspace add-on | Gmail API intake and reply synchronization. | Governed Gmail draft action proposals are live; direct send, reply, thread actions, and public add-on scope remain planned and are tracked in Google Workspace Marketplace. |
| [planned] | Packaged messaging channel. | Packaged message actions. |
CRM and helpdesk
| Integration | Status | Knowledge | Actions |
|---|---|---|---|
| Jira | [live] governed action payloads and Atlassian/Jira OAuth install binding; [planned] Atlassian Marketplace approval and packaged knowledge sync | Planned packaged knowledge source. | Governed issue create/update action proposals are live; the shared marketplace OAuth install path now supports Atlassian 3LO install, selected Jira Cloud site discovery, tenant-scoped Secret Manager credentials, and a runtime-bound Jira issue-context capability with runtime-enforced jira_create_issue and jira_update_issue action allowlists; Studio exposes the public install handoff at https://studio.threada.ai/integrations/atlassian/install; a private Forge manifest scaffold exists at packages/atlassian-marketplace-app; public Atlassian setup/support is tracked in Atlassian setup and support, and public Marketplace scope is tracked in Atlassian Marketplace; deployed Forge UX, public Marketplace approval, packaged knowledge sync, and broader Jira write claims remain planned. |
| Zendesk | [live] governed action payloads and subdomain-scoped OAuth install path; [planned] Zendesk Marketplace approval and packaged knowledge sync | Planned packaged knowledge source. | Governed ticket create/update action proposals are live; the shared marketplace OAuth install path now supports a Zendesk global-OAuth install for one subdomain, tenant-scoped Secret Manager credentials, and a runtime-bound zendesk_create_ticket action allowlist; a private integration-app package scaffold exists at packages/zendesk-marketplace-app; public Zendesk setup/support is tracked in Zendesk setup and support, and public Marketplace scope is tracked in Zendesk Marketplace; comments, macros, public Marketplace approval, request-header evidence, and packaged app workflows remain planned. |
| HubSpot | [live] governed action payloads and portal-keyed contact OAuth install path; [planned] HubSpot App Marketplace approval and packaged knowledge sync | Planned packaged knowledge source. | Governed contact/deal upsert and ticket-update action proposals are live; the shared marketplace OAuth install path now discovers the authorized HubSpot portal through token introspection, stores tenant-scoped Secret Manager credentials, and binds marketplace installs to a runtime-enforced hubspot_upsert_contact action allowlist; a private OAuth app package scaffold exists at packages/hubspot-marketplace-app; public HubSpot setup/support is tracked in HubSpot setup and support, and public App Marketplace scope is tracked in HubSpot App Marketplace; packaged HubSpot app approval, deal/ticket Marketplace claims, and packaged knowledge workflows remain planned. |
| Salesforce | [live] governed action payloads and contact OAuth install path; [planned] Salesforce AppExchange approval and packaged knowledge sync | Planned packaged knowledge source. | Governed contact and opportunity upsert action proposals are live; the shared marketplace OAuth install path now supports PKCE Salesforce contact installs and stores the authorized org instance URL; a private AppExchange API integration scaffold exists at packages/salesforce-appexchange-app; public Salesforce setup/support is tracked in Salesforce setup and support, and public AppExchange scope is tracked in Salesforce AppExchange; AppExchange approval, opportunity Marketplace claims, and packaged Salesforce app workflows remain planned. |
| ServiceNow | [live] governed action payload; [planned] ServiceNow Store app and broader CRUD | Planned packaged knowledge source. | Governed incident creation action proposals are live; a private ServiceNow Store app scaffold exists at packages/servicenow-store-app; public ServiceNow setup/support is tracked in ServiceNow setup and support, and public Store scope is tracked in ServiceNow Store; request, change, problem, catalog, CMDB, attachment, and packaged knowledge sync remain planned. |
| Freshdesk | [live] governed action payload, admin credential install, Studio runtime config, and signed Freshworks Marketplace callback; [planned] Freshworks approval and packaged knowledge sync | Planned packaged knowledge source. | Governed ticket creation action proposals are live and Freshdesk can be bound to a pack from the Studio connector readiness panel with tenant-scoped endpoint/secret references. Authenticated tenant admins can also install a Freshdesk account API key through POST /api/v1/integrations/freshdesk/directory-install, which writes the credential to Secret Manager and upserts a runtime-bound Freshdesk integration with the freshdesk_create_ticket allowlist. Studio exposes the public setup handoff at https://studio.threada.ai/integrations/freshdesk/install; a private Freshworks Marketplace package exists at packages/freshworks-marketplace-app with generated Freshworks CLI source, packed ZIP, and a signed BFF callback that dispatches tenant-bound FreshdeskCreateTicket actions; submission readiness remains blocked until real Developer Portal values, FDK validation/pack evidence, reviewer-safe install evidence, and Freshworks approval exist; public Freshworks Marketplace for Freshdesk scope is tracked in Freshworks Marketplace for Freshdesk; comments, updates, public Marketplace approval, and packaged knowledge workflows remain planned. |
| Intercom | [live] governed ticket action + workspace-keyed OAuth install path; [planned] App Store listing | Planned packaged knowledge source. | Governed ticket creation action proposals and the shared marketplace OAuth install path are implemented with runtime action allowlisting; OAuth callbacks discover the installed Intercom workspace through /me app.id_code and key the runtime integration and credential to that workspace; the Intercom Developer Hub app must be configured with write_tickets permission; a private Intercom App Store config scaffold exists at packages/intercom-marketplace-app; public follow-on setup/support is tracked in Marketplace follow-on setup and support; no real Developer Hub app, review submission, or App Store approval has been observed. |
Commerce and billing
| Integration | Status | Knowledge | Actions |
|---|---|---|---|
| Stripe | [live] billing webhook and refund action; [planned] broader customer actions | N/A | Billing webhooks and refund action payloads are live; subscription and customer ops are planned. |
| Shopify | [live] governed action payloads; [planned] Shopify App Store app and packaged knowledge sync | Planned packaged knowledge source. | Governed refund and order-update action proposals are live; public Shopify App Store scope is tracked in Shopify App Store; packaged Shopify app workflows remain planned. |
| AWS Marketplace | [live] signed procurement callback boundary and private package artifact; [planned] public SaaS listing | N/A | The aws_marketplace runtime identity is bound to the commercial marketplace procurement path, and the public BFF accepts signed adapter callbacks at /api/v1/commercial-marketplaces/aws/procurement before recording adapter-supplied buyer, entitlement, product, plan, active/suspended/canceled state, subscription metadata, and billing audit events through BillingService. The private package at packages/aws-marketplace-app now emits AWS technical configuration, listing metadata, required asset checklist, readiness output, and reviewer smoke test from the shared commercial marketplace package kit. Public setup/support is tracked in Commercial Marketplaces and Marketplace follow-on setup and support; seller registration, SaaS listing approval, provider fulfillment-adapter verification/mapping evidence, reviewer smoke evidence, and approval evidence are still missing. |
| Microsoft Commercial Marketplace | [live] signed procurement callback boundary and private package artifact; [planned] public SaaS offer | N/A | The microsoft_marketplace runtime identity is bound to the commercial marketplace procurement path, and the public BFF accepts signed adapter callbacks at /api/v1/commercial-marketplaces/microsoft/procurement before recording adapter-supplied buyer, entitlement, product, plan, active/suspended/canceled state, subscription metadata, and billing audit events through BillingService. The private package at packages/microsoft-commercial-marketplace-app now emits Partner Center offer configuration metadata, listing metadata, required asset checklist, readiness output, and reviewer smoke test from the shared commercial marketplace package kit. Public setup/support is tracked in Commercial Marketplaces and Marketplace follow-on setup and support; Partner Center offer approval, provider fulfillment-adapter verification/mapping evidence, certification, reviewer smoke evidence, and approval evidence are still missing. |
| Google Cloud Marketplace | [live] signed procurement callback boundary and private package artifact; [planned] public SaaS listing | N/A | The google_cloud_marketplace runtime identity is bound to the commercial marketplace procurement path, and the public BFF accepts signed adapter callbacks at /api/v1/commercial-marketplaces/google_cloud/procurement before recording adapter-supplied buyer, entitlement, product, plan, active/suspended/canceled state, subscription metadata, and billing audit events through BillingService. The private package at packages/google-cloud-marketplace-app now emits Google Cloud Marketplace configuration metadata, listing metadata, required asset checklist, readiness output, and reviewer smoke test from the shared commercial marketplace package kit. Public setup/support is tracked in Commercial Marketplaces and Marketplace follow-on setup and support; partner listing approval, provider fulfillment-adapter verification/mapping evidence, entitlement smoke evidence, reviewer smoke evidence, and approval evidence are still missing. |
| Oracle Cloud Marketplace | [live] signed acquisition callback boundary and private package artifact; [planned] public listing | N/A | The oracle_cloud_marketplace runtime identity is bound to the commercial marketplace procurement path, and the public BFF accepts signed adapter callbacks at /api/v1/commercial-marketplaces/oracle/procurement before recording adapter-supplied buyer, entitlement, product, plan, active/suspended/canceled state, subscription metadata, and billing audit events through BillingService. The private package at packages/oracle-cloud-marketplace-app now emits Oracle listing configuration metadata, listing metadata, required asset checklist, readiness output, and reviewer smoke test from the shared commercial marketplace package kit. Public setup/support is tracked in Commercial Marketplaces and Marketplace follow-on setup and support; partner portal approval, listing approval, provider fulfillment-adapter verification/mapping evidence, customer handoff/acquisition evidence, reviewer smoke evidence, and approval evidence are still missing. |
Operations
| Integration | Status | Purpose |
|---|---|---|
| PagerDuty | [live] action, admin credential install, and Studio runtime config; [packaged] private directory artifact; [planned] public directory listing | Trigger incident action payloads can be bound to a pack from the Studio connector readiness panel with tenant-scoped endpoint/secret references. Authenticated tenant admins can also install a PagerDuty Events API routing key through POST /api/v1/integrations/pagerduty/directory-install, which writes the credential to Secret Manager and upserts a runtime-bound PagerDuty integration with the pagerduty_trigger_incident allowlist. The private package at packages/pagerduty-integrations-directory-app now emits listing metadata, the setup install URL, runtime binding, data-sharing disclosure, required assets, readiness output, and reviewer smoke test. Public follow-on setup/support is tracked in Marketplace follow-on setup and support; partner submission, service guide approval, reviewer smoke evidence, and listing approval evidence are missing. |
| Datadog | [live] event action and admin credential install; [packaged] private Marketplace artifact; [planned] public listing | Post-event action proposals are live through runtime integration config. Authenticated tenant admins can install a Datadog API key through POST /api/v1/integrations/datadog/directory-install, which writes the credential to Secret Manager and upserts a runtime-bound Datadog integration with the datadog_post_event allowlist. The private package at packages/datadog-marketplace-app now emits listing metadata, the setup install URL, runtime binding, data-sharing disclosure, required assets, readiness output, and reviewer smoke test. Public follow-on setup/support is tracked in Marketplace follow-on setup and support; partner approval, Marketplace offer, reviewer smoke evidence, and approval evidence are missing. |
| Google Meet | [live] action | Create call/link action payloads; summary workflows are planned. |
| Okta | [live] action, admin credential install, and Studio runtime config; [blocked] identity-provider marketplace publication | Upsert-user action payloads can be bound to a pack from the Studio connector readiness panel with tenant-scoped endpoint/secret references. Authenticated tenant admins can install an Okta-managed org API token through POST /api/v1/integrations/okta/directory-install, which writes the credential to Secret Manager and upserts a runtime-bound Okta integration with the okta_upsert_user allowlist. Studio exposes the setup handoff at https://studio.threada.ai/integrations/okta/install. Tenant SSO is IdP-initiated SAML configured in Admin; no OIN sign-in submission, diagnostics pass, or approval evidence has been observed. See Marketplace follow-on setup and support. |
| Custom HTTP | [live] | Authenticated outbound calls to approved HTTPS endpoints. |
| Zapier / Workato | [live] Workato webhook; [live] Zapier app scaffold and Studio runtime config; [planned] public Zapier app | Bridge to additional apps via Workato webhook or custom HTTP/webhook workflows. Workato webhook recipes must return a JSON response with a nonblank id, key, reference, request_id, requestId, or configured external_reference_pointer value before runtime marks the action succeeded. A private action-only Zapier Platform scaffold exists at packages/zapier-platform-app, and Studio exposes the public setup handoff at https://studio.threada.ai/integrations/zapier/install; public Zapier setup/support is tracked in Zapier setup and support, and public app scope is tracked in Zapier Public Integration. |
| Discord | [live] webhook intake, admin credential install, and Studio runtime config; [packaged] private App Directory artifact; [planned] public listing | Runtime Discord webhook intake and signature verification exist, and Discord integration records can be bound to a pack from the Studio connector readiness panel with tenant-scoped secret references. Authenticated tenant admins can also install Discord app credentials through POST /api/v1/integrations/discord/directory-install, which writes public_key and bot_token to Secret Manager and upserts a runtime-bound Discord integration with the signed webhook intake and bot reply capability set. The private package at packages/discord-app-directory-app now emits listing metadata, the setup install URL, runtime binding, data-sharing disclosure, required assets, readiness output, and reviewer smoke test. Public follow-on setup/support is tracked in Marketplace follow-on setup and support; Developer Portal app binding, install mapping, discovery profile, reviewer smoke evidence, and approval evidence are missing. |
Productivity marketplace follow-ons
| Integration | Status | Purpose |
|---|---|---|
| GitHub Marketplace | [live] governed issue action + OAuth install path; [planned] GitHub App and Marketplace listing | Runtime issue creation and a shared OAuth install path are implemented. The public GitHub Marketplace listing still needs the provider-correct GitHub App posture, webhook smoke evidence, review submission, and approval; public GitHub Marketplace scope is tracked in GitHub Marketplace. |
| Notion Marketplace | [live] governed page action + workspace-keyed OAuth install path; [packaged] private Marketplace artifact; [planned] public connection listing | Runtime page creation, the shared OAuth install path, and a private Notion Marketplace launch-control package at packages/notion-marketplace-app are implemented. OAuth installs are keyed by Notion workspace_id; runtime execution still requires a configured Notion database mapping and rejects mismatched database payloads. Public connection listing, reviewer-safe workspace/database evidence, and approval remain planned and are tracked in Marketplace follow-on setup and support. |
| Asana App Directory | [live] governed task action + workspace-keyed OAuth install path; [packaged] private App Directory artifact; [planned] public app listing | Runtime task creation, the shared OAuth install path, and a private App Directory launch-control package at packages/asana-app-directory-app are implemented. OAuth installs are keyed by the selected authorized Asana workspace GID; runtime execution rejects mismatched workspace/project payloads. Public app listing, reviewer workspace/project evidence, and approval remain planned and are tracked in Marketplace follow-on setup and support. |
| monday.com Marketplace | [live] governed item action + board-keyed OAuth install path; [packaged] private Marketplace artifact; [planned] public app listing | Runtime item creation, the shared OAuth install path, and a private monday.com Marketplace launch-control package at packages/monday-marketplace-app are implemented. OAuth install now requires a selected monday board mapping, verifies the selected board/group through monday.com before storing credentials, and upserts a board-keyed runtime integration; runtime execution rejects mismatched mapped board/group payloads. Public app listing, share link, reviewer board evidence, and approval remain planned and are tracked in Marketplace follow-on setup and support. |
CMS
| Integration | Status | Knowledge |
|---|---|---|
| Generic CMS | [custom] | Crawl and index editorial content through a configured source profile or custom adapter. |
How integrations work
- Every integration is tenant-scoped. Credentials live in your tenant’s Secret Manager namespace, never shared across tenants.
- Knowledge sources respect a per-tenant allowed-domain allowlist to prevent unauthorized fetches.
- Outbound calls go through the same audit pipeline as any other governed action: a pack’s policy controls whether the call needs human approval before execution.
- Webhook deliveries are signed and verified; failed attempts are retried and exposed via the webhook replay surface in Studio.
Setting up an integration
In Studio → Integrations:
- Choose a live or custom system you want to connect.
- Authorize Threada (OAuth where available, API key otherwise).
- Configure scopes — what Threada can read and write.
- Optionally attach the integration to a pack as a knowledge source, channel, or action target.
Planned rows are roadmap labels, not setup instructions. Treat them as available only after your workspace has an explicit implementation or release note for that connector.
See the getting started guide for the broader onboarding flow.