Make

Make (formerly Integromat) builds visual scenarios that connect FormGrid to hundreds of other services. A scenario starts with the Watch Responses module and then routes, filters, and transforms the answers however you like.

You start the connection in FormGrid and finish it in Make, which is also where you choose what happens to each answer.

Before you start

Publish your form. Make reads your questions from the published version, so an unpublished form gives it nothing to work with.

Setting it up

1. Open your form and go to the Connect tab
2. Click Connect next to Make. FormGrid shows you a connection key
3. Copy the key, then follow the Add FormGrid to Make link
4. Create a scenario and add the FormGrid app
5. Choose the Watch Responses module
6. Click Create a connection, name it after the form, paste the key into Connection Key, and click Save
7. Turn the scenario on, then submit a response so Make learns the shape of your data

The link in step 3 adds FormGrid to your Make account. It only needs doing once, and it is what makes FormGrid available as a module.

There is no form to pick in Make. The key belongs to the form you created it on, so the module watches it automatically. When Make asks you to name the connection, naming it after that form is worth doing: the form’s title is shown under the connection on your Connections page, but the name is yours to choose.

Note: The key is shown once, when you create it. If you lose it before pasting it in, disconnect the row in the Connect tab and connect again for a new one.

How it works

Every time someone submits your form:

1. FormGrid sends the response to your scenario
2. The scenario runs, with every answer available to the modules after it
3. The delivery is recorded in the form’s event log

A delivery that fails is retried 5 times over the following day: after 5 minutes, 30 minutes, 1 hour, 6 hours, and 1 day.

What your scenario receives

Field	What it is
Response ID	The ID FormGrid gave the response
Form title	Your form’s name
Form version	Which published version was filled in
Submitted at	When the response came in
Response URL	A link to the response in FormGrid
Your questions	One per question, under the label you wrote

File uploads arrive as links Make can download, so they can be attached to an email or saved to cloud storage.

A question inside a repeat group is answered once per repetition, so the picker labels it (all repetitions) and every answer arrives as one value, separated by commas: Ada, Grace, Alan.

Connecting more than one form

A key works for one form only. To automate a second form, open that form’s Connect tab, connect Make there too, and add its key in Make as another FormGrid connection.

Each connection shows the form it belongs to, so you can tell them apart when a scenario asks which one to use. It also means a scenario can only ever reach the form you connected it to.

Using more than one scenario

Each connection carries one scenario. To build a second scenario on the same form, connect the form again in the Connect tab for a second key, and add that as its own connection.

The form then has two rows in the Connect tab, one per scenario. If you reuse a connection that is already in use, Make tells you so rather than quietly taking the first scenario’s place.

Watching and pausing

Each connected scenario appears in the form’s Connect tab as its own row, showing what it is doing:

• Open in Make while responses are being delivered
• Inactive while nothing is, whether the scenario is not set up yet or has been switched off
• Check again re-reads the state, which is useful right after you switch a scenario on

The switch on the row is FormGrid’s side of it: Make decides whether the scenario runs, and this decides whether the form sends to it. Both have to be on. Switch the row off to pause a scenario without touching anything in Make.

Note: Turning the scenario off in Make and on again clears a pause you set here.

When something is not working

Open the row’s menu and choose Event log to see every delivery, including the exact data that was sent and the reason for anything that failed.

• The scenario is on but the row says Inactive. Click Check again. Make registers the scenario when you switch it on, and the row catches up from there.
• Your questions are missing in the mapping. Publish the form, then reopen the module.
• Nothing arrives when you submit. Check both switches: the scenario in Make and the row in FormGrid.
• A scenario you deleted is still listed in FormGrid. Deleting a scenario while it is switched on does not always tell FormGrid to stop. The row clears itself after a few rejected deliveries, and the reason appears in the event log.

Disconnecting

To stop a scenario for a while, switch the row off in the Connect tab, or turn the scenario off in Make. Either way the connection and its key stay valid, so switching it back on resumes delivery with nothing to paste.

To cut Make off for good, open the row’s menu and choose Disconnect. This revokes the key, and the scenario using it stops working. Connecting again issues a new key, which you would have to paste into Make.