Integrations

After a submission is safely stored, Gather Grove Forms can fire integrations — send the data onward to other systems. Add them per form under Integrations (with no field selected). Each can fire only on certain conditions or for certain conversational outcomes (the same rule grammar as conditional logic).

Integrations never block a submission: if one fails, the entry is still saved and the failure is logged.

Keys and secrets are write-only. Once you save an API key, signing secret or secret key, it is never shown again — not to you, and not to staff who can edit forms. The field reads Saved — leave blank to keep it: leave it empty to keep the saved key, type a new one to replace it, or choose Remove saved key. Removing the integration removes its key too.

Webhook (Free)

The universal, no-credentials integration. Sends the submission as a JSON POST to any URL you choose — so you can fan out to Zapier, Make, n8n, or your own endpoint, even on the free tier.

  • URL — where to send the JSON.
  • Secret (optional) — when set, each request is signed with an X-GG-Signature: sha256=… HMAC header so your receiver can verify it.
  • Field map (optional) — limit or rename which fields go in the payload.

Mailchimp (Pro)

Add subscribers to a Mailchimp audience directly — no Zapier in between.

  • API key — stored server-side, never exposed to the browser.
  • Audience — the list to add subscribers to.
  • Field map — map form fields to merge fields (e.g. email → email, first_name → FNAME).
  • Tags — apply tags to new subscribers.
  • Status — subscribe immediately or require confirmation (double opt-in).

Mailchimp is enforced on the server — an unlicensed site won’t fire it even if configured.

Kit (ConvertKit) (Pro)

Subscribe submitters to Kit (formerly ConvertKit) directly — no Zapier in between. Works on free Kit accounts too: tagging both subscribes and tags, no automations required.

  • API key (v4) — from Kit → Settings → Developer; stored server-side, never exposed to the browser.
  • Email & First name — map the form fields that supply the subscriber’s email and (optionally) first name.
  • Kit form ID (optional) — also add the subscriber to one of your Kit forms.
  • Kit sequence ID (optional) — enroll the subscriber into a sequence.
  • Field map (optional) — map form fields onto Kit custom fields.
  • Tags — comma-separated Kit tag IDs (numbers, from each tag’s URL in Kit) applied to the subscriber.

Like Mailchimp, Kit is enforced on the server — an unlicensed site won’t fire it even if configured.

When a member changes their email

If a signed-in member sent their address to Mailchimp or Kit through a form, and later changes the email on their account — themselves, at the front desk, or by an admin in WordPress — Forms changes the address on their existing Mailchimp or Kit subscriber within a few minutes. It never adds a second subscriber, and if the subscriber isn’t there any more it leaves it at that. If Mailchimp or Kit can’t be reached, it tries once more ten minutes later. Addresses submitted by someone who wasn’t signed in are left alone, because a shared inbox isn’t proof they belong to the member.

Sync to Notion (Free)

When the Gather Grove Notion Sync plugin is active, each submission can be pushed straight into a Notion database — no Zapier in between. The option only appears when Notion Sync is installed, and there’s nothing to configure here: Notion Sync owns the database and field mapping on its side, so Forms hands over every submitted field and lets you map them in Notion Sync. As with every integration, you can still scope when it fires with conditions or conversational outcomes.

Gather Grove Pulse: your member list (Free)

With Gather Grove Pulse on the site, form submissions can become members, on the lists you choose, without adding anything here. The quickest way is the Newsletter signup starter: a first name, an email address and an unticked Yes, send me news and updates box. Place it like any form and it connects itself the first time someone signs up. Everyone joins your members, and only those who ticked the box are sent your news. Each signup also appears on the person’s record in Pulse.

Any other form can be connected from Pulse → Members → Add members from a form, choosing its fields from dropdowns. To have a form of your own connect itself the way the starter does, turn on This is a mailing-list signup in its settings (with no field selected). Submissions marked as spam never become members.

If your studio needs people to confirm their email address before they get news (often called double opt-in, and usually needed in the EU, the UK and Canada), turn on Ask people to confirm by email for the form in Pulse. Someone who ticks the box then sees “Almost done… check your inbox” instead of the form’s thank-you, and joins your list once they press the button in the email.

Create Booking (Pro)

When the Gather Grove Booking plugin is active, a submission can create a booking directly — turning an application or registration form into the front door for a class or session. The option only appears when Booking is installed.

  • Session — book a fixed session (enter its ID) or let the booker pick one (map a form field whose value is the session ID; the field’s value wins when both are set).
  • Name & Email — map the form fields that supply the booker’s name and email. Booking finds or creates the client record from these — Forms never touches Booking’s client list.
  • Phone, Group size, Notes (optional) — map additional fields if your form collects them.

Bookings made this way pass through every one of Booking’s own rules. If the class requires approval, the booking lands as pending approval for an instructor to confirm — Forms never bypasses that. Like Mailchimp, Create Booking is enforced on the server, so an unlicensed site won’t fire it.

Stripe (Pro)

Create or update a Stripe customer from a submission — a lead or contact record you can bill, invoice, or subscribe later. Forms never collects or touches card data, so this stays out of PCI scope; it just keeps your Stripe customer list in sync.

  • Secret key — your sk_… key, stored server-side and never exposed to the browser.
  • Email field — the form field that supplies the customer email. Resubmissions with the same email update the existing customer rather than creating duplicates.
  • Name field (optional) — maps to the customer name.
  • Field map (optional) — map form fields onto the customer’s metadata.

Google Sheets (Pro)

Append each submission as a row to a Google Sheet. To avoid asking you for Google account access, this works through a tiny Apps Script Web App you deploy on your own sheet:

  1. In your Google Sheet, open Extensions → Apps Script and paste a short doPost that appends JSON.parse(e.postData.contents).row to the sheet.
  2. Deploy → New deployment → Web app, set access to “Anyone”, and copy the /exec URL.
  3. Paste that URL into the integration’s Apps Script Web App URL field.
  • Field map (optional) — choose which fields become which columns; without it, every submitted field is sent.

Power users who’d rather not deploy a script can use the free Webhook with any no-code tool instead. Both Stripe and Google Sheets are enforced on the server.

What’s logged

Every fire records a verdict — success, failed, or skipped — with a response code and a hashed fingerprint of the payload. Full submission contents are never written to the integration log; the entry itself remains the system of record.

Coming next

The framework is open: the Gather Grove ecosystem plugins connect through it, and developers can register their own integrations — see Developer & API.


Applies to Gather Grove Forms v1.41.5. Last synced November 11, 2026.