Connect Jotform to WPOS with an API key. Embed forms, clone them for landing pages and understand the permissions needed to create or edit forms.
A campaign often needs a form that already exists in Jotform, or a variation of it for a new audience. WPOS can use the connected form account to place the form on WordPress and work with supported form-management tasks while Jotform handles its form service.
A Jotform account. The free tier works, with limits on forms and monthly submissions. A Jotform API key with Full Access if you want WPOS to create or edit forms. Check your Jotform region. Accounts on EU or HIPAA data residency use different API endpoints.
Choose Set up for Jotform in Settings → Connectors. Create a key under Jotform My Account → API and provide it in the connection panel. Use Full Access for create or edit work, and check the API endpoint for your account’s region.
Clone this Jotform for the new landing page, then add it to that WordPress page and check that the embedded form loads.
Load the page at desktop and mobile widths, submit a test entry and confirm it reaches the intended Jotform form. Check the connected account’s submission and form limits.
Use the connected account for a specific task, with the permissions and plan available to you.
Add an existing Jotform to a WordPress page and style the surrounding page to fit the site.
Clone a form for a new landing page so the campaign can use its own version.
Use supported label-management actions to keep the connected forms organized.
Verify the embedded form and its submission destination before using the page for a campaign.
Connection requirements, workflow limits and troubleshooting from the WPOS documentation.
Connect Jotform to WPOS with an API key. Embed forms, clone them for landing pages and understand the permissions needed to create or edit forms.
Choose Set up for Jotform in Settings → Connectors. Create a key under Jotform My Account → API and provide it in the connection panel. Use Full Access for create or edit work, and check the API endpoint for your account’s region.
A valid read-only key can connect successfully while form-editing requests fail. The form remains a Jotform service, so its plan limits and region settings still apply.
The most common Jotform problem. New keys default to Read Access, and nothing in WPOS warns you. The connection reports Connected either way, because the key is valid, just limited. Raise the key to Full Access in Jotform and reconnect.
Correct behaviour. Jotform has no managed authorization, so WPOS asks for credentials before it can connect anything.
Check for whitespace copied along with the key, confirm the key still exists, and confirm your account region matches.
Connect your account and give WPOS a specific WordPress task. Start free with 5,000 credits, one live site and a staging sandbox.
Start free