Integration reference
Jotform Trigger and Action reference
Start FastHook Workflows from new form submissions and work with forms, questions, and response data.
Authentication
Connect with a Jotform API key from My Account → Settings → API. FastHook validates the key and stores it encrypted.
- Trigger account type:
api_key; reconnect byreplace_credentials. - Action connection type:
api_key; available modes: Connected Jotform account.
Create or reuse the account from a Trigger or Action dialog, or manage it under Settings → Connected accounts. See Authentication and permissions for scopes and access diagnostics, or Connected accounts for reuse, reconnect, revocation, and credential rotation.
Scopes and permissions
The Trigger manifest does not declare a fixed base OAuth scope list. Installation access, API credentials, or the selected event configuration can still control available resources.
Operation-specific requirements appear in the tables below. Custom event selections can add scopes dynamically, so the current Trigger or Action dialog remains authoritative for the exact consent request.
Use Jotform as a Trigger
The current provider manifest contains 1 available Trigger definitions. Representative definitions include:
- New Submission
View all 1 available Trigger definitions
| Trigger | Manifest key | Delivery | Additional scopes |
|---|---|---|---|
| New Submission | jotform.submission_created.instant | instant | None declared |
Choose the narrowest event definition that fits the Workflow. Configure provider-specific resource and event filters in the Source dialog before adding broader Workflow Filters.
Use Jotform Actions
The current Action manifest contains 8 operations. Representative Actions include:
- List Forms
- Get Form
- List Form Submissions
- Get Submission
View all 8 available Action definitions
| Action | Manifest key | Access and auth | Manifest rate limit |
|---|---|---|---|
| Get User | jotform.get_user | None declared FastHook-managed account | 1/second |
| List Forms | jotform.list_forms | None declared FastHook-managed account | 1/second |
| Get Form | jotform.get_form | None declared FastHook-managed account | 1/second |
| List Form Questions | jotform.list_form_questions | None declared FastHook-managed account | 1/second |
| List Form Submissions | jotform.list_form_submissions | None declared FastHook-managed account | 1/second |
| Get Submission | jotform.get_submission | None declared FastHook-managed account | 1/second |
| Create Form | jotform.create_form | None declared FastHook-managed account | 1/second |
| Custom API Request | jotform.custom_api_request | None declared FastHook-managed account | 1/second |
The Action editor reads its required permissions, fields, remote resource pickers, output schema, and rate limit from the provider manifest. Available fields can change with the selected operation and authentication mode.
Build a Workflow
- Create a Source using a Jotform Trigger definition.
- Create a Workflow with that Source as its Trigger.
- Add the required Jotform Action and select the connected account.
- Map Trigger or earlier-Step data into the Action fields with the field picker.
- Add a Filter, Paths, Delay, or Transformation when the route needs it.
- Activate the Workflow, produce a controlled event, and verify the run in Audit and in Jotform.
Troubleshooting Jotform
- The account is missing or cannot be selected
- Confirm the active FastHook team, provider, account status, and authentication mode. A disabled or revoked account cannot execute an Action.
- A resource picker is empty
- Verify that the connected provider identity can access the resource itself. OAuth consent does not add workspace, repository, channel, drive, project, base, or record permissions.
- The editor asks for additional scopes
- Reconnect the same account from the affected Trigger or Action so FastHook can request its current manifest scopes. Then reopen the editor and select the resource again.
- An active Workflow returns 401, 403, or a permission error
- Compare the selected operation’s access requirements below with the account recorded in Audit. Check provider-side membership and object access before repeating the Action.
- The provider returns 429 or a temporary 5xx
- Inspect the Step attempt and retryability in Audit. FastHook can retry temporary failures, but provider quotas and idempotency rules still apply.
Provider-specific checks
- Choose the data region that owns the account: Standard, EU, or HIPAA. FastHook sends API calls only to that Jotform host.
- FastHook creates a webhook for each form used by an active Source and protects its callback URL with an encrypted random secret.
- Jotform sends submission fields inside rawRequest. FastHook decodes that JSON and preserves the complete payload for mapping.
- Form questions determine the response fields, so New Submission uses an open output schema with stable form_id and submission_id fields.
- Jotform API quotas depend on the connected customer's plan.