> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/unlimited-automations/automation-triggers-and-actions-reference.md).

# Automation triggers and actions reference

Review the triggers and actions you can use when building an automation.

Use this reference when you choose a trigger and actions for an automation.

### Triggers

| Entity      | Available triggers                                                                                                                                                           |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Work orders | Work order created; work order planned; work order completed; work order status changed; SLA pending response; SLA pending resolve; subcontractor events                     |
| Relations   | Relation created; relation updated                                                                                                                                           |
| Objects     | Object created; object updated                                                                                                                                               |
| Quotations  | Quotation created; quotation updated; quotation sent; quotation rejected; quotation accepted; quotation invoiced; quotation executed; quotation cancelled; quotation revised |

The trigger determines which criteria and actions are available.

### Actions

| Action                         | Description                                                     |
| ------------------------------ | --------------------------------------------------------------- |
| Create task                    | Creates a task for the selected record or user.                 |
| Send email or SMS              | Sends a message, optionally after a delay and with attachments. |
| Copy order                     | Creates a copy of the current work order.                       |
| Archive order                  | Archives the current work order.                                |
| Update order fields            | Changes selected fields on the current work order.              |
| Create quotation or invoice    | Creates a quotation or invoice from the current record.         |
| Apply price rules              | Applies the configured price-management rules.                  |
| Recalculate routes             | Recalculates routes for the selected work order.                |
| Sync to timesheet or warehouse | Syncs the work order to Timesheets or Warehouse.                |
| Update object or project       | Changes data on a linked object or project.                     |
| Trigger webhook                | Sends an event to an external webhook URL.                      |

### Related topics

* Create a new automation in OutSmart
* Manage and monitor existing automations
* Automation ideas for OutSmart


---

# 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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/unlimited-automations/automation-triggers-and-actions-reference.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.
