Jotform Sign
for LuumenAI
Read Jotform forms and submissions, and register webhooks with approval
Connect the Jotform account behind your Sign workflows and ask about it in plain language. Luumen reads form schemas, submissions, uploaded files, and webhook registrations for context, then registers or removes a callback, or files a submission, as a previewed step. Dedicated Sign document creation, signer management, and completed-document download are not part of Jotform's public API, so they are out of scope here.
The Jotform Sign toolbox
10 tools: 6 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Form SchemaInspect a form's metadata, properties, and question definitions so an agent can understand its fields.
- ReadGet SubmissionReturn one ordinary Jotform submission by ID with its question-ID-keyed answers and workflow status when present.
- ReadList Form FilesList uploaded-file metadata associated with a Jotform form.
- ReadList FormsReturn one page of forms visible to the connected Jotform account for ID discovery; results may include soft-deleted forms and are not classified as Jotform Sign assets.
- ReadList Form WebhooksList webhook registrations for one Jotform form as webhook IDs and callback URLs.
- ReadList SubmissionsReturn one page of ordinary Jotform submissions across the account or for one form, including answer maps and workflow status when present.
- WriteCreate SubmissionCreate an ordinary Jotform submission from simple question-ID answers. Approval by default
- WriteDelete Form WebhookDelete one general Jotform form webhook registration by its object-key webhook ID and return the registrations that remain. Approval by default
- WriteDelete SubmissionDelete one ordinary Jotform submission by ID. Approval by default
- WriteRegister Form WebhookRegister an HTTPS callback URL to receive general Jotform form-submission notifications; this does not configure or guarantee a dedicated Jotform Sign event stream. Approval by default
One prompt, start to finish
What a governed Jotform Sign run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create submission, delete form webhook, delete submission, register form webhook — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Jotform Sign — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
ConfluenceSOPs and runbooks that become skills the whole team can run.
NotionRunbooks in Notion, followed and turned into skills.
SharePointRead SharePoint sites for context, then change files and permissions on approval.
Google DriveSearch Drive for the file you need, then write the change back as an approved stepPut Jotform Sign to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.