Skip to main content
The common use is a client who fills a Jotform form to ask for work, such as a new starter, a leaver or a new device. The agent finds the submission behind the ticket, reads each answer against its question, does the work with its other tools, and marks the submission handled.
Automatically enabled when you configure Jotform permissions in your agent workflow.

​
What it does

  • Find the submission behind a ticket, by its id, by the form and the answers, or by a search across all forms
  • Read a submission’s answers, each against its question, and the files uploaded with it
  • Mark a submission read or flagged, edit an answer, add a submission, or delete one
  • List new submissions of a form for a scheduled agent that opens a ticket for each
  • Read forms with their questions and properties, and create, clone, change or delete a form
  • Read and create reports, read, add and delete webhooks, and organize forms in folders and labels
  • Read the account’s plan usage against its daily API limit

​
Permission groups

​
Safety Controls

These always ask a technician, whatever the profile:
  • Deleting a form, which deletes every submission on it
  • Changing the account’s settings, which can change the account’s email and its security question and answer
Neo does not sign in to Jotform with a password, sign out, or create Jotform accounts: it calls Jotform with the API key on the Jotform tile. Neo removes from what Jotform returns any field whose name ends in password, secret, token, apikey, api_key or securityanswer, and refuses a change that sends such a removed value back. Answers in a submission come back as the person typed them.

​
Setup

See Connecting Jotform to Neo.