Redirect
Audience:
Low-code EngineersSkill Prerequisites:
Actions,Tokens
The Redirect actions send the user somewhere else: to a page of your portal, to any URL, or to a portal file. They work in Forms, Listings, User Guides and APIs, and each one ends the action list.
Choosing an action
| Action | What it does | Use it to |
|---|---|---|
| Redirect to Portal Page | Sends the user to a page of the current portal, picked from a list, with an optional query string. The URL follows the site's friendly URL settings and can point to the page in the user's language. | Go to a confirmation page after a submit, or open an edit page with the row's ID in the query string. |
| Redirect to URL | Sends the user to any URL, which can come from tokens. It can open the URL in a popup or a new tab, or force a download. | Go to a page chosen at run time or on another site, or download a file created earlier in the action list. |
| Send File for Download | Sends the user to a portal file picked at design time. The browser downloads it or shows it. | Give users a fixed brochure, price list or template. |
Fixed or chosen at run time?
- Fixed target. Redirect to Portal Page and Send File for Download use a page or file you pick when you set up the action. Page, Portal File and File don't support tokens. Only the query string of Redirect to Portal Page does.
- Run-time target. Redirect to URL takes a URL with tokens, so use it for a page, site or file that's only known when the actions run. For example, redirect to the URL token of a Generate PDF action.
How the redirect works
The result depends on where the action runs:
| Where the action runs | What happens |
|---|---|
| Forms and Listings, button actions and form events other than On Page Load | The browser goes to the target. The popup and new tab options apply. |
| Forms, On Page Load | The server answers with a 302 redirect before the form is shown. The popup and new tab options are ignored. |
| User Guides | The browser goes to the target in the same window. |
| APIs | The API answers with 302 Found and the target in the Location header. |
Redirect to Portal Page and Redirect to URL aren't available in workflows.
Considerations
- Put it last. The action ends the action list. Save data and send emails before it.
- Encode token values. Redirect to Portal Page adds query string values as they are, so a space,
&or#can break the URL. For values like names or search text, use Redirect to URL with Escape URL special characters in tokens on. - Check user input. Don't redirect to a URL from a token the user controls, such as a return URL, without checking it first. See Redirect to URL.
- Permissions aren't checked by the action. For a page, the site checks access when the page opens. For a file, Send File for Download gives the file's direct URL and doesn't check folder permissions, so don't use it for private files.
- Popups use an iframe. Sites that don't allow being shown in a frame won't display in a popup.
What isn't covered
- Sending data with a
POST. Use Repost Data. - Returning a file's content from an API. Use Download File or File Response.
- Downloading text built from tokens. Use Send Plain Text as File Download.
- Switching to another tab of a form. Use Change Tab and Stop Execution.
See also the UI Actions, Output and Message actions.
Revised 10/02/2026