# Automations

Automations turns data into action:

***

**User Flows** – visual builder for event‑driven journeys, from onboarding emails to complex branching logic.

{% content-ref url="/pages/nyKkeBLRwurPEp4uwbNP" %}
[User Flows](/userflux-docs/feature-guides/user-journeys/user-flows.md)
{% endcontent-ref %}

***

**Data Flows** - powerful automations that allow you to process data from external sources, perform actions based on incoming information, and run jobs on a schedule.

{% content-ref url="/pages/gDgrHtgGylc5dcuAaacd" %}
[Data Flows](/userflux-docs/feature-guides/automations/data-flows.md)
{% endcontent-ref %}

***

**Destinations** – forward events or profile changes to any tool (or webhook) in seconds, no custom plumbing.

{% content-ref url="/pages/wvViTsi4VywW4YtIiPOI" %}
[Destinations](/userflux-docs/feature-guides/automations/destinations.md)
{% endcontent-ref %}

***

**Automation Logs** – inspect deliveries, retries and errors for total transparency.

{% content-ref url="/pages/VRPLzpHi5B97WkG8BYAg" %}
[Automation Logs](/userflux-docs/feature-guides/automations/automation-logs.md)
{% endcontent-ref %}

***


---

# Agent Instructions: 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:

```
GET https://userflux.gitbook.io/userflux-docs/feature-guides/automations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.