Connectors
Connect the tools you already use
Connect Notion, Slack, Stripe, Google, your data warehouse and other tools once, share the connection, and use it in your apps and in the chat.
On this page
A connector lets your apps and Ahamo's AI work with a service you already use, such as your Notion workspace or your Slack channels. You connect an account once. That connection can then be used by any of your apps and by Ahamo's AI in the chat.
Availability. Ahamo turns each connector on before anyone can use it, and your organisation decides which connectors its workspaces get. If your company has its own Ahamo organisation, each connector starts off there until your admin turns it on. If a connector isn't listed, it isn't on for your workspace.
Connectors you can use
| Connector | What it does |
|---|---|
| Notion | Read and update pages and databases. |
| Slack | Send messages and read conversations. |
| Discord | Post and read messages in your Discord servers. |
| Linear | Read and create issues and projects. |
| Gmail | Read, send and organise email. |
| Google Calendar | See your schedule and create events. |
| Google Docs | Read, create and update documents. |
| Google Sheets | Read and update spreadsheets. |
| Google Slides | Read, create and update presentations. |
| Google Drive | Pick, read and upload files. |
| Google Analytics | Show visitors, traffic and conversions. |
| Google Search Console | See how your site does in Google Search. |
| Google Maps Platform | Turn addresses into coordinates, and get directions and travel times. |
| Google Cloud API | See your Google Cloud projects, folders and who has access. |
| Gemini | Use Google's Gemini models in your app with your own key. |
| HubSpot | Read and update contacts, companies and deals. |
| Salesforce | Read and update accounts, contacts and deals. |
| Stripe | Work with customers, products and payments in your Stripe account. |
| Canva | Find, export and create designs. |
| Figma | Build screens from your Figma designs and read comments. |
| Supabase | Let Ahamo's AI look at your Supabase project. |
| BigQuery, Snowflake, Databricks, SQL Server, Azure SQL, Microsoft Fabric | Query your data warehouse. See Connect a data warehouse. |
Each card in the store shows who makes the service, for example "by Google", and a Verified by Ahamo mark for connectors Ahamo built and reviewed.
If the tool you need is missing, choose Add › Request a connector and tell Ahamo which one you need.
Find your connections
Open Connectors in the workspace navigation. The page starts with how many of your connections are working.
- Yours lists your connections by connector, whether each one works, and which apps use it.
- Discover lists every connector you can connect. Search or filter by category, then choose + on a card to open its page.
A connection is one account, such as "Acme Notion". It has an owner, a name, the people it is shared with, and a status.
Connect an account
- Open the connector's page and choose Connect.
- Give the connection a name that helps your team pick the right account later.
- Choose who may use it. By default only you can. You can share it with the whole workspace or with chosen people.
- Connect:
- Most connectors open the service's own sign-in window. Sign in there and allow the access it asks for. If your browser blocks the window, the tab goes there and comes back.
- Stripe connects with a key you create in your Stripe account, as described below.
- Snowflake, Databricks, SQL Server, Azure SQL and Microsoft Fabric connect with an account you make for Ahamo. See Connect a data warehouse.
- Wait for Connected to … It works. Ahamo asks the service for something small to make sure the connection works.
Connecting needs permission to connect accounts in the workspace. If you don't have it, ask a workspace admin.
Connect Stripe with a restricted key
Stripe connects with a restricted key that you create in Stripe. A restricted key can do only what you allow.
- On Stripe's page in Connectors, choose Connect. The dialog links to Stripe's keys page and lists the permissions to set.
- In Stripe, create a restricted key. Set the listed permissions to Read or Write as shown, leave out what your app won't use, and set everything else to None. Balance must be Read.
- Paste the whole key and choose Test and connect.
A key that starts with rk_test_ is a Sandbox key, so no real money moves so use it while you build. A key that starts with rk_live_ is a Live key for real payments in your published app. Ahamo refuses publishable keys and webhook signing secrets because they cannot work here. A full secret key is accepted only after you confirm that it can do everything in your Stripe account.
The key goes straight to Ahamo's vault. Nobody can see it again, not even you. To replace it, choose Paste a new key on the connection. Apps keep using the old key until Stripe accepts the new one.
Share, rename, or disconnect
Open the connection on the connector's page:
- Sharing changes who may use it. People it is shared with can add it to their apps and let Ahamo's AI use it. You and workspace admins manage it. Removing someone stops them adding it to apps; apps that already use it keep working.
- Test again checks that the connection still works.
- Sign in again fixes a connection whose sign-in has expired. Apps that use it keep working meanwhile.
- Disconnect stops every app that uses it from reaching the service, and Ahamo asks the service to forget the sign-in. The dialog names the apps that will stop.
The page also shows Linked Apps, each app that uses the connection, in the preview or in the published app, and who linked it.
Sign-ins and keys stay with Ahamo
Sign-ins and keys are kept in Ahamo's vault and are added to each request on its way to the service. They never reach your app's code, the browser, or the chat. Your app's code names the connector, never a key.
Who turns connectors on and off
Connectors are controlled at three levels:
- Ahamo decides which connectors exist and which are available to your organisation.
- Your organisation turns each available connector on or off for its workspaces in Tenant admin › Configuration › Connectors, and can Lock it so that no workspace can turn it off by itself.
- A workspace admin can turn a connector off for one workspace with Use … in this workspace at the bottom of the connector's page, unless the organisation locked it.
When a connector is turned off, its connections can't be added to apps and don't work in previews or new publishes. Apps published before keep their connection until you remove it. The connector's page says who turned it off and who can turn it on again.
Use your organisation's own sign-in app
When people connect an account, the service's sign-in window names the app that asks for access. By default that is Ahamo's. An organisation admin can set up the organisation's own sign-in app for a connector, so the window shows your organisation's name instead:
- Open Tenant admin › Configuration › Connectors and choose Sign-in app on the connector's row.
- Create the app at the service, using the return address and permissions the dialog shows.
- Paste the client ID and secret and save. The secret is never shown again.
Google connectors share one sign-in app. Set up the Google sign-in app once and Gmail, Google Sheets, Google Calendar, and Google Drive all use it. Connections made before keep the app they were made with.
Some connectors, such as Salesforce, can be connected only after your organisation has set up its own sign-in app. The connector's page says so.