Redirects
Send responders to other URLs during a flow, or once completed.
You can define conditions for each redirect, and redirects set without conditions will finalize the flow.
Redirects can be templated to included variables available in the schema. See templating urls for more.
From the flow studio, you can specify a flow's redirects in the Redirects tab.
These redirects take effect whenever a responder has completed a flow, and they have not triggered any redirects tied to a particular step.
Redirects may also be defined at the level of an individual step: with a step selected, click the Redirects tab.
Conditions on step-level redirects may use answers defined on that same step.
If you have a redirect specified on a step without a condition, completing that step will finalize the flow for everyone who reaches that step.
Query Parameters can be appended to a Redirect URL: simply add the question mark (?) separator to the Redirect URL, and enter a key-value pair. Add ampersand (&) separators to the URL string to add additional key-value pairs.
Templated variables can be used as values in the query parameters. For example, if you want to pre-populate the redirect page with information collected from the flow, you could do so by specifying a URL like
https://example.com?email={{responder_email}}. If using query parameters in your redirect URL, you can specify a URL fallback, in case the query parameters are not present.
If you need access to the current expected redirect URL, to show to the responder, or to save in your data, you can add the expected redirect URL library answer to the schema.
Users can be redirected into Formsort and data from from the source site can be passed in. The URL parameters passed in can be stored as an external variable, or used to set the answers for questions.
For instance, if a user is coming from a site with a
utm_source attached to the url, and you want to capture that data, you can use an external variable. The URL that redirects to Formsort should look something like https://flow.formsort.com/client/{{your_account_name}}/flow/{{your_flow_name}}/variant/{{your_flow_variant_name}}/?utm_source=exampleThe utm_source data being passed in can be captured in an external variable by creating an external variable in your schema called "utm_source". Formsort will now know to look for that value in the url parameter, and can update your variable as such.
Answers passed with the wrong type, or to non-existent variable names, are ignored when loading the flow.
Check the javascript console if you are having problems ingesting answers - a warning will be present if URL parameters don't match known answers, or the value you're providing is invalid.
Last modified 11mo ago