Skip to main content
Integrations are the building blocks of every Atmet workflow. Each integration connects Atmet to an external app or service, giving your AI agents the ability to read data, react to events, and take actions on your behalf — without writing a single line of code. Whether you want to route incoming emails, post Slack messages when a GitHub PR is merged, or update a Notion database when a form is submitted, integrations make it possible.

Available integrations

Atmet supports 18 integrations across communication, productivity, development, and CRM categories. Click any card to view the full setup guide.

Gmail

Send, receive, draft, and organize emails via Google’s mail platform.

Google Calendar

Read and create calendar events, manage schedules and reminders.

Google Sheets

Read and write spreadsheet data for reporting and data pipelines.

Google Drive

Monitor files, upload documents, and organize your Drive folders.

Google Docs

Create, update, and read Google Docs inside automated workflows.

Google Contacts

Sync and manage your Google Contacts from within Atmet.

Slack

Send messages, create channels, and react to channel activity.

Telegram

Send bot messages and trigger workflows from Telegram chats.

GitHub

Automate issue triage, PR reviews, and repository workflows.

Notion

Query databases, create pages, and sync knowledge base content.

HubSpot

Manage CRM contacts, deals, and marketing workflows.

Instagram

Monitor mentions and automate social media content workflows.

Jira

Create and update Jira issues from anywhere in your workflow.

Asana

Manage tasks and projects with automated Asana actions.

Salesforce

Automate CRM updates, lead routing, and opportunity tracking.

Discord

Post messages, manage channels, and respond to Discord events.

X (Twitter)

Post, monitor, and engage with content on X.

ChatGPT / OpenAI

Call OpenAI models directly from your Atmet workflows.

Authentication types

Different services use different authentication standards. Atmet handles the complexity for you, but it helps to know which type applies to each integration before you start.

OAuth 2.0

Used by Google services, Slack, Notion, GitHub, Instagram, Discord, X, HubSpot, Jira, Asana, and Salesforce. You are redirected to the service’s own login page to grant Atmet permission — your credentials are never stored by Atmet.

API Key / Bot Token

Used by Telegram (bot token from @BotFather) and ChatGPT/OpenAI (API key from platform.openai.com). You paste the token directly into Atmet’s connection form.

Connecting an integration

1

Open the Integrations page

In the Atmet sidebar, click Integrations. You’ll see all available integrations and the connection status of each.
2

Select an integration

Click the integration you want to connect. OAuth-based integrations will open a browser authorization flow. API key integrations will show a token input form.
3

Authenticate

  • OAuth integrations: Click Connect and complete the authorization flow in the pop-up window. Grant the requested permissions, then return to Atmet.
  • API key integrations: Paste your API key or bot token into the input field and click Connect.
4

Test the connection

Atmet automatically runs a connection test after you authenticate. A green status badge confirms the connection is live and ready to use in workflows.
You can connect the same integration more than once — for example, two different Gmail accounts or multiple Slack workspaces. Each connection appears as a separate, named entry you can reference individually in your workflows.

Managing connections

Connection status

Each connection displays one of three statuses:

Multiple connections per workspace

Your workspace can hold multiple connections for the same integration. This is useful when different team members work with different accounts, or when you need to separate production and sandbox environments.

Per-member access

Each connection belongs to the member who created it. You choose which connections to expose to specific workflows — Atmet never uses a connection in a workflow you haven’t explicitly authorized.

Workspace-level visibility

Workspace owners and admins can view all connections created by any member of the workspace. This makes it easy to audit active integrations and remove stale credentials.

Frequently asked questions

Yes. Gmail, Google Drive, Google Sheets, Google Docs, Google Calendar, and Google Contacts each use a separate OAuth connection, but you can authorize the same Google account for all of them. Permissions are scoped per service.
If you revoke Atmet’s access in the external service (for example, removing Atmet from your Google account’s authorized apps), the connection status will change to Error the next time Atmet tries to use it. You’ll need to reconnect from the Integrations page.
Atmet processes data in transit to execute your workflow steps but does not persistently store the contents of your emails, files, or messages beyond what your workflow explicitly writes to a destination.
Open the Integrations page, find the connection you want to remove, click the three-dot menu next to it, and select Disconnect. Any workflows that rely on that connection will pause until you reconnect or reassign them to another connection.