Integrations Overview
A91I connects to your tools through MCP (Model Context Protocol) servers. Each integration provides a set of tools — individual operations you can use as workflow nodes.
How Integrations Work
Under the hood, every integration is an MCP server — a lightweight process that exposes a set of tools to the workflow engine. When you drag an action node onto the canvas, you are selecting a tool from one of these servers.
The MCP layer handles:
- Credential management — encrypted storage, automatic token refresh, and connection health monitoring.
- Rate limiting — per-provider limits to prevent API throttling.
- Retry logic — automatic retry with exponential backoff for transient failures.
- Error standardization — consistent error formats regardless of the underlying API.
- Circuit breaking — if a service is down, the circuit breaker stops sending requests and recovers automatically when the service returns.
Integration Categories
- Send, read, and manage emails across Gmail, Outlook, and SendGrid. Handle both personal email workflows and transactional email at scale.
- Chat & Messaging
- Post messages, manage channels, and handle notifications in Slack and Microsoft Teams. Real-time communication integrated directly into your automations.
- Meetings
- Create, schedule, and manage meetings across Webex, Microsoft Teams, Google Meet, and Zoom. Access recordings and transcripts.
- Social Media
- Manage posts, comments, stories, and engagement on Facebook Pages, Instagram, WhatsApp, and X (Twitter).
- Storage
- Upload, download, organize, and share files on Google Drive and Microsoft OneDrive.
- Documents
- Create, read, and edit spreadsheets and documents in Google Sheets, Google Docs, Microsoft Excel, and Microsoft Word.
- Dev & Project Management
- Manage repositories, issues, pull requests, sprints, and projects in GitHub, Jira, Linear, Notion, Sentry, and Salesforce.
- Business
- Handle payments, CRM, SMS, databases, and more with Stripe, HubSpot, Twilio, Airtable, Discord, PostgreSQL, and Brave Search.
- Utilities
- Browser automation with Puppeteer, document parsing for PDFs, and web search with Brave Search.
Authentication
Most integrations use OAuth 2.0. You authenticate once through a redirect flow, and A91I stores the encrypted credentials. Tokens are refreshed automatically before they expire — you never have to re-authenticate unless you revoke access.
Some integrations use API keys instead of OAuth (e.g., SendGrid, Stripe). These are entered directly in the connection setup dialog and stored with the same encryption.
Credential security
Custom Integrations
For services without a built-in integration, you have two options:
- HTTP Request node — call any REST API directly using the HTTP Request node. Configure the URL, method, headers, and body manually.
- Custom MCP server — for Enterprise customers, A91I can build custom MCP servers tailored to your internal APIs and business processes. Contact your account manager to discuss requirements.