Data & Storage · Integration
GoCanvas
Add GoCanvas to your product for your customers, and give your AI agents governed access to it.
Embed a GoCanvas integration so your customers can bring the data their field teams capture on mobile forms into your product, and send work back out to them. Every customer builds their own forms, so field mapping is configuration per tenant rather than code, and a form that changes on their side is a mapping update rather than a release on yours. fastn handles per-customer authorisation, pagination, and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read their own form submissions into your product, mapped to their own fields.
Dispatch a form to a field worker from your product so the job reaches their device.
Read a form's structure at runtime so your product adapts to each customer's form design.
Trigger your product when a submission is received so downstream work starts immediately.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads recent submissions before summarising what field teams reported.
An agent dispatches a form to the right worker within governed permissions, with the action logged.
An agent reacts to a submission with a failed inspection result and escalates it.
Example prompt
Show submissions from the last 48 hours that recorded a failed check, grouped by site.
Set up GoCanvas in 4 steps
- 01Open the GoCanvas connector from your fastn dashboard.
- 02Have each customer authenticate their own GoCanvas account.
- 03Map the forms and fields your product reads and dispatches, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the GoCanvas integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a GoCanvas integration without building it. Your customers connect their own GoCanvas account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a GoCanvas update is not your on-call problem.
- One integration serves your product and your agents. The same governed GoCanvas connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
FormAssembly
Google Sheets
AirtableOften used alongside
Tools the same teams tend to run next to GoCanvas, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceGoCanvas integration FAQ
How do I add a GoCanvas integration to my product?
Enable the GoCanvas connector in your fastn dashboard, then let each customer authenticate their own GoCanvas account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no GoCanvas client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own GoCanvas account?
Yes. Every connection is scoped to the individual customer, so each authorises their own GoCanvas account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this GoCanvas integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads recent submissions before summarising what field teams reported.
Who maintains the GoCanvas integration?
fastn does. When GoCanvas changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the GoCanvas integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large GoCanvas reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the GoCanvas integration?
A common starting point: read their own form submissions into your product, mapped to their own fields. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the GoCanvas integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding GoCanvas does not change your per-connector cost. You can start free with 3 connected accounts.
Add GoCanvas to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.