Build
Flows
A flow decides what happens to every submission of one form. Drag steps onto the canvas, connect them, and each submission follows the path its answers lead to: checked, sorted, and delivered to the right people.
On this page you will learn
- How a submission travels through a flow
- Every step, what it needs and what it does
- How branches work in Validate, Route by answer and If / else
- Waits, and why they end on a 5 minute mark
- Test runs, test submissions and live runs
- Go live checks, statuses and what to do when a delivery fails
How a flow runs
- 01Form submittedQuote request receives a submission.
- 02ValidateForm rules and spam filter. Failures stop here.
- 03Route by answerBy the service picked: one path per option.
- 04Send emailThe right person gets the lead.
- When a submission arrives, every live flow of its form starts at the trigger and follows the connections.
- Logic steps decide which path comes next. Action steps deliver, then pass the submission on.
- A step can lead to several next steps, and they all run. Each step runs at most once per submission, and connections can never form a loop.
- When a delivery fails, the path stops there. Other paths carry on.
- Each run records what every step did, and the inbox shows it on the submission.
Create a flow
On the Flows page, choose New flow, or Build a flow on a form. Pick the form it starts from, a name, and a template. New flows start as drafts.
| Template | What you get |
|---|---|
| Route by answer | Validate, then send each option of a dropdown to a different place. |
| Notify the team | Validate and email every submission to your team. |
| Notify and confirm | Email the team and send the sender a confirmation. |
| Blank flow | Start with the trigger and build the rest yourself. |
Route by answer needs a dropdown, single choice or yes or no field in the form. It adds a route for up to four of its options, an Anything else path, and an email step on every path. Add the recipients to those emails before you go live.
Work on the canvas
- Click a step in the palette to add it after the selected step, or after the lowest step when none is selected, already connected. Drag it onto the canvas to place it yourself.
- Drag from the dot under a step to the top of another to connect them. Routes, conditions and checks have one dot per path.
- Select a step or a connection and press Delete or Backspace to remove it.
- Click a step to open its settings. Every step has a name you can change, shown on its card.
- Changes save on their own. The graph is written as you edit, except while you drag a step.
Steps
Steps come in three categories, shown by their color: the trigger starts the flow, logic steps decide and prepare, and actions deliver.
AI
| Step | Category | What it does |
|---|---|---|
| Ask AI | Logic | Summarize, sort, extract or translate answers, then use the result in later steps. |
Logic
| Step | Category | What it does |
|---|---|---|
| Validate | Logic | Check answers and filter out spam before anything is sent. |
| Route by answer | Logic | Send each submission down a different path based on a dropdown or choice. |
| If / else | Logic | Split the flow in two based on one answer. |
| Set values | Logic | Combine or clean up answers to reuse in later steps. |
| Wait | Logic | Pause before the next step, for follow-ups and reminders. |
Actions
| Step | Category | What it does |
|---|---|---|
| Send email | Action | Email the submission to your team. |
| Reply to sender | Action | Send a confirmation to the person who filled in the form. |
| Post to Slack | Action | Post a message in a Slack channel. |
| Post to Teams | Action | Post a card in a Microsoft Teams channel. |
| Post to Discord | Action | Send a message to a Discord channel. |
| Post to Google Chat | Action | Post a message in a Google Chat space. |
| Post to Mattermost | Action | Post a message in a Mattermost channel. |
| Send to Telegram | Action | Send a message to a Telegram chat or group through your bot. |
| Send webhook | Action | Send the submission as JSON to your CRM, backend or any URL. |
Step by step
Form submitted
Trigger Starts the flow when a form receives a submission.
- Every flow has exactly one trigger. It cannot be deleted, and nothing can connect into it.
- Choose the form. When the form has more than one source, tick sources under Only from these sources to run for those only, or leave all unticked to run for every source.
- Each live flow of a form runs once for every submission, so two live flows of the same form both run.
Ask AI
Logic Summarize, sort, extract or translate answers, then use the result in later steps.
Reads text you choose and saves AI's answer as a value, such as {{ai_summary}}. If AI cannot answer, the value is empty, the step is skipped and the flow carries on. Every job is described in AI features.
Validate
Logic Check answers and filter out spam before anything is sent.
Turn on any mix of three kinds of check. The step needs at least one.
- Use the form's rules: required answers, email and number formats, options, lengths and ranges from the form builder. See Required answers.
- Filter spam: a filled spam trap field, an email field on one of 20 known throwaway domains, or a long text answer with more than 3 links.
- Extra checks: rules on one field each, from the table below.
| Check | Example value | Meaning |
|---|---|---|
| is filled in | None | Fails when the answer is empty. |
| is a valid email | None | Fails when an answer is there but is not an email address. |
| is a valid phone number | None | Fails when an answer is there but is not a phone number of 7 to 15 digits. |
| is a valid web address | None | Fails when an answer is there but is not a web address. |
| is not a throwaway email | None | Counts as spam when the email uses a throwaway domain. |
| has at least N characters | 20 | Fails when the answer is shorter than N characters. |
| has at most N characters | 500 | Fails when the answer is longer than N characters. |
| has at most N links | 2 | Counts as spam when the answer contains more than N links. |
| matches a pattern | ^NW-[0-9]+$ | Fails when an answer is there but does not match the regular expression. |
When everything passes, the submission continues down Passed. Otherwise the step is Stopped, lists every problem, and continues down Failed or spam. Spam signals mark the run as spam, other problems as invalid. Leave Failed or spam unconnected to simply stop there.
Route by answer
Logic Send each submission down a different path based on a dropdown or choice.
Pick the field to route by. Choice fields are listed first and work best, with one route per option and Add every option for lists of up to 30. For other fields and step values, type the answer each route matches.
- By default a route matches when the whole answer equals its value, ignoring case and spaces around it. For multiple choice, any of the picks can match.
- Each route can compare another way instead: pick an operator above its value, such as is a company email, domain is, is at least or contains. Every operator in the table under If / else works.
- Routes are checked from the top and the first one that matches wins, so put the most specific route first.
- Everything that matches no route, including an empty answer, goes down Anything else, the last path.
- Each option can be used by one plain route only.
If / else
Logic Split the flow in two based on one answer.
Add one or more checks. Each check picks a field or a step value, how to compare it, and the value. With several checks, choose whether all must hold or any one can hold. Matches continue down Yes, everything else down No.
The operators on offer depend on the field: emails get company and personal email checks and domains, numbers get ranges, dates get before, after and the coming or past days, multiple choice gets all of and counts. Step values from Set values and Ask AI can use every text and number operator.
| Operator | Works on | Matches when |
|---|---|---|
| is | text, email, website, phone, numbers, single choice, multiple choice, dates, times | The answer is exactly this value. Capitals and spaces at the ends do not matter. For multiple choice, one of the picks is this option. |
| is not | text, email, website, phone, numbers, single choice, multiple choice, dates, times | The answer is anything but this value. For multiple choice, none of the picks is this option. |
| is any of | text, email, website, phone, numbers, single choice, multiple choice | The answer is one of the values in a comma separated list, or one of the options you tick. |
| is none of | text, email, website, phone, numbers, single choice, multiple choice | The answer is not any of the values in the list. |
| includes all of | multiple choice | Every option you tick was picked, other picks allowed. |
| contains | text, email, website, phone | The text has this word or phrase anywhere in it. |
| doesn't contain | text, email, website, phone | The text does not have this word or phrase anywhere in it. |
| starts with | text, email, website, phone | The text begins with this, such as a country code or an order prefix. |
| ends with | text, email, website, phone | The text ends with this. |
| matches the pattern | text, email, website, phone | The text matches a regular expression, without regard to capitals. |
| is longer than (characters) | text | The text has more characters than this number. |
| is shorter than (characters) | text | The text has fewer characters than this number. |
| has more words than | text | The text has more words than this number. |
| has fewer words than | text | The text has fewer words than this number, such as a one word message. |
| is a company email | A valid address on a company domain: not Gmail, Outlook, Yahoo or another free provider, and not a throwaway address. | |
| is a personal email | An address at a free provider such as Gmail, Outlook, Yahoo, iCloud, Proton or GMX. | |
| is a throwaway email | An address at a throwaway inbox service, often used for spam. | |
| domain is | email, website | The email domain or website address is one in the list. Subdomains count, so acme.com also matches eu.acme.com. |
| domain is not | email, website | The email domain or website address is none in the list. |
| is valid | email, website, phone | The answer is a well formed email address, phone number or web address. |
| is not valid | email, website, phone | The answer is filled in but not a well formed email address, phone number or web address. |
| is more than | numbers | The number is higher than this value. |
| is less than | numbers | The number is lower than this value. |
| is at least | numbers | The number is this value or higher, such as a rating of at least 4. |
| is at most | numbers | The number is this value or lower, such as a detractor score of at most 6. |
| is between | numbers | The number is between two values, both included. |
| is before | dates, times | The date or time is earlier than this one. |
| is after | dates, times | The date or time is later than this one. |
| is within the last N days | dates | The date is today or up to this many days ago, counted from when the submission arrived. |
| is within the next N days | dates | The date is today or up to this many days ahead, such as a booking in the coming week. |
| falls on | dates | The date falls on one of the weekdays you pick. |
| has at least N picked | multiple choice, files | At least this many options were picked, or files attached. |
| has at most N picked | multiple choice, files | At most this many options were picked, or files attached. |
| is empty | text, email, website, phone, numbers, dates, times, single choice, multiple choice, files, consent | Nothing was sent for this field. |
| is filled in | text, email, website, phone, numbers, dates, times, single choice, multiple choice, files, consent | Something was sent for this field. |
Choice fields of up to 30 options let you tick the options. For longer lists, like countries, type the values with commas. Dates count from the moment the submission arrived. A company email is a valid address that is not at Gmail, Outlook, Yahoo, iCloud, Proton, GMX or another free provider, and not a throwaway inbox.
Set values
Logic Combine or clean up answers to reuse in later steps.
Add values, each with a name and a template, such as greeting = Hi {{name | there}}. Names use lowercase letters, numbers and underscores. Values are worked out in order, so a value can use one set above it in the same step.
Later steps use them like answers: {{greeting}} in templates, under Values in Route by answer and If / else, and in the values of webhooks.
Wait
Logic Pause before the next step, for follow-ups and reminders.
- Wait for a number of minutes, hours or days. Only the path behind the Wait pauses: steps on other paths run right away.
- Waits are checked every 5 minutes, so a wait ends at the first check after its time. A 10 minute wait takes 10 to 15 minutes.
- While it waits, the run is Waiting and the submission stays Stored.
- When the wait is over, the run continues with the flow as it is then. If the flow was deleted meanwhile, the run fails with "Could not continue after the wait".
- Test runs skip waits and say how long the live run would wait.
Send email
Action Email the submission to your team.
- To and Cc: addresses separated by commas, and they can use variables. Invalid addresses are dropped, and with no valid one left the step fails with "No valid recipient".
- Reply to:
{{email}}lets your team answer the sender straight from the email. It is used only when it is a valid address. - Subject: line breaks become spaces. An empty subject becomes "New submission: " and the form name.
- Message: plain text.
{{submission.all_fields}}lists every answer. - Emails come from your workspace name "via Formpik". When To uses a variable, the address counts as visitor-typed and gets at most 3 emails a day.
Reply to sender
Action Send a confirmation to the person who filled in the form.
- Goes to
{{email}}by default, or to the form's first email field when no field has the key email. Only the first valid address gets it, and there is no Cc. - Comes from your workspace name, with Reply to and Subject as in Send email.
- Long free text answers are left out, other answers and step values are cut after 80 characters, and one address gets at most 3 emails a day. See Auto-replies stay safe.
Post to Slack
Action Post a message in a Slack channel.
- Pick a connected Slack channel. Connect channels on the Destinations page first.
- Write the message with variables. Slack formatting such as *bold* works.
- Include every answer adds the answers under the message as labeled fields, up to 40. Hidden fields are left out.
Post to Teams
Action Post a card in a Microsoft Teams channel.
- Pick a connected Teams channel. The message is posted as a card.
- Include every answer adds the answers to the card as a list of facts, up to 30. Hidden fields are left out.
Post to Discord
Action Send a message to a Discord channel.
- Pick a connected Discord channel.
- Include every answer adds the answers as an embed with one field each, up to 25. Hidden fields are left out.
- Mentions are switched off, so an answer like @everyone never pings anyone.
Post to Google Chat
Action Post a message in a Google Chat space.
- Pick a connected Google Chat space.
- Write the message with variables. *Bold* works.
- Include every answer adds each answer on its own line, label in bold, up to 40. Hidden fields are left out.
Post to Mattermost
Action Post a message in a Mattermost channel.
- Pick a connected Mattermost channel. The message is posted as Markdown, signed as Formpik.
- Include every answer adds each answer on its own line, label in bold, up to 40. Hidden fields are left out.
Send to Telegram
Action Send a message to a Telegram chat or group through your bot.
- Pick a connected Telegram chat. Your own bot sends the message.
- The message goes out as plain text, so answers can never change its formatting, and link previews are off.
- Include every answer adds each answer on its own line, up to 40. Hidden fields are left out.
Send webhook
Action Send the submission as JSON to your CRM, backend or any URL.
- Pick a connected webhook. The body is always the same JSON: the submission id, the form, the source, the time, every answer under data, and the values of earlier steps and readable answers under values.
- Each request is signed with
X-Formpik-Signatureand carriesX-Formpik-Event,X-Formpik-Deliveryand anIdempotency-Key. See Webhooks. - Any 2xx answer is a success. Anything else, or no answer within 10 seconds, fails the step with the status and the start of the response.
Branches
Branching steps have one dot per path, and each connection remembers which dot it starts from. Every other step has a single path out.
| Step | Paths |
|---|---|
| Validate | Passed, and Failed or spam |
| Route by answer | One per route, named after its option, plus Anything else |
| If / else | Yes and No |
| Every other step | One path |
Removing a route also removes the connection from its dot. To act on a combination, chain steps: an If / else behind a route only sees the submissions of that route.
Test before you go live
| Way to test | Where | What happens |
|---|---|---|
| Test run | Flow editor | Fills in sample answers that you can change, runs this flow and highlights the path the submission took, step by step. Nothing is stored or sent: emails, messages and webhooks are described, waits are skipped and Ask AI uses a stand-in answer. |
| Test submission | Preview in the form builder | Saves a submission marked as a test and runs every live flow of the form the same simulated way. It shows in the inbox with its runs. |
| Live run | Your website | Real deliveries, real waits and real AI answers. |
Go live
Go live checks the whole flow first. Problems that would break a step block it: the header shows how many there are, and the first one opens. Every step must have its settings, every field it uses must still be in the form, every variable must be a field or a value set earlier, and destinations must still be connected. These are the problems the check can find:
| Step | Problems |
|---|---|
| Form submitted | Choose which form starts this flow. The selected form no longer exists |
| Validate | Turn on at least one check. A check points to a field that is not in the form |
| Route by answer | Choose a field to route by. The field "..." is not in the form. Add at least one route |
| If / else | Choose a field to check. The field "..." is not in the form. Add a value to compare with |
| Wait | Set how long to wait |
| Set values | Add at least one value. Every value needs a name |
| Ask AI | Name the value the answer is saved as. The value name is already a field key, pick another one. Choose the text the AI reads. List at least two categories. Choose a language. Describe what to pull out. Write the instructions |
| Send email | Add at least one recipient. Add a subject |
| Reply to sender | Choose who receives the reply. The form has no field with the key "email". Add a subject |
| Slack, Teams and Discord | Choose a connected channel. The selected destination was removed |
| Send webhook | Choose a webhook to send to. The selected destination was removed |
Any template can also show "Unknown field" for a variable that is neither a field of the form nor a value from a step. Two things are only warnings: a step nothing connects to, which never runs, and a trigger with nothing after it.
Flow statuses
| Status | Meaning |
|---|---|
| Draft | New and duplicated flows. They never run for real submissions. |
| Live | Runs for every new submission of its form. |
| Paused | Stopped by Pause. New submissions are stored, but this flow does not run for them. Go live again to restart it. |
Run results
| Run | Meaning | Submission shows |
|---|---|---|
| Completed | Every step on the path ran. | Delivered |
| Stopped | A Validate step found spam or invalid answers. | Spam or Invalid |
| Failed | A delivery failed or a step was missing its destination. | Needs attention |
| Waiting | A path is paused behind a Wait step. | Stored |
When a submission runs several flows, the strongest result wins: spam, then invalid, then failed, then waiting, then delivered.
When a delivery fails
- 01
Find the step
Open the submission in the inbox. Its run shows the step that failed and the reason, such as the status and response a webhook answered with. - 02
Fix the cause
Reconnect the channel, correct the address or fix your endpoint. Owners and admins also get an email when Delivery problems is on under notifications in Settings. - 03
Run it again
Choose Run flows again on the submission. It replaces the earlier runs and runs every live flow of the form from the start.
Examples
Sales to Slack, support by email
- 01Contact form submittedStarts on every submission.
- 02ValidateForm rules and spam filter.
- 03Route by topicSales, Support, Anything else.
- 04DeliverSales to #sales, Support to support@, the rest to hello@.
- For a form made from the Contact form template, create a flow with the Route by answer template. It routes on
topic, with a route for each of its four options. - Keep the Sales and Support routes and remove the others, so Partnerships and Something else go down Anything else.
- Replace the Sales email with Post to Slack to
#sales, messageNew lead: {{full_name}} ({{email}}), with Include every answer on. - Set the Support email To
support@yourcompany.comand the Anything else email Tohello@yourcompany.com. - Run a test with each topic, then Go live.
Confirm to the sender
The Notify and confirm template connects two steps to Passed: Email the team and Confirm to sender, a Reply to sender step. Both run for every valid submission.
Subject: We got your message, {{full_name | there}}
Hi {{full_name | there}},
Thanks for contacting us about {{topic}}. We reply within one working day.Summarize, then post to Slack
- 01Quote request submittedStarts on every submission.
- 02ValidatePassed only.
- 03Ask AISummarize into
{{ai_summary}}. - 04Post to SlackSummary on top, answers below.
*{{name}}* asked for a quote ({{budget}})
{{ai_summary | No summary this time}}Alert on low scores
For a feedback form with an NPS question, add If / else with When recommend_score, Is is less than, value 7. Connect Post to Slack to Yes, so the team hears about every score of 6 or lower. Add Wait 2 days on No, then a Reply to sender that asks happy customers for a review.