Integration hub
The integration hub connects leadmaps to the rest of your commercial stack. You can notify a team channel, send a signed webhook to your own service, start a workflow in an automation platform, or bring aggregate advertising spend into attribution from selected provider accounts.
Availability. Slack, HubSpot, Pipedrive, and secure webhooks are available to eligible workspaces after completing production canaries. Native Google Ads, Meta Ads, and LinkedIn Ads remain unavailable while their provider approvals and live canaries are incomplete.
Open Settings, then Integration Hub in the leadmaps dashboard. You can search the catalog, connect a tool, preview an automation, and review delivery history without writing code. An unfinished connection is marked Unavailable and cannot open an incomplete setup flow. Choose Request this integration to record one request for your workspace. leadmaps stores the workspace and integration choice, not a message or provider credential.
If your workspace already uses the older webhook-destinations screen, open the Existing webhooks compatibility card. It returns you to that screen without migrating, duplicating, or changing an active destination. The separate Webhooks card creates the newer Integration Hub connection described below.
Every automation uses the same five-step editor:
- Confirm the connected account.
- Choose the recipe and trigger.
- Map the destination fields or channel.
- Preview the result without sending customer data.
- Review and activate the automation.
CRM fields, pipelines, and stages are shown by the names from the connected account. You do not need to find or paste internal provider identifiers.
Connections run in the background. A slow or unavailable destination does not slow down your leadmaps dashboard or data collection. Each delivery has a status, and temporary failures are retried automatically.
Available connections
Section titled “Available connections”- HubSpot can send qualified contacts. Contact fields use the readable labels from the connected account. Deal actions are unavailable unless an owner or admin reconnects with an explicitly supported write-access profile.
- Webhooks can send a versioned, signed JSON message to an HTTPS endpoint you control. The production canary covered direct delivery, retry, duplicate suppression, delivery history, and disconnect cleanup.
- Zapier, Make, and n8n can use the same dependable webhook delivery and provide a quick route into thousands of other tools.
- Slack can send privacy-safe alerts to an approved channel. Its production canary covered connection, delivery, pause, resume, reconnect, duplicate suppression, and disconnect cleanup.
- Pipedrive can send qualified people and explicitly approved deal updates. Its production canary covered readable field and stage choices, duplicate prevention, delivery history, and provider credential revocation.
Staged advertising preview
Section titled “Staged advertising preview”Google Ads, Meta Ads, and LinkedIn Ads use OAuth and explicit account selection to import aggregate campaign spend each day. They preserve every account’s currency and do not apply an exchange rate. The connectors remain unavailable until each provider’s production application, access review, and provider-side canary are complete. Manual entry and CSV upload remain available on the Attribution page in the meantime.
Shopify and warehouse exports can also appear in the catalog, but they keep their existing setup and billing screens. They do not use an integration hub connection slot.
Customer health private beta
Section titled “Customer health private beta”Selected Business workspaces in the customer health private beta can build opt-in automations for an account becoming at risk, recovering, scheduling a cancellation, churning, reactivating, or receiving a ready review. Customer health is not generally available.
Slack and secure webhook actions receive only a bounded account identifier, the selected transition, a health band when applicable, and an opaque review reference. They do not receive raw analytics, page contents, contact details, or replay data.
HubSpot and Pipedrive can use a separate Customer health and lifecycle access profile. An owner or admin maps the stable account identifier and the specific company or deal status values that should become trusted lifecycle updates. CRM reconciliation repairs missed or repeated provider updates without allowing observed browser behavior to confirm churn.
Read Customer health and churn autopsies before activating an account automation. A provider’s existing production canary does not by itself promote this customer-health extension beyond the selected beta.
Plans and connection limits
Section titled “Plans and connection limits”| Plan | Connections | What the plan supports after provider verification |
|---|---|---|
| Free | 0 | View the catalog and available upgrades. |
| Hobby | 1 | Slack, a direct webhook, or one automation bridge. |
| Pro | 5 | Basic connections plus supported CRM and advertising connections. |
| Business | 25 | All supported connections and advanced automation controls. |
The dashboard always applies the limit from your current plan. Disconnecting a connection releases its slot. Existing Shopify, Snowflake, and BigQuery setups do not count against this total.
CRM connections start with contact or person access. Deal and revenue access is never enabled silently. Business owners and admins must choose the additional access and activate a matching recipe.
Who can manage connections
Section titled “Who can manage connections”A workspace owner or admin can connect, test, pause, resume, reconnect, or disconnect a provider. Other workspace members can see connection health and delivery history but cannot change credentials.
Every sensitive change is written to the workspace audit log. Provider tokens, webhook URLs, and signing secrets are encrypted at rest and are never returned by the connection API after setup.
Disconnecting stops new work immediately. The encrypted credential is removed, while non-sensitive delivery history remains available for troubleshooting and audit purposes.
The Integration Hub protects the required trigger, action, and connection fields. You can change supported mapping and delivery options or choose which advertising accounts are synchronized, but cannot remove fields that a destination needs to work safely.
If the connected provider cannot load its available choices, leadmaps keeps the saved mapping unchanged and disables activation. Retry the load or reconnect the account when the connection needs updated permissions.
Connection states
Section titled “Connection states”| Status | Meaning | What to do |
|---|---|---|
| Connected | The connection can receive new work. | No action is needed. |
| Paused | New work is held for this connection. | Resume it when you are ready. |
| Needs attention | Authorization is no longer usable. | Reconnect the provider. |
| Error | A permanent destination problem stopped delivery. | Review the delivery and test the connection. |
| Disconnected | Credentials were revoked and removed. | Start a new connection if you need it again. |
Privacy boundary
Section titled “Privacy boundary”leadmaps sends only the fields needed for the outbound action you configured. The first release uses commercial metadata such as a lead stage, state, currency, and value together with a link back to the dashboard. It does not put contact details, visitor identities, page contents, replay data, or provider secrets in Slack or generic webhook messages.
Native advertising connections are inbound and read aggregate account, campaign, spend, impression, click, and provider conversion totals. They do not import audiences, contact lists, ad creative, or individual conversion records. Provider tokens are encrypted and never returned to the browser.
You control the destination and remain responsible for its access settings and retention. Disconnect a tool immediately if its destination URL or credentials might have leaked.