Get started
How Formpik works
Five building blocks make up every workspace. Each one can be paused or changed on its own, so you can rework a flow without touching your website.
On this page you will learn
- What sources, forms, flows, destinations and submissions are
- What every status means, as you see it in the app
- The life of one submission, from arrival to delivered, failed or spam
- How field keys and source keys connect everything
The building blocks
| Block | What it is | Where you manage it |
|---|---|---|
| Source | One website or tool that sends submissions, with its own endpoint key. | Sources, or a form's Connect tab |
| Form | The fields a submission carries, and the rules for who may send it. | Forms |
| Flow | A graph of steps that runs when its form receives a submission. | Flows |
| Destination | A connected Slack, Teams or Discord channel, or a webhook. Email is built in. | Destinations |
| Submission | The answers, where they came from, and the run of every flow that handled them. | Submissions |
Sources
A source is one place that sends submissions: a Webflow site, a WordPress page, your own app, or a Zapier zap. Each source has a unique endpoint address, https://formpik.com/api/in/{key}, and belongs to exactly one form.
Why separate sources? Because one form often lives in several places. An agency might run the same quote form on its main site and on a landing page. With two sources, the inbox shows which page every request came from, a flow can run only for one of them, and you can pause the landing page without touching the main site.
Forms
A form describes the fields a submission carries. Each field has a key (the name your website sends), a label (what people read), a type such as email, dropdown or file, and rules such as required. Several sources can feed one form.
The form also holds the rules for taking submissions: the success message and redirect, the allowed websites, the spam trap and bot check, the hourly limit per visitor, and how long submissions are kept. Read more in Forms.
Flows
A flow is a chain of steps you draw in the editor. It starts with a Form submitted step that names its form and, optionally, only some of its sources. After that come logic steps (Validate, Route by answer, If / else, Wait, Set values, Ask AI) and action steps (Send email, Reply to sender, Post to Slack, Post to Teams, Post to Discord, Send webhook).
A form can have several flows, and every live one runs for each submission. For a SaaS support form, one flow might route messages by topic to Slack, while a second flow sends every message to the help desk by webhook. See Flows.
Destinations
A destination is a connected place to deliver to: a Slack, Microsoft Teams or Discord channel, or a webhook address in your own system. You connect it once and pick it in any flow. Email needs no destination: email steps send straight from Formpik. See Destinations.
Submissions
A submission is one set of answers. Formpik keeps the answers, any uploaded files, where it came from (the source, the page, the country and the browser) and the run of every flow that handled it. You find them all in the Submissions inbox.
Statuses
Each block has a status, shown as a badge in the app. These are the same labels you see there.
| Thing | Status | Meaning |
|---|---|---|
| Form | Accepting | Takes submissions. Switch Accept submissions off in its settings to pause it. |
| Form | Paused | Every source of the form answers 403 and stores nothing. |
| Source | Waiting for first submission | Created, but nothing has arrived yet. |
| Source | Receiving | At least one submission came in. |
| Source | Paused | This source answers 403. The form keeps working for its other sources. |
| Flow | Draft | Being built. It never runs on real submissions. |
| Flow | Live | Runs for every new submission of its form. |
| Flow | Paused | Kept, but does not run. New submissions are still stored. |
| Submission | Stored | Stored. No live flow ran yet, or a flow is waiting behind a Wait step. |
| Submission | Delivered | Every flow finished without a failed step. |
| Submission | Needs attention | A delivery did not work. The inbox shows which step and why. |
| Submission | Invalid | A Validate step stopped it because an answer broke a rule. |
| Submission | Spam | Caught by the spam trap, the bot check, a Validate step's spam filter, or marked by a person. |
Each flow run of a submission has its own status too:
| Run status | Meaning |
|---|---|
| Completed | The flow reached its end. |
| Waiting | The flow is paused at a Wait step and carries on when the wait is over. |
| Stopped | A Validate step found a problem or spam, so the run went down its failed path. |
| Failed | A step could not deliver, such as a webhook that answered with an error. |
The life of a submission
Here is what happens, in order, when a visitor sends your form.
- 01ArrivesYour website posts to the source address.
- 02CheckedKey, allowed websites, pauses, limits, spam.
- 03StoredAnswers and files are saved. Your site gets its answer.
- 04Flows runEvery live flow of the form, one after another.
- 05SettledDelivered, needs attention, invalid or spam.
- 01
It arrives and is checked
Formpik finds the source by its key and checks, in this order: that the sending website is allowed, that the source and the form are not paused, that the address has not sent more than 120 submissions in the last minute, that the body can be read and is not empty, that it is not a repeat, that the workspace has submissions left this month, and that the visitor is within the form's hourly limit. Anything that fails is refused with a clear message and nothing is stored. - 02
Spam is held back
If the hidden_gotchafield is filled in, or the form's bot check is missing or failed, the submission is stored as Spam with the reason, and no flows run. Nothing is thrown away: you can release it from the inbox. - 03
It is stored and answered
The answers are saved, uploaded files go to private storage, and the source becomes Receiving. New answer names become new fields when the form learns fields. Your website gets its answer now, before any flow runs. - 04
The flows run
Every live flow of the form whose trigger matches the source runs, step by step, and sends its emails, messages and webhooks for real. A Wait step parks the run, and Formpik picks it up again when the time is up (checked every 5 minutes). - 05
It settles
When the runs end, the submission gets its final status. Spam wins over invalid, invalid over a failure, and a waiting run keeps it Stored. If every run finished cleanly, it is Delivered. If a delivery failed, owners and admins get an email about it, unless Delivery problems is off in Settings.
Keys connect everything
Field keys
The key of a field, such as email or budget, is the name your website sends. It is also how flows refer to the answer, for example {{email}} in an email step or the field a Route by answer step looks at. Keys appear as column names in CSV exports and as property names in webhooks and the API.
Website <input name="budget" value="5000">
Submission { "budget": "5000" }
Flow If / else: budget is greater than 2000
Email New project with a budget of {{budget}}
CSV a "Budget" columnWhen you rename a key in the form builder, Formpik updates every flow of that form that uses it, including routes on option values. Your website has to send the new name too, so change both together.
Source keys
The source key is the last part of the endpoint address. It tells Formpik which form a submission is for and where it came from, so your website never needs to send a form id. Treat it like an address, not a secret: it sits in your page's HTML. Protect a form with allowed websites, the spam trap and a bot check instead, see Spam, privacy and security.