# Submissions inbox

Every submission your forms receive lands in Submissions, with where it came from and every step every flow took. New ones appear on their own every 30 seconds.

**On this page you will learn**

- What the inbox shows and how to read it
- How to search and filter, and share a filtered view
- What you find inside one submission
- How to fix a failed delivery and run flows again
- How to review spam and release a submission
- How to export to CSV and how long submissions are kept

## The inbox at a glance

Open **Submissions** in the sidebar. Each row is one submission, newest first, 25 to a page. The list holds the latest 1,000 submissions of the workspace and refreshes every 30 seconds while the tab is open. To read older ones, use the [Submissions API](https://formpik.com/docs/api/submissions).

| Column | What it shows |
| --- | --- |
| From | The name and email of the person who sent it, taken from the answers. |
| Form and message | The form, the source it came through, a test mark for test submissions, and the start of the message. |
| Outcome | The status of the submission, see below. |
| Received | How long ago it arrived. |

The outcome is one of these:

| Outcome | What it means | What to do |
| --- | --- | --- |
| `Delivered` | Every flow finished without a failed step. | Nothing. |
| `Stored` | Stored. No live flow handled it yet, or a flow is waiting behind a Wait step. | Turn a flow on if none is live, then run its flows again. |
| `Needs attention` | A step could not deliver, for example a webhook that answered with an error. | Open it, read the failing step, fix the cause and run its flows again. |
| `Invalid` | A Validate step found an answer that breaks a rule. | Check the answers. Often nothing, as the flow did what you asked. |
| `Spam` | Held back as spam by the endpoint, flagged by a Validate step, or marked by a person. | Review it, and release it if it is real. |

## Search and filter

- **Search** looks through every answer of every submission, and the submission id. Type a name, an email address, a company or a word from the message.
- **Form** shows the submissions of one form only.
- **Outcome** narrows the list to one group, see the table below.

| Filter | Shows |
| --- | --- |
| All | Everything. |
| Delivered | Submissions that are `Delivered` or `Stored`. |
| Needs attention | Submissions with a failed delivery. |
| Spam or invalid | Submissions that are `Spam` or `Invalid`. |
| Tests | Test submissions from the form builder. |

The form and outcome filters, and the submission you open, are kept in the page address. Bookmark a view or send it to a teammate, and it opens the same way:

*Addresses*

```
/submissions?status=failed              Needs attention
/submissions?status=blocked             Spam or invalid
/submissions?status=test                Tests
/submissions?form=FORM_ID               One form
/submissions?id=SUBMISSION_ID           Opens one submission
```

## Inside a submission

Click a row to open the submission in a panel on the right. From top to bottom you see:

- **The header**: the sender, their email, the outcome, a test badge for tests, the form and when it arrived. When the endpoint held it as spam, a note says why, for example that the hidden spam trap field was filled in.
- **Answers**, shown by their labels. Choice fields show the option label people picked. An answer under a name the form does not have is shown under its key with a small `new` tag. Uploaded files are listed with their size and open through a private link that works for 15 minutes.
- **Flow runs**: one card per flow that handled it, with how long it took and the run status. Each card is a timeline of steps: what each step did, which path a branch took, what AI wrote, and the reason for any failure. The flow name links to the flow.
- **Details**: the source and its website, the exact time, the page it was sent from, the browser, the country and the IP address. When IP addresses are anonymized, the last part is removed and the panel says so.
- **Raw data**: the answers exactly as they were stored, as JSON.

## Actions

| Action | What it does |
| --- | --- |
| Run flows again | Runs every live flow of the form again and replaces the earlier runs. For a real submission it asks first, because every email, chat message and webhook goes out again. A test submission stays a test, so nothing is sent. |
| Mark as spam | Sets the outcome to Spam. It stays in the inbox under Spam or invalid. |
| Not spam | Releases a submission. One the endpoint held back as spam has never run its flows, so they run now. One that already has runs goes back to the outcome of those runs. |
| Copy JSON | Copies the id, form, time and answers as JSON, ready to paste into a ticket or a chat. |
| Delete | Removes the submission, its answers, its run history and its files for good. It does not undo emails or messages that were already sent. |
| Export CSV | Downloads the submissions that match your search and filters. |

> **Spam never runs flows**
>
> Run flows again is not offered for a submission marked as spam. Choose **Not spam** first.

### Example: fix a failed delivery

A SaaS team routes billing questions to a Slack channel. Someone renames the channel and removes the app, so the Post to Slack step starts failing. If **Delivery problems** is on in Settings, owners and admins get an email naming the form, the flow and the reason. To fix it:

1. **Find what failed**

   Open Submissions and choose **Needs attention**.
2. **Read the reason**

   Open a submission. In its flow run, the failed step is marked and shows the answer the channel or webhook gave.
3. **Fix the cause**

   Reconnect the channel on the Destinations page, or fix the step in the flow. See [Destinations](https://formpik.com/docs/destinations).
4. **Run it again**

   Back in the submission, choose **Run flows again** and confirm. The new run replaces the failed one, and the outcome changes to `Delivered` when it works.

> **Run flows again runs every flow**
>
> It runs every live flow of the form, not only the one that failed. If another flow already emailed the sender, that email goes out again. Check the runs before you confirm.

## Review spam

Formpik never throws spam away silently. Choose **Spam or invalid** to see what was held back. A submission the endpoint caught shows its reasons at the top, such as a filled spam trap or a missing bot check, and has no flow runs. If it is real, choose **Not spam**: its flows run right away and it is handled like any other submission.

See [Spam, privacy and security](https://formpik.com/docs/security) for every spam layer and how to tune them.

## Export to CSV

Choose **Export CSV** at the top of the page. You get a file named `formpik-submissions-YYYY-MM-DD.csv` with the submissions that match your current search and filters, so filter first to export one form or one outcome.

- The first columns are `Submission ID`, `Received at (UTC)`, `Form`, `Source` and `Status`.
- Then one column per field, named by its label. Answers under names the form does not have get a column named by their key.
- Choice fields show the option label, and lists are joined into one cell.
- The file is UTF-8, so names with accents and other alphabets come through as they are.
- The export covers the submissions loaded in the inbox, which is the latest 1,000. For more, page through the Submissions API.

## Test submissions

When you submit the live preview in the form builder, Formpik saves a **test submission**. It shows a test badge in the inbox, its source reads "Form builder test", and the live flows of the form run as a test: every step is worked out, but no email, message or webhook is sent. Test submissions do not count toward your plan's monthly submissions. Use the **Tests** filter to find them, and delete them when you are done.

## How long submissions are kept

Each form keeps submissions for the time set under **Keep submissions for** in its Settings tab. Formpik deletes older submissions and their files every hour. New forms start with the workspace default, set under **New forms keep submissions for** in Settings. The choices depend on your plan:

| Plan | Longest time | Choices |
| --- | --- | --- |
| Starter | Up to 30 days | 30 days |
| Pro | Up to a year | 30 days, 90 days, 1 year |
| Max | Forever | 30 days, 90 days, 1 year, Forever |

Deleting a form deletes its stored submissions too. Read more in [Plans and limits](https://formpik.com/docs/plans).

## Who can do what

Everyone in the workspace can read submissions, open files, copy JSON and export CSV. Running flows again, marking spam, releasing spam and deleting need the editor role or higher. See [Workspaces and team](https://formpik.com/docs/team).

## Questions

### Why does a new submission take a moment to appear?

The inbox checks for new submissions every 30 seconds while the tab is open. Reload the page to check right away.

### A submission says no live flow used the form. What now?

No flow of that form was live when it arrived, so it was only stored. Go live with a flow in Flows, then open the submission and choose **Run flows again**.

### Can I undo a delete?

No. Deleting removes the submission and its files for good. Export to CSV first if you might need it.

### Does spam count toward my monthly submissions?

Spam the endpoint stores counts, because it arrived through a source. Test submissions do not count.

### Can I search older submissions than the inbox shows?

The inbox holds the latest 1,000. Use `GET /api/v1/submissions` with `since` and `before` to read further back.

## Next steps

- [Spam, privacy and security](https://formpik.com/docs/security): Every spam layer, and how your data is kept.
- [Flows](https://formpik.com/docs/flows): What each step does, so you can read a run timeline.
- [Submissions API](https://formpik.com/docs/api/submissions): List, filter and read submissions from your own code.
- [Plans and limits](https://formpik.com/docs/plans): Monthly submissions and retention per plan.

---

Source: https://formpik.com/docs/submissions
