Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.elasticfunnels.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

ElasticFunnels has its own customer-record store and CRM views. The integrations below let you push EF data into an external CRM as well — useful when sales, success, or marketing teams already work inside their CRM and shouldn’t have to learn a new tool.
For information on the built-in CRM (segments, customer profile, automations), see CRM overview.

​
Supported providers

ProviderAuthWhat you can do
HubSpotPrivate App access tokenCreate / update contacts, write custom contact properties, push deals
Keap (Infusionsoft)OAuth 2.0Create / update contacts, retrieve a contact, apply tags
OntraportAPI key + App IDCreate / update contacts, check existence, manage tags
PipedriveAPI keyCreate / update persons, create deals on the right pipeline / stage
Close (closeio)API keyCreate / update leads + contacts, push opportunities
Agile CRMAPI key + domain + admin emailCreate / update contacts, manage tags
All six are exposed as actions inside the Automation Builder so you can wire them into any flow (form-submit, sale, refund, abandoned cart, dunning failure, etc.).

​
Setup pattern

1

Open the provider in EF

Go to Integrations → CRM and click the provider. The form is provider-specific.
2

Authenticate

Paste an API key (HubSpot Private App token, Pipedrive API key, etc.) or OAuth into the provider (Keap).
3

Map the right account / pipeline

For Pipedrive and Keap, the form loads your pipelines / lists from the provider so you can pick them by name. For HubSpot, the integration writes to your default contact pipeline unless you configure a specific one in your automation.
4

Add the actions to an automation

Open Automations, edit a flow, and add an action like HubSpot: Create or Update Contact. Map EF variables (customer.email, customer.first_name, custom fields) to the provider’s fields.
5

Test with a dummy record

Trigger the automation manually (Insert Test Run) and verify the record appears in the external CRM.

​
Field mapping notes

  • Custom properties / custom fields — All six providers support custom fields. Add them in the provider first, then they show up in the action’s mapping dropdown the next time you open the form.
  • Tag management — Each provider exposes its own list of tags / labels. EF lists them dynamically; you can also pass a tag name as a string to create it on the fly.
  • Re-keying contacts — All actions are upsert-style: EF tries to match by email first (or the provider’s primary identifier) and updates if a match exists; otherwise it creates a new record.

​
When to push, when not to

Don’t pipe every EF event into your CRM — most CRMs charge per contact and slow down with low-quality records. A common pattern:
  • Push qualified leads (form-submit, demo-booked) into the CRM immediately.
  • Push customers (first sale) into the CRM when they hit a paid plan or subscription.
  • Skip abandons unless your sales team works abandons by hand — keep them inside the EF callcenter or email engine.
You can encode that gating with the EF automation’s condition step (e.g. only run the HubSpot action when total > 0).

​
Troubleshooting

Re-authenticate the integration. HubSpot Private App tokens, Pipedrive API keys, and Ontraport API keys can be regenerated from the provider’s dashboard; OAuth-based providers (Keap, AWeber) need to be re-authorized through EF’s connect flow.
Create the custom field in the external CRM first, then re-open the EF action — the dropdown is fetched live and will include the new field.
Most CRMs match on email. If you have multiple contacts with the same email but different IDs, the EF action picks the first match. Clean up duplicates in the CRM and re-run.