Release0
FormsUse the Release0 builder API for its no-code conversational agent and form builder, covering agents, submissions, analytics, and workspaces. Agents pull submissions into the systems that act on them.
What This Integration Enables
Release0 builds conversational forms, and it makes one structural decision that everything useful here depends on: the draft and the published version are separate objects with separate endpoints. Get Agent returns the draft. Get Published Agent returns what visitors are actually talking to. Publish Agent is the only thing that moves one to the other. That separation means a FlowRunner flow can rewrite a form definition all afternoon with zero effect on a single visitor, then promote the result in one deliberate call. Most builder APIs do not give you that, and building an approval on top of one that does not is guesswork.
A word on vocabulary, because it matters when reading this page. Release0 calls its conversational forms "agents". They are flow documents made of groups, blocks, events, variables, a theme and settings, and they are not the same thing as a FlowRunner agent. Throughout this page, the FlowRunner side is the flow doing the work and the Release0 side is the object being worked on. With that straight, the surface divides cleanly. There is full lifecycle control over the conversational forms themselves, covering create, partial update, delete, publish and unpublish. There are submissions with their answers and captured variables, cursor-paginated up to 100 per page and narrowable to a preset reporting window or explicit dates. There are per-submission execution logs capturing integration calls, webhook responses and errors. And there is aggregate reporting on views, starts and completions, alongside workspace management with member listing. Release0 documents no webhook subscription API, so there are no triggers, and flows either sweep on a schedule or act from the system that has news.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A wording change that reaches the public on purpose
A compliance review says a consent question needs different wording. Rather than someone editing the live form in a browser, the flow calls Get Agent for the draft, applies the change with Update Agent, then calls Get Published Agent and compares the two definitions block by block. It posts the difference to the owning team: the old wording, the new wording, and confirmation that the variable names downstream systems read from are unchanged. A person approves, the flow calls Publish Agent, and the change is live with a record of who authorised it. The draft and published split makes this possible without a staging copy.
Submissions that reach the system that acts on them
A scheduled flow calls List Results for each published form over a rolling window, walking the cursor until the window is covered. For each submission it calls Get Result to read the answers and the variable values captured during the conversation, then creates or updates the matching record in HubSpot and assigns an owner. Because results are cursor-paginated with a stable order, the sweep is resumable, which matters more than it sounds when a form has a good week.
A failing form diagnosed from the submission that failed
Completions drop and nobody knows why. The flow calls Get Agent Stats for views, starts and completions to confirm the drop is real rather than seasonal, pulls the recent results, and calls List Result Logs on the submissions that ended early. The logs capture integration calls, webhook responses and errors for that specific conversation, so the answer is usually visible in one record: a webhook returning 500, an integration timing out at the same block every time. The flow posts the failing block and the error to the team channel rather than the observation that numbers are down.
Human-in-Loop Highlight
Publish Agent is the moment on this connector that carries real consequence, and it is not really about the software. A published Release0 form is a machine that asks members of the public questions and keeps their answers. Which questions it asks, which of them are required, what it says about why it is asking, and what it stores are decisions with legal and ethical weight, and Publish Agent moves all of them from a draft nobody has read to a live conversation with real people, immediately. There is no gradual rollout and no scheduled window. The instant the call returns, the next visitor is talking to the new version.
So a FlowRunner flow may edit the draft freely and may never publish on its own. It calls Get Published Agent alongside Get Agent, computes the actual difference, and routes it as a human-in-the-loop decision through Slack: "Draft of the Contractor Intake form differs from live in two blocks. Question 4 changes from 'Do you have insurance?' to 'Upload your current certificate of insurance', which turns an optional yes or no into a required file upload. Question 7 now stores a date of birth that was not previously collected. Publish, or hold?" A person answers, the flow publishes exactly what was approved, and the approval is on the record next to the change. Unpublish Agent is the matching reverse, taking the live version down while preserving the draft, so a bad publish has a clean exit.
One further action deserves the same treatment for a different reason. Delete Results removes submissions permanently, and when no result identifiers are supplied it removes every result for that form. That default makes it the right tool for a right-to-erasure request and a serious hazard in a scheduled cleanup, so a flow should always pass explicit identifiers and confirm the list before it runs.
Agent Capabilities
19 actionsAgents
8- List Agents Lists every conversational agent inside a Release0 workspace, returning the identifiers, names and publication state the result and analytics operations need. The workspace identifier is required by the API, so a workspace lookup comes first.
- Get Agent Retrieves the full draft definition of a single agent, including its groups, blocks, theme and settings, plus the calling token's access mode of guest, read or write. Read this before updating so a flow modifies the existing definition rather than replacing it blindly.
- Create Agent Creates a new conversational agent in a workspace. The definition is Release0's flow document containing groups, blocks, events, variables, theme and settings, supplied when cloning or generating a flow programmatically. The name and icon given here merge into that definition, so a simple agent can be created from those alone.
- Update Agent Applies a partial update to an existing agent using Release0's document format. Changes affect the draft only, so nothing a visitor sees moves until Publish Agent runs.
- Delete Agent Permanently deletes an agent along with its draft and published versions. This cannot be undone, so export or archive the results first.
- Get Published Agent Retrieves the currently published version of an agent, which is the definition visitors actually interact with. Comparing it against the draft from Get Agent is how a flow detects unpublished changes and builds the difference a reviewer reads.
- Publish Agent Publishes the current draft, making the latest changes live for visitors immediately. This changes what real people are asked and what is stored about them, so it belongs behind an approval rather than at the end of an editing sequence.
- Unpublish Agent Removes the published version so it is no longer reachable by visitors, while preserving the draft for later. The clean exit from a publish that should not have happened.
Results
4- List Results Retrieves the submissions collected by an agent, newest first, cursor-paginated between 1 and 100 per page with 50 by default, narrowable to a preset reporting window or explicit start and end dates. Pass the returned cursor back in to walk a large set, which makes a sweep resumable.
- Get Result Retrieves a single submission by identifier, including the answers given and the variable values captured during the conversation. Identifiers come from List Results.
- Delete Results Permanently deletes submissions from an agent. Supplying specific identifiers removes only those, and supplying none deletes every result for the agent. Suited to data-retention and right-to-erasure work, and a step that should always carry explicit identifiers.
- List Result Logs Retrieves the execution log entries recorded while a specific submission was collected, capturing integration calls, webhook responses and errors. The primary way to find out why a form stopped working rather than only that it did.
Analytics
1- Get Agent Stats Returns aggregate performance for an agent: total views, total conversation starts and total completions. Combine with a reporting window and time zone to build conversion reporting that distinguishes a traffic problem from a completion problem.
Workspaces
6- List Workspaces Lists every workspace the API token can access. The identifiers returned here are required when listing or creating agents.
- Get Workspace Retrieves a single workspace by identifier or slug, including its plan and branding, with an option to fall back to the token owner's default workspace.
- Create Workspace Creates a new workspace owned by the token holder. Workspaces separate agents, members and billing, which makes this the onboarding step for a new client or brand.
- Update Workspace Updates the name, icon or slug of an existing workspace. Only the fields supplied are changed.
- Delete Workspace Permanently deletes a workspace together with the agents and results it contains. This cannot be undone, and the blast radius is every form in it.
- List Workspace Members Lists the members of a workspace with their roles. Used to audit who can view or edit the forms in a given workspace.
Frequently Asked Questions
What can FlowRunner do with Release0?
FlowRunner agents can run List Agents, Get Agent, and Create Agent in Release0, plus 16 more actions.
Does connecting Release0 to FlowRunner require OAuth?
No. Release0 connects to FlowRunner with an API key, no OAuth flow required.
Can Release0 trigger a FlowRunner workflow automatically?
Release0 doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Release0
$100 in credits. No card required. Connect in minutes.