Settings

New connectors: Klaviyo, RD Station, ServiceNow, Jira, GA4, PostHog, TikTok Ads, Microsoft Ads, Databricks, Azure Synapse and BigCommerce

A new batch of bring-your-own-account (BYO) connectors. They all start inert: you paste the credential in Settings → Integrations, enable it, and only then do they work. Credentials are encrypted and never shown back. No cost from us.

These connectors follow the same model as the others: bring your own account (BYO). Open Settings → Integrations, find the card, paste the credential (always encrypted) and enable it. Until it is configured and enabled, nothing happens.

Marketing: Klaviyo and RD Station

They sync (outbound) your Contacts as profiles in Klaviyo and RD Station Marketing, matched by email.

Klaviyo: under Settings → API keys, create a Private API Key (scope profiles:write) and paste it into the Klaviyo card.
RD Station: generate an RD Station Marketing access token and paste it into the RD Station Marketing card.
Enable it. Use "Sync contacts" to push your current base; new contacts go automatically.

💡 These two are outbound only (no unsubscribe webhook for now). The RD Station token is OAuth and expires: if syncing stops, paste a fresh token.

Help desk: ServiceNow and Jira Service Management

Each incident/issue becomes a CRM Ticket (inbound via webhook) and you can create tickets from the CRM (outbound).

ServiceNow: enter the instance URL (https://yourco.service-now.com), an integration user with Table API access, and a webhook secret.
Jira: enter the site URL (https://yourco.atlassian.net), the project key, the account email, an API token (id.atlassian.com → Security → API tokens), and a webhook secret.
Copy the webhook URL from the card and configure, in ServiceNow (Business Rule) or Jira (Automation), a POST to that URL sending the secret header (X-ServiceNow-Secret or X-Automation-Webhook-Token).

Neither ServiceNow nor Jira signs webhooks natively, so verification uses a shared secret you send in the header and that matches the value stored in the CRM.

Product analytics: GA4 and PostHog

They send product events (e.g. deal won) to your Google Analytics 4 (Measurement Protocol) or PostHog (capture). Outbound only.

GA4: get the Measurement ID (G-XXXX) and create an API secret under Admin → Data Streams → Measurement Protocol API secrets.
PostHog: get the Project API key (phc_...) in Project Settings; choose the US/EU region or enter your self-hosted host.
Enable it and use "Send test event" to validate end to end.

Ads: TikTok Ads and Microsoft/Bing Ads

They import campaigns and spend for ROI. TikTok Ads works fully. Microsoft/Bing Ads stores and validates the OAuth credential, but reading metrics depends on Microsoft's SOAP Reporting API (not wired yet), so for now it imports 0 campaigns.

TikTok: enter the Business Center advertiser_id and a long-lived access token from your TikTok Marketing API app.
Microsoft: enter developer token, customer id, account id, and the OAuth app (client id/secret + refresh token).
Enable it and click "Sync now".

Data warehouse: Databricks and Azure Synapse

They follow the same model as Snowflake/Redshift: we generate a file (NDJSON/CSV) per object and send it to a staging URL you control; the final load is a COPY INTO you run.

Enter the staging URL (e.g. a volume/container or signed URL), the format and, if needed, an auth header + secret.
Choose the objects to export, enable it and click "Export now".
In Databricks or Synapse, run COPY INTO your table pointing at the uploaded file.

Example: Databricks: COPY INTO crm.opportunity FROM '/Volumes/main/crm/stage/opportunity' FILEFORMAT = JSON COPY_OPTIONS ('mergeSchema' = 'true');

E-commerce: BigCommerce

Syncs customers and orders from your BigCommerce store. Unlike Shopify, the BigCommerce webhook carries only the resource id, so the CRM fetches the details from the Admin API; that is why the Admin API token is required.

Enter the store hash, a webhook secret (which becomes the X-BigCommerce-Secret header), and a store-level API account token (with Customers and Orders read scopes).
Copy the webhook URL and, in your store, create webhooks pointing to it for the store/customer/created|updated and store/order/created|updated scopes, with the X-BigCommerce-Secret header.
Enable it. Each customer becomes a Contact and each order a sales order.

If the card does not sync: check the Admin API token (without it the CRM cannot fetch details) and the header secret. A secret different from the one stored in the CRM is rejected (401).

Open this article inside the system →