Integration connection and history reference
You'll find the controls for your integration's credentials, connection status, request history, cached fields, and dependent forms and questions.
Updated
View as MarkdownUse your integration's settings to check its connection, refresh its field list, or find out why a contact update failed. Open Project settings (the gear at the bottom of the sidebar), then Integrations. The page has four tabs: Email platform, Analytics, Connected apps, and Webhooks.
A project supports one email platform or CRM at a time. Analytics and other app connections are separate.
Find your platform
The Email platform tab connects one email platform to sync leads. Until you connect one, it shows 18 providers. A locked card shows the plan you need and opens the upgrade page when you select it. Existing connections aren't subject to this lock. Selecting a provider opens its own page under Integrations.
Once you're connected, the tab shows only your provider, when you connected it, and a status tag such as Healthy, Connection issue, or Reconnect needed. Choose Manage to open its page. The same tab also holds Lead attribution.
The Analytics tab has a switch for each of Google Analytics, Google Tag Manager, Fathom Analytics, and PostHog. Google Tag Manager sends A/B test impressions to your data layer. Publish a change to any of these switches to apply it on your website. These switches don't install the analytics service's JavaScript library.
The Connected apps tab lists Senja and Stripe. Each app stores its key separately from your email-platform connection. A row shows Connect until you connect the app, then Manage connection, with a tag such as Connected. Stripe's row also shows Importing, Sync delayed, or Key rejected, a Test data tag for a test key, and a status line such as when it last synced. When Stripe rejects its key, the row's button becomes Reconnect.
Every app uses the same dialog. Before you connect, it's titled Connect followed by the app's name, with the key field and Cancel and Connect. Once you're connected, it's titled with the app's name and status tag, and has a Replace key field with Disconnect, Close, and Save key. Save key replaces the stored key with the one you entered. Each app's guide covers what its dialog shows.
The Webhooks tab holds the project's webhook signing secret. On plans without webhooks, the tab names the plan you need.
The email platforms and CRMs are ActiveCampaign, Beehiiv, Bento, Braze, Customer.io, Drip, Encharge, GoHighLevel, HubSpot, Intercom, Keap, Kit, Klaviyo, Mailchimp, MailerLite, Ontraport, Salesforce/Pardot, and Userlist. Each platform guide covers its required fields and identification methods.
Connect or replace credentials
Key-based providers show the credential fields they need. Connect saves a new connection. Save changes saves replacement credentials. Existing secret values are hidden, with a control to reveal them.
OAuth providers show Connect to, followed by the provider's name. You'll authorize access on the provider's website instead of entering access or refresh tokens. To renew an existing connection, use Reconnect to, followed by the provider's name.
Some OAuth providers need more details after authorization. Drip needs Account ID, and Salesforce/Pardot needs Business Unit ID. Save configuration saves those fields. GoHighLevel's selected location and HubSpot's portal come from authorization, so you don't enter equivalent fields yourself.
A connection from RightMessage's older integration system shows a message that RightMessage can't sync until you reconnect or re-enter your credentials. If your provider rejects the saved credentials, Status shows Connection issue with the provider's message. After saving new credentials, test the contact actions you use. Each action still needs the right permissions.
If your project already uses another email platform, a provider's page tells you to remove the current one first.
Connection status and cache
The provider page's Overview tab has a Status section with a connection indicator in four states:
| What you see | What it means |
|---|---|
| Checking connection status... | A health check is pending. |
| Connection status: OK | Your provider's health check passed. |
| Connection issue | The health check found a problem. Its message explains what happened. |
| Connection status: Unknown | There's no usable health check response. |
Each provider has its own health check. You'll still need to test a form submission separately. Userlist needs an authorized test write before it can confirm the connection, so saving credentials alone won't show Connection status: OK.
Clear cache, under Cached data, reloads custom fields, tags, and lists from your provider. Use it to refresh the pickers after you've changed fields or tags in your provider. It doesn't delete previous question responses or resend them to contacts.
Request history
The History tab shows recent integration requests in a table with Date, Critical, Action, and Status. The table displays 10 rows per page.
Keyword Search searches the request and response text. Expand a row to see Request and the request URL. Successful rows show Response. Other rows show Error.
A provider that isn't connected asks you to connect it to start tracking sync activity. History keeps recent requests, not a permanent record of every update. Check the request for the action you're investigating. A successful contact lookup and a later subscription are separate requests.
Request details can include contact data. Review them and hide private information before sharing screenshots.
See what uses the connection
The Usage tab lists the parts of your project that depend on this connection: segment groups and questions that sync answers or segment with provider data, forms that submit to the provider, forms with provider field mappings, and flows with conditions on provider data. Long lists show the first five, with Show all to expand them.
Remove, in the Overview tab's danger zone, disconnects the provider after you confirm. While something still depends on it, the button is unavailable and points you to Usage. Remove or replace those settings before changing providers.
Removing a connection doesn't delete contacts in your provider. Review the affected mappings and conditions before replacing it.
Give your AI assistant context for emails
Once your provider is connected, the LLM Mappings tab contains a read-only LLM Context for Email Personalization text area and Copy to Clipboard.
This text describes your platform's email syntax, mapped segments, and available project context. Give it to your AI assistant to help draft personalized emails. It doesn't send emails or give the assistant access to your account. Its syntax is specific to your connected platform.
Review the copied text before sharing it with another service, then check the assistant's draft in your email platform.
Related tasks
After replacing credentials, check a new and existing contact. For answer destinations, see Map answers to contact fields and tags. If contacts aren't updating, use contact-sync troubleshooting.