Integrations · ProductivityConnect Jotform to Well
Index Jotform submission, form field, and respondent so questions about lead record and structured attribute answer themselves in conversation.
What Well pulls from Jotform
Jotform feeds submission, form field, respondent into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Jotform’s access.
| From Jotform | In Well | Relation | |
|---|---|---|---|
| Submission | Lead record | Becomes | |
| Form field | Structured attribute | Maps to | |
| Respondent | Person | Resolves to |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Jotform → Well
What Well does with your Jotform connection
Connect
Connect Jotform over OAuth (MCP DCR): Well registers a client through Jotform's OAuth Dynamic Client Registration and you approve on Jotform's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings submission, form field, and respondent in from Jotform on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.
Enrich
Well resolves each Jotform entity into lead record, structured attribute, and person, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Jotform lands in the workspace as lead record, structured attribute, and person you can search, chart, and automate.
Questions Jotform unlocks
Ask in plain language. Well answers from your connected Jotform connection, resolved against the rest of your stack.
Ask anything about your Jotform connection
Ask about your Jotform connection…
Connect Jotform in three steps
- 01
Authorise Jotform via MCP
From Well's Connections panel, search for Jotform and click Connect. Well discovers Jotform's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Jotform's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.jotform.com/mcp-app
- 02
Map your entities
Well's MCP client discovers submission, form field, and respondent from Jotform that Jotform's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
- 03
Use the data
Ask questions in conversation, build records tables, or let agents act on Jotform records. Because Jotform ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes
MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Jotform records happens in the background.
How Jotform stays secure with Well
Well connects to Jotform's MCP server (mcp.jotform.com/mcp-app) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Jotform secret. Tokens are scoped to the submission, form field, and respondent Jotform exposes and refreshed server-side. Reads only, Well cannot modify or delete Jotform records.
- granted
Read Jotform records
Resources the Jotform MCP server exposes, scoped by your OAuth approval.
- granted
Resolve submission, form field, and respondent across your stack
Match identifiers in Jotform against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Jotform records
Not granted; Jotform is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Jotform passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about Jotform and Well
From Well, open Connections, find Jotform, and click Connect. Well discovers the OAuth metadata at mcp.jotform.com/mcp-app/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Jotform's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in submission, form field, and respondent from Jotform and reshapes each entity into your workspace: submission becomes lead record; form field becomes structured attribute. Every record arrives with the source identifier preserved, so Jotform stays the source of truth while Well lets you query the data alongside the rest of your stack.
Jotform items linked to engineering issues, deploys, or revenue commitments inherit those joins in your workspace. The product roadmap question "what's blocking enterprise rollout this quarter" returns the Jotform items, the engineering work they depend on, and the customers waiting on the outcome, all in one answer.
Well watches for updates to submissions and applies them on the next sync, preserving the original workspace identifier so anything downstream (records tables, conversation history, agent runs) keeps pointing at the right lead record. Edits flow in incrementally; nothing is duplicated, and the Jotform source identifier is retained on every revision.
Well combines live Jotform events with periodic reconciliation reads of submission, form field, and respondent. New rows appear within seconds when Jotform pushes them; periodic reads catch anything a push missed. The first connect backfills history from Jotform in the background.
Open Connections > Jotform in Well and click Disconnect. Well calls Jotform's token revocation endpoint and stops calling Jotform immediately on its side; provider-side propagation to Jotform's admin panel varies by provider. The submission, form field, and respondent Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
Jotform records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.
Pairs well with Jotform
More in Productivity
Asana
Connect Asana to Well to sync tasks, projects, and team workflows.
Atlassian
Connect Atlassian to Well to sync tasks, projects, and team workflows.
Circleback
Connect Circleback to Well to sync tasks, projects, and team workflows.
ClickUp
Connect ClickUp to Well to sync tasks, projects, and team workflows.
Popular cross-category
Ready to connect Jotform?
Connect once. Every submission, form field, respondent from Jotform becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.