Skip to main content

Connections

Introduction​

A connection is a saved set of credentials for a third-party service, set up once on Formidable › Connections and then chosen wherever it is needed. Connections need the Manage connections permission, because they hold credentials.

Providers​

ProviderUsed byAsks for
MailchimpWorkflowsAPI key; optional double opt-in
Campaign MonitorWorkflowsAPI key; consent to track
Constant ContactWorkflowsAccess token
DotdigitalWorkflowsAPI user, API password, region
HubSpotWorkflowsAccess token
SalesforceWorkflowsInstance URL, access token, API version
MailjetWorkflowsAPI key, secret key; optional force subscribe
TurnstileThe Turnstile fieldtypeSite key and secret key
hCaptchaThe hCaptcha fieldtypeSite key and secret key

The shipped providers, as listed in the add-on's configuration: Mailchimp, CampaignMonitor, Dotdigital, ConstantContact, Hubspot, Salesforce, Mailjet, Turnstile, Hcaptcha.

Every shipped provider can test its saved credentials from the connections screen, before any form depends on them.

Using a connection​

  • In a workflow: choose Send to a connection, pick the connection, the target (a list or audience, where the provider has one), and map form fields to the provider's fields. See Workflows.
  • In a CAPTCHA field: on a Turnstile or hCaptcha field's settings, choose the connection. Different forms can use different keys, such as separate staging and production widgets.

When a provider fails​

Connections run during the visitor's submission, so each request has a tight time limit: 8 seconds in total, 4 seconds to connect. A provider having a bad day becomes a logged failure within seconds, rather than a visitor waiting on a spinning button. The failure is recorded in the workflow log, with what was sent and what the provider answered, and the submission itself is unaffected. Fix the cause, then use Run again.

Developers can add providers. See Custom connections.