Resources · Make integration

GoCanvas Make integrationAutomate GoCanvas with Make.

What if every completed GoCanvas form started the next task on its own? The GoCanvas Make integration gives you 7 modules: 1 instant trigger on submissions, 5 actions and 1 search around dispatches. This page is for field and ops teams: connect your account, then build a first working scenario.

Try the GoCanvas integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the GoCanvas Make integration let you automate?

The GoCanvas Make integration links your GoCanvas account to Make, a visual tool where you chain apps together without writing code. Make reacts the moment a mobile form is submitted, and it can create, read, change, find or remove dispatches for you, so paperwork from the field turns into follow-up work without anyone retyping it.

Submissions that reach the office right away. Watch Submissions hands each completed form to Make as soon as the worker sends it. From there, a scenario (the automation you build in Make, a chain of steps) can push the answers into a spreadsheet, a CRM or a team chat.

Jobs sent to the field from another tool. When a request lands in your booking system or your helpdesk, Create a Dispatch sends the matching assignment to GoCanvas. Update a Dispatch keeps it aligned if the request changes, and Delete a Dispatch removes it when the job is cancelled.

A clean view of what is open. Search Dispatches pulls back the dispatches that match what you are looking for, and Get a Dispatch reads one in full when you already know which one you need.

What Make does not do here: the listed modules only cover dispatches, and the single trigger only watches submissions. For any other part of the GoCanvas API, the Make an API Call module reuses the same connection. If you are still choosing a platform, the n8n vs Make comparison lays out the criteria, and the Make review covers the tool itself. To learn the editor step by step, see the Make training.

Connect

How do you connect GoCanvas to Make?

  1. 01

    Create an API key in GoCanvas

    You need an active GoCanvas account. Open Account, then Account Settings, scroll to Security Settings and pick Settings by API Keys. Turn on Enable API Keys, click Create API Key, name it, choose a department or All, save and copy the key.

  2. 02

    Add a GoCanvas module in Make

    In your scenario, add any GoCanvas module and click Create a connection. A connection is your GoCanvas account linked to Make once, then reused by every GoCanvas module. The Connection name field is optional, but a clear name helps when you have several accounts.

  3. 03

    Paste the key and save

    Paste the API key you copied from GoCanvas, or follow the instructions Make shows on screen, then confirm. Once the connection exists, Make can read your GoCanvas data and fill the module fields with real choices instead of empty boxes.

First scenario

Your first scenario with GoCanvas and Make

GoalWhen a new job request appears in another app, Make creates the matching dispatch in GoCanvas.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to place the first module. This first module is the one that decides when the whole chain starts.

  2. 02

    Pick the app that holds the requests

    Search for the app where new jobs land, a form tool or a spreadsheet for example, and choose its trigger. Link that account with Create a connection and pick the list or sheet to watch.

  3. 03

    Add Create a Dispatch

    Click the + on the right of the first module, search GoCanvas and choose Create a Dispatch. Map the request details from the previous module into the dispatch fields Make displays once your connection is ready.

  4. 04

    Test with Run once

    Add a sample request in the source app, then click Run once. Each module shows the bundles it received, a bundle being one item passed along. Check that the new dispatch appears in GoCanvas.

  5. 05

    Schedule and switch it on

    Open the clock on the first module: a new scenario runs every 15 minutes by default, and the Free plan cannot go lower. Pick your interval, then switch the scenario on so it keeps working without you.

Triggers

What can start a GoCanvas scenario?

1 module starts a scenario when something happens in GoCanvas. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by GoCanvas as soon as it happens.

GoCanvas1Watch Submissions

Watch Submissions

Instant trigger

In Make“Triggers when a new submission has been got.”

Watch Submissions starts your scenario each time a worker sends a completed form, so the answers leave the phone and reach your other tools without anyone exporting them. Every submission becomes one bundle you can map into the next module.

How it fires
instant, GoCanvas calls Make through a webhook as soon as the submission happens, with no polling interval to wait for.
When to use it
an inspection or delivery form whose results should land in a spreadsheet, a CRM record or a message to the office.
Watch out
create the webhook before the connection, otherwise the trigger stays silent.
Modules

What can Make do in GoCanvas?

GoCanvas gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

GoCanvas1

Create a Dispatch

Action

In Make“Creates a new dispatch.”

Create a Dispatch puts a new assignment in GoCanvas from data another app already holds, so the field worker receives the job without anyone typing it twice, which is why it usually closes a scenario that starts in another tool.

When to use it
a customer books a visit in your scheduling tool and the technician should see it in GoCanvas.
Watch out
each run creates a new dispatch, so a test repeated with Run once leaves duplicates to clean up.
GoCanvas2

Delete a Dispatch

Action

In Make“Deletes a dispatch.”

Delete a Dispatch removes an assignment from GoCanvas, which keeps the worker's list free of jobs that no longer exist. It needs to know exactly which dispatch to remove, often found by a search placed just before it.

When to use it
a booking is cancelled in the source app and the visit should disappear from the field.
Watch out
test it on a throwaway dispatch before switching the scenario on, so a wrong mapping never removes a real job.
GoCanvas3

Get a Dispatch

Action

In Make“Retrieves an existing dispatch.”

Get a Dispatch reads one existing assignment in full when you already know which one you want, and passes its details to the next module. Think of it as the lookup step before a message or a report.

When to use it
a submission refers to a dispatch and you want its original details next to the answers in your summary email.
Watch out
it returns a single dispatch; when you only have search criteria, Search Dispatches is the right choice.
GoCanvas4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any part of the GoCanvas API that the other six modules leave aside, using the connection you already created. It is the fallback when no ready-made module matches your need.

When to use it
you need a GoCanvas feature beyond dispatches and submissions, and the API documentation shows the right endpoint.
Watch out
you write the request yourself, so read the GoCanvas API reference first and test the call with Run once.
GoCanvas5

Update a Dispatch

Action

In Make“Updates an existing dispatch.”

Update a Dispatch changes an assignment that already exists in GoCanvas, so the worker always sees the latest version of the job instead of an outdated copy. You point it at one dispatch and map the new values.

When to use it
the customer moves the appointment or adds a detail after the dispatch was sent.
Watch out
it edits the dispatch you name; pair it with Search Dispatches when your source app does not store the GoCanvas reference.
GoCanvas6

Search Dispatches

Search

In Make“Searches for dispatches or lists them all.”

Search Dispatches finds the assignments that match your criteria, or lists all of them, and hands each result on as a separate bundle. It turns a vague question (which jobs are open for this client?) into items you can act on.

When to use it
before an update or a deletion, to locate the right dispatch when your source app does not store its GoCanvas reference.
Watch out
it can return zero, one or many dispatches, and every following module runs once per result, which counts operations.
Need help

Need help automating GoCanvas with Make?

A person reads every message.

FAQ

Common questions about GoCanvas and Make

01Is the GoCanvas Make integration free?
Yes, on the Make side. GoCanvas is a standard app, available from the Free plan like the 3,000+ other standard apps. The Free plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run on one bundle. You still need an active GoCanvas subscription, which is billed by GoCanvas.
02What do you need to connect GoCanvas to Make?
An active GoCanvas account and an API key. In GoCanvas, go to Account, then Account Settings, then Security Settings and Settings by API Keys. Enable API keys, create one, give it a name, choose a department or All, save and copy it. In Make, add a GoCanvas module, click Create a connection, optionally name it, and paste the key. For the Watch Submissions trigger, click Create a webhook first, then Create a connection. The same connection then serves all 7 GoCanvas modules in your scenarios.
03Does the GoCanvas trigger in Make work in real time?
Yes. Watch Submissions is an instant trigger: GoCanvas calls Make through a webhook as soon as a form is submitted, so the scenario starts right away instead of waiting for a schedule. That is the only trigger of the app. The dispatch modules are actions and a search, which run when the scenario reaches them. If you want to start from something other than a submission, open the scenario with a trigger from another app, which Make checks on the schedule you set, every 15 minutes by default.
04What if a GoCanvas module is missing in Make?
Use Make an API Call. The listed modules cover submissions and dispatches; when your need goes beyond that, this module lets you call any endpoint of the GoCanvas API with the connection you already have, without creating a second one. You write the request yourself from the GoCanvas API documentation, then test it with Run once before switching the scenario on. The Make documentation for GoCanvas publishes no specific limits, and it notes that its content was generated from the vendor documentation, so check important details with GoCanvas directly.
05Should you use Make or n8n for GoCanvas?
It depends on what you need to cover. On Make, GoCanvas comes with 7 ready-made modules: an instant trigger on submissions, 5 actions including Make an API Call, and a search on dispatches, all configured in a visual editor without code. Before choosing n8n, check whether it offers a node for GoCanvas and whether that node covers the same events. Compare the modules each tool gives you for your exact use case rather than the tools in general. The n8n vs Make comparison on this site lists the criteria that matter.
Same platform

Other docs you might need on this stack.

Browse all integrations