> For the complete documentation index, see [llms.txt](https://manual.senseforce.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.senseforce.io/manual/sf-platform/automations/test-your-automation.md).

# Test your Automation

There are two tests you can do for your automation. The test for the trigger and the test for the actions.

![](/files/-MA1FV9uOBXzJNXm-ezp)

## Trigger Test

The test for the trigger will only tell you if the data source condition is true or false. So the trigger test telling you that the trigger is active means that there is at least one row in every data source after the given filters were applied. If the trigger test tells you that trigger is not active, at least one of the data sources has 0 rows after the filters are applied.

{% hint style="info" %}
The trigger test does not hold any information if you are using the [Schedule trigger](/manual/sf-platform/automations/trigger.md).
{% endhint %}

## Action Test

The test for the actions simply executes all actions defined in this automation regardless of the trigger.

{% hint style="warning" %}
If you appended any data to an email, the data will not be appended if you use the action test to execute your action.
{% endhint %}


---

# 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://manual.senseforce.io/manual/sf-platform/automations/test-your-automation.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.