How integrations work

Integrations bring leads in from tools outside your website and send new leads on to the tools your team watches. A call from your phone provider, a form from a form builder or a Zap, a chat from your widget and a request or quote from Jobber all arrive as leads; Slack or your own endpoint can be told about each one. Everything is managed from Settings, Integrations, and any member of your company can connect or disconnect a card.

The categories

• Agencies: Connect the agency that manages your marketing.
• Phone Tracking: Track and record calls from your campaigns.
• Live Chat: Capture chat conversations as attributed leads.
• Website Forms: Receive form submissions as leads automatically.
• CRM: Send your leads to the CRM your team already uses.
• Automation: Bridge any tool via Zapier or outbound webhook.
• SEO: Bring organic search data into your analytics.
• Ad Platforms: Import ad spend for cost per lead and ROAS.

Available today: Resend, Gravity Forms, Jotform, Zapier, Outbound Webhook, Jobber, Google Search Console, Service Titan, Slack, CallRail, Quo, Tawk.to, Crisp, Google Ads and Service Scalers. A card marked Coming soon cannot be connected.

What the status pill means

Each card shows one of Available, Coming soon, Awaiting first event, Active, Quiet, Error and Needs setup. On a card that receives deliveries, Awaiting first event means the connection exists and nothing has been delivered yet, and Quiet means nothing has arrived for more than 7 days. Error carries the reason. Needs setup means a Google connection is still waiting for you to choose an account or property.

Secrets, and seeing them once

Connecting a webhook, a form handler or an outbound endpoint generates a 48-character secret. It is shown once, in the window that confirms the connection, with the words: Copy this secret now. It will not be shown again. If you lose it, use Rotate secret on the card to get a new one, then update it in the tool. The old secret stops working straight away. The webhook URL stays the same and is always on the card, with the last four characters of the secret beside it.

Events

Cards you connect with a webhook URL, a code snippet, an outbound address or saved credentials have an Events button once connected: Resend, Gravity Forms, Jotform, Zapier, Outbound Webhook, Service Titan, Slack, CallRail and Service Scalers. On the cards that receive deliveries, Resend, Gravity Forms, Jotform, Zapier and CallRail, it lists the last 30deliveries, newest first, each marked ok, rejected or failed, with the event and, when something went wrong, the reason in the provider's or our own words. Until anything has arrived it reads: No events yet. Fire a test from your tool.

On Outbound Webhook, Slack and Service Scalers nothing is recorded there: what we send to Slack or to your webhook is not listed, so the panel keeps that line. On Service Titan it lists the nightly sync runs, one row per run, marked ok, rejected or failed in the same way, with the reason when one is recorded.

Cards you connect by signing in with Google or Jobber, or with a key your team pastes, have no Events button: Jobber, Google Search Console, Quo, Tawk.to, Crisp and Google Ads. Each one's page here says what its card shows instead.

Reconnect, rotate, disconnect

A Google or Jobber card in Error offers Reconnect, which runs the authorization again. Rotate secret, on Resend, Gravity Forms, Jotform, Zapier, Outbound Webhook and CallRail, asks you to confirm that any tool still using the old secret will stop working until you update it, then shows the new secret once. Disconnect always asks first, and the question states exactly what stops for that provider; each provider's page here repeats that sentence.

What Disconnect keeps, and what it stops

Disconnect removes the connection and what you entered to make it: the address or key, the account you chose, the secret. Everything the connection brought in stays where it is. Leads, calls and chats stay on Leads with their details; ad spend imported from Google Ads stays in your reports; payments imported from ServiceTitan stay stored. What stops is the flow: deliveries to a webhook card are refused, reads from Google or ServiceTitan stop, and messages to Slack or your webhook stop. The Events history on that card is cleared with the connection. Connecting again starts the flow afresh; a webhook card gets a new URL and secret.