> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/saas-data-monitoring/events/sample-events.md).
# Sample events
Readymade sample events are synthetic events that weren't yet received from your integrated SaaS apps. Since DoControl is an event-driven security platform, all events are usually received from your organization’s integrated SaaS apps. Events can only be applied as triggers in workflows after they were received at least once.
By having readymade event samples in the trigger action step, you can create, define and implement security workflows faster and without having to wait for real events to arrive.
#### To use readymade sample events:
1. Create a new workflow from scratch or by using our playbooks.
2. In the trigger action step, select the Events dropdown. Sample events are displayed with a blue `Sample` label.
3. Select the relevant event based on the use case you would like to implement.
4. Implement the relevant logic in your workflow.
5. Save and activate the workflow.
{% hint style="info" %}
When DoControl receives a real event for the first time, the workflow will trigger and the sample label will disappear and be replaced with real data.
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.docontrol.io/docontrol-user-guide/saas-data-monitoring/events/sample-events.md?ask=&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.
