Jotform integrations and what each connection passes along

An integrations directory answers a question nobody actually has. It tells you whether a name appears on a list. What matters when a form goes live is narrower: at the moment somebody presses submit, what data leaves, where does it land, and does anything ever come back the other way.

Those three answers vary far less across Jotform's directory than the size of the directory suggests. Most connections do the same thing to a different destination. Knowing the small number of shapes, rather than the long list of logos, is what lets you decide whether a connection removes work or just moves it somewhere harder to see.

How many there are, and why the number moves

Jotform publishes three different figures depending on where you look. The footer on every page states 150+ integrations. The link at the bottom of the navigation menu says 200+ integrations. The category counts on the directory itself add up to well over eight hundred.

All three can be defensible. A single entry is filed under several categories, so a tool that sends data to a spreadsheet and posts a notification appears twice. The directory also filters by product, with separate views for Form, E-Sign and Workflows, which means a listing you are reading may describe a connection available to a workflow rather than to the form you are building.

The practical move is to ignore the headline number and read the category sizes, because those tell you where the depth is.

The shape of that table is the real information. Sales and marketing destinations dominate, which reflects what most forms are used for. The categories that stay small are the ones worth checking before committing, because a category with three or four entries means your particular tool is probably not among them.

The four jobs the popular connections do

The directory sorts by popularity, and the twenty or so entries at the top reduce to four jobs once you read the one line description under each name rather than the logo above it.

Keep the answers somewhere else. Google Sheets, Airtable, Google Drive, Dropbox, OneDrive and Box. The submission, or the file attached to it, is copied into storage you already use. Useful, and an archive rather than a queue.

Tell somebody. Slack, Microsoft Teams, Trello and Google Calendar. A message or an event appears where the team is already looking. This is the job most worth doing first, because a submission nobody sees is worse than one recorded untidily.

Create a record in a sales system. HubSpot, Salesforce, Pipedrive, Zoho CRM, ActiveCampaign, Keap, Mailchimp and Constant Contact. The respondent becomes a contact, a lead or a subscriber. The CRM category is the largest in the directory at 182 entries, which says plainly what most forms are for.

Take the money. PayPal, Stripe, Square, Authorize.Net and WorldPay UK among 40 payment processor entries.

Everything else in the directory is a variation on one of those four. There is no fifth job in which the form learns what happened after the handoff, which is the point the next sections turn on.

What a connection actually passes

Four examples from the directory cover most of the range, and the published descriptions are unusually plain about what each one does.

Google Sheets. Filed under Data Management. New submissions are added to a spreadsheet, and the listing also offers updating existing data on a sheet from a form. So this connection writes rows, and it can overwrite them. That second capability is what makes it usable as something more than an archive.

Slack. Filed under Communication. Submissions are sent to channels or as direct messages. Nothing is stored at the other end. The message is a notification with the content attached, which is why it works well for awareness and badly as a record.

Salesforce. Filed under CRM, and the most capable of the four. The listing covers adding leads, contacts or accounts, connecting to custom objects, prefilling forms with real time Salesforce data, generating prefill links with integration logs, and sending file attachments, PDFs and signed documents across. Prefill is the notable case on the whole directory where data travels into the form rather than out of it.

Webhooks. Filed under Automation. An HTTP post is sent to a URL you specify when a submission arrives. This is the raw version of everything above, and it is the one to reach for when the destination is a system you built.

Read those four together and the pattern is clear. A connection fires once, at submission, and copies the answers to somewhere else. That is genuinely useful and it is also the entire mechanism.

Native connections and brokered ones are not the same purchase

The Automation category holds 56 entries and includes Zapier, Make, Microsoft Power Automate, IFTTT, Pabbly Connect, Unito, Tray.io and plain webhooks. Those are not destinations. They are brokers, and appearing in the directory through one of them is different from a native connection in three ways worth knowing before you build a process on it.

The first is cost. A broker has its own plan and its own task or operation allowance, and a busy form consumes that allowance at the same rate it collects. A connection that is free inside Jotform can be the thing that pushes an automation subscription up a tier.

The second is failure. A native connection fails in one place. A brokered one fails in three, and the failure is usually silent: submissions keep arriving, the broker stops relaying, and nobody notices until a week of leads is missing from the destination. Whatever the connection, it is worth knowing where the log lives before you need it.

The third is latency and order. A broker polls or queues, so arrival order at the destination is not guaranteed to match submission order. For a notification that does not matter. For anything numbering or sequencing records, it does.

None of that argues against brokers. It argues for knowing which kind you have, because the directory presents both in the same grid.

Payment connections are metered separately

The Payment Processor category lists 40 entries, and Jotform publishes that it charges no additional transaction fee, so the only percentage taken is the processor's own published rate. That is a real advantage and it is also not the constraint that binds.

The constraint is that payment submissions are counted separately from ordinary submissions on every plan: 10 a month on the free Starter plan, 100 on Bronze, 250 on Silver and 1,000 on Gold. A form can be inside its submission allowance and outside its payment allowance at the same time, and the payment counter is the smaller of the two by a factor of ten.

So the question to ask about a payment integration is not whether your processor is on the list. With 40 entries it probably is. The question is whether the monthly payment allowance on your plan covers your busiest month, since that number, rather than the connection, is what stops a form taking money.

Where a connection is attached, and the newest category

Two details about setup change how integrations behave in practice.

Every integration page offers an Add to Form action rather than an account level switch, which means a connection belongs to a single form. Build the same intake twice and the second copy collects nothing anywhere until its connections are attached too. This is the most common reason a duplicated form appears to be losing submissions, and it is worth checking first whenever a destination stops receiving.

The second detail is that the Automation category now includes AI assistants. The directory lists a Claude entry described as connecting Jotform so that forms can be created, fields edited and submissions managed directly in chat, and a ChatGPT entry alongside it. That is a different kind of connection from the rest of the list, since the data movement is driven by a person typing a request rather than by a submission arriving. It is genuinely useful for building and for one off questions about stored responses, and it is not a substitute for a process, because nothing about it records who is handling what.

What no connection carries back

Everything in the directory is described in terms of submissions going out. Salesforce prefill is the one documented exception, and it brings data into the form rather than bringing status back.

That asymmetry is the thing to design around. Once a submission has been copied to a spreadsheet, a channel, a board or a CRM, the destination becomes the place where the work happens, and the form has no idea what happened there. Marking a lead as contacted in a CRM does not change anything in the form's submission table. Closing a card on a project board does not either. The two records drift apart from the moment of the copy, and the drift is discovered the day somebody asks what happened to a request from three weeks ago and gets two different answers.

There is a second pattern worth naming, because integrations are often the symptom rather than the fix. Jotform lists one user on Starter, Bronze, Silver and Gold, and describes Enterprise as its only multiuser platform. A team on any of the first four plans cannot give colleagues a login, so it pipes submissions to a shared spreadsheet or a Slack channel instead, and calls that the integration. It works, in the sense that everyone can see the responses. It does not give a response an owner, a status or a reply that stays on the record, because a spreadsheet row and a chat message cannot hold those things reliably once more than one person is editing.

Before adding any connection, the useful question is which system is the record for this piece of work. If the honest answer is both, the process will drift. If the honest answer is that the record is a spreadsheet because nobody else can log in to the form tool, the integration is patching a seat limit, and it is worth pricing the two solutions side by side.

What to change first

Write down, for each connection you already have, what it sends and in which direction. Anything that only sends out is an archive or a notification, not a place where work gets tracked, and treating it as the latter is where duplicated replies come from. If the reason data is being piped somewhere is that colleagues cannot log in, look at what response handling on one screen involves instead and try it against real submissions. Halict prices only the number of people, with forms and responses unlimited, which removes the reason to route responses through a spreadsheet in the first place.

Q1. How many integrations does Jotform have?

Jotform publishes 150+ in its site footer and 200+ in the navigation link to the directory, while the directory's own category counts add up to well over eight hundred. The difference comes from entries being filed under several categories and from the directory covering three products, with separate filters for Form, E-Sign and Workflows.

Q2. Does a Jotform integration send data both ways?

Almost all of them send one way, out of the form, at the moment a submission arrives. The Salesforce listing is the notable exception, since it can prefill a form with live Salesforce data as well as create leads, contacts and accounts. Nothing in the directory is described as sending a status back to the submission once the work is done elsewhere.

Q3. Is Zapier the same as a native Jotform integration?

No, and the distinction matters. Zapier, Make, Power Automate, IFTTT and Pabbly Connect appear in the Automation category as brokers rather than destinations, so they add a second subscription with its own task allowance, a second place for the connection to fail quietly, and no guarantee that arrival order matches submission order.

Q4. Do Jotform integrations cost extra?

The connections themselves are part of the plan, and Jotform states that it adds no transaction fee to payments, so a payment integration costs only the processor's published rate. Brokered connections are the exception, since the automation platform charges for its own usage. The limits that bind are the plan allowances, including payment submissions at 10 a month on the free plan.

Q5. Which integration should a small team add first?

Usually a notification to wherever the team already looks, since the cost of a missed submission is higher than the cost of an unsynced spreadsheet. After that, stop and decide which system holds the record before adding a second connection. Two systems both claiming to be the record is the failure that integrations create rather than solve.