---
title: "Trigger a flow from a submission"
description: "Make a form the start of an automation: when someone submits it, they are enrolled with the submission date as the reference date, so you can thank them, route a request or follow up."
sidebar:
  order: 2
area: flows
feature: forms
appPath: /flows/home
lastVerified: 2026-10-22
version: "2026-10-16"
audience: admin
related:
  - flows/automations/trigger-a-flow-from-a-form-submission
  - flows/forms/tutorial-buddy-selection-form
  - flows/automations/configure-a-team-change-trigger
intercom:
  - id: "16304943"
    title: Set up a buddy automation (Pyn 2)
    url: https://intercom.help/pyn/en/articles/16304943-set-up-a-buddy-automation-pyn-2
    note: replaces
---

A form answered is a moment in itself. An interest form deserves resources the same day; a request form should land with the team that handles it. The **Form Submission** trigger starts an automation for the person who submitted a given form.

## Before you start

- The form is published. See [Build a form](https://support.pynhq.com/flows/forms/build-a-form/).
- You know who submits it. The enrolled person is the submitter, so a form the manager fills in enrols the manager.

## Steps

1. In Pyn, open **Flows** in the left navigation, select **Forms**, and confirm the form shows a tick under **Publish**.

2. Select **Automations**, then **Create New**. In **Select Trigger**, choose **Form Submission**, choose the form from the list, then **Done**.

3. Add the steps that should follow a submission, with **To** set to **Employee** (the submitter) or whoever should hear about it. Schedule them **on the day of** or shortly after.

4. Select **Publish**, then set the mode. [Trigger a flow from a form submission](https://support.pynhq.com/flows/automations/trigger-a-flow-from-a-form-submission/) covers the trigger's settings.

5. Embed the form in a message step elsewhere, or send its respond link, so people can submit it: see [Embed a form in a message](https://support.pynhq.com/flows/forms/embed-a-form-in-a-message/).

> **Note:** Polls never trigger a flow, and test submissions are ignored. Each completed submission creates a new enrollment, even from the same person, unless you change the trigger's repeat-enrolment setting.

## When the trigger is the wrong tool

If what you care about is the *relationship* the form writes, not the submission, trigger on that instead. A Buddy field in a manager's form sets the new starter's buddy; the **Buddy Assigned** trigger then fires for the new starter, who is the person your buddy flow is about. See [Configure a team change trigger](https://support.pynhq.com/flows/automations/configure-a-team-change-trigger/) and the [buddy selection tutorial](https://support.pynhq.com/flows/forms/tutorial-buddy-selection-form/).

## What you should see

Each submission creates an enrollment under [Enrollments](https://support.pynhq.com/activity/enrollments/) with the submitter as the employee and the submission date as the **Reference Date**; its steps schedule from there. The form's **Activity** drawer and the enrollment both show the same submission.

## Related

- [Trigger a flow from a form submission](https://support.pynhq.com/flows/automations/trigger-a-flow-from-a-form-submission/) for the automation side.
- [A buddy selection form that triggers a flow](https://support.pynhq.com/flows/forms/tutorial-buddy-selection-form/) for a worked example.
- [Configure a team change trigger](https://support.pynhq.com/flows/automations/configure-a-team-change-trigger/) for Buddy Assigned.

## Related Intercom articles

- [Set up a buddy automation (Pyn 2)](https://intercom.help/pyn/en/articles/16304943-set-up-a-buddy-automation-pyn-2) — replaces