> For the complete documentation index, see [llms.txt](https://docs.goless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goless.com/workflow/customization.md).

# Customization

You can always set up each workflow by going to the workflow > settings menu. There are three sections in the settings menu:

## General

* Error Tracking: Choose what to do in the event of a workflow error.
* Running Mode: Choose to execute the workflow from a pop-up dashboard or in the background.
* Alarms: Turn alarms on/off when workflow stops.
* Debuging: Run the workflow using the Chrome DevTools Protocol.
* Autocomplete: Activates autocomplete in each block input.
* Reuse State: Use the state data such as tables, variables, and global data from the last run.
* Save Logs: Keep logs of the workflow.
* Show Executed Block: Show the block the workflow executes on the webpage at this moment. Note that this option only displays blocks in the "Web interaction" category (for example, Click Element and Forms blocks).
* Public ID: The public ID of the workflow that can be used in the execution of the workflow using Javascript CustomEvent.

When selecting "pop-up" or "background" for workflow execution, some features and benefits will not be available.

### Table

* Insert into Default Column: Insert the data into the default column if no column is chosen within the block or if the column does not exist.
* Default Column Name: The name of the default column.

### Blocks

* Block Delay: Add a delay before running each block.
* Tab Load Timeout: Maximal tab loading time in milliseconds.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.goless.com/workflow/customization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.