Weavely

Weavely is an AI form builder that turns a plain language brief, a Figma design, a PDF or a screenshot into a themed multi-page web form. Agents generate forms on demand, create and edit them from a specification, read field structure, pull responses, and react the moment a form is submitted.

1 trigger 12 actions API key available

Weavely website Platform Documentation Capability data verified 2026-08-26

A request arrives asking for an intake form that does not exist yet

Agent reads the brief and any attached PDF or photo of the paper original

Generate Form builds a themed draft from that description and those documents

Get Form Fields returns the generated fields, their labels and their identifiers

Agent confirms the specification carries an ending page, because Weavely will publish one without it

Create Form publishes the form and returns its public link

The requester reviews the field list and the live link before it reaches respondents

What This Integration Enables

Weavely is built for teams whose forms are disposable. Most form platforms assume a form is a fixture: someone designs it, someone owns it, and it lives for years. Weavely assumes the opposite, because it can build a themed multi page form from a plain language brief, a Figma file, a PDF or a screenshot of a paper original. That changes what a form is for. A form stops being an asset you maintain and becomes an output a workflow produces, one per campaign, one per market, one per request that needed structured answers.

FlowRunner agents work that surface end to end. They generate a draft from a description, assemble a complete specification of pages, elements, theme and logic and publish it, read the field identifiers that submissions are keyed by, pull responses on a schedule, and wake the moment somebody presses submit. Every one of those operations is built and verified against Weavely's own API. What keeps disposable from meaning careless is FlowRunner's human-in-the-loop discipline: the agent can stand a form up in seconds, and the decisions that reach respondents still belong to a person.

Without FlowRunner

Forms queue behind one person Every new intake waits for whoever owns the form builder to have an hour free

Paper stays paper An existing PDF or printed form is never migrated because retyping it is nobody's job

Mapping redone every time Field labels are invented in the builder, then matched to CRM properties by hand afterwards

With FlowRunner

The form is part of the request The agent generates the form from the message that asked for it and replies with the link

A scan becomes a route A PDF or a photograph is source material the generator converts into a live web form

Identifiers read, not remembered Get Form Fields resolves element identifiers to labels, so the mapping is looked up rather than recalled

Use Case Scenarios

The form that did not exist an hour ago

An operations lead asks in Slack for a vendor onboarding form with insurance details and a signature field. The agent reads the request, calls Generate Form with the description, and gets back a themed draft. It reads the result with Get Form Fields, checks that the structure includes an ending page, then calls Create Form with Publish set and posts the live link back into the thread. The brief, the field list and the published URL land together as a page in Notion so the next person who needs the same form starts from a specification rather than a blank builder.
Paper into the pipeline

A folder in Box collects scanned intake sheets from field offices that still work on paper. The agent feeds each scan to Generate Form, which reads the document and produces the equivalent web form, then publishes it with Create Form. From there the On Form Submitted trigger takes over: each submission wakes a flow that reads the authoritative record with Get Form Submission, maps the answers onto the element identifiers it learned from Get Form Fields, creates or updates the contact in HubSpot, and posts a summary to the team channel. The paper form and the web form finally collect into the same place.
Revising a form that is already collecting

A campaign form has been live for three weeks and the marketing team wants two questions reworded and one logic rule changed. The agent reads the live definition with Get Form Specification, builds the revised specification alongside it, and shows the before and after to the form's owner. It does not write. Weavely replaces each nested object whole rather than merging it, so supplying pages replaces the entire structure and supplying logic rules replaces every rule the form has. The owner sees exactly which parts are being replaced, approves, and only then does the agent call Update Form.

Human-in-Loop Highlight

Weavely publishes no delete route for a form. Retirement is Update Form with Stop Submissions turned on, which means the same operation that edits a live form is also the one that closes it. Update Form is not a patch either: each nested object it receives replaces the stored one whole, so an agent that sends pages to fix a typo replaces the entire form structure, and one that sends a single logic rule removes every other rule the form had. There is no version history to fall back on and no form to recreate from. So the revision agent stops before the write and posts the diff: "Update Form on Vendor Onboarding, live since March 4 and currently accepting responses. Sending 6 pages, which replaces the 6 stored now. Sending 3 logic rules, which removes the 4 currently live. Stop Submissions stays off. Apply?" The agent has already read the live specification, built the replacement and shown its work. What it will not do is decide on its own that the replacement is the one the team meant.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

12 actions

Forms

Generate Form Builds a complete form from a plain language description using Weavely's AI generator, optionally reading source documents such as a PDF, a screenshot or a photograph of an existing paper form, and returns the editor URL of the new draft. This route needs no personal token, so a flow can call it before a connection is finished.
Create Form Creates a form from a full specification: pages and elements, theme, and optional logic rules and event triggers. Publish makes it live immediately; without it the form is a draft with no public URL. Include at least one ending page, because Weavely does not check for one.
Update Form Applies a partial update to an existing form. Each nested object is replaced whole rather than merged, so send every key of a group you want to keep. This is also how a form is retired, by turning Stop Submissions on while the published link keeps working.
Get Form Fields Returns a form's input fields with their identifiers, labels and types, plus the timestamp of the published version. This is how a flow learns the element identifiers that answers are keyed by, so an answer can be mapped onto a named column or CRM property.
Get Form Specification Returns the complete published specification of a form: pages, elements, theme, field variables, logic rules, event triggers and language settings. Use it to clone a form, to audit what is live, or as the starting point for an Update Form call. A published specification is public and needs no token.
List Team Forms Lists the forms belonging to one team, optionally narrowed to those with a published version. The way a flow iterates an account's forms or resolves a form name to the identifier every other action needs.

Account

List Teams Lists every team the personal token can reach, with identifiers and names. A team identifier is required to create a form and to list forms, so this is usually the first call in a Weavely flow.
Get Profile Returns the identity behind the personal token: user identifier, name and email address. Used to confirm a connection is authenticated and to record who a flow is acting as.

Responses

List Form Responses Lists the responses collected by a form. The route is live and verified but not part of Weavely's published reference, so its filtering and paging options are passed through rather than named, and the result is normalized so responses is always an array.
Get Form Submission Retrieves one submission by identifier, with the value submitted for every field and the time it arrived. Answer shapes follow the element type: a string for text and single choice, an array for multi select, and a URL for file uploads and signatures. This is the authoritative read to pair with the trigger.

Webhooks

Create Webhook Registers a URL that Weavely posts each new submission of a form to, and returns the webhook identifier. Use it to feed an endpoint outside FlowRunner; inside FlowRunner the trigger manages its own.
Delete Webhook Removes a webhook from a form so Weavely stops posting to that URL. Weavely publishes no route for listing a form's webhooks, so keep the identifier returned at creation if you register one by hand.

Triggers

1 triggers

Event Triggers

On Form Submitted Fires the moment a respondent submits the watched form. FlowRunner registers a Weavely webhook when the flow is deployed and removes it when the flow stops, so no manual setup is needed. The delivery carries the submission identifier and every answer, both as the raw list Weavely sends and as a map keyed by element identifier. Weavely signs nothing, so when the submission drives something consequential, read the authoritative record with Get Form Submission before acting on it.

Frequently Asked Questions

What can FlowRunner do with Weavely?

FlowRunner agents can run Generate Form, Create Form, and Update Form in Weavely, plus 9 more actions.

Does connecting Weavely to FlowRunner require OAuth?

No. Weavely connects to FlowRunner with an API key, no OAuth flow required.

Can Weavely trigger a FlowRunner workflow automatically?

Yes. Weavely supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Weavely

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us