> For the complete documentation index, see [llms.txt](https://docs.loopboard.io/loopboard.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.loopboard.io/loopboard.io/product-features/workflow-automations.md). # Workflow Automations ### Overview A **workflow automation** is a way to let technology handle repetitive tasks for you automatically, so you don’t have to do them manually. Imagine you have a series of steps you need to follow, like sending an email, updating a spreadsheet, or moving a file when something happens. Instead of doing each step yourself, a workflow automation does it for you, following a set of rules you create. ### Triggers *– It’s what initiates the process, the **"Starting Point".*** A **trigger** is the event that starts the workflow. It's like the spark that sets everything in motion. ### Actions *– It’s the specific task that gets carried out automatically, the **"Task"*** An **action** is what happens after the trigger. It’s the task that the automation performs automatically in response to the trigger. You can have multiple actions in a workflow. ### Conditions *– It’s the rule that determines when and how tasks should be executed, the **"Rule"*** A **condition** is a rule that decides whether or not an action should happen. It’s like a checkpoint that says, "Only do this if certain criteria are met." ### Putting It All Together In a workflow automation, the **trigger** kicks off the process, the **condition** decides if certain actions should happen based on specific criteria, and the **action** is what the system does automatically once the conditions are met. --- # 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.loopboard.io/loopboard.io/product-features/workflow-automations.md?ask=&goal= ``` `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.