Get started
How Formera 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.
The building blocks
| Block | What it is | Where you manage it |
|---|---|---|
| Source | One website or tool that sends submissions. Each source has its own endpoint key, so you can pause, replace or remove it without touching the others, and every submission knows where it came from. | Sources, or a form's Connect tab |
| Form | The fields a submission carries: a key, a label, a type, options and rules for each. Several sources can feed one form. | Forms |
| Flow | A graph of steps that starts when its form receives a submission. A form can have several flows. | Flows |
| Destination | A connected Slack, Teams or Discord channel, or a webhook. Email is built in and needs no setup. | Destinations |
| Submission | The answers, where they came from, and the run of every flow that handled them. | Submissions |
Statuses
| Thing | Status | Meaning |
|---|---|---|
| Form | active | Takes submissions. |
| Form | paused | The endpoint answers 403 and stores nothing. |
| Source | waiting | Created, but nothing has arrived yet. |
| Source | live | At least one submission came in. |
| Source | paused | This source answers 403, the form keeps working for other sources. |
| Flow | draft | Being built. It never runs on real submissions. |
| Flow | active | Runs for every new submission of its form. |
| Flow | paused | Kept, but does not run. |
| Submission | received | Stored. No flow ran yet, or a flow is waiting behind a Wait step. |
| Submission | delivered | Every flow finished without a failed step. |
| Submission | failed | 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, a bot check or the spam filter. No delivery steps ran. |
Field keys connect everything
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. When you rename a key in the form builder, Formera updates every flow that uses it, but your website has to send the new name too.