Someone submits your form. You want their answers in your team's sheet or your CRM, or sent somewhere different depending on what they picked, without copying anything by hand.
Submits a Form starts a Flow Builder automation every time a chosen form is submitted. Flow Builder is included on Pro, Ultimate and Business. Sharing the form link in a DM is a separate automation: see Share a form from an Instagram automation.
Set up the trigger
Publish your form in the same workspace as the automation.
Go to Automations, create a new automation and choose Flow Builder.
In the trigger list, under Forms, choose Submits a Form. If it's greyed out, it isn't switched on for your workspace yet; contact support.
Click Select a form and pick your form. If you haven't published one yet, you'll see Create a form first.
Choose what happens next
After this trigger you can add Condition, Randomize, Smart Delay, Send HTTP Request and Add row to Google Sheets. Send a DM and Send Meta Conversion Event aren't offered, because a form submission doesn't open an Instagram conversation.
Add row to Google Sheets (Ultimate and Business): see Add rows to Google Sheets from Flow Builder.
Send HTTP Request: see Send an HTTP request from Flow Builder. If it's greyed out, it isn't switched on for your workspace yet.
Not sure which to pick? See Choose what happens after a form is submitted.
Route submissions with a Condition
A Condition checks the answers and sends each submission down its Yes or No path.
Add a Condition step and click Add Condition.
Under Form Fields, pick the question to check. Required Email and Phone questions aren't listed, since every submission has them.
Choose how to compare, then the value: - Text and Country: contains or doesn't contain - Number and Rating: above or below - Date: before or after - Dropdown and Checkbox: is one of or is not one of - Email, Phone, URL and Upload: exists or doesn't exist
With more than one rule, choose whether a submission must match all or any of them.
Connect the next step to the Yes path, and another to the No path if you need it.
For example, a workshop form with a City dropdown can send City is one of Bengaluru to the workshop sheet, and everyone else to a waitlist sheet.
Build your rules from Form Fields. Contact Properties and Engagement rules check an Instagram contact, and a form submission doesn't come with one.
Keep rules in step with your form
A rule finds its answer through the question's Form field slug, which you set in the form editor. If you change a question's slug after adding the rule, or the rule was added before slugs arrived in August 2026, the rule can't find the answer and submissions won't follow the path you expect. To fix it, click the bin icon on the rule, add the question again from Form Fields, then click Update.
Use the answers in an HTTP request
In a Send HTTP Request step, type {{form. followed by the question's Form field slug and }} wherever you want an answer. For a question with the slug city, a body could look like this:
{"city": "{{form.city}}", "email": "{{email}}"}
Questions whose slug is exactly name, email or phone also work as {{name}}, {{email}} and {{phone}}. Type these yourself: the Form Answers list in the body editor currently inserts a placeholder that's sent as plain text. Endpoint, method and header setup are in Send an HTTP request from Flow Builder.
Go live and test
Click Go Live. Only live automations run. After later edits, click Update so the changes take effect.
Open your form's link and submit a test entry.
Check the entry on the form's Submissions tab, then check the destination: the row in your sheet, or the record in your other tool.
Good to know:
Every submission runs the flow, including repeat submissions from the same person.
If more than one live automation uses the same form, each of them runs.
If the form verifies email addresses, the flow runs as soon as the form is submitted, before the person enters their code.