Help Centre › Building Processes
This article describes the RPA Browser functionality to set extra HTTP headers for all subsequent requests.
For a full list of available functions, please read BROWSER functions.
Description
The BROWSER Set extra HTTP headers function allows you to add custom HTTP headers to all subsequent browser requests using the Chrome DevTools Protocol (CDP). This is useful for setting authentication tokens, custom API headers, language preferences, or any other headers needed for your automation.
Setting it up
To use the BROWSER Set extra HTTP headers function, follow these instructions:
{{popups:rpas/add:action=browser-set-headers}}
Once on a process map:
- Navigate to the process where you would like to add the BROWSER Set extra HTTP headers function
- Click on the green button's drop-down (right side of the green button labelled "Process")
- On the menu that appears, click on the "+ Activity" item
- From here you can select the BROWSER Set extra HTTP headers option
- Click "Add" once you are done
Input parameters
| Parameter | Required | Type | Default | Description |
|---|---|---|---|---|
| Header name / Value pairs | Yes | Table | – | Header name-value pairs (e.g. X-Custom: value, Accept-Language: en-US). |
Output variables
This action does not produce output variables.
Errors
| Error | Description |
|---|---|
| Browser not open | No browser session is active. |
Tips
- Headers persist for all subsequent requests until cleared with Clear extra HTTP headers.
- Use this to pass Bearer tokens or API keys in automation workflows.
- Setting new headers replaces all previously set extra headers.