Skip to main content
A form collects answers from your team or your clients. Each submission starts every active workflow connected to it.

Build your first form: creating it, adding fields and their Field IDs, previewing it, connecting a workflow and sharing the link (1:27).

The form designer for New starter request: the Fields list on the left, the Form Authentication bar set to Microsoft authentication above a New starter section with First name, Last name, Start date and Department fields, and Field Properties on the right showing Field ID department, Label Department, Required field ticked and the options Sales and Finance.

The form designer: fields on the left, the form in the centre, the selected field's properties on the right.

​
Build a new starter request form

Client staff use this form to request a new user. Microsoft sign-in tells Triggr which client they belong to, so each client needs a microsoftTenantId variable (Clients and variables).
1

Create the form

In Forms, click New Form, enter New starter request and click Create Form.
The Create New Form dialog with Form Name New starter request, and Cancel and Create Form buttons.
2

Add the fields

Drag each field onto the canvas, click it, and set its Label, Field ID and Required field. For Department, type each option’s label and value.Workflows read each answer by its Field ID, such as {{ ctx.params.firstName }}, so replace the default property1, property2… before you build the workflow. Click Save in the bar at the bottom of the designer.
3

Require Microsoft sign-in

Click Form Authentication, choose Microsoft and click Save.
The Form Authentication panel with Authentication Type options None, Password, Microsoft, Google and Internal, Microsoft selected, and Visibility toggles List on Homepage, Restrict to usernames, Restrict to groups and Restrict to group names, all off.
4

Connect a workflow

In your workflow, click the Trigger, set Trigger Type to Form, choose New starter request and click Save. Only Active workflows start from a form.
The Trigger panel with Trigger 1 set to Trigger Type Form and Form New starter request, collapsed Trigger 2 and Trigger 3 entries, and an Add Trigger button.
5

Test as a client user

Click Share Form > Impersonate, pick a Client and a Microsoft user, and click Open as this user. Submitting runs the workflow for real.
The Share Form dialog on the Impersonate tab with Client set to Acme Corp, a Microsoft user search box, Jane Doe selected from a list of users with their email addresses, and an Open as this user button.
6

Share the link

In Share Form, click Copy next to Public Form URL and send it to the client. With a Custom Forms Domain (Settings > Branding), the link uses your own domain.
The Share Form dialog on the Public Form tab, with Webhook Trigger and Impersonate tabs, a Public Form URL on forms.yourmsp.com, a Copy button and an Open in new tab link.

​
Who can open a form

Form Authentication lets in anyone (None), anyone with the password (Password), client staff who sign in with Microsoft or Google, or your own team (Internal). Only Microsoft, Google and Internal with Manually Set Client tell the workflow which client the person belongs to; see Form authentication. Send your clients’ staff the guides for your clients.

​
See submissions

Click Submissions in the designer header or on the form’s row. It lists the last 24 hours until you change Date Range. Click View on a submission for its Data and its Metadata, including who signed in, and untick Pretty Format (Show Display Values) to see each answer by Field ID, as your workflow receives it.

​
Troubleshooting

No client’s microsoftTenantId matches the person’s tenant, or they aren’t in the usernames or groups you restricted the form to.
Preview never submits. Test with Share Form > Impersonate or the Public Form URL instead.

​
Go further

  • Field reference: every field type and its settings.
  • Dynamic options: fill a dropdown from a workflow, Microsoft or an integration, and reload it when another answer changes.
  • Conditional fields: show or hide fields and sections based on other answers.
Next: Introduction to workflows.