Integrations

Integrations

Connect Leapio to the rest of your stack. Install it in your framework or CMS, and connect destinations so signals and action results land where you work.

Integrations connect Leapio to the rest of your stack. Install Leapio in your framework or CMS to start collecting events, and connect a destination so signals and action results reach the tools your team already uses.

Install Leapio

To start collecting events, add Leapio to your site or app.

For the underlying libraries, see the SDKs.

Connect a Destination

Once data is flowing, you can send it onward. A signal or an action result can post to a Slack channel, POST to your own endpoint, flow into a Clay table, or update a company in your CRM. You manage this from the Integrations section in the app, which has a catalog you connect from, the list of what you have connected, and AI & API Access for assistants and API keys.

Who Can Connect

Browse Catalog and Your Integrations are for owners and admins, since connecting a tool changes what leaves your organization. AI & API Access is open to every member; the AI Assistants (MCP) connection is personal to your own account, and managing API keys and OAuth clients stays owner and admin only.

Browse Catalog

The catalog lists every connector, grouped into four categories: Outbound, Notifications, Developer, and CRM. Search by name, or filter to one category. Each card is either Available (click to connect) or Coming Soon (browse-only for now). If the tool you need is not listed, use Request Integration to tell us what to build next.

Connecting

How you connect depends on the tool.

  • Slack and Telegram connect with a single value you paste into the connect dialog:
    • Slack: a Slack Incoming Webhook URL.
    • Telegram: a Chat ID. Message /start to the Leapio bot to get yours.
  • Webhook, Clay, and Discord can each be connected more than once, and each connection has a name that actions pick it by. Click Connect Webhook, Connect Clay, or Connect Discord for the first one, and Add Another Webhook, Add Another Clay Table, or Add Another Discord Channel after that. Give it a Name and paste its URL:
    • Webhook: your endpoint URL, which must be HTTPS. Each webhook gets its own signing secret.
    • Clay: your Clay Monitor Webhook URL (in Clay, + Add → Webhooks → Monitor webhook), one per Clay table. See Clay for the full setup.
    • Discord: a Discord Webhook URL, one per channel.
  • HubSpot, Salesforce, and Attio connect over OAuth. You click Connect, approve access in the CRM, and come back to Leapio. See HubSpot, Salesforce, and Attio for the full setup. Salesforce and Attio are in early access.

Your Integrations

This is the list of what your organization has connected, one card per connection, each with a single status: Connected, Needs Setup (a step is left, with a Set Up Fields button), or Error (the connection lost access, with a Reconnect button). To remove a connection, open the card's ⋮ menu and choose Disconnect. Actions that send to that integration stop delivering until you connect it again.

Webhook, Clay, and Discord cards show the connection's name, and their ⋮ menu has Edit and Remove instead of Disconnect. Edit changes the name or the URL. Clay and Discord URLs are never shown again, so leave that field blank to keep the saved one. Leapio won't remove a connection while an action or an enrichment notification still sends to it. The message names them, so you can change their destination first.

Plans

Slack, Discord, and Telegram require the Essentials plan or higher. Webhook, Clay, HubSpot, Salesforce, and Attio require the Pro plan or higher. Email notifications work on every plan.

AI & API Access

The last part of Integrations connects code and assistants to your data:

In This Section