Jotform Integration

The Jotform integration connects your Jotform account to your Hyperstack organization. With it you can:

• Map each Jotform form to a credential group.
• Pick which questions give the name and the email on the credential. Any question works, hidden fields too.
• Add a rule, so only some submissions issue a credential. For example: Score is at least 8.
• See every submission on the Logs tab, with the credential it issued or the reason it issued nothing.

You sign in to Jotform once, or paste an API key. Hyperstack adds the webhooks to your forms for you: you don’t copy a URL, and you don’t need Zapier.

​

Before you start

• Hyperstack: any plan. You must be an administrator of the organization.
• Jotform: a Jotform account. The API and webhooks are on every Jotform plan, the free Starter plan included. EU and HIPAA accounts work too.
• At least one credential group with its design, or let Sync forms create them for you.

One Jotform account connects to one Hyperstack organization. Hyperstack sees every form of that Jotform account.

​

Step 1: Connect Jotform

​

Or paste an API key

Use this if the sign-in window doesn’t work for you. Some browsers block a sign-in inside a window of another site, and Google sign-in can refuse it.

1. In Jotform, open Settings → API (jotform.com/myaccount/api).
2. Click Create New Key. Set its permission to Full Access. Hyperstack needs full access to add the webhooks to your forms.
3. Copy the key.
4. On the Connect Jotform page, click Or paste an API key, paste the key into Jotform API key, and click Connect with this key.

Hyperstack checks the key with Jotform before it saves anything. It never shows the key again.

​

Step 2: Map your forms to credential groups

• To map one form, click Choose group on its row, type to search, and pick a credential group.
• To map many forms at once, click Sync forms. Hyperstack creates a credential group for each form that is not mapped yet, named after the form, with the design you pick.

​

Step 3: Pick the name, the email and an optional rule

Each mapped form has a Name and email column. It says Matched by label until you pick. Then Hyperstack reads the form’s Email question and its Full Name question (or questions named First name and Last name). To pick the questions yourself, click the button in the Name and email column.

• Name: the question whose answer is the name on the credential. A Full Name question gives the first and the last name together.
• Add to the name (optional): a second question added after the first one. Use it for a form that asks for the first name and the last name in two questions.
• Email: the question whose answer is the email address. Hyperstack sends the credential there. A hidden field works too, so you can put the email in the form’s link.
• Only issue when (optional): pick a question, a comparison and a value.

For a multiple-choice or dropdown question, Hyperstack compares the text of the option. For a question with more than one answer, such as check boxes, the answers are joined with commas. Click Save. The column shows what you picked, for example Full Name · Email and Only if Score is at least 8.

​

Step 4: Turn on auto-issue

Click Turn on under Auto-issue on form submission. Hyperstack adds one webhook to each mapped form in Jotform. In Jotform, the webhook shows in the form builder under Settings → Integrations → Webhooks, which says Integration up and running!. Don’t edit or remove it there: Hyperstack manages it. Your own webhooks on the form stay as they are. Now, when someone submits a mapped form, they get that group’s credential. Hyperstack issues and publishes it at once, and sends the email if the group sends one.

​

Check what happened: the Logs tab

The Logs tab lists every submission that Jotform sends, for 90 days.

• Issued: a credential was created. Its ID shows in the Credentials column.
• Skipped: nothing was issued, and the line says why. For example: the rule wasn’t met, the email answer isn’t an email address, or the person already has a credential in that group.
• Failed: the call was refused, for example because it came to an old webhook address.

Click a row to see the full submission that Jotform sent.

​

Good to know

• One credential per email per group. If a person submits the form again, nothing new is issued.
• What Hyperstack keeps: an API key for your Jotform account and the account’s email. A credential keeps only the form, its name and the submission ID. Hyperstack doesn’t copy the form answers into the credential.
• Security: Jotform doesn’t sign its webhooks, so each webhook address has a secret of its own. When you disconnect, the secret is deleted, and Hyperstack refuses calls to the old address.
• Encrypted forms can’t issue credentials: Jotform sends their answers encrypted.
• API limits: Jotform’s free plan allows 1,000 API calls a day. Hyperstack uses a few when you open the forms page or map a form, and none for a submission once you’ve picked the name and email questions.
• Turn off auto-issue to stop issuing but keep your mappings. Hyperstack removes the webhooks from your forms.

​

Disconnect Jotform

Click the ⋯ button at the top right of the Jotform page, then Disconnect Jotform. Hyperstack removes its webhooks from your forms in Jotform and deletes your mappings. Credentials you already issued stay as they are. To also remove Hyperstack’s key in Jotform, open Settings → API in Jotform and delete the key.

​

Troubleshooting

Questions or problems: support@thehyperstack.com.