GoCanvas
FormsPull completed field submissions out of GoCanvas, the mobile forms platform. Agents list forms and reference datasets, retrieve submission records with their captured field data, and route inspections, work orders, and checklists into downstream systems.
What This Integration Enables
GoCanvas puts the data collection where the work happens, on a technician's phone at the job site. What it does not do is decide what happens next, and "what happens next" is the entire value of an inspection. FlowRunner agents close that gap: they discover the account's forms with List Forms, sweep completed work with List Submissions, and pull full field detail with Get Submission so that inspections, work orders, and checklists become inputs to a workflow instead of records in a silo. Because GoCanvas API v2 is a legacy API that often returns XML, the connector absorbs that translation so your workflows deal in clean fields, not markup. That matters for the teams this platform serves: field operations rarely have an engineer on staff to parse legacy payloads, and the whole value of mobile forms evaporates if the data needs a developer to leave the platform it was captured in. - Route completed inspections, work orders, and safety checklists into CRMs, spreadsheets, and audit archives as they arrive - Detect failed items and out-of-range values in submissions and escalate them to a named person the same hour - Use List Reference Data to inspect the lookup lists that drive form dropdowns, so mappings into other systems stay aligned - Keep the dispatch decision with a supervisor while agents handle the reading, parsing, and filing
Without FlowRunner
With FlowRunner
Use Case Scenarios
The failed inspection that reached a human before the next shift
A field tech completes a fire safety checklist and two items fail. Within the hour, the sweep agent's List Submissions call surfaces the record, Get Submission pulls the failed items with photos and readings, and a [Slack](/integrations/slack) message lands with the operations team naming the site, the tech, and exactly what failed. The supervisor reads the readings and dispatches a repair crew. The alternative timeline, where the submission sits until the weekly review, is the one the insurance auditor asks about.
Field operations reporting without the Friday export
Every submission across the company's work order forms flows into [Google Sheets](/integrations/google-sheets) as it arrives: form name, submitting tech, timestamp, and the key captured fields. The ops lead opens one sheet on Monday and sees the week's field activity by site and crew, current to the last hour. Nobody exported anything, and the columns match because the agent checked the reference datasets before mapping the values into the sheet.
The site contact who made it into the CRM
Work order forms capture a site contact name and number that historically died in the submission record. Now, when List Submissions returns new work orders, the agent extracts the contact fields and upserts them into [HubSpot](/integrations/hubspot) tied to the account, so the office knows who the crew dealt with on site. Sales follow-ups stop starting with "who did we talk to there?", and the field data starts earning revenue twice.
Human-in-Loop Highlight
Get Submission is a read, but the workflows it feeds are not. When it retrieves a failed safety inspection, the natural next step is expensive in every direction: dispatch an emergency crew and you spend real money on what might be a mis-tapped checkbox; file it as routine and you have a paper trail showing the failure was known and nobody acted. So the agent never makes that call. It assembles the case, the failed items, the captured readings, the tech's notes, the site history from prior submissions, and puts it in front of the site supervisor as a decision with evidence attached. The supervisor picks dispatch, hold, or re-inspect, and the workflow records who decided and when. The audit trail that results is the difference between an incident report and a liability.
Agent Capabilities
4 actionsForms
1- List Forms Lists the forms available in the connected GoCanvas account. Forms are the mobile data-collection templates field users fill out, and the returned name or ID scopes every submission query. GoCanvas API v2 is a legacy API and may return data as XML depending on account configuration.
Submissions
2- List Submissions Lists submission records, optionally filtered by form and submitted date range. Returns submission metadata such as ID, form, submitter, and timestamp, with pagination. The sweep operation behind every scheduled sync on this page.
- Get Submission Retrieves the full detail of a single submission by ID, including all captured field values and metadata such as the submitting user and timestamp. The step that turns a submission ID into routable, checkable data.
Reference Data
1- List Reference Data Lists the reference datasets configured in the account, the lookup lists that populate form dropdowns and auto-fill fields. Used to keep downstream mappings aligned with what field users can actually select. May not be exposed on every account or plan.
Frequently Asked Questions
What can FlowRunner do with GoCanvas?
FlowRunner agents can run List Forms, List Submissions, and Get Submission in GoCanvas, plus 1 more action.
Does connecting GoCanvas to FlowRunner require OAuth?
No. GoCanvas connects to FlowRunner with an API key, no OAuth flow required.
Can GoCanvas trigger a FlowRunner workflow automatically?
GoCanvas doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with GoCanvas
$100 in credits. No card required. Connect in minutes.