> For the complete documentation index, see [llms.txt](https://help.leadboxer.com/leadboxer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.leadboxer.com/leadboxer/guides/how-to-create-a-workflow-automation.md).

# How to create a Workflow Automation

To add your first Workflow, log into LeadBoxer as Admin and open **Workflow** from your profile menu (top right). See [Workflow Automation](/leadboxer/using-the-app/elements/workflow-automation.md) for what each trigger and action does.

1. Click Add Workflow
2. Provide a Name and Description for your workflow.

   <figure><img src="https://3748765316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy0YIHtmtqLfLnxMS5laM%2Fuploads%2Fgit-blob-fcb247640a2f5dfa2c23ed12a38cc860d00c1404%2FLeadBoxer_Workflow_automation_step_1.png?alt=media" alt=""><figcaption></figcaption></figure>
3. Add one or more Triggers and configure them to 'fire' when specific criteria are met, for example a visit to a URL, a lead property (industry, employee size, country), a lead tag or a LeadBoard stage.

   <figure><img src="https://3748765316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy0YIHtmtqLfLnxMS5laM%2Fuploads%2Fgit-blob-01a4ed1227fe49068985a23486fdaf37e2240bb7%2FWorkflow_Automation_step_2.png?alt=media" alt=""><figcaption></figcaption></figure>
4. Define your action(s). What do you want to happen? You can set a lead tag or account tag, set a custom property, create or move a LeadBoard card, or set the card owner (optionally with automatic ownership).

   <figure><img src="https://3748765316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy0YIHtmtqLfLnxMS5laM%2Fuploads%2Fgit-blob-ea78a35a067fcd370e7d8ff06badbbf295f7f246%2FLeadBoxer_App%20(1)%20(2)%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>
5. Review your Workflow automation and save.

   <figure><img src="https://3748765316-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy0YIHtmtqLfLnxMS5laM%2Fuploads%2Fgit-blob-d2a7e9cdc6f005240b2865f6c7f094966b820003%2FLeadBoxer_App%20(5)%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>

Going forward, each new event or piece of data that goes through our engine will be evaluated to match triggers and execute the relevant action(s) when triggers are met.

Please let us know if you are missing a trigger or action!


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.leadboxer.com/leadboxer/guides/how-to-create-a-workflow-automation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.