The alpha testing program is now open to the public! We’d love to hear your feedback.Join!

Forms

Approvals & automations

Route responses through approval steps, act on new responses automatically, countersign them and print them as documents.

Basics

Setting up approvals

Approvals make each response wait for one or more people to approve it. To set them up, open the form's settings and go to Workflow → Approvals.

  1. Turn on Require approval. A first step called Manager is added for you.
  2. Give each step a Step name, and under Approvers type the email addresses of the people who can decide it. Any one of them can decide. Leave it empty to let anyone who can edit forms decide.
  3. Optional: choose Add step for more steps, and use the arrows to put them in order. The trash icon removes a step.
  4. Choose Save changes.

An approval chain needs at least one step: Forms won't save until it has one.

Concepts

How approval steps work

A new response to a form with approvals starts with the status Pending, and the first step's approvers get an email titled "Approval needed" with a Review response button. A response that's awaiting payment waits until it's paid, and then its approval starts.

  • Each approval moves the response to the next step, and that step's approvers get the same email.
  • When the last step approves, the response becomes Approved.
  • A rejection at any step closes the chain, and the response becomes Rejected.

After the final decision, the respondent gets an email saying their response was approved or declined, with any note you added. Approvers named on the step can decide it, and so can anyone whose role can edit forms: Owner, Admin, Manager or Member.

Pending responses are counted under Pending approval on the project overview.

Approvals

Approving or rejecting a response

To decide on a response, open it in the Response Inbox and choose the Approvals tab in its details. A dot on the tab means a decision is waiting.

  1. Check Approval chain: each step with its approvers, with the current step marked.
  2. Optional: under Decision, add a note.
  3. Choose Approve or Reject.

History lists each decision with who made it, the step and the note. A decided response can't be decided again. Until the form has approvals turned on, the tab says so.

Workflow

Automations

Automations act on each new response that matches your conditions. To add one, open the form's settings, go to Workflow → Automations and choose Add automation.

  1. Name the automation. The switch next to the name turns it on or off.
  2. Under When, choose All match or Any matches, and add conditions with Condition: a field, an operator and a value. An automation without conditions runs on every new response.
  3. Under Then, add one or more actions with Action.
  4. Choose Save changes.

The actions are:

  • Set status and Set priority. A response awaiting payment keeps that status.
  • Add tag: one tag, or several separated by commas.
  • Assign to: a teammate's email or name. When it matches a member of the project, they get a notification in the bell.
  • Send email to: emails the response's answers and a link to it to the addresses you type.
  • Call webhook URL: sends the response to another tool. See Integrations and API.

The trash icon removes an automation. Each run is recorded in the project's activity log.

Approvals

Countersigning a response

A countersignature adds your signature to a response someone signed, such as an agreement. Open the response in the Response Inbox, open the ⋯ menu in its details and choose Countersign.

  1. Draw your signature in the box.
  2. Type your Full name.
  3. Choose Countersign.

Your signature, name and the time are stamped onto the response and its printed record. Choose Countersign again to replace it. Countersigning needs a role that can edit forms.

To collect the respondent's signature first, add a Signature field (see Field types) and send the form with personal signed links (see Publishing and sharing).

Workflow

Document template

A document template turns each response into a formatted document, such as a contract or certificate, when you print it. Open the form's settings, go to Workflow → Document Template and turn on Use a document template.

  • Document title: the heading, like Agreement: {Full name}.
  • Body: plain text with merge tags such as {Full name}, {score}, {outcome} and {total}. A blank line starts a new paragraph.

The respondent's signatures and any countersignature are added under the text for you. The document prints as its own page, before the response's full record. Choose Save changes to keep it. With the template off, printing gives the full record only.

Workflow

Printing a response and saving a PDF

To print a response or save it as a PDF, open it in the Response Inbox and choose Print / PDF in its details. The printable record opens in a new tab, and your browser's print dialog opens once it's ready. Choose to save as PDF there, or use Print / Save as PDF at the top of the tab. To print several responses at once, select them in the Response Inbox and choose Export → Print / PDF, up to 100 at a time.

Each printed record has:

  • The form's name, the respondent, the response number, when it was submitted and its status.
  • The answers the respondent saw. Sensitive answers stay hidden.
  • The countersignature, and a receipt or invoice when the response has a payment.
  • An Audit trail: when it was submitted and edited, its score, priority, outcome and quiz result, browser details, who it was submitted on behalf of, the attestation, policy and consent records, and each approval decision.

Every print is recorded in the form's access log.