ecaguide.org valid

ECA - Drupal Events, Conditions, Actions

Documentation, tutorials and resources for Drupal's ECA module and its eco-system.

For agents: Documentation for Drupal's ECA module (Events, Conditions, Actions): install guides, modeler docs, plugin reference, example models and tutorials.

drupaleca moduleworkflow automationpluginsdrupal events conditions actions

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T20:58:26.890Z. Cached copy · Source on ecaguide.org

# ECA - Drupal Events, Conditions, Actions

> Documentation, tutorials and resources for Drupal's ECA module and its eco-system.

Documentation for Drupal's ECA (Events-Conditions-Actions) module, the recommended rules engine for Drupal 10/11+. Covers core concepts, plugin reference, visual modelers, example models, and developer guides.


## ECA Guide

- [Drupal ECA Documentation](https://ecaguide.org/index.md): Home page and overview of the ECA module for Drupal.
- [Installation](https://ecaguide.org/eca/install/index.md): Installation instructions for ECA and its dependencies.
- [Upgrading from ECA 2](https://ecaguide.org/eca/upgrade/index.md): How to upgrade an existing site from ECA 2 to ECA 3: the two supported routes, the manual uninstall of eca_modeller_bpmn, Drupal core version stepping, what happens to models, and the integrations extracted in 3.1.
- [Usage](https://ecaguide.org/eca/usage/index.md): How to use ECA after installation.
- [Importing Models](https://ecaguide.org/eca/importing/index.md): How to import ECA models.
- [Exporting a model as a recipe](https://ecaguide.org/eca/exporting/index.md): How exporting a model as a recipe works: the three model-level settings recipes, export_config and config_actions, how the recipe's config set is built and routed, and why downstream config has to be declared.
- [Authoring models as configuration](https://ecaguide.org/eca/authoring/index.md): How to write an ECA model directly as a Drupal configuration entity: file format, successor shape, plugin IDs, entity type selectors.
- [ECA concepts](https://ecaguide.org/eca/concepts/index.md): Core concepts: events, conditions, actions, tokens, loops, gateways, permissions.
- [Actions](https://ecaguide.org/eca/concepts/actions/index.md): Core concepts: events, conditions, actions, tokens, loops, gateways, permissions.
- [Conditions](https://ecaguide.org/eca/concepts/conditions/index.md): Core concepts: events, conditions, actions, tokens, loops, gateways, permissions.
- [Custom events](https://ecaguide.org/eca/concepts/custom_events/index.md): Core concepts: events, conditions, actions, tokens, loops, gateways, permissions.
- [Entity events](https://ecaguide.org/eca/concepts/entity_events/index.md): Core concepts: events, conditions, actions, tokens, loops, gateways, permissions.
- [Events](https://ecaguide.org/eca/concepts/events/index.md): Core concepts: events, conditions, actions, tokens, loops, gateways, permissions.
- [Using Gateway](https://ecaguide.org/eca/concepts/gateways/index.md): Core concepts: events, conditions, actions, tokens, loops, gateways, permissions.
- [Loops](https://ecaguide.org/eca/concepts/loops/index.md): Core concepts: events, conditions, actions, tokens, loops, gateways, permissions.
- [Permissions](https://ecaguide.org/eca/concepts/permissions/index.md): Core concepts: events, conditions, actions, tokens, loops, gateways, permissions.
- [Tokens](https://ecaguide.org/eca/concepts/tokens/index.md): Core concepts: even
…

Related sites

Find similar publishers by meaning →

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=ecaguide.org · GET /v1/domain/ecaguide.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for ecaguide.org:
1. POST https://agentwebmap.com/v1/sites/ecaguide.org/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://ecaguide.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/ecaguide.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/ecaguide.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.