FormCan
FormsFormCan, formerly PlatoForms, is an online and PDF form builder. Agents read forms and fields, search and update submissions, create pre-filled invitations, download generated PDFs, attachments and signature certificates, keep dropdown options in sync with an external system, and react on every submission.
What This Integration Enables
FormCan, formerly PlatoForms, is a form builder where the document is the point. A submission is not just a row: it generates a PDF, it can carry a signature certificate and uploaded attachments, and it keeps revisions, so the record shows what changed and when. That is why it turns up in processes where the completed form is the evidence rather than the data entry step, and it is a different job from a survey tool.
FlowRunner agents work that document lifecycle end to end. They push new submissions into the CRM or database the instant a respondent hits submit, archive the generated PDF and its certificate into long term storage, build pre-filled and locked invitation links from data a flow already holds, keep live dropdowns in step with an external catalog, and read revision history to reconcile what changed. Because the artifacts here are signed documents containing real personal data, the human-in-the-loop step sits where a document is about to leave the system that authenticates access to it.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
A submission arrives and files itself
New Form Submission fires. The agent calls Get Submission Detail, reads the answers by field identifier, and creates or updates the contact in HubSpot. Download Submission File then pulls the generated PDF, the uploaded attachments and the signature certificate, and each is archived to Box in a folder named for the submission. A message to the owning team in Slack carries the key answers and the archive location, so the first person to see the record does not have to go looking for the paperwork.
-
The order form that always offers what is actually in stock
A public order form has a product dropdown that used to be edited by hand whenever the catalog changed. Now the agent reads the current catalog from Airtable on a schedule and calls Update Dropdown Options with the field identifiers it read from Get Form Fields. The response reports success per field rather than in the status code, so the agent checks the body and reports any field that could not be found. Applying to the live form is deliberate rather than automatic, because FormCan warns that reordering options while respondents have the form open can misalign answers already in progress.
-
Someone asks for a copy of a signed document
A customer, an auditor or a broker asks for the signed agreement behind a submission. The agent finds it: List Form Submissions with a field filter narrows to the record, Get Submission Revisions confirms which version is current, and Download Submission File proves the certificate exists. It then assembles the request for a person, naming who is asking, which document it is, and what expiry it proposes. Only after that answer does it mint anything, because the alternative is a link to a signed document with a customer's details in it, sitting in an email thread with no way to take it back.
Human-in-Loop Highlight
Create Submission Sharing URL produces a download link that needs no credential at all. That is what makes it useful and what makes it dangerous: the authenticated route requires the API token, the sharing route requires only the URL, so anyone who ends up holding it can read a signed document. Expiry is a parameter, and passing zero means the link never expires, which the vendor advises against. Read the action list on this page and note what is missing: there is a Delete Form Invitation, there is a Delete Webhook, and there is nothing that revokes a sharing URL. So the agent gathers the evidence and asks: "Broker Mainline Partners has asked for the signed supply agreement on submission 41822, signed on 12 August by the named signatory. Mint a sharing link for 24 hours, choose a different window, or send it through the authenticated route instead?" The reviewer picks. The agent's job was to find the right document and lay out the options. Deciding that a signed customer document should be readable by whoever holds a URL is a person's call, because nothing in this API takes it back.
Agent Capabilities
29 actionsAccount
1- Get API User Reads the account the token authenticates as. Worth calling first, because FormCan grants permissions per form rather than per token, so a valid token can still be refused on a specific form.
Forms
8- List Forms Lists the forms the token can reach.
- Search Forms Searches forms by name, the resolver when a flow has a title rather than an identifier.
- Get Form Reads one form's configuration.
- Get Form Fields Lists a form's fields with the identifiers everything else addresses. Submissions, invitations and dropdown updates all key on these, so this is the first call in most write flows.
- Get Form Field Layout Reads how fields are laid out on the form, which matters when a generated document has to match the page a respondent saw.
- Update Form Fields Updates field definitions on a form.
- Update Dropdown Options Replaces a dropdown's options, which is how a product, branch or staff list stays in step with the system that owns it. Success is reported per field in the response body rather than in the status code. Changes land on the draft form unless the action is told to apply them to the live one.
- Create Web Form From Description Creates a web form from a written description, useful for standing up a first draft that a person then reviews.
Submissions
10- List Form Submissions Lists submissions, with field level filters supporting exact, typed and ranged comparisons. The workhorse read for reconciliation, because keyword search only matches fields explicitly marked searchable on the form.
- List Draft Submissions Lists submissions a respondent started and has not completed, which is what a follow up or abandonment flow acts on.
- List Submissions By Custom Field Reads submissions by the custom field value carried on a public form URL. The vendor has deprecated this route and plans to remove it, so prefer a field filter on List Form Submissions where the data allows.
- Get Submission Detail Reads one submission in full. Simple fields carry a value; tables, choice groups and file uploads carry a structured array, so read one real submission before fixing a mapping.
- Get Draft Submission Detail Reads an incomplete submission in full.
- Get Submission Revisions Reads a submission's revision history. Because updates write a new revision rather than overwriting, this is the audit read that shows exactly what changed and when.
- Delete Submission Permanently deletes a submission along with every revision, the generated PDF, the signature certificate and the uploaded attachments. There is no undo, and no partial version of this action.
- Submit Form Creates a submission from data a flow already holds, so a form that is legally the record of truth also captures machine originated entries. The PDF generates in the background.
- Update Submission Updates a submission, writing a new revision rather than overwriting, so earlier values stay readable.
- Get Webhook Test Data Returns real submissions in the exact shape a webhook delivers, which is the cheapest way to build and test a flow before a live submission arrives.
Invitations
4- Create Form Invitation Creates pre-filled invitation links, optionally locked read only, password protected and time limited. Supplying email invitees sends immediately and returns no link list, so treat that variant as an outbound send rather than a link generation.
- Get Form Invitation Reads an invitation's configuration and state.
- Update Form Invitation Updates an invitation, for example extending its window.
- Delete Form Invitation Deletes an invitation. Worth running on invitations no longer needed, because generated links consume tracking capacity.
Files
2- Download Submission File Downloads a generated PDF, a signature certificate, a CSV export or an uploaded attachment into FlowRunner file storage using the authenticated route. The archive step.
- Create Submission Sharing URL Mints a link that downloads the file without any credential, with an expiry taken from the form's setting unless overridden. Nothing in this connector revokes one afterward. The operation this page's human gate exists for.
Webhooks
4- List Form Webhooks Lists the webhooks registered on a form, including any created outside this connector.
- Create Form Webhook Registers a webhook on a form for a receiver other than a FlowRunner trigger.
- Get Webhook Reads one webhook's configuration.
- Delete Webhook Removes a webhook. Deleting the one a trigger created silently stops that trigger, so remove the trigger in FlowRunner instead.
Triggers
1 triggersEvent Triggers
1- New Form Submission Fires the moment a form is submitted, delivered by a webhook the trigger registers for itself and removes when the trigger is removed. Leaving the form unset subscribes to every form in the team. Each event carries the answers keyed by field identifier, and batched deliveries are unwrapped into one event per submission. FormCan documents no signing secret or verification header for its deliveries, so the unguessable callback URL is the only thing protecting the endpoint: this connector additionally matches every delivery against the form its trigger watches, and anything security relevant should be re-read with Get Submission Detail rather than trusted from the payload.
Frequently Asked Questions
What can FlowRunner do with FormCan?
FlowRunner agents can run Get API User, List Forms, and Search Forms in FormCan, plus 26 more actions.
Does connecting FormCan to FlowRunner require OAuth?
No. FormCan connects to FlowRunner with an API key, no OAuth flow required.
Can FormCan trigger a FlowRunner workflow automatically?
Yes. FormCan supports 1 trigger that can start a FlowRunner workflow automatically.
Other Forms integrations
Start building with FormCan
Free plan, no card required. Connect in minutes.