Skip to main content

​
What Are Integrations?

Integrations extend your agents’ capabilities by connecting them to external services and data sources. Think of them as tools that allow your agents to interact with the outside world - reading emails, posting to Slack, managing GitHub repositories, updating CRM records, and more. Celeria supports two types of integrations:
  • Native Integrations - Pre-built, first-class integrations that connect in seconds (most use OAuth authentication)
  • Custom Integrations - Add MCP (Model Context Protocol) servers to extend your agents with custom capabilities
Once connected, you can assign integrations to any agent, giving them access to the tools those integrations provide.

​
Native Integrations

Native integrations are pre-built with one-click OAuth authentication. Connect your account and your agents can immediately start using the available tools.
IntegrationCapabilitiesWebhook Events
SlackList channels, post messages, reply to threads, add reactions, retrieve message history, get user informationapp_mention, message
GitHubCreate and update files, manage branches, create and review pull requests, search code, manage issuespull_request, pull_request_review_comment, issue_comment, issues, push
LinearCreate and manage issues, update workflow states, organize projects and cycles, manage initiatives, add comments, assign team members, set priorities, track issue historyIssue, Comment, Project
HubSpotSearch and list CRM records, get detailed context with associations, create and update contacts/deals/companies/tickets, query schema informationN/A

​
Email Integrations

Email integrations work like native integrations but you can connect multiple email accounts (personal, team inboxes, support emails, etc.) to give different agents access to different inboxes.
ProviderCapabilitiesMultiple Accounts
GmailCheck and search emails with filters (from, subject, body, labels/folders, read status, time range), send emails directly or create drafts for review, reply to existing threads, multi-step email composition workflowsYes - connect as many Gmail accounts as needed
OutlookCheck and search emails with filters (from, subject, body, labels/folders, read status, time range), send emails directly or create drafts for review, reply to existing threads, multi-step email composition workflowsYes - connect as many Outlook accounts as needed

​
Database Integrations

Database integrations allow your agents to connect directly to your databases for querying data and schema exploration. Like email integrations, you can connect multiple database instances to give different agents access to different data sources.
ProviderCapabilities
PostgreSQLExecute SQL queries, list tables and schemas, describe table structures with columns and relationships, explore foreign keys and primary keys
MySQLExecute SQL queries, list tables and schemas, describe table structures with columns and relationships, explore foreign keys and primary keys
Microsoft SQL ServerExecute SQL queries, list tables and schemas, describe table structures with columns and relationships, explore foreign keys and primary keys
SnowflakeExecute SQL queries, list tables and schemas, describe table structures with columns and relationships, explore foreign keys and primary keys

​
Available Tools

Once connected, database integrations provide two core tools to your agents:
  • executeQuery - Execute SQL statements with security validation and automatic result truncation
  • describeSchema - List all tables or get detailed metadata for specific tables including columns, data types, constraints, and relationships

​
Security Features

Database connections include built-in security:
  • SQL validation - Queries are analyzed before execution to prevent unauthorized operations
  • Access modes - Configure read-only or read-write access per connection
  • Table/column allowlists - Restrict which tables and columns agents can access
  • Result limits - Automatic truncation of large result sets (configurable, max 1000 rows)
  • Encrypted credentials - All database credentials are encrypted at rest

​
Connecting a Database

To add a database integration:
  1. Navigate to the Integrations page
  2. Click “New Integration” and select your database provider
  3. Enter connection details:
    • Host - Database server address
    • Port - Database port number
    • Username - Database user
    • Password - Database password (encrypted)
    • Database - Database name
    • Schema (optional) - Default schema to use
  4. Configure security settings (optional):
    • Set access mode (read-only or read-write)
    • Define table and column allowlists
    • Set maximum rows per query
  5. Test the connection
  6. Save and assign to agents

​
Custom Integrations

Custom integrations let you add MCP (Model Context Protocol) servers to extend your agents with custom capabilities. MCP is an open standard that allows AI models to securely interact with external tools and data sources. The Model Context Protocol (MCP) is an open protocol that standardizes how AI models connect to external systems. Instead of building custom integrations for every tool, MCP provides a universal way to expose tools, resources, and prompts to AI agents.

​
Adding a Custom Integration

To add a custom MCP integration:
  1. Navigate to the Integrations page
  2. Click “New Integration”
  3. Provide a name for your integration
  4. Enter the npx command to run your MCP server
  5. (Optional) Add environment variables if your MCP server requires credentials
Important: All custom MCP integrations must use npx-based commands for compatibility with Celeria’s execution environment.

​
Example: Web Fetch (No Credentials Required)

The simplest custom integration requires only a name and server command. Here’s how to add a web scraping integration: Name: Web Fetch Server Command (npx): @celeria-ai/fetch-mcp Available Tool:
  • fetch - Fetch URL content and extract as markdown
That’s it! This integration requires no additional configuration or credentials. Once added, you can assign it to any agent to give them web scraping capabilities. Use Cases:
  • Web content extraction and analysis
  • Documentation fetching
  • News and content monitoring
  • Competitor research

​
Example: Integration with Environment Variables

Some MCP servers require credentials or configuration through environment variables. Here’s how to configure those: Name: My Custom API Server Command (npx): @organization/my-custom-mcp-server Environment Variables: Add key-value pairs for any credentials your MCP server needs:
KeyValue
API_KEYyour-api-key-here
BASE_URLhttps://api.example.com
TIMEOUT30000
Celeria securely encrypts and stores these environment variables. When an agent uses this integration, Celeria provisions the MCP server with these credentials injected as environment variables.

​
Finding MCP Servers

Explore available MCP servers to extend your agents:

​
Building Your Own MCP Server

Want to build a custom MCP server for your specific needs? Check out: Requirements for Celeria Compatibility:
  • Must be executable via npx command
  • Handle credentials through environment variables

​
Removing Integrations

Disconnect a native integration (Slack, GitHub, Linear, HubSpot, Gmail, Outlook) to revoke Celeria’s access:
  1. Navigate to the Integrations page
  2. Find the integration to disconnect
  3. Click “Disconnect”
  4. Confirm the action
Disconnecting removes the integration from all agents and stops all webhook triggers. You can reconnect anytime by going through the OAuth flow again. Delete a custom MCP integration permanently:
  1. Navigate to the Integrations page
  2. Find the integration to delete
  3. Click “Delete”
  4. Confirm the action
Deleting a custom integration removes it completely and cannot be undone. You’ll need to recreate it if needed later.

​
Security and Permissions

OAuth Tokens: All OAuth access and refresh tokens are encrypted at rest using industry-standard encryption. Credential Storage: Custom MCP credentials are encrypted and only decrypted when provisioning servers for agent execution. Scope Management: Each integration requests only the permissions (scopes) necessary for its tools to function. Organization Isolation: Integrations are scoped to your organization. Other organizations cannot access your integration credentials or data. User Audit: Integration connections track which user connected them and when, providing audit trails for compliance.

​
Next Steps

  • Actions - Create reusable prompts for your agents to execute
  • Tasks - Set up autonomous agentic workflows