JotForm integration guide

Overview

The JotForm integration turns each form submission into a contact in your Flowgration CRM. Flowgration is not listed in JotForm's own app directory, so there is nothing to install inside JotForm: you create an API key in JotForm, paste it in Flowgration, choose the form and map its questions. Flowgration then registers a webhook on that form and every new submission arrives within seconds, deduplicated by email and ready to trigger your journeys.

Prerequisites

• A JotForm account with at least one form. US and EU accounts both work; HIPAA accounts are not supported.
• A Flowgration account and an owner or admin role (members cannot connect integrations).
• Permission to create an API key in JotForm. If the form belongs to a JotForm team, use a key from an account that is a member of that team.

Step 1: create a JotForm API key

1. Sign in to JotForm. Click your avatar, then Settings, then the API tab (EU accounts: eu.jotform.com/myaccount/api; other accounts: www.jotform.com/myaccount/api).
2. Click Create New Key and name it "Flowgration".
3. Set Permissions to Full Access. Flowgration needs it to add its webhook to your form and to remove it when you disconnect. A Read Access key can still be used if you add the webhook by hand (see Troubleshooting).
4. Copy the key. You do not need to choose a data centre: Flowgration detects whether the key belongs to a US or an EU account.

Step 2: connect the form in Flowgration

1. In Flowgration open Connected apps and choose JotForm (or go straight to app.flowgration.com/app/integrations/jotform).
2. Paste the API key and press Verify key. Flowgration lists your forms, grouped by My forms and one group per JotForm team. If a form is missing, type its number in the box under the list.
3. Choose the form. Flowgration reads its questions and suggests a mapping.
4. Review the mapping: for each question pick the CRM field it fills, or leave it as Don't import. Map at least the email or the phone question.
5. Tick the confirmation that you have the right to store the people who submit the form, and press Connect form. Flowgration stores the key encrypted and registers its webhook on the form.
6. Send a test submission from your form. The contact appears in Contacts within seconds, and in Recent submissions on the JotForm page you can see whether each entry was saved.

What you can map

Each question can fill one CRM field. The list is read live from your own CRM, so a custom field you created a minute ago is already available.

• Core contact fields: first name, last name, email, phone, company, job title, address, city, country, postal code, website and notes.
• Full name: a JotForm Full Name question (first and last) or a single text answer is split into first and last name.
• Consent: map a checkbox to Marketing consent, Privacy policy accepted, Commercial communications, SMS or WhatsApp consent. A ticked box sets the flag (marketing consent also stores the date). An unticked box never removes consent a contact already gave.
• Your own custom fields. Checkbox answers with several choices are joined with commas, and multi-part answers such as an address are combined into the field you chose.
• Questions are matched by their number, so renaming a question's unique name in JotForm does not break the mapping.

What happens when someone submits

The contact is created or updated by email (a repeat email updates the same contact). Flowgration adds a Form submission entry to the contact's timeline, makes sure the contact has an opportunity, and fires your journeys: a journey whose trigger is Form submission starts, with the form number and the form name available. To restrict a journey to one form, put the JotForm form number (or jotform:<number>) in the trigger's Form ID. The mapped answers are available to the journey as the submission's fields.

Importing past submissions

Webhooks only deliver new submissions. To bring in earlier ones press Import past submissions on the connected form: up to 500 of the most recent entries are queued per run and become contacts within a few minutes. Running it twice never duplicates, and journeys are deliberately not triggered for imported history, so old leads do not receive today's automations.

Managing a connection

• Check connection verifies the key and re-registers Flowgration's webhook if someone removed it from the form.
• Edit mapping changes which question fills which field. It applies to new submissions; existing contacts are not rewritten.
• New address replaces the secret webhook address of a form (use it if the address leaked). The old one stops working immediately.
• Retry failed re-queues entries that could not be saved, including those parked because your plan's contact limit was reached.
• Disconnect removes Flowgration's webhook from the form and deletes the stored key. Contacts already imported are kept.

Other form tools (no JotForm needed)

Typeform, Tally, Google Forms through a script, your own website or any tool that can send a webhook can feed the same CRM. POST the answers as JSON to your private form address, which you can copy from Connected apps, JotForm, Other form tools (or read from GET /api/webhook/token). The contact is created or updated by email and your Form submission journeys fire. The full contract is in the API reference.

curl -X POST "https://app.flowgration.com/api/webhook/form/<your_webhook_token>" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "ana@example.com",
    "first_name": "Ana",
    "last_name": "García",
    "phone": "+34 600 000 000",
    "form_name": "Contact form",
    "form_id": "contact-1",
    "fields": { "message": "I would like a quote" }
  }'

Form intake in the API reference

How it works

On connect, Flowgration registers a webhook on your form. The address contains a secret token specific to that form, so JotForm needs no password and Flowgration can tell which organization and form a request belongs to without trusting anything in the submission. Each submission is stored first, then matched against your mapping and written as a contact; if something fails it is retried automatically with increasing delays, and what still cannot be saved is kept with its error so you can retry it. Only the fields you mapped are stored.

Troubleshooting

FAQ