Integrations, webhooks, and CRM workflows

Settings → Integrations shows supported business systems such as HubSpot, Salesforce, Pipedrive, Slack, Zapier, and Make, together with connection state. Native connections require a Pro or Team entitlement and administrator-configured OAuth credentials.

Connected inboxes

Google and Microsoft connections are foundational integrations. They power provider-backed sending, response analytics, attachment indexing, and mailbox synchronization. Manage them under Settings → Inbox, not the general integrations grid.

Google Sheets

Campaign contact import can connect Google with read-only Sheets access. Provide the spreadsheet URL and a range such as Contacts!A1:Z5001. The first row must be headers, one column must be email, and up to 5,000 rows are imported. Imported headers become merge/custom fields where supported.

CRM and automation

HubSpot, Salesforce, and Pipedrive have an individual Connect button. After provider authorization, the connection performs a resumable initial contact backfill and then incremental synchronization. Use Sync now for an immediate run, Pause to stop scheduled work without deleting credentials, Resume to restart it, or Disconnect to erase the stored OAuth tokens.

Field mappings control the local field, remote field, direction, and conflict policy. Two-way mappings can use newest-wins, local-wins, remote-wins, or manual review. Manual conflicts appear in the same screen with Keep local and Use provider actions. Email should remain mapped because it is the stable contact identity used during matching.

Slack has an individual OAuth connection and a channel-ID setting for selected activity notifications. It does not expose contact field mappings.

Zapier, Make, and custom clients use scoped API tokens from the same page. Select only the required events:read, contacts:read, or contacts:write scopes and set an expiration where practical. The secret is shown once; losing it requires revoking it and creating a replacement.

Treat each destination as another copy of personal data. Configure only needed fields and events, document the purpose, and remove connections that are no longer used.

Webhooks and event meaning

Likely-open webhooks should represent human-classified opens, while privacy/scanner evidence remains separate. Click events are also classified. Consumers must handle retries and idempotency and should not assume event arrival order equals user intent.

Disconnecting

Disconnecting prevents future synchronization/actions but does not automatically delete records already sent to the third party or historical Elite data. Use each provider's deletion controls and Elite privacy/account controls as appropriate.

Connection shown but action unavailable

Confirm the account plan and provider authorization. A native tile says Awaiting admin setup when its deployment credentials are absent, Connect when it is ready, and Reconnect when provider authorization has expired or failed. Zapier and Make do not use provider OAuth tiles; create a scoped API token instead.