# Event Block

## Overview

The **Event block** is a workflow component used to trigger and record an event at a specific point in the flow.

It allows you to measure when something happens during execution.

<figure><img src="https://4264750556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4dIFGOeVbHW1PRwnG0Z8%2Fuploads%2FPu2yymLI0t2CKicgngfs%2Faction%20event.png?alt=media&#x26;token=ca58c043-5e7b-4a2a-9932-040c66108a45" alt=""><figcaption></figcaption></figure>

### When to use it

Use the Event block to:

* track key steps in a workflow
* measure conversions or user actions
* connect workflows to business metrics

### How it works

When the workflow reaches the block:

* the selected event is triggered
* a new occurrence is recorded
* metadata (if defined) is saved

The process is automatic and asynchronous.

### Configuration

<figure><img src="https://4264750556-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4dIFGOeVbHW1PRwnG0Z8%2Fuploads%2FeMKgNzyFa6RwWQgGsRrV%2Faction%20event%202.png?alt=media&#x26;token=460f4415-22c2-48ae-b884-e2c5c333f8c6" alt=""><figcaption></figcaption></figure>

#### Select event

Choose an event from the Events section.

You can select:

* Active events
* Disabled events (but they won’t be tracked)

#### Metadata (optional)

You can add dynamic data such as:

* workflow variables
* user input
* outputs from previous steps

### Metadata logic

The system combines:

* global metadata (defined in Events)
* local metadata (defined in the block)

Rule:

* values are merged
* local values override global ones

### Behavior by status

* **Active** → event is recorded
* **Disabled** → workflow continues, no tracking
* **Archived** → event not available and not tracked

The workflow is never interrupted.

### Error handling

* Tracking is asynchronous
* Automatic retries in case of failure
* Invalid metadata is still recorded with error flag