Trigger a flow from a submission

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.
You know who submits it. The enrolled person is the submitter, so a form the manager fills in enrols the manager.

Steps

In Pyn, open Flows in the left navigation, select Forms, and confirm the form shows a tick under Publish.
Select Automations, then Create New. In Select Trigger, choose Form Submission, choose the form from the list, then Done.
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.
Select Publish, then set the mode. Trigger a flow from a form submission covers the trigger’s settings.
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.

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 and the buddy selection tutorial.

What you should see

Each submission creates an enrollment under 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.

Trigger a flow from a form submission for the automation side.
A buddy selection form that triggers a flow for a worked example.
Configure a team change trigger for Buddy Assigned.