Connections
Send each entry to email marketing, CRMs, sheets, chat, webhooks and WordPress, with mapping, conditions, logs and retries.
Connections send each entry somewhere else: a mailing list, a CRM, a spreadsheet, a chat channel, a cloud folder, another site's address, or WordPress itself. A service is set up once for the whole site, then each form adds its own connections and says what to send, when and under which conditions. Nothing is gated: every connection listed here is part of Kindly Forms.
How it fits together#
- Site-wide setup. Kindly Edit > Forms > Connections holds each service's keys and sign-ins. Only people with the site settings right (administrators) can open it.
- Per form. The builder's Connections tab lists the form's connections. Each one names a service, the values to send, when it runs and optional conditions. Connections are part of the form, so Save draft, Publish, Undo and History cover them like fields.
- Running. After an entry is stored, each connection that is switched on, set up and whose conditions hold either runs on the spot or goes into a background queue. Every call is logged with what was sent and what came back, with keys and tokens hidden.
Add a connection to a form#
- Open the form and choose the Connections tab.
- Choose Add a connection. Pick a service from the groups, or type in Find a service. A service that still needs its site-wide setup shows Needs setting up.
- The connection's drawer opens. Set its Name (shown in the list, the logs and the entry's notes), then the service's own settings: the list, audience, table or channel, and the values to send.
- Choose when it runs with Run, and optionally switch on Run only when conditions are met.
- Save draft, then Publish. Visitors' entries only use published connections.
If the service isn't set up yet, the drawer says "%s isn't set up for this site yet" with a Set it up link. It saves your draft first, then opens the hub's Connections screen.
The list shows each connection with a switch to turn it off without removing it. Badges mark connections that are Not installed (the service's code isn't on this site), Not set up, or With conditions. The More menu has Duplicate and Remove.
What to send (field mapping)#
Most services have a Fields table: one row for each of the service's fields, with a box for what to send.
- Type plain words, or choose Insert an answer or other value to add a smartcode such as
{inputs.email}. Several smartcodes and words can be combined. See Smartcodes. - When the table first appears, Kindly fills obvious rows for you: an email field into the service's email, a phone field into phone, the first and last parts of a Name field into first and last name, and any field whose label matches the service's field.
- An empty row is skipped. Required rows are marked with an asterisk.
- For services whose fields come from your account (lists, tables, databases, CRM modules), choose the list or table first. Its fields then load from the service. Load the fields again picks up fields you added there since.
Lists, tags, boards and other choices are loaded from the service and kept for 10 minutes. Load again beside a list asks the service again. If the service can't be reached, the box becomes a plain text box where you can type the ID instead, with the service's error below it.
Some services also have Other fields (key and value rows for custom fields), Tags (comma separated, smartcodes allowed) and Tags when answered (a tag that applies when its answer isn't empty or no).
When it runs#
| Run | Runs |
|---|---|
| When sent | After the entry is stored. For an entry that waits for email confirmation or approval, it runs once the entry is confirmed or approved. |
| When the sender confirms their email | When a double opt-in entry is confirmed. |
| When approved | When someone approves an entry in Entries. |
| When payment succeeds | When the entry's payment is paid. |
Email confirmation and approval are set up in the form's Settings: see After sending.
Conditions#
Run only when conditions are met uses the same conditions editor as fields: compare answers with values, and require all or any of the rules. The connection is skipped for entries that don't match. See Conditions and calculations.
On the spot or in the background#
Most connections run in the background queue, so the visitor never waits for another service. A few run on the spot, during the submission:
- the WordPress connections in the Posts and accounts group (Create a post, Register a user, Update the user profile)
- connections to plugins on the same site (FluentCRM, Mailster, MailPoet, AffiliateWP)
- OpenAI, when it runs on When sent for an entry that goes straight through, so its reply is ready for the emails and the confirmation message
The services#
The builder groups services like this. The hub's Connections screen uses the same services with a Kind filter.
Email marketing#
| Service | What it does |
|---|---|
| ActiveCampaign | Adds or updates contacts in a list with fields, tags and a note. |
| Automizy | Adds contacts to an Automizy list. Automizy has closed; this is for accounts that still work. |
| Brevo | Creates or updates contacts in a list with their attributes, with optional double opt-in. |
| Campaign Monitor | Adds subscribers to a list with custom fields. |
| CleverReach | Adds or updates recipients in a CleverReach group. Signs in with CleverReach. |
| Constant Contact | Creates or updates contacts in lists with tags and custom fields. Signs in with Constant Contact. |
| Gist | Creates or updates Gist contacts with tags. |
| GetResponse | Adds contacts to a list, optionally into the autoresponder cycle. |
| iContact | Adds contacts to an iContact list. |
| Kit (ConvertKit) | Subscribes people to a Kit form with fields and tags. |
| Mailchimp | Adds or updates audience members with merge fields, groups, tags and notes. |
| MailerLite | Adds or updates subscribers in groups with their fields. |
| Mailjet | Adds contacts to a contact list with their properties. |
| Mautic | Creates or updates Mautic contacts with tags and segments. |
| Moosend | Adds subscribers to a mailing list with custom fields. |
| SendFox | Adds contacts to SendFox lists. |
| Mailster, MailPoet | Add subscribers to lists in those plugins on this site. Shown only when the plugin is active. |
CRM#
| Service | What it does |
|---|---|
| amoCRM (Kommo) | Adds contacts, leads (with their contact and company), companies or tasks. Signs in with amoCRM. |
| Drip | Creates or updates Drip people with tags and consent. |
| FluentCRM | Adds or updates FluentCRM contacts with lists and tags. Shown only when FluentCRM is active on this site. |
| HubSpot | Creates or updates HubSpot contacts and adds them to a static list. |
| Insightly | Adds contacts, leads, organizations, opportunities, projects or tasks. |
| OnePageCRM | Adds contacts, and deals, notes or next actions for them. |
| Pipedrive | Adds people, organizations, deals, leads, activities or notes. |
| Salesflare | Adds Salesflare contacts with tags and custom fields. |
| Salesforce | Creates leads, contacts, cases or any other Salesforce record. Signs in with Salesforce. |
| Zoho CRM | Creates or updates records in any Zoho CRM module. Signs in with Zoho. |
Messages#
| Service | What it does |
|---|---|
| Slack | Posts each new entry to a channel through an incoming webhook address. |
| Discord | Posts each new entry to a channel through a channel webhook address. |
| Telegram | A bot posts each new entry to a chat or channel. |
| Twilio | Texts a message to staff or to the person who filled in the form. |
| ClickSend | Sends a text, texts a contact list, or adds the person to a ClickSend list. |
Slack and Discord have a Title, a Message, a Footer and Choose which answers to include (off sends every answer).
Automation#
| Service | What it does |
|---|---|
| Webhook | Sends the answers to any web address. See below. |
| Zapier | Sends every answer, with the entry's details, to a Zap's Catch Hook. |
| Platformly | Adds contacts to a Platformly segment with tags and a note. |
Zapier's drawer has Send sample answers, which sends made-up answers through the connection so Zapier can learn the fields while you build the Zap.
Sheets and data#
| Service | What it does |
|---|---|
| Google Sheets | Adds a row to a spreadsheet for each entry. Signs in with Google. |
| Airtable | Adds a record to an Airtable table for each entry. |
| Notion | Adds a page to a Notion database for each entry. |
| Trello | Makes a card on a Trello board for each entry. |
Posts and accounts#
| Service | What it does |
|---|---|
| Create a post | Makes a post, page or custom post type from each entry, or updates one from the front end. |
| Register a user | Makes a WordPress account from each entry, with a role, profile and custom fields. |
| Update the user profile | Saves the answers to the signed-in person's own profile. |
These need no setup. They are described in Quizzes, landing pages and post forms.
File storage#
Dropbox, Google Drive, OneDrive, Amazon S3 and S3-compatible storage, and Box keep uploaded files in the cloud. See File storage.
Other#
| Service | What it does |
|---|---|
| OpenAI | Writes a reply from the answers with ChatGPT. The reply is shown wherever you put {chatgpt.FEED} (FEED is the connection's ID), such as the confirmation message or an email. The answers go to OpenAI, so leave out anything private. |
| Clearout | Turns away fake, disposable and mistyped email addresses on every form. It is set up in the hub only and has no per-form connection. |
| AffiliateWP | Credits the affiliate who sent the visitor (?ref=) with a referral. Shown only when AffiliateWP is active. |
Clearout checks every Email field as the form is sent. Its options are Check email answers, Also turn away disposable addresses, Also turn away role addresses (info@, sales@) and Also turn away catch-all domains. If Clearout can't be reached, the form is accepted; only an address Clearout says is bad is turned away. Each address's result is kept for a day.
Payments have their own setup: see Payments.
The webhook#
The webhook is the one connection every site has, with no setup. Its settings:
| Setting | What it does |
|---|---|
| Address | The address to send to. Smartcodes work here. It must be an http or https address. |
| Method | POST (the default), PUT, PATCH, GET or DELETE. |
| Send as | JSON (the default) or Form data. JSON sends Content-Type: application/json. |
| Send every answer | On: every answer by its field name, plus _entry. Off: only the rows in Fields to send. |
| Fields to send | Name and value rows. Values can use smartcodes. Shown when Send every answer is off. |
| Headers | Name and value rows sent as request headers, for example an authorization header. Values can use smartcodes. |
With Send every answer, password answers are never sent, and _entry holds the entry's id, the form ID, created_at and source_url (the page it was sent from). A GET request puts the values in the address's query string instead of a body.
The call waits up to 15 seconds. It uses WordPress's safe request, which refuses addresses on the server's own private network. A response from 200 to 299 counts as sent. A 4xx response other than 429 fails at once without retrying, since sending the same thing again won't help; anything else is tried again (see below). The response's first 2,000 characters are kept in the log.
Forms moved from a Simple form keep their webhook as a connection with Send every answer on. See Move an old page form.
Logs and retries#
On the entry#
Each entry's view in Entries shows a note for every connection that ran, with its name and result. Run connections again (in the entry's actions, or as a bulk action on the entries list) runs every connection set to When sent for those entries again, through the queue for background connections. Storage connections skip files they already stored.
Kindly Edit > Forms > Logs#
The Logs screen has three tabs:
- Activity: what happened to entries and forms, such as answers received, entries kept as spam and site copies of files removed.
- Connection calls: one line per call, with its result (Worked, Failed or Note). Open a line to see what was Sent and the Answer. Keys, tokens and passwords are hidden.
- Queue: connections waiting to send or that failed, with their attempts and last result.
Lines can be filtered by form, result and source, and searched. People who can delete entries can delete chosen lines or Delete every matching line. Settings > Privacy has Keep logs for (days); 0 keeps them.
How retries work#
A queued connection is sent within moments of the entry, through WordPress's scheduled tasks. If it fails, it is tried again every 5 minutes, up to 4 attempts in all. Its queue status is Waiting, Running, Trying again, Done, Failed or Skipped (the entry or connection was removed before it ran).
A failure that can't succeed by trying again stops at once: a missing required value, an address that isn't a web address, a plugin that isn't active, or a service answer in the 4xx range other than 408, 409, 423 and 429.
On the Queue tab, Try again sends one failed or waiting line now; select several and choose Try again now for all of them. Both need the right to change entries.
Background sending relies on WordPress's scheduled tasks (WP-Cron). On a site where those only run on visits, a quiet site sends later. A server cron that calls wp-cron.php regularly keeps the queue prompt.
Site-wide setup#
Kindly Edit > Forms > Connections shows every installed service as a tile with Connected, Not connected or Needs attention. Use Search connections, Kind and Show (Every connection, Connected, Not connected) to find one.
Open a tile to set it up:
- Keys and IDs. Type the service's keys, then Save and check. Kindly saves them and asks the service whether they work; the result shows as Connected, Connected as an account name, or the service's error. How to find these details links to the service's own instructions.
- Sign in. Services that use OAuth (Google Sheets, Google Drive, Dropbox, OneDrive, Box, Salesforce, Zoho CRM, amoCRM, Constant Contact, CleverReach, Mautic, Notion) use your own app at the service. Create the app there, give it the address shown as Address to give the service, type its client ID and secret, save, then choose Sign in to the service. Kindly refreshes expired tokens before each call. Sign in again replaces the account.
- Check again asks the service again with the saved details.
- Disconnect removes the saved details. Forms stop sending to that service until it is connected again.
Services with nothing to set up (the webhook, Zapier, Slack, Discord and the WordPress connections) say "Nothing to set up. Add it to a form from the form's Connections."
How keys are kept#
Keys, secrets and tokens are stored in the site's database (the kindly_forms_connections option) so the server can call each service. They are never shown back: after saving, a secret's box is empty with "Saved. Type to replace it." Leaving it empty keeps the saved value. The REST API returns __kept__ in place of each secret, and the logs replace keys, tokens and passwords with [hidden].
Anyone with access to the site's database or files can read them, as with any WordPress plugin's keys. Give each service a key with only the access the form needs.
For developers#
Services are registered with the kindly_forms_feed_providers filter. The REST routes for site-wide setup, remote choices, field mapping and samples are under kindly-forms/v1/connections. The kindly_forms_feed_failed action fires when a queued connection fails for good. See Developer reference.