> 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/automations-for-invoices-quotations-and-contracts.md).

# Automations for Invoices, Quotations, and Contracts

With automations for **Invoices**, **Quotations**, and **Contracts**, you speed up administrative follow-up.

You automate status-based actions, internal notifications, and recurring next steps.

{% stepper %}
{% step %}

### Choose the right module

First decide whether your process starts from an **invoice**, **quotation**, or **contract**.

Then choose the event that should start the flow.
{% endstep %}

{% step %}

### Create a new automation

Go to **Settings → General → Automation**.

Click **Add**.
{% endstep %}

{% step %}

### Give the flow a clear name

Use a name that explains the purpose immediately.

For example: `Reminder for open quotation`.
{% endstep %}

{% step %}

### Choose trigger and criteria

Select the correct event.

Then filter by status, type, or customer group.
{% endstep %}

{% step %}

### Add actions

For example, choose an internal notification, a follow-up task, or a status-based update.

Then check whether the order of actions is correct.
{% endstep %}

{% step %}

### Save and test

Test the flow with a realistic example.

Then check the result in the module and in the **Notification log**.
{% endstep %}
{% endstepper %}

### Practical examples

* send a reminder for an open quotation
* notify internally when a contract is about to expire
* start follow-up when an invoice status changes

### Frequently asked questions

<details>

<summary>Can I use one automation for multiple modules?</summary>

You choose one trigger per automation.

Actions can still affect other modules afterward.

</details>

<details>

<summary>Which processes fit best here?</summary>

Recurring follow-up, status notifications, and internal alerts.

</details>

<details>

<summary>Where do I check whether the flow worked?</summary>

In the **Notification log** and in the module where the action should be visible.

</details>

### Related topics

* [**What is Unlimited Automations?**](/marketplace-packages-and-power-ups/power-ups/unlimited-automations/what-is-unlimited-automations.md)
* [**Create a new automation in OutSmart**](/marketplace-packages-and-power-ups/power-ups/unlimited-automations/create-a-new-automation-in-outsmart.md)
* [**Manage and monitor existing automations**](/marketplace-packages-and-power-ups/power-ups/unlimited-automations/manage-and-monitor-existing-automations.md)


---

# 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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/unlimited-automations/automations-for-invoices-quotations-and-contracts.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.