Send responders to other URLs during a flow, or once completed.

Redirects can be set on a particular step in a flow or for all terminal steps in a flow.

You can define conditions for each redirect. When redirecting, the first enabled redirect is the one to which the responder will be redirected.

Redirects can be templated to includes variables available in the schema. See templating urls for more.

Default redirects

In a flow, 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.

Redirecting at 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, passing that step will finalize the flow for everyone who reaches that step.

Query Parameters

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{{responder_email}}.

If using query parameters in your redirect URL, you can specify a URL fallback, in case the query parameters are not present.

Accessing the expected redirect URL as an answer

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.