Connector Catalog
Connect AI agents with external tools like Airtable, Notion, Slack, and GitHub to search data and execute workflows from your conversation
Connect AI agents with external tools and work with data, content, and workflows directly from your conversation.
Key Benefits and Use Cases
With the Connector Catalog, you can connect AI agents with external tools. Depending on the connector, the agent can search and analyze data, read and edit content, or execute actions.
Which actions are available depends on your connected account, your permissions, and the tools enabled by the provider.
Currently, 29 connector presets are available:
-
Data and Content: Airtable, Box, Contentful, Dropbox Dash, Google Workspace, Notion, WordPress.com
-
Development and Infrastructure: Cloudflare, GitHub, LaunchDarkly, Sentry, Supabase
-
Sales, Marketing and CRM: HubSpot, Kickscale, Moco, PostHog, Typeform
-
Communication and Collaboration: Atlassian Rovo, Calendly, Intercom, Microsoft 365, Miro, Slack, Zoom
-
Analytics and Other Tools: Apify, Bitly, Metabase, Mobbin
Figma, Pitch, and Canva are not yet available in awork. The respective integrations are currently in progress.
How to Use the Connector Catalog
A connector can share data with an external tool. Where supported, an agent can also create or modify data there. The available actions correspond to the permissions you grant to your connected account.
Connect a Connector
-
Open the Library
- via Settings (gear icon in the bottom left of the main menu) > Library
- or open the AI section in the left main menu and click the Library button in the top right
-
Select Connectors in the left navigation to go to the overview of available connections.
-
Next, click the + Connector button in the upper area to add a new connector.
-
Select a Connector from the Catalog
The Set Up Connector modal opens with a catalog of available integrations. You can use the search field to find a specific connector, or scroll directly through the tiles. Select your desired connector by clicking on the corresponding tile. -
Fill in the specified connector settings
-
Add a connection
-
Sign in to the respective provider and confirm access
You've now selected a connector from the catalog and can proceed with further setup of the connection.
Important: Adding a connector does not yet connect your account. Access is only established by the additional connection with sign-in and approval.
Most connectors only require a sign-in. You'll find additional settings in the individual connectors.
Permissions and Access
Which actions a connector can perform depends not only on the connector itself. What matters is the permissions of your connected account, the access you grant during authorization, and any settings from your organization or administrator.
Important: Before connecting, check which permissions the respective connector requires and which actions are possible with it.
Preconfigured Connectors
Airtable
With Airtable, an agent can search and analyze your base data, create and update records, and work with bases, interfaces, and automation drafts. Existing Airtable permissions remain in place. Users with read-only access cannot make changes.
Permissions: The connector can read and modify records, comments, and base structure in the bases you authorize.
Prerequisites: Airtable account, data in bases, and permission for third-party integrations in your Airtable organization. An organization administrator may need to allowlist the integration.
Apify
With Apify, an agent can find and run Actors. These are ready-made tools in the Apify Store that collect and process web data. The agent can also retrieve results and search the Apify documentation.
Permissions: The connector gets access to your Apify account to run Actors and read or manage their data and results within your account permissions.
Prerequisites: Apify account and authorization for the hosted connection.
Atlassian Rovo
Atlassian Rovo brings information from Jira, Confluence, Compass, and Teamwork Graph into your conversation with an agent. You can search for work items, summarize pages, and create content with your existing Atlassian permissions.
Permissions: The connector can read and modify Jira work items, Confluence content, and supported Compass and Teamwork Graph data within your account permissions.
Prerequisites: Atlassian Cloud account with access to the relevant Jira, Confluence, or Compass apps. For OAuth, your organization must allow the AI tool's domain. Organization-wide IP allowlists and authentication policies can also block calls. API token authentication is an advanced option that depends on an organization setting.
Bitly
With Bitly, you can manage link workflows through naturally phrased requests in the agent. Access depends on your Bitly account.
Permissions: Access is set during authorization and can include managing your links. The permissions shown during authorization determine what the connector can do.
Prerequisites: Bitly account and authorization for the hosted connection.
Box
With Box, an agent can search for and work with files and folders. The connector also provides access to Box AI tools. Access remains limited by your existing Box permissions.
Permissions: Access depends on the permissions configured for the Box integration and your access to files and folders. The permissions shown during authorization determine what the connector can read or modify.
Prerequisites: A Box administrator must enable MCP in the Box Admin Console. For custom clients, additional Box Integration Credentials are required, including OAuth Client ID, Client Secret, Redirect URI, and appropriate scopes like Content Actions. All calls remain subject to Box permissions.
Calendly
With Calendly, an agent can find availability, book or cancel meetings, and create scheduling links. It can also list your event types. Actions depend on your Calendly account permissions.
Permissions: The connector can read scheduling information and perform actions like booking and canceling meetings.
Prerequisites: Active Calendly account. Authorization occurs via the hosted connection. Pre-registered client secrets or personal access tokens are not supported.
Canva
Canva is not yet available in awork. Canva currently restricts its MCP server to certain clients. Integration with awork is in progress.
Cloudflare
With Cloudflare, an agent can work with DNS, Workers, R2, and Zero Trust, among other things. It can read account settings, suggest changes, and apply changes within the permissions granted.
Permissions: The Cloudflare account permissions selected during authorization determine which services the connector can read or modify.
Prerequisites: OAuth login to Cloudflare with the permissions selected during authorization. For CI/CD or automation, a Cloudflare API Token with the required permissions can be passed as a bearer token. User and account tokens are supported.
Contentful
With Contentful, an agent can read and edit content, manage content models and assets, and work with spaces and environments. Available actions depend on your Contentful permissions and the tools enabled for spaces and environments.
Permissions: The connector follows your Contentful permissions and the tools your administrator has enabled for the respective spaces and environments.
Prerequisites: Contentful account with access to the desired spaces and environments. Additionally, the Contentful MCP App must be installed and configured in each environment for remote use. For data residency, choose the appropriate global or EU endpoint. A local server needs a Content Management API Personal Access Token instead. Space and environment defaults are optional.
Dropbox Dash
With Dropbox Dash, an agent can search your connected enterprise sources and read documents and files. Available search functions are read-only.
Permissions: The connector requests access to your identity and read and write access to Dash content. The documented tools currently focus on finding and reading information.
Prerequisites: Dropbox Dash account with connected sources. Dropbox requires authorization for the hosted connection.
Figma
Figma is not yet available in awork. Figma currently restricts its MCP server to certain clients. Integration with awork is in progress.
GitHub
With GitHub, an agent can work with repositories, issues, pull requests, and discussions. Depending on your account and available tools, it also supports development workflows, automated checks, and code security.
Permissions: The connector requests permissions to read and modify repositories and projects, download or publish packages, work with gists, and manage notifications. Actual access is limited by your account permissions and the permissions of the installed GitHub App.
Prerequisites: GitHub account and authorization for the hosted endpoint. The upstream documentation lists no additional client ID, tenant, or token fields in the catalog. Access and available actions depend on your logged-in GitHub account and the selected toolset or read-only URL.
Google Workspace
With Google Workspace, an agent can work with Gmail, Calendar, Drive, Docs, Sheets, and Slides. Depending on enabled tools, it can manage emails and appointments, create documents and spreadsheets, and create presentations.
Permissions: The connector requests permissions to send emails, manage calendars, and read or modify documents, spreadsheets, and presentations. It also requests basic profile and email address information.
Important: The connector does NOT request permission to read your Gmail inbox. Access to Google Drive is currently limited to files created by an awork AI Agent. Other Google Drive files are not accessible.
HubSpot
With HubSpot, an agent can query CRM records, sales activities, marketing content, campaigns, conversations, and account information. It can create or update selected CRM records and activities, publish landing pages and blog posts, manage campaigns, and prepare marketing email drafts. Available actions depend on your HubSpot permissions.
Permissions: The connector's permissions depend on your HubSpot user permissions, your account subscription, and the access you grant during authorization.
Prerequisites: An MCP Auth App must be set up in your HubSpot account. Authorization occurs via the hosted connection. Available scopes result from the permissions of the logged-in user and the account's subscriptions.
Intercom
With Intercom, an agent can search for and retrieve workspace data like conversations and contacts. The documented tools also support Intercom actions like creating help center articles. Access depends on the authenticated user.
Permissions: The connector needs access to contacts, companies, and conversations. The documented permissions also enable internal conversation notes and creating or updating help center articles.
Prerequisites: According to Intercom, the hosted MCP server currently only supports US-hosted workspaces. Each connection is authenticated. No separate provider credentials or additional setup steps were visible on the available first-party page.
Kickscale
With Kickscale, an agent connects to Sales Insights. This lets you bring conversation and deal context into your workflows. Kickscale combines CRM, meeting, email, and calendar data in its advanced integrations to analyze customer conversations, coaching signals, and deal progress.
Permissions: Access is set during authorization of the Kickscale connection. You can see which information and actions are available during authorization.
Prerequisites: The linked page confirms an MCP server but does not document authentication, account requirements, or setup steps.
LaunchDarkly
With LaunchDarkly, an agent can manage feature flags and targeting rules in natural language. It can also manage AgentControl configurations and query observability data like logs, traces, errors, metrics, and dashboards.
Permissions: The connector requests read and write access and access to observability data. Which actions are possible depends on your LaunchDarkly permissions.
Important: The hosted MCP server must be enabled in LaunchDarkly before use. The hosted server is not available in Federal and European Union environments. The local server must be used there.
Metabase
With Metabase, an agent can access governed business data, create and run queries, and return results as text or inline bar, line, or table charts. It can also provide database metadata so an agent can prepare Metabase questions and dashboards with real tables and fields.
Permissions: Depending on your Metabase configuration, the connector can access available business data, run queries, and create or modify saved questions, metrics, dashboards, and collections. Your Metabase permissions and administrator settings determine which actions are actually available.
Prerequisites: A Metabase administrator must first enable AI features and then the MCP server under Admin > AI > MCP. Per connection, the permissions of the logged-in Metabase user apply.
Required Configuration: Subdomain – the part before .metabaseapp.com in your account address. For example.metabaseapp.com, enter example. Letters, numbers, and hyphens are allowed with a maximum of 63 characters. The value must begin and end with a letter or number. Enter only the subdomain, without https://, periods, or paths. Then sign in and confirm access.
Microsoft 365
With Microsoft 365, an agent can work with Outlook emails and calendars, OneDrive files, Excel workbooks, OneNote, To Do, Planner, contacts, and Microsoft Search. Depending on enabled tools and account access, it also supports Teams, SharePoint, meeting transcripts and recordings, and shared mailboxes and calendars.
Permissions: The connector requests access to read and modify emails, calendars, contacts, and files, send messages, and read SharePoint content. Depending on your account permissions, Teams permissions can also include creating or deleting channels and changing team membership.
Prerequisites: The linked upstream server requires Microsoft authentication and requests appropriate Microsoft Graph permissions depending on enabled tools. The standard app supports interactive authentication. For your own production deployment, you can use an Azure Entra app registration with Tenant ID, Client ID, optional Client Secret for public apps, and appropriate redirect URIs instead.
Miro
With Miro, an agent can search and summarize boards, build boards, create diagrams, and work with comments. Frames, sticky notes, shapes, text, cards, documents, tables, and images from public URLs are supported.
Permissions: The connector can read and modify accessible boards and their content. It can also access your identity and email address.
Prerequisites: During authorization, you select a Miro team. The connector can only access boards shared according to the user's current permissions. The server is available on all Miro plans. In an enterprise environment, an administrator may need to enable it for the organization or selected teams.
Moco
With Moco, an agent can query company data on leads, quotes, projects, scheduling, time tracking, invoicing, customers, and business development. With write access enabled, it can also create or update projects, contacts, scheduling entries, time entries, leads, and quotes.
Permissions: The connector can read the data you have access to in Moco. If your administrator enables write access, it can also create or modify supported records.
Prerequisites: An account administrator must enable the AI feature under Settings > Account > AI and select read or read/write access for MCP. Users then authorize with their personal Moco login via an OAuth-capable client. Existing Moco permissions remain in place. Depending on the client, a paid plan or admin rights may be required.
Required Configuration: Subdomain – the part before .mocoapp.com in your account address. For example.mocoapp.com, enter example. Letters, numbers, and hyphens are allowed with a maximum of 63 characters. The value must begin and end with a letter or number. Enter only the subdomain, without https://, periods, or paths. Then sign in and confirm access.
Mobbin
With Mobbin, an agent gets access to a searchable library of real product screens and design patterns. It can find examples of flows like onboarding, checkout, pricing, and permissions, compare solutions from published products, and use these references in product design.
Permissions: The connector requests access to login, profile, and email address, and permission to keep the connection active. Access to the design library is governed by your Mobbin account.
Prerequisites: Mobbin paid plan. Sign in with your Mobbin account and confirm the connection in your browser. According to Mobbin, no API key is required.
Notion
With Notion, an agent can read and update pages and other content you have access to in the selected workspace. It can find workspace knowledge, summarize or organize content, create and update pages, add comments, and upload files within Notion's limits.
Permissions: The connector uses the workspace access you've shared. This can include reading and editing content. Your Notion permissions determine which pages and other content are accessible.
Prerequisites: Notion account with access to the desired workspace. Connection occurs via a browser-based OAuth flow. You select the workspace to connect. Notion currently requires interactive authorization.
Pitch
Pitch is not yet available in awork. Pitch currently restricts its MCP server to certain clients. Integration with awork is in progress.
PostHog
With PostHog, an agent can work with product analytics and development data. This includes analytics and HogQL queries, errors and stack traces, feature flags and experiments, support tickets, and CDP destinations.
Permissions: The connector requests extensive access to analytics, feature flags, experiments, recordings, data sources, and project and organization settings. Many of these permissions enable not only viewing but also modifying data and settings.
Prerequisites: Sign in to the PostHog organization containing the desired project and confirm OAuth access. Some tools using PostHog AI require enabled AI data processing and can incur PostHog AI usage costs.
Sentry
With Sentry, an agent can search for errors, analyze performance, triage issues, read Sentry documentation, and manage projects. This lets you investigate errors and performance problems directly with current Sentry context.
Permissions: The connector requests organization information and permissions to create or modify projects and teams and update issues.
Prerequisites: Sentry account with access to the required organization or desired project. The first connection starts a browser-based OAuth flow.
Slack
With Slack, an agent can search messages, files, people, and channels, and read channel or thread history. It can also send or draft messages, create conversations, add reactions, manage canvases and lists, and upload files. Which actions are possible depends on the scopes granted and workspace permissions.
Permissions: The connector can search and read accessible channels, direct messages, files, and profiles. It can also send messages, manage conversations, edit canvases and lists, and upload files.
Prerequisites: Register a Slack app or use an existing one and set up confidential OAuth with client ID and client secret. For the Slack MCP server, Slack currently only allows apps published in the marketplace and internal apps. Unpublished apps are not supported. Add the scopes for your desired actions and get workspace administrator approval if needed.
Required Configuration: Register an OAuth app with the provider first, then fill in these fields.
| Field | Description |
|---|---|
| OAuth client ID | The identifier issued by Slack for the registered app. It identifies the app, not your user account |
| OAuth client secret | The secret issued for the app. You'll find it in the app settings. It's not your account password |
Supabase
With Supabase, an agent can examine and edit Supabase projects and Postgres databases. Depending on enabled tool groups, it can query or migrate databases, review logs and advisors, generate TypeScript types, deploy edge functions, manage projects and branches, and search Supabase documentation.
Permissions: The connector requests permissions to read and modify projects, databases, edge functions, environments, and storage. Depending on your account permissions, it can also access analytics and project API keys or secrets.
Prerequisites: Supabase account and selection of the organization containing the desired project. The hosted server normally uses browser OAuth with dynamic client registration. For production data, Supabase recommends restricting to the desired project and read-only mode.
Typeform
With Typeform, an agent can create and edit forms including fields, logic, and publishing. It can also manage automations, contacts, and lists, and analyze responses via raw data, aggregates, rankings, and time series.
Permissions: The connector can read and modify forms, responses, contacts, automations, webhooks, and workspaces. It can also access account information and insights.
Prerequisites: Typeform account. The first connection starts an OAuth 2.0 flow. EU-hosted Typeform accounts use different endpoints. Typeform also requires that the redirect domain of a hosted connector be allowlisted before a connection is possible.
Required Configuration: Data region – Select the region your Typeform account uses: Global (api.typeform.com, standard), EU (api.eu.typeform.com), or EU2 (api.typeform.eu). Choose your existing account's region. This setting doesn't move your data. Then sign in and confirm access.
Webflow
With Webflow, an agent can work directly with your Webflow projects. It can create and edit responsive pages, elements, styles, components, variables, assets, CMS collections, and custom code. It can also read site analytics while respecting your existing Webflow role and permissions.
Permissions: The connector uses the site or workspace access you've shared. Which content it can read or modify depends on your Webflow role and the permissions granted during authorization.
Prerequisites: Webflow account with access to at least one site. Sites are authorized via a browser-based OAuth flow. During this, Webflow installs the MCP Bridge App.
WordPress.com
With WordPress.com, an agent can edit your connected websites in natural language. It can use tools for website content and administration. For suitable self-hosted sites, the same connection can also provide Jetpack features like backup, monitor, newsletter, and scan.
Permissions: The connector requests extensive access to accounts and websites, including content, users, comments, media, and stats. Which actions are possible depends on your WordPress permissions and enabled connector tools.
Prerequisites: MCP must be enabled in your WordPress.com account. MCP is available on paid WordPress.com plans, during the first 30 days of a newly created free site, and on self-hosted sites connected via Jetpack with a Jetpack AI or Jetpack Complete plan.
Zoom
With Zoom, an agent can find meeting information and work with cloud recordings, Zoom Docs, and Zoom Hub. Usage depends on your existing permissions and Zoom licenses.
Permissions: The connector can find and read meeting content, recordings, documents, and notes. It also requests permissions to create, modify, or delete meetings, change meeting settings, manage document collaborators, and write Zoom Hub content.
Prerequisites: Zoom account with admin or developer authorization and the required licenses for desired Zoom products. Create a General App in the Zoom App Marketplace, configure the required OAuth scopes, and obtain client ID and client secret. Zoom's remote MCP servers require manual client registration and OAuth with PKCE. Dynamic client registration is not supported.
The connector uses the current unified streamable endpoint https://mcp.zoom.us/mcp/zoom/streamable.
Required Configuration: Register an OAuth app with the provider first, then fill in these fields.
| Field | Description |
|---|---|
| OAuth client ID | The identifier issued by Zoom for the registered app. It identifies the app, not your user account |
| OAuth client secret | The secret issued for the app. You'll find it in the app settings. It's not your account password |
Notes
- A connector doesn't automatically extend your access rights: An agent works within the permissions your connected account and the respective provider allow. This also applies to actions that enable changes to data.
Important: Before connecting, check whether your account and, if applicable, your organization or administrator has enabled and approved the required features. This is an explicit prerequisite for several connectors.
- Apply specific settings correctly: With Metabase and Moco, you must enter the subdomain from your account address. With Typeform, you must select the data region of your existing account. With Slack and Zoom, OAuth client ID and client secret are also required.
Tip: Copy configuration values exactly from the settings of the respective provider. For Metabase and Moco, for example, the subdomain must not contain a URL, periods, or paths.
FAQ
Is it enough to add a connector to the library?
No. After adding it, you must set up a connection, sign in to the respective provider, and confirm access.
Can an AI agent change data with connected tools?
Where the respective connector supports write actions, an agent can create or modify data. Which actions are available depends on your account permissions, the access you grant, and the provider's enabled tools.
Can an AI agent access all my Google Drive files?
No. The Google Workspace connector can currently only retrieve Google Drive files created by an agent. Other Google Drive files are not accessible.
Do available actions depend on my account?
Yes. Available actions depend on your connected account, its permissions, and the tools enabled by the provider.
What do I do if the connection doesn't work?
First, check whether the connector is available in awork, whether the required provider settings are enabled, and whether your account has the needed permissions. For connectors with additional fields, also check the specified configuration values.
What permissions do connectors have?
Required permissions differ by connector. They determine which data the connector can read or modify. Additionally, your account permissions and your organization's or administrator's settings can restrict access.
Can a connector change data?
Yes, many connectors support not only read access but also modifications. Which actions are actually available depends on the respective connector, your account permissions, and the access granted during authorization.
Powered by happysupport.ai