HigherStack What happens when someone submits
Follow a submission from the respondent’s click to your inbox and integrations.
Step by step
| Stage | What happens |
|---|---|
| Submit | The respondent submits. The server checks the form is live and accessible, applies rate limits, password, duplicate and origin rules, then re-runs validation, logic and routing. |
| Save | The validated response (plus any attribution data) is stored. |
| Fan-out | Saving the response fires a trigger that delivers to all configured destinations. |
| Deliver | Notification + confirmation emails, integrations (Notion/Airtable/Sheets), webhooks, and ad-platform conversions all go out. |
Why validation runs again on the server
The browser checks answers for a smooth experience, but the server is the source of truth. It re-evaluates your required rules, conditional logic and routing using the same definition the form uses — so only the questions a respondent actually saw are enforced, and the rules can’t be bypassed. Calculations are recomputed server-side too.
Tip
Delivery is resilient: a failed integration or email doesn’t stop the others, and conversions are retried automatically. See Integrations overview.
Still need help?
A dedicated support form is coming soon. In the meantime, jump back into the product or reach the team from the contact page.