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 cloud connections authorize fresh authored sending with gmail.send. Gmail mailbox history and replies remain in the browser or device-only client; cloud Gmail cannot detect replies or bounces or supply mailbox history to CRM/automation. Microsoft connections support sending and the mailbox capabilities authorized by the selected consent. Manage them under Settings → Mailboxes & sync.

Google Sheets

Where selected-file import is enabled, choose the spreadsheet in Google Picker and authorize drive.file, then provide a range such as Contacts!A1:Z5001. Elite reads the selected data; the OAuth permission itself is not a read-only Sheets scope. 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. Google Contacts import separately uses contacts.readonly and depends on its release flag.

CRM and automation

HubSpot, Salesforce, and Pipedrive have an individual Connect button. After authorization, synchronization starts disabled. Choose selected contacts or all contacts, enable the intended import, export and activity directions, preview the changes and save the route. An enabled import starts a resumable contact backfill followed by incremental updates. Sync now runs the saved route; Pause stops work while retaining credentials, Resume restarts it and Disconnect erases the stored tokens and attempts provider revocation. If revocation cannot be confirmed, remove the app in the provider's connected-app settings.

With activity routing enabled, HubSpot, Salesforce and Pipedrive receive available engagement summaries associated with the matching contact. These summaries are separate from a full email copy. For CRMs that provide a forwarding address, add it under External CRM auto-BCC. Supported sending surfaces add the hidden destination to authored messages. Gmail browser forwarding is limited to recognized new drafts; the Gmail add-on asks you to confirm a new authored message. Outlook's taskpane and send runtime also use saved destinations. Inbound CRM BCC capture separately imports mail sent to an Elite-owned capture address.

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.

Pipedrive uses name rather than writable first_name/last_name fields. Use display name or custom fields for separate names. Its job_title field requires Pipedrive contact sync to be enabled for the company. Salesforce mappings require access to each mapped field and related record.

Slack has an individual OAuth connection, a channel-ID setting and per-event notification controls. Invite the bot into the channel, save its channel ID, then use Send test to saved channel to verify delivery. It uses chat:write and does not read channel history. Events wake the delivery worker when they are recorded.

Zapier and Make include instant first-open, first-click, and first-document-view triggers, general engagement events, contact lookup/upsert, and tracked sending through a connected Gmail or Outlook mailbox. Synced CRM contacts remain available to campaigns through the existing Import recipients → From Lists tab.

Automation clients use scoped API tokens from the same page. Select only the required events:read, contacts:read, or contacts:write scopes; instant triggers additionally need webhooks:write and tracked sending needs emails:send. Set an expiration where practical. The secret is shown once; losing it requires revoking it and creating a replacement.

Revoking or expiring a token stops webhook subscriptions created with that token. Legacy subscriptions paused during the authorization migration must be subscribed again. Local Zapier validation and Make component tests do not publish either marketplace app; private platform validation and marketplace review are separate steps.

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.

Webhook id and event_id are stable event identifiers; use aggregate_id for the tracked message/document identifier. Verify the signature against the actual request bytes. Supply a stable source event/run key when automating tracked sends so a retry does not send a second message.

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.