> For the complete documentation index, see [llms.txt](https://doc.aissist.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.aissist.io/capabilities/connectors.md). # Connectors Connectors link Aissist to your help desk, store, database and other systems once per project, for every workspace to use. *Last updated: October 25, 2026* A connector is a connection to one of your systems: a help desk, a store, a database, an API. You set it up once per project, and every workspace, action and gateway in that project can use it. This page explains what connectors are, which systems you can connect, and how they sign in. ### Connect once, use everywhere Connectors live under **Build → Connectors**, at the project level ("shared by every workspace in this project"). One help desk connector can serve: * a [gateway](/capabilities/gateways.md) that answers tickets * an [action](/capabilities/actions.md) that creates a ticket (Zendesk, Intercom or Freshdesk) * the help desk history that [Onboarding Analysis](/tutorial/onboarding-analysis.md) reads Because everything shares the connection, you sign in, test and fix it in one place. Each connector shows its state: **Connected**, **Needs sign-in**, **Not tested**, **Failing**, **Re-authorize** or **Disabled**. A connector that something uses cannot be deleted until you remove or move what uses it. ### What you can connect **Help desks**: Zendesk (with Messaging on the same connector), Intercom, HubSpot, Salesforce, Front, Kustomer, Gorgias, Freshdesk, Freshchat, Chatwoot, eDesk and WATI (WhatsApp team inbox). **E-commerce and shipping**: Shopify, WooCommerce, Adobe Commerce (Magento), ShipStation and ParcelPanel (CWILL Tracking). **Databases**: PostgreSQL (also Amazon RDS, Aurora, Supabase, Neon), MySQL or MariaDB, Snowflake, Google BigQuery and Databricks SQL, all with read-only queries. Supabase is also available through its project's REST API. **Knowledge bases**: Google Drive, Microsoft OneDrive (and SharePoint document libraries) and Notion. **Messaging**: Slack (the Aissist Slack app, installed with **Add to Slack**, for alerts and reports; see [Weekly Reports and Alerts](/capabilities/weekly-reports.md)), Slack gateway (your own Slack app's bot token, for the AI agent to answer in Slack), Microsoft Teams and Twilio (SMS and WhatsApp). **APIs**: any REST API, any GraphQL API, and AWS Lambda functions in your own account. ### How connectors sign in Most well-known systems use a sign-in (OAuth): you click **Sign in with Zendesk**, **Sign in with Shopify**, **Sign in with Google** and so on, and approve access on the vendor's own page. No key is copied. This is how Zendesk, Intercom, HubSpot, Salesforce, Front, Kustomer, Gorgias, Google Drive, OneDrive, Teams, Notion and Slack (**Add to Slack**) connect, and it is one option for Shopify and BigQuery. Others use a key or token that you create in the vendor's admin and paste in: Freshdesk and Freshchat (API key), Chatwoot (user access token), WATI and eDesk (API token), WooCommerce (REST API key), Adobe Commerce (integration access token), ShipStation and ParcelPanel (API key), Twilio (account SID and auth token), Slack gateway (bot token), the databases (username and password, an access token or a key), and AWS Lambda (access key). A REST or GraphQL connector lets you choose: no authentication, an API key in a header or query parameter, a bearer token, username and password, OAuth 2.0 client credentials, or OAuth 2.0 sign-in. Keys and tokens are write-only: once saved, they show only masked, and you can replace them. {% hint style="info" %} Some sign-ins expire after a period of inactivity, or when an admin revokes access. The connector then shows **Re-authorize**. Sign in again on the connector's page and everything that uses it works again. {% endhint %} ### Actions and assets only use a connector Actions and assets never change a connector. They do not sign it in, test it, refresh it or change its state. Only the connector's own page (and a gateway's setup) does that. So nothing an action or asset does can disturb the connection the rest of the project relies on, and when a connection needs attention you fix it once, on **Connectors**, not in every action. ### With Ask Engine You set up the connector itself on **Connectors**. Once it is connected, Ask Engine builds on it: ``` Cancel an order that has not shipped yet, after the customer confirms the order number ``` ``` Create a Zendesk ticket of type Refund, with the order number, when a customer asks for a refund ``` On **Add Action**, Ask Engine lists the project's connectors and their ready-made actions, picks the right one and proposes the action. If no connector can do what you asked, add one on **Connectors** first. ### Best practice * **Connect your help desk first.** It powers the gateway, ticket creation and onboarding analysis. * **Use a dedicated admin or service account** to sign in, so access does not end when one person leaves. * **Give databases a read-only user** limited to the tables the AI needs. * **Check the state column** after changes on the vendor side, and sign in again when it shows **Re-authorize**. ### Related * [Actions](/capabilities/actions.md) * [Gateways](/capabilities/gateways.md) * [Add Actions](/tutorial/add-actions.md)