Make

Make (formerly Integromat) connects a form to thousands of other apps. Creating the webhook adds a workflow to your form that sends every new response to the scenario; move its Send to app step to send only after an approval, or only on one branch. Every delivery shows in the workflow’s runs, with what Make answered. It’s available on every plan.

Connect Nextforms in Make

Nextforms on Make is in review, so it’s available by invitation: accept the invitation once with your Make account, and Nextforms appears among your apps.

In a scenario, add the Nextforms → Watch responses module. Add a connection: sign in to Nextforms and allow access to the team you’re working in. That access is yours: it ends when you leave the team, and any editor can end it under Settings → Connected apps.

Make calls this a webhook: click Create a webhook, pick your connection, the form and a name in Nextforms (“Invoice to Xero”), then save the module. Keep that name: it is how a workflow you changed finds the scenario again. Save the scenario and turn it on; Make only accepts responses for a scenario that is saved.

What this does in Nextforms

Creating the webhook adds a workflow to the form, named “Make: “ and the name you gave it: Form submitted, then a Send to app step pointing at your scenario. Every new response now goes to Make, and the scenario runs at once. To send only some responses, move the step after an Approval step’s Approve branch, or onto one branch of a Route step. Deleting the webhook in Make removes that workflow, unless you changed or renamed it; then it stays, and a new webhook with the same name in Nextforms picks it up again, live at once unless its workflow has unpublished edits.

Event names

When one scenario should tell the steps apart, give each step an event name (“approved”, “declined”). It arrives in Make as Workflow → Event name, so a Router can branch on it.

What Make receives

Each answer, named after its question (its short name when it has one), as Answer and Raw value, plus the response number, the time, a link to the response in Nextforms, the payment outcome when the form takes payment, and the outcome and comment of an approval that came before the step. Some questions carry more:

• Choice: the Selected options as a list.
• Email: whether the address was Verified, when the question asks for it.
• Address: each part (lines, city, region, postal code, country code).
• File upload: Files, with each file’s ID, name, size and type.

Files

Add Nextforms → Download a file after the trigger and map Response ID and the file’s File ID. It hands the next module the file itself, so Google Drive, Dropbox or an email attachment can take it directly. For a question that takes several files, put an Iterator on its Files first to download each one.

Each file also comes with a download link, but that link stops working after a few minutes. Download a file works at any time, including runs Make queues or retries later.

Fixing problems

• A run failed with “not listening yet”: Make only accepts responses for a saved scenario. Save the scenario and turn it on, then use Retry on the run. If it isn’t listening for 3 days, the scenario is disconnected; add a new webhook with the same name in Nextforms to bring the step back.
• No workflow appeared: the webhook was created for another form, the form already had ten workflows, or it has a Send to app step whose app was disconnected. Add the scenario to a Send to app step yourself; the Workflows page names the scenario nothing sends to.
• Make’s access ended (removed in Settings, or the member who connected Make left the team): what the scenarios set up in Nextforms is removed, with the workflows made for them. A workflow you changed stays, and its Send to app step says the app was disconnected. To come back, reauthorize the Nextforms connection in Make, then add a new webhook in the scenario’s Nextforms trigger (the old webhook doesn’t register again on its own) with the same name in Nextforms. Steps that sent to the scenario follow it again; a step that still says it was disconnected needs the scenario picked again. Responses that failed meanwhile can still go: Retry them and choose Use the latest published version.
• A run failed with “The app did not take the response”: Make answered 404, 401 or 403, usually because the webhook or scenario was deleted without telling Nextforms. The run fails rather than waiting, and the team’s owners get an email. If the scenario still exists, turn it on and Retry the runs. If it answers like this for 3 days, it is disconnected as if its webhook had been deleted; a new webhook with the same name in Nextforms brings the step back.
• A run failed with another status: Make answered with an error; the step’s detail shows it. Nextforms retries a temporary failure a few times over several hours before giving up.