Loading…
Productivity · Integration Guide5.0/5.0 on Upwork · Top Rated
Jotform SharePoint integration
Jotform to SharePoint, wired so submissions become documents or list items in the right library instead of sitting in a form tool nobody in IT checks.
Buri IlterEx-Jotform engineering lead · LinkedIn
SharePoint is where enterprise teams store documents, track project data, and enforce the folder structures and permission hierarchies that IT spent weeks designing. The problem it creates is intake: information still walks in through email, shared drives, and form tools that sit outside SharePoint entirely. Connecting Jotform to SharePoint means submissions—and their file attachments—land where IT expects them instead of accumulating in a separate form tool nobody in operations checks.
Jotform doesn't have a native SharePoint connector. The integration is done through Microsoft Power Automate or Zapier, both of which sit between Jotform's webhook output and SharePoint's API. Power Automate is the better choice for teams already in the Microsoft ecosystem because it handles authentication, triggers, and SharePoint's internal column types more gracefully. Zapier works for simpler setups but hits limits on file handling and nested folder routing.
This page covers how to wire Jotform submissions into SharePoint lists and document libraries, how to map form fields to SharePoint columns, where the permission model fights you, and what breaks when you scale past a dozen forms.
How it works
How Jotform and SharePoint connect.
- 01
Set up the Jotform webhook or use Power Automate's Jotform trigger
Power Automate has a built-in Jotform trigger ('When a new submission is received') that authenticates with your Jotform API key. Alternatively, configure a Jotform webhook that POSTs submission data to a Power Automate HTTP trigger or a Zapier catch hook. The native trigger is easier to set up; the webhook approach gives you more control over payload structure and works across automation platforms.
- 02
Configure the SharePoint action (create list item or upload file to library)
Choose between two SharePoint actions: 'Create item' writes form data as a row in a SharePoint list; 'Create file' uploads a document (generated from submission data or a file attachment) to a document library. For forms with file uploads, the document library route is usually what you want. For structured data like project requests or HR submissions, a list is cleaner. Some workflows use both.
- 03
Map form fields to SharePoint columns and metadata
Each Jotform field maps to a SharePoint column. Text fields map to text columns, dropdowns map to choice columns, dates map to date/time columns. The mismatch point is SharePoint's internal column names versus display names—Power Automate uses internal names, and they don't always match what you see in the SharePoint UI. Test the mapping with a single submission before turning the flow on for real traffic.
- 04
Set permissions and folder routing
SharePoint's permission model is inherited: folders inherit from their parent library, and libraries inherit from the site. If you need submissions routed to different folders based on form data (e.g., department or project), configure dynamic folder paths in the 'Create file' action. Set the folder permissions in SharePoint beforehand—Power Automate runs under the flow owner's credentials, so the flow owner needs write access to every target folder.
Common workflows
What Jotform plus SharePoint is actually good at.
- 01
Document intake to SharePoint library
Client onboarding or application form collects signed documents, IDs, and supporting files. Power Automate takes each file attachment from the Jotform submission and uploads it to a SharePoint document library under a folder named after the submitter. Metadata columns (submitter name, submission date, document type) are populated from form fields so the files are searchable inside SharePoint.
- 02
HR form submissions to employee records
New hire paperwork, benefits enrollment, and policy acknowledgements flow through Jotform. Each submission creates a list item in a SharePoint HR list keyed on employee ID, with columns for form type, status, and manager. File attachments (signed forms) go to a corresponding folder in the HR document library. Managers see only their own employees' records through SharePoint's item-level permissions.
- 03
Project requests to SharePoint list
Internal project request form writes directly to a SharePoint list that the PMO uses as their intake queue. Columns capture project name, sponsor, priority, estimated budget, and target date. Power Automate sends an approval notification to the PMO lead when a new item is created. The list replaces the shared spreadsheet that was losing requests.
- 04
Vendor submissions with file attachments
Vendor registration and qualification forms collect company details, insurance certificates, and W-9s. Submissions create a SharePoint list entry for the vendor and upload attached documents to a vendor document library sorted by vendor name. Compliance team gets an automated email with links to the new files so they can review certificates before they expire.
What breaks
Edge cases that bite in production.
Risk 01
Power Automate licensing requirements (premium connector)
SharePoint is a standard connector in Power Automate, but the Jotform trigger is a premium connector. If your organization only has Office 365-level Power Automate licenses (included with most business plans), you cannot use the Jotform trigger without upgrading to a per-user or per-flow premium license. Workaround: use a Jotform webhook posting to an HTTP trigger (standard connector), which avoids the premium connector cost but requires you to parse the JSON payload yourself.
Risk 02
SharePoint column type mismatches
SharePoint's choice columns, lookup columns, and managed metadata columns don't accept arbitrary strings. If your Jotform dropdown sends 'Full-time' but the SharePoint choice column has 'Full Time' (no hyphen), the item creation fails silently or writes a blank value. Date fields need ISO 8601 format. Number fields reject commas in large numbers. Audit every field-to-column mapping and test with real form values before going live.
Risk 03
File size limits in document libraries
SharePoint Online document libraries accept files up to 250 GB, but Power Automate's file handling has practical limits. Large file uploads through the 'Create file' action can time out on files above 50 MB. Jotform's file uploads are stored as URLs in the submission payload—Power Automate needs to download the file from Jotform's CDN first, then upload it to SharePoint. For files over 50 MB, use SharePoint's chunked upload API or accept the file as a URL link in a list item instead.
Risk 04
Permission inheritance on nested folders
If your workflow creates nested folders (e.g., /Vendor Documents/2026/June/Vendor Name/), each new folder inherits permissions from its parent. If you break inheritance at the library level to restrict access, every dynamically created folder inherits that restriction. If you need per-folder permissions (e.g., each vendor sees only their own folder), Power Automate can set item-level permissions after creation, but this adds latency and requires the flow owner to have full control of the library. Test permission propagation before trusting it with real data.
Hit one of these edge cases?
I ran into them for five years on the Jotform product team. Book a free call and I'll tell you exactly how to handle your SharePoint setup, or send me the details first.
When not to use
When Jotform plus SharePointisn't the right call.
If your organization runs on Google Workspace instead of Microsoft 365, skip SharePoint and use the Google Drive or Google Sheets integration. OneDrive is sufficient if you just need file storage without SharePoint's permission hierarchy, metadata columns, or list capabilities. And if you only need structured data in a spreadsheet (no document library, no file attachments, no permissions), writing to Google Sheets or Airtable is simpler and faster to set up than routing through Power Automate into SharePoint.
Kits that use this
hr
sales
agency
Automation kits built on SharePoint.
Job Application Pipeline Kit
Knockout screening, resume routing, candidate tracking. ATS-free for under 10 hires a year.
B2B Quote Automation & RFP Intake Kit
Quote requests that qualify themselves: conditional scope capture that routes to the right rep
Client Onboarding Kit
The onboarding flow every agency wishes they had before their first client was late with assets
Frequently asked
Questions I get before setting this up.
How do I connect Jotform to SharePoint?
Use Microsoft Power Automate or Zapier as the bridge. In Power Automate, add the Jotform trigger ('When a new submission is received'), authenticate with your Jotform API key, then add a SharePoint action ('Create item' for lists or 'Create file' for document libraries). Map the form fields to SharePoint columns and turn on the flow. Zapier follows the same pattern with Jotform as the trigger app and SharePoint as the action app.
Should I use Power Automate or Zapier for the Jotform-SharePoint integration?
Power Automate if you're already in the Microsoft 365 ecosystem. It handles SharePoint authentication natively, respects your organization's conditional access policies, and doesn't require a separate Zapier account. Zapier is fine for simple list-item creation without file handling. For anything involving document libraries, file uploads, or nested folder routing, Power Automate is more reliable and doesn't require workarounds for file downloads from Jotform's CDN.
Should I use a SharePoint list or a document library?
Use a list for structured data without file attachments: project requests, HR records, vendor details. Use a document library when you need to store files (PDFs, images, signed documents) with metadata. Many workflows use both—a list for the structured record and a document library for the attached files, linked by a shared identifier like submission ID or employee number.
What are the file size limits for uploading Jotform attachments to SharePoint?
SharePoint Online accepts files up to 250 GB. The practical bottleneck is Power Automate: file uploads through the 'Create file' action can time out on files over 50 MB. Jotform stores uploaded files on its CDN and returns URLs in the submission payload. Power Automate downloads the file first, then uploads it to SharePoint. For large files (50 MB+), either link to the file URL in a list item instead of uploading, or use SharePoint's chunked upload API outside of Power Automate.
Want this wired up without the reading?
Free 20-minute call. I'll tell you which workflow fits your SharePoint setup and what it would take to build, or you can send me the details first.