Yay! Forms

Yay! Forms is an AI powered form and survey builder from Brazil. Agents manage workspaces, folders, forms and questions, read responses with AI enrichment on every answer, work the response kanban, manage themes and media, and drive the built in AI assistant to edit a form.

Verified 1 trigger 50 actions API key available

Yay! Forms website Platform Documentation Capability data verified 2026-08-26

On New Response fires when someone completes the qualification form

List Response Answers returns each answer with the keywords, sentiment, emotion and classification already attached

Agent branches on that enrichment rather than paying for a second analysis pass

A qualified respondent becomes a contact and a deal in the CRM

Update Response Card moves the submission to the Qualified stage and adds the matching label

The owning rep is told in the channel, quoting the answer that decided it

The rep confirms the stage or sends the card back with a comment explaining why

What This Integration Enables

Most form platforms hand you answers and leave the reading to you. Yay! Forms is built on the assumption that the reading is the expensive part, so every free text answer arrives with keywords, key phrases, sentiment, emotion and text classification already computed against it, and every submission lands on a kanban card with a stage, an assignee, labels and a comment thread. That combination is unusual. It means a flow can branch on what a respondent meant, not just on what they picked, and it means the triage board a team would otherwise build in a project tool already exists inside the form product.

FlowRunner agents run all of it: workspaces, folders, forms and questions, the response list in three different shapes, the enrichment filters, the kanban card, themes and media, the integration delivery logs that tell you when a connected provider has quietly stopped delivering, and the built in AI assistant that can edit a form on instruction. Every one of those operations is built and verified against the Yay! Forms API. The human-in-the-loop line is drawn where the platform's own safety net stops, which on this connector is a very specific place.

Without FlowRunner

Every answer read twice Free text is exported and then run through a second analysis pass that costs money and adds a day

The board is updated by hand Someone moves cards after the CRM changes, or the two records quietly stop agreeing

Editing a live survey is a gamble Changing a running form means guessing what the edit does to the answers already collected

With FlowRunner

Enrichment arrives with the answer Sentiment, emotion, keywords and classification are on the record when the flow first opens it

The board moves with the system of record The card changes stage in the same run that writes the CRM, with the reason recorded as a comment

Edits staged, deletions held Structure changes wait in the draft until published, and the operations that destroy answers wait for a person

Use Case Scenarios

Qualify on what they said, not just what they clicked

A demand generation form collects a mix of choice answers and a free text description of the problem the visitor is trying to solve. On New Response fires, and the agent calls List Response Answers to get the enrichment Yay! Forms already produced: the extracted key phrases, the sentiment and the classification. Where the classification matches an active campaign and the sentiment is not hostile, the agent creates the contact and the deal in HubSpot and calls Update Response Card to move the submission to Qualified, add the campaign label and post the reasoning as a comment on the card. The owning rep gets the summary in Slack with the answer that decided it quoted verbatim.
A reporting sheet nobody exports

Nightly, the agent calls List Responses with the Answer Grid format, which returns one flattened row per submission, and appends the new rows to a tab in Google Sheets. Alongside them it writes the figures from Get Form Statistics: views, starts, completions, completion rate and average time to complete, split by device class. Because the same run also reads List Integration Logs and List Credentials, a provider that has started failing or a credential whose expiry has passed shows up in the same digest as the conversion numbers, instead of being discovered a fortnight later when someone asks where the leads went.
Letting the platform's own assistant propose an edit

A survey has a completion rate problem and the team wants the assistant's opinion. The agent calls Ask AI Assistant in Plan mode, which returns an ordered plan of edits rather than carrying them out. It reads the plan against List Questions with draft changes included, works out which steps touch questions that already hold answers, and posts the annotated plan to the form owner. Approval sends the same conversation identifier back with Execute Plan enabled. A rejection costs nothing, because in Plan mode nothing has been written.

Human-in-Loop Highlight

Yay! Forms protects the form and not the data. Update Form, Create Question and Update Question all land on a draft copy, and Publish Or Discard Form Changes can throw those edits away, so almost every structural change is reversible. Delete Question is the exception, and it is not a small one: removing a question also removes the answers already collected for it, and deleting a Group takes the questions nested inside it along with their answers. Nothing in the draft mechanism brings those back. That matters most when the edits are being proposed by the platform's own AI assistant, because Ask AI Assistant in Action mode carries an instruction out directly and the assistant is allowed to edit the form itself. So the agent never runs it that way on a live form. It asks in Plan mode, then stops: "The assistant proposes 4 edits to Customer Fit Survey. Step 3 deletes question Q7, What is blocking you today, which holds 214 free text answers with enrichment. Steps 1, 2 and 4 are draft edits and reversible. Execute all, execute steps 1, 2 and 4 only, or discard?" The vendor built the pause into the mode selector. The agent's job is to use it and put the choice in front of the person who owns the responses.

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

50 actions

Workspaces and Folders

List Workspaces Lists every workspace the token can reach, each with its name, subdomain, time zone, owner, member count and plan. A workspace owns the forms, folders, themes, media and connected credentials, and every form operation is scoped to one.
Get Workspace Retrieves one workspace with its complete folder tree, owner, billing summary, member count, time zone and subdomain. The folder list is returned only here, so this is how a flow resolves a folder before filing a form.
Create Workspace Creates a workspace. Only the name is required. A supplied subdomain becomes the address published form links use and must be unique across Yay! Forms.
Update Workspace Updates a workspace name, subdomain or time zone. The time zone drives how submission timestamps are displayed and reported.
Delete Workspace Permanently deletes a workspace and everything inside it: forms, questions, collected responses, themes and uploaded media. This cannot be undone from the API.
List Workspace Members Lists the people with access to a workspace, with identifier, name, email and photo. This resolves the assignee identifier Update Response Card needs, and doubles as an access audit.
Create Folder Creates a folder inside a workspace so forms can be grouped, optionally nested under a parent. The identifier it returns is what the folder parameter of Create Form and Update Form expects.
Update Folder Renames a folder or moves it under a different parent. Moving a folder carries its forms and nested folders with it.
Delete Folder Deletes a folder. Forms filed inside it are not deleted; they return to the workspace root.

Forms

List Forms Lists a workspace's forms with identifier, public key, title, theme, folder, response count and status. Supports title search, folder filtering, sorting and paging. The public key is the value that appears in a published link.
Get Form Retrieves one form in full: title and description, language, theme, hidden fields, logic variables, tracking parameters, kanban configuration, response counts and limit, closing message, publication timestamps and the webhook URL configured on it. Call it before editing, because Update Form replaces the fields it is given.
Create Form Creates a form in a workspace. Everything is optional, so an empty call produces a blank draft. Supply a form subject to have the Yay! Forms AI generate the questions. A new form is a draft and is not publicly reachable until it is published.
Duplicate Form Copies a form with its questions, logic, theme assignment and settings into a workspace as a new draft. Collected responses are not copied, and the target workspace can differ from the original, so this doubles as a way to move a template between teams.
Import Form Creates a form from an exported form key, which encodes the whole structure of the source form. Paired with the export action, this moves a form between accounts that share no workspace.
Update Form Updates a form, sending only the fields supplied. The list fields replace rather than merge, so sending hidden fields replaces the whole hidden field list and the same applies to variables. Changes are draft changes until published.
Publish Or Discard Form Changes Applies one of three lifecycle actions: publish the draft so respondents see the edits, discard the draft and restore the live version, or export the form as a key that Import Form can turn back into a form elsewhere.
Delete Form Permanently deletes a form together with its questions and every response collected through it. This cannot be undone from the API.
Get Form Statistics Returns views, starts, completions, completion rate and average time to complete, optionally narrowed to a date range and a device class. The quickest way to compare mobile against desktop.

Form Questions

List Questions Lists a form's questions and screens in display order with type, title, description, options, validation, conditional logic, layout and per question analytics including drop off. Include draft changes to read the unpublished working copy.
Get Question Retrieves one question or screen with its full definition and collected analytics. Call it before an update, because an update replaces the fields it is given.
Create Question Adds a question or screen to a form. The type decides what the respondent sees, from text and email capture through choice lists, ratings, Net Promoter Score and file upload, to the welcome and ending screens. A welcome or ending screen is always placed first regardless of the position sent.
Duplicate Question Copies a question with its options, settings and conditional logic and appends it to a form, which can be a different form from the original. This is how a question is reused across forms.
Update Question Updates a question or screen. Options replaces the whole answer list rather than merging into it, so read the current choices first when adding one. Edits stay in the draft copy until the form is published.
Delete Question Removes a question or screen from its form, along with the answers already collected for it. Deleting a Group removes the questions nested inside it. This is the operation this page's human gate exists for.

Responses

List Responses Lists a form's submissions with the respondent metadata Yay! Forms captured. The result format changes the shape entirely: full records, a flattened one row per submission grid suited to spreadsheets, or preview submissions only. Paging is by page number or by feeding the returned pagination token back in.
Get Response Retrieves one submission with its complete respondent metadata and answers. Used after a trigger fires, or to re-read a submission whose card or answers are about to change.
Delete Response Permanently deletes one submission and the answers recorded with it. Useful for honoring a data deletion request or clearing test submissions, and it reduces the counts Get Form Statistics reports.
List Response Answers Lists the individual answers inside one submission, each carrying the AI enrichment Yay! Forms produced: extracted keywords and key phrases, sentiment and emotion, and text classifications. Filters on the enrichment let a flow pull only the answers whose sentiment or classification matches.

Response Kanban

Get Response Card Retrieves the kanban card representing one submission, with its stage, assignee, labels and comment thread, plus the full list of stages and assignees available on that board. Read it first to learn the identifiers an update expects.
Update Response Card Moves a submission across the board and edits the working notes on it. Stage moves the column, assignee hands it to a workspace member, and the label and comment lists carry add, remove and update operations rather than replacement values. The card is created on first use.

Themes

List Themes Lists a workspace's themes with font, the five palette colors, typography scale and button shape. This resolves a theme name to the identifier Create Form and Update Form expect.
Get Theme Retrieves one theme with its complete palette, font, typography scale, button shape and layout settings. Read it before an update, because the color fields are all required on a write.
Create Theme Creates a theme in a workspace. Colors cover the five surfaces of a Yay! Forms page. Supply a theme to copy from to start from an existing look rather than the defaults.
Update Theme Updates a theme. All five colors are required on every update, so this is a full palette replacement rather than a partial edit, and every form using the theme picks up the new look immediately.
Delete Theme Deletes a theme. Forms that were using it fall back to the workspace default appearance.

Media

List Media Lists the files in a workspace media library with public URL, thumbnail, name and alternative text. This resolves a file name to what a picture choice option, a form logo or a screen background points at.
Get Media Retrieves one media item with its public URL, thumbnail, name, alternative text and metadata. Used to read back the hosted URL of a file just uploaded.
Upload Media Uploads a file into a workspace media library from a publicly reachable URL, returning the hosted URL. Alternative text is worth setting, because it is what screen readers announce to respondents.
Delete Media Removes a file from the library. Questions and screens still pointing at it lose their image, so check where it is used first.

Integrations

List Form Integrations Lists the integrations configured on a form with name, provider type, linked credential and active state. Yay! Forms integrations are created in its interface, so this is a read only view and the way to find the identifier the log listing needs.
List Integration Logs Lists the delivery attempts made by one integration, each naming the response that triggered it, the trigger that matched and the outcome, which is succeeded, failed, or voided when a conditional rule suppressed the send. The operation to poll when an integration has quietly stopped delivering.
Get Integration Log Retrieves one delivery attempt in full, including the payload and the provider reply. Used to read why a delivery failed after the listing has shown a failure.
List Credentials Lists the third party accounts connected to a workspace with provider, display name, expiry and active state. An integration that has started failing is often a credential whose expiry has passed.

Account

List Account Statements Lists usage statements one per billing period, pairing what was consumed with what the plan allows across users, workspaces, forms, questions, responses, answers, keyword extractions and text analyses. This is how a flow checks remaining quota before starting work that would exceed it.
List Time Zones Returns every time zone identifier Yay! Forms accepts. These are the only values a workspace or account profile update takes, and they decide how submission timestamps are displayed and grouped.
Update Account Profile Updates a user account's display name, email, phone, time zone, interface language, company details and default workspace. Changing the email address changes the sign in identity.
Delete Account Permanently deletes a Yay! Forms user account and the data owned by them. This is the account level delete, not a workspace one, and it cannot be undone from the API.

AI Assistant

Get AI Assistant Suggestions Returns the opening suggestions the assistant offers for a form, which are the prompts its interface shows before the first message. They make reasonable defaults when a flow wants to offer a person a menu rather than a blank box.
Ask AI Assistant Sends an instruction to the Yay! Forms AI assistant for a form and returns its reply. The assistant can edit the form, configure its integrations or analyze collected responses. Mode decides how much autonomy it has: Chat answers only, Action carries the instruction out directly, and Plan proposes an ordered plan to approve before anything is executed.
Send AI Assistant Feedback Records a rating on one assistant message, optionally with a category and a written comment. Feeding evaluations back is what lets a flow keep a quality record of the assistant edits it has been applying.

Triggers

1 triggers

Event Triggers

On New Response Fires when a form receives a new submission, emitting the response record with its answers, respondent metadata, hidden field values and tracking parameters. Yay! Forms exposes no webhook management endpoints, so this polls the form's response list. The first cycle records the submissions already present without firing, so a form with existing responses never replays them, and test responses can be included to fire for preview submissions while a flow is being built.

Frequently Asked Questions

What can FlowRunner do with Yay! Forms?

FlowRunner agents can run List Workspaces, Get Workspace, and Create Workspace in Yay! Forms, plus 47 more actions.

Does connecting Yay! Forms to FlowRunner require OAuth?

No. Yay! Forms connects to FlowRunner with an API key, no OAuth flow required.

Can Yay! Forms trigger a FlowRunner workflow automatically?

Yes. Yay! Forms supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Yay! Forms

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us