Integrations
Connect to your stack.
Configure CRM, MCP, optional browser and LSP services, notifications, search backends, and export formats for self-hosted autonomous work.
Integration Categories
Connectors for one worker runtime
Choose the connectors your deployment needs. Configure credentials and endpoints; workers discover available tools while governance controls side effects.
Configured amoCRM (API v4), Bitrix24 (REST API), and HubSpot (CRM v3) connectors let workers sync contacts and findings. Deduplication by crm_id and retry behavior depend on the connector configuration.
stdio and HTTP transports support dynamic tool discovery and reconnect handling. Configured external tools become available to workers subject to policy; define them with the supported `name`, `transport`, `command`, `args`, and `url` fields.
mcp-serve exposes the runtime's available tools over Model Context Protocol and executes real tool calls. Optional browser tools appear when a CDP endpoint is reachable, and computer tools appear when COMPUTER_URL is configured; MCP clients can drive the toolbox permitted by policy.
When an operator supplies a reachable Chrome DevTools Protocol endpoint, workers can use navigate, screenshot, click, type, and extract against that browser, including JS-heavy pages and authenticated sessions.
Configured webhook (JSON POST), email (SMTP via lettre), or Telegram Bot API channels can receive run events. Fan-out and per-channel error isolation are runtime behaviors to verify in your deployment.
With a configured language-server command, workers can use document_symbols, goto_definition, find_references, hover, and workspace_symbols through LSP. Installation and supported languages remain operator-managed.
Configured search backends can include Linkup, Parallel.ai, Exa, Tavily, Serper, Brave, or DuckDuckGo. Select a default in config or per query where supported; custom implementations can use the SearchBackend trait.
Workers can export structured results as CSV (RFC 4180), vCard 3.0, JSON, XLSX, PDF, HTML, or DOCX where the corresponding exporter is enabled — contacts, findings, and reports included.
Configuration
Configure the runtime you operate
The self-hosted runtime reads integration settings from ~/.fathom/config.toml where supported. Define CRM credentials, MCP servers, notification channels, and search defaults; some services also require their own endpoint or process.
# ~/.fathom/config.toml
[crm]
provider = "hubspot" # hubspot | amocrm | bitrix24
domain = "mycompany.hubspot.com"
api_key = "pat-xxx"
[[mcp.servers]]
name = "postgres"
transport = "stdio"
command = "npx"
args = ["-y", "@modelcontextprotocol/server-postgres"]
[[mcp.servers]]
name = "internal-api"
transport = "http"
url = "https://mcp.internal.corp"
# HTTP transport uses the configured URL
[notifications]
webhook_url = "https://hooks.slack.com/..."
telegram_bot_token = "..."
email_smtp = "smtp://mail.corp:587"
[search]
default_backend = "tavily"
tavily_api_key = "..."Connect deliberately, then run
Configure only the credentials and services your workers need, start the runtime, and let governed tool calls sync contacts, notify channels, or export results under your operator policy.