Jotform lists its integrations by app name: Google Sheets, Slack, HubSpot, PayPal, Dropbox, and a long tail after that. That list answers "can it connect to X", which is rarely the real question once a team is handling submissions every day. The real question is what travels across each connection, in which direction, at what moment, and what happens when something on the other end changes. This guide sorts the popular Jotform integrations by that question, using Jotform's own help pages as they read on October 8, 2026, so a team can decide which connection to add, which one to remove, and where the gaps will still need a person.
How many integrations there are, and why the count is the wrong place to start
Jotform's integrations directory currently invites visitors to "See 200+ integrations", while the boilerplate at the bottom of the same site still says 150+. Both numbers are on jotform.com today. The gap is not important in itself, but it shows how fast the catalogue grows and why a count tells a team very little.
Almost every connection in that directory does one of four jobs:
- Copy a submission into a table. Google Sheets, Airtable, Excel, database exports.
- Announce a submission to people. Slack, Microsoft Teams, email, SMS, WhatsApp Business.
- Create a record somewhere else. HubSpot, Salesforce, Zoho CRM, Mailchimp, a project board.
- Store the files. Google Drive, Dropbox, OneDrive, Box.
Payments are a fifth family, but they work differently because they sit inside the form and decide whether the submission happens at all.
The useful habit is to pick the job first and the app second. A team that needs "someone to know within five minutes" is choosing a notification connection. A team that needs "a record the sales pipeline can see" is choosing a CRM connection. Choosing by app tends to produce three connections that all copy the same data to three places, and none that answers the question of who is handling it.
The table below summarises what the most common connections send, based on the Jotform help and integration pages checked for this guide.
| Connection | What it sends | Direction | What it does not do |
|---|---|---|---|
| Google Sheets | Selected form fields, plus the Submission ID | Jotform to Sheets | Edits in the sheet do not change Jotform entries |
| Slack / Microsoft Teams | A message with the submission, to a channel or a person | Jotform to chat | Does not record who replied or whether it was handled |
| HubSpot | New contacts, deals, tickets or companies | Jotform to CRM | The form keeps no view of what sales did next |
| Webhook | The submission, posted to a URL you control | Jotform to your server | Requests time out after 30 seconds |
| Zapier | Whatever a Zap maps, to thousands of apps | Mostly Jotform outward | Each step is another moving part to maintain |
Google Sheets: the connection almost everyone adds first
The Google Sheets integration is the default answer to "where is all of this tracked". Jotform's help article on it describes a setup that is quick and mostly one-way. From the form builder you open the Integrations area, choose Google Sheets, sign in with a Google account, and then pick an action: create a new spreadsheet, or add a new worksheet to an existing one. All form fields are selected by default and can be unchecked, and there is an option to send submissions the form already holds. The Submission ID travels with the data, which matters later when a row needs to be matched back to the original response.
Three details on that help page are worth reading before a team builds a process on top of the sheet.
Changes in the sheet do not flow back. Jotform states plainly that edits in the Google Sheets spreadsheet do not affect the Jotform entries. If a coordinator types "replied" into a status column, the form never learns it.
The sheet's structure is fragile. Renaming column headings may break the integration, and adding filters can stop the spreadsheet from updating. Both are things a team naturally does once the sheet becomes its working list.
"Use existing spreadsheet" does not mean "use existing rows". Choosing an existing spreadsheet creates a new worksheet inside it rather than appending to the tab the team already uses. Comments under the help article show people expecting the opposite.
None of this makes the integration a bad choice. It makes it a copy, not a workspace. If the sheet is for reporting and a weekly look at totals, it fits well. If the sheet is where people mark who owns a response and whether it has been answered, every one of those marks lives only in the sheet, beside data that the form keeps writing below it. The usual result is a second set of columns that only some people fill in, and a filter that someone adds and someone else removes.
Chat notifications: fast to set up, silent about what happens next
Jotform's Slack integration page describes it as a way to "sync form submissions to Slack channels or teammates". The same family covers Microsoft Teams, Mattermost, WhatsApp Business notifications, SMS tools and Facebook Messenger. Setup takes a few minutes, and for many small teams it is the single change that most improves response time, because a submission stops sitting in an inbox nobody checks on Fridays.
The limit is built into the shape of a chat message. A message announces that something arrived. It does not say who took it, and it cannot change once the conversation scrolls past. Teams usually patch this with emoji reactions: an eyes emoji for "looking at it", a tick for "done". That works at ten submissions a week and starts to fail at fifty, because a reaction cannot be filtered, counted or reported on, and nobody searches a channel for submissions without a tick.
Two practical rules keep chat notifications useful:
- Send to a channel, not to a person. A notification sent to one teammate disappears when that person is on leave. A channel at least leaves a visible trail.
- Notify on the events that need a human. If every submission pings the channel, people mute it. If the form has a field that separates urgent requests from routine ones, conditional notifications for the urgent path are worth the extra setup.
The question to ask before adding another chat connection is whether the team needs to know sooner, or needs to know who is handling it. A notification solves the first. It does not touch the second.
CRM, email marketing and storage: creating records elsewhere
The HubSpot integration page says the connection can create new contacts, deals, tickets and companies automatically from a form. Salesforce, Zoho CRM, Pipedrive and similar tools sit in the same CRM category of the directory. Mailchimp and other email platforms add a respondent to a list. Google Drive, Dropbox and OneDrive receive uploaded files.
These connections are the right choice when the work genuinely belongs in the other system. A sales team that lives in HubSpot should not be asked to open the form tool to see new leads. A support team that works from a ticket queue should receive a ticket, not a spreadsheet row.
The trade-off is that the submission is now split. The answers live in the form tool. The follow-up lives in the CRM. Anyone looking at the form later sees responses with no indication of whether a deal was won or a ticket was closed, and anyone looking at the CRM sees records that started life somewhere they cannot open. For a single sales pipeline this is fine. For a mixed inbox, where some submissions are leads, some are support questions and some are job applications, each kind of response ends up in a different tool, and the question "did everything that came in last week get an answer" has no single place to be asked.
Storage integrations deserve one extra check. Jotform's pricing page states that if an account goes over its total submission storage, the oldest response is deleted to make room for new ones. Sending uploaded files to Drive or Dropbox is a sensible backup on any plan where volume is close to the limit.
Webhooks and Zapier: when the built-in list runs out
When no native connection does what a team needs, there are two routes.
A webhook posts each submission to a URL. Jotform's help article on webhooks notes a 30-second request timeout and warns that the receiving endpoint may reject a submission that is larger than it accepts. That means the receiving server has to answer quickly and do any slow work afterwards. A webhook suits a team with a developer who already runs a server and wants submissions inside its own application.
Zapier sits between Jotform and thousands of other apps, and its Jotform listing is one of the top results for this search. A Zap can take a submission, look something up, branch on an answer and write to several places. It is the fastest way to build something the native list does not cover. Each Zap, though, is one more thing that can stop working quietly when someone renames a field, and on Zapier's side tasks are metered separately from the Jotform plan.
Jotform also limits API calls by plan. The pricing page data shows 1,000 calls a day on the free plan and 10,000 on Bronze, which matters for any custom integration that polls for new data rather than waiting for a webhook.
The pattern that holds up best is to use webhooks and Zapier for moving data, and keep the decisions (who owns a response, what stage it is at) in one system that people actually look at.
What it costs to keep submissions flowing
Integrations themselves are included on Jotform plans, but the plan limits decide how far they reach. Jotform's pricing page, checked on October 8, 2026, lists these limits for monthly billing:
| Plan | Price per month | Forms | Submissions per month | Upload space |
|---|---|---|---|---|
| Starter (free) | $0 | 5 | 100 | 100 MB |
| Bronze | $39 | 25 | 1,000 | 1 GB |
| Silver | $49 | 50 | 2,500 | 10 GB |
| Gold | $129 | 100 | 10,000 | 100 GB |
Yearly billing lowers the monthly equivalent, and Jotform offers 50% off Bronze, Silver and Gold for nonprofits and educational institutions. Forms on the free plan carry Jotform branding.
For integrations, the submission column is the one that bites. Every submission that a connection copies into Sheets, Slack or HubSpot counts against the monthly allowance whether or not anyone acts on it, and a busy month can push a team up a tier for reasons unrelated to the number of people doing the work.
A different pricing model exists among form tools: unlimited forms and responses, priced only by how many people use the tool. Under that model, the integrations that matter shift. A Sheets connection becomes optional, because owner, stage and history can live on the response itself, and the remaining connections only need to announce arrivals and hand data to the systems that genuinely own it. The feature list of one such tool shows a Sheets connection that appends each new response as a row and then updates that same row when the stage changes, which closes the one-way gap described above. Its pricing page shows how the per-person model compares at a given team size.
A quick audit of the connections already running
Before adding anything, it is worth listing what is connected today. A short audit takes about twenty minutes:
- Open each form's Integrations tab and write down every active connection.
- Mark each one by job: copy, announce, create elsewhere, store, or pay.
- Find duplicates. Two connections doing the same job to different places is common, and usually one of them has been forgotten.
- Find the status columns. Anywhere a person types a status by hand (in a sheet, in a chat reaction, in a CRM note), write down where it is.
- Count those places. If status lives in more than one place, the team is reconciling by memory.
The result is usually a clear picture. Copy connections are fine. Notifications are fine. The trouble sits in step four, where the work of handling a response is spread across tools that each hold part of the picture.
What to change first
Pick the one connection where people type a status by hand, usually the Google Sheets tab, and decide whether that status should live on the response instead. If it should, try a tool that keeps owner and stage on each response and treats Sheets and chat as outputs; the demo of Halict shows that flow with sample responses. If it should not, rename nothing in the sheet, leave its filters alone, and add a channel notification for the urgent path.
Q1. Do Jotform integrations send changes back to the form?
Mostly no. Jotform's Google Sheets help page states that changes in the spreadsheet do not affect Jotform entries, and chat notifications are one-way messages. Data flows out of the form, and anything typed in the other tool stays there.
Q2. Why did my Jotform to Google Sheets integration stop updating?
Jotform's help article lists two common causes: renaming column headings, which may break the integration, and adding filters in Sheets, which can stop updates from appearing. Redoing the integration from the form's Integrations tab usually fixes the first, and reapplying the filters fixes the second.
Q3. Is a Jotform webhook better than Zapier?
They suit different teams. A webhook posts each submission straight to a server you run, with a 30-second timeout, so it needs a developer. Zapier needs no code and reaches thousands of apps, but each Zap is another moving part with its own task limits.
Q4. Do Jotform integrations cost extra?
The integrations are available on Jotform plans, but every submission they move counts against the plan's monthly limit: 100 on the free Starter plan and 1,000 on Bronze at $39 a month, as listed on October 8, 2026. Third-party tools such as Zapier bill separately.
Q5. Which integration should a small team add first?
A notification to a shared channel in Slack or Microsoft Teams, because it shortens the time before someone sees a submission. Add a Sheets copy only if someone needs totals, and keep the record of who is handling each response in one place.