# Create a submission export flow

When a user or automation marks a Formflow submission as "completed", then you likely want to make use of the data somewhere else. 

It is straightforward to set up a custom export flow. There are a number of helpful third party services for such processing, including [n8n](https://n8n.io/), [Zapier](https://zapier.com/) and [IFTTT](https://ifttt.com/), or you can roll your own solution. 

All approaches can make use of Formflow's [webhook](https://docs.ai.insly.com/nora/api-documentation/webhooks) notifications, [API](https://docs.ai.insly.com/nora/api-documentation) and MCP services.

### Be notified of new submissions

You will want to react to new submissions in the `completed` status. There are two ways to automate this:

* Regularly poll [`GET /submission`](https://docs.ai.insly.com/nora/configuration-guide/broken-reference) for a list of the most recent submissions, maintain a list of processed submissions, and choose which submissions to process
* Register a [webhook subscription](https://docs.ai.insly.com/api-documentation/webhooks#post-webhook-subscription). In this case, Formflow will `POST` at your designated endpoint and include a submission ID.

### Fetching completed submissions

Regardless of how you became aware of a new completed submission, you will want to [`GET /submission/{id}`](https://docs.ai.insly.com/nora/configuration-guide/broken-reference) using the unique submission ID. The response will include:

* submission metadata
* presigned temporary file download URLs (if configured)
* the complete data payload in JSON format

You can then process the submission `payload` per your business logic.