Skip to main content

Integration Hub

info

Enterprise Plan — This module is available on the Enterprise plan.

Integration Hub is the central control plane for connecting your CRM to the outside world. You can install pre-built connector templates, define your own custom connectors, map fields between systems, register webhooks, run data sync jobs, and replay any event that failed to deliver — all without writing integration code.

What's Included​

  • Connector templates — A catalog of pre-built integration blueprints you install in seconds
  • Custom connectors — Build connections to any CRM, support platform, analytics tool, messaging service, storage provider, or custom API
  • Field mappings — Define how fields translate between your CRM and each external system, with push, pull, or bidirectional sync and optional transform rules
  • Mapping presets — One-click field mapping configurations for common connectors
  • Webhooks — Register outbound webhooks for any event type, with HMAC-SHA256 signing, configurable retry logic, and secret rotation
  • Sync jobs — Plan and execute data sync operations with scoped push, pull, or bidirectional direction
  • Event outbox — Durable event store that ensures no outbound event is lost; filter by status and replay any event on demand
  • Replay Center — Inspect and requeue failed outbox events, dead-letter events, and rejected webhook receipts from a single interface

Installing a Connector Template​

Navigate to Integration Hub → Templates to browse the pre-built catalog.

  1. Find the template you want (for example, Salesforce, HubSpot, Stripe, or Slack).
  2. Choose Install.
  3. Provide a connector name, optional key, and the credentials or configuration the template requires.
  4. After installation you land on the field mappings screen for the new connector, ready to configure data flow.

Creating a Custom Connector​

Go to Integration Hub → Connectors and choose New Connector.

  1. Enter a name and select the connector type: CRM, support, analytics, messaging, storage, or custom.
  2. Choose the authentication method: API key, OAuth 2.0, or none.
  3. Provide the configuration and credentials in the respective JSON fields.
  4. Save. The connector is now available for field mappings, sync jobs, and webhooks.

To update credentials or change the configuration later, open the connector and choose Edit. Deleting a connector also removes all associated field mappings.

Configuring Field Mappings​

Navigate to Integration Hub → Field Mappings and select a connector from the left panel.

Adding a mapping

  1. Choose New Mapping.
  2. Specify the source field (the field in your CRM) and target field (the field in the external system).
  3. Set the direction: Push (CRM to external), Pull (external to CRM), or Bidirectional.
  4. Optionally add a transform rule — a short expression that converts the value during sync (for example, formatting a date or mapping an enum).
  5. Mark the mapping as required if the sync should fail when this field is missing.

Mapping presets

If a preset exists for your connector, choose Apply Preset to install a recommended set of field mappings in one action. You can adjust individual mappings after applying the preset.

Webhooks​

Go to Integration Hub → Webhooks to register outbound event listeners.

Creating a webhook

  1. Choose New Webhook and enter a name and the target URL that will receive the payload.
  2. Select the event type — for example, deal.won, ticket.created, or contact.updated.
  3. Set the maximum retry attempts (default is 5) and optionally add custom headers.
  4. Save. The system generates a secret and signs every delivery with HMAC-SHA256 so the receiving endpoint can verify authenticity.

Rotating a secret

If a webhook secret is compromised, choose Rotate Secret. The previous secret remains valid for one hour during the transition, then expires automatically.

The webhooks list shows receipt counts per webhook. The recent receipts panel on the same page shows the latest deliveries and their status.

Sync Jobs​

Navigate to Integration Hub → Sync Jobs to run data synchronisation operations.

Creating a sync job

  1. Choose New Sync Job.
  2. Select the connector and the sync direction (push, pull, or bidirectional).
  3. Optionally set a record count estimate and a JSON scope to limit which records are included.
  4. Choose Execute Now to run immediately, or save for later scheduling.

Managing running jobs

  • Resume a paused or failed job to continue from where it stopped.
  • Dead Letter a job that cannot be recovered, providing a reason. This moves the job to the dead-letter state for auditing.

The sync jobs page also shows the current event outbox so you can monitor pending events alongside active jobs.

Replay Center​

Go to Integration Hub → Replay Center when you need to recover from delivery failures.

The Replay Center shows three lists side by side:

ListWhat it contains
Outbox EventsAll events in the outbox, filterable by status (pending, dispatched, failed)
Dead LettersEvents that exhausted all retry attempts
Failed ReceiptsInbound webhook deliveries that were rejected

To requeue an outbox event, open it and choose Replay. The system creates a new outbox entry with the original payload and marks it as a replay, preserving the audit trail back to the original event.

API Reference​

Manage connectors and mappings programmatically, push events directly into the outbox, or query sync job status via the REST API.

Integration Hub API Reference