> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/trigger/on-an-event/event-received.md).

# Event received

**Category:** Trigger

**Version:** 1.0

**Last updated:** January 28, 2026

**Author:** Any2Info

***

### Description

The **Event Receiver trigger** starts a dataflow when a named event is raised.

This trigger is purely **event-driven** and has no scheduling or time-based options.\
The event can be raised from multiple sources within the Any2Info platform, making it a flexible trigger for interactive and event-based workflows.

The Event Receiver trigger can be used in the following scenarios:

* Triggering a dataflow from a **Dashboard**
* Triggering a dataflow from a **Form**
* Triggering a dataflow from **another dataflow** using the **Start dataflow** node

Each time the event is raised, the dataflow is executed immediately.

***

### Configuration Options

| Setting               | Required            | Description                                                                                                                                                                                                                                                                       |
| --------------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Event name            | No, but recommended | The name of the event. This name must be unique by convention, but uniqueness is **not enforced** by the application. If the same event name is used multiple times, a single action (from a dashboard, form, or dataflow) will trigger **all** matching Event Receiver triggers. |
| Advanced (Parameters) | No                  | Defines the parameters that the event can receive. Each parameter consists of a name, value type, and description. These parameters become available to the dataflow when the event is raised.                                                                                    |
| Log parameters        | No                  | Determines whether received parameters are logged in reports. Disable this option if parameters contain sensitive information.                                                                                                                                                    |

***

### Supported Parameter Types

When configuring **Advanced parameters**, the following value types are supported:

* Text
* Boolean
* Integer
* Fraction
* Date
* DateTime
* Image
* Base64
* File
* Multiple files

***

### Behavior

* The trigger is raised **every time** the event is called.
* Events can be raised from dashboards, forms, or other dataflows.
* There are **no scheduling options** such as start time, repeat, or random delay.
* Multiple dataflows can respond to the same event name.
* A dataflow can contain **only one trigger**.

***

### Usage

Use the **Event Receiver trigger** when a dataflow should start as a direct response to a user action or another process.

Typical use cases include:

* Submitting a form and processing the submitted data
* Running backend logic from a dashboard button
* Chaining dataflows together using the **Start dataflow** node
* Implementing event-driven workflows without time-based scheduling

***

### Tips & Best Practices

* Use **unique and descriptive event names** to avoid unintentionally triggering multiple dataflows.
* Carefully review parameter definitions to ensure consistent usage across dashboards, forms, and dataflows.
* Disable **Log parameters** when handling credentials, personal data, or other sensitive information.

***

### Changelog

| Version | Date             | Change                               |
| ------- | ---------------- | ------------------------------------ |
| 1.0     | January 28, 2026 | Initial documentation version added. |


---

# 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://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/trigger/on-an-event/event-received.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.