# Start a scenario from public link submissions

Run a Make scenario when someone submits, edits or abandons a form through its share link, and map each answer by its question.

## Before you start

You need a [Formstep connection in Make](https://formstep.io/docs/guides/make/connect/) and a published form with a share link. A submission to a request link does not start this trigger; [Watch requests](https://formstep.io/docs/guides/make/requests/#watch-requests) covers those.

## 1. Add the trigger

Create a scenario, click the big **+**, search for **Formstep** and pick **Watch public link submissions**. Under **Webhook**, click **Create a webhook**, pick your connection, the **Form**, and the **Event**:

| Event | Fires when | Needs |
| - | - | - |
| Submission created | A respondent submits the form through a share link. | Nothing extra. |
| Submission updated | A respondent edits a submission they already sent. | [Edit after submit](https://formstep.io/docs/submissions-analytics/edit-after-submit/) turned on for the form. |
| Submission abandoned | A respondent starts the form and leaves it unfinished for the time you choose, from 12 hours to 1 week. | A Pro or Business plan, which saves [partial submissions](https://formstep.io/docs/submissions-analytics/partial-submissions/#unfinished-drafts). |

Click **Save**. Formstep now sends that event for that form to Make. For the abandoned event, Formstep checks once an hour, so the scenario can start up to an hour after the time you chose.

> **One trigger, one event**
>
> Each trigger hears one event. To act on new submissions and on edits, add two scenarios, one per event. A submission through a request link never reaches this trigger, so a scenario that watches both requests and public links on the same form runs once per completion.

## 2. Test the trigger

Click **Run once**, then submit the form through its share link. The trigger shows one bundle. Open it to see what arrives:

| Field | Holds |
| - | - |
| Event type | `submission.completed`, `submission.updated` or `submission.abandoned`. |
| Data › Answers | The value a scenario compares: the [option key](https://formstep.io/docs/requests/field-keys/) of a choice, a number, a date. |
| Data › Answers (display) | The text a person reads: the option label, a formatted date. |
| Data › Form | The form the submission belongs to. |
| Data › Submission | The submission's id, time, language and PDF link. |

## 3. Map the answers

Add the next module. In its fields, open the mapping panel: each question of the form is listed under **Answers** and **Answers (display)** by its title. Use **Answers (display)** in messages and **Answers** in filters and lookups.

The list comes from the form’s published questions. If you add a question, publish the form and reopen the module so Make loads it. The full shape of the event is in the [webhooks reference](https://formstep.io/docs/developers/webhooks-reference/).

## 4. Turn the scenario on

Save the scenario and switch it on. Formstep sends every new event as it happens. Deleting the trigger’s webhook in Make removes the subscription in Formstep too.

## Next steps

[Send requests and act on their outcome](https://formstep.io/docs/guides/make/requests/) — Create a request, then run a scenario when it ends

[Webhook API reference](https://formstep.io/docs/developers/webhooks-reference/) — Format, signing and retries, for developers