Redirects After a monday.com Form Submission
Published on September 4, 2026
The default thank-you screen after a form submission is fine for most forms. It stops being fine when you need the respondent to land somewhere specific next: a scheduling page, a payment link, a resource download, or your own branded confirmation page instead of a generic message inside monday.com.
Both WorkForms and FormFlow can redirect a respondent after they submit. Neither one can send different respondents to different URLs based on what they answered. Here is what each actually supports, and where the static-URL limit shows up in practice.
Quick answer
- WorkForms has a native Redirect URL toggle in form settings that sends every submitter to one static URL after a brief success message. It does not support conditional or per-response redirects.
- FormFlow has a Success Page URL and a separate Error Page URL, plus an Automatic Redirect option so the redirect fires without the respondent clicking anything. It is also one static URL per outcome, not a per-respondent dynamic link.
- If you need the destination to vary by answer (route a lead form to a different landing page depending on which product they picked, for example), neither tool does that natively — you need an automation step in between to compute the URL first.
- Install FormFlow to set a Success and Error Page URL on your next form.
How WorkForms’ Redirect URL Works
WorkForms lets you turn on a redirect under the form’s settings, documented in monday.com’s own Get started with WorkForms article. Enter one destination URL, and every submitter who completes the form is sent there after a short built-in success message.
The limitation is the single URL:
- One URL for everyone. There is no way to point different respondents at different pages based on their answers, form used, or any other condition.
- The success message shows first. Submitters see WorkForms’ own confirmation notice briefly before the redirect happens, which you cannot fully suppress or restyle.
- No separate error destination. If the submission fails, there is no distinct failure-page URL to send them to.
Teams that need conditional destinations — a different link per product line, per region, or per campaign — end up scripting it with an automation and a third-party app, since WorkForms’ setting itself only accepts one static URL.
How FormFlow’s Success and Error Page URLs Work
FormFlow’s external redirect settings split the destination into two:
- Success Page URL — where the respondent goes after a successful submission.
- Error Page URL — a separate destination if the submission fails, instead of leaving them on a generic error state.
- Automatic Redirect — when enabled, the redirect happens without the respondent needing to click a button.
To set it up:
- Open your form in the FormFlow builder and go to Settings.
- Find Post-Submission Experience → External Redirect.
- Enter a Success Page URL (and an Error Page URL if you want failed submissions handled differently).
- Turn on Automatic Redirect if you don’t want the respondent to see FormFlow’s thank-you screen first.
- Publish and test the full submission flow yourself before sharing the link.
Like WorkForms, each URL is fixed at the form level — FormFlow does not evaluate the respondent’s answers to pick a destination. The difference from WorkForms is the separate success/error destinations and the option to skip the intermediate confirmation screen entirely.
Side-by-Side
| Behavior | WorkForms | FormFlow |
|---|---|---|
| Redirect on successful submission | Yes, one static URL | Yes, one static Success Page URL |
| Separate URL for failed submissions | No | Yes, a distinct Error Page URL |
| Skip the built-in confirmation message | No — success message shows first | Yes, with Automatic Redirect enabled |
| Redirect destination varies by answer | No | No |
| Where to configure | Form settings toggle | Form settings |
When You Need a Conditional Redirect
If the destination genuinely needs to change based on what the respondent submitted — a scheduling link that differs by service selected, or a payment link sized to the plan they chose — a static redirect setting cannot do that on its own, on either tool. The usual pattern is to compute the URL in an automation step first (using the submitted values), write it to a column, and send it to the respondent by email or on a follow-up page rather than relying on the form’s own redirect field. That is a heavier build than either tool’s native redirect setting, so reserve it for cases where a single shared destination genuinely will not work.
Frequently Asked Questions
Can WorkForms redirect different respondents to different URLs?
No. The Redirect URL setting in WorkForms accepts a single destination that applies to every submitter, regardless of what they entered on the form.
Does FormFlow support a redirect that changes based on form answers?
No. FormFlow’s Success Page URL and Error Page URL are each fixed at the form level, the same static-URL model as WorkForms, just split into a success and a failure destination.
Can I skip the “Thank you” message and go straight to my own page?
With FormFlow, yes — enable Automatic Redirect alongside the Success Page URL and the respondent is sent straight to your page. WorkForms always shows its own success message briefly before redirecting, and that cannot be turned off.
What if my failed submissions need to go somewhere different than successful ones?
FormFlow supports that directly with a separate Error Page URL. WorkForms does not have a distinct failure-page setting.
Next Steps
- External redirect settings →
- Track UTM sources in monday.com form submissions →
- Prefill monday.com forms with URL parameters →
- Show respondents their own answers instead of redirecting them away →
- Install FormFlow and set a Success and Error Page URL on your next form.
Last reviewed: 2026-09-04. WorkForms’ Redirect URL behavior (single static URL, no conditional destinations, built-in success message) verified against monday.com’s Get started with WorkForms documentation and cross-checked against TaskRhino’s coverage of the same limitation . Features may change.