Rules

The rules module allows site administrators to define conditionally executed actions based on occurring events (known as reactive or ECA rules). It's a replacement with more features for the trigger module in core and the successor of the Drupal 5 workflow-ng module.

Example use cases

• Build flexible content publishing workflows changes
• Send customized mails to notify your users about important
• Create custom redirections, system messages, breadcrumbs, ...

And many more...

Modules may use the rules module's API to provide new events, conditions, actions, rule sets as well as default rules, which can be customized by users. Check out the developer docs.

Features

• Obviously, you may use reaction rules to react upon any event with custom conditions and actions.
• Allows functionality to be re-used via components (Drupal 6: Rule sets only).
• Flexible scheduling system that allows scheduling any component / action.
• Users can share their customizations by using the built-in import/export feature. For that the module also integrates with Features.
• Modular input evaluation system - for example you can install the Token module and use it in every action.
• The module has been developed with site performance in mind, so it makes use of caching routines to speed up rule evaluation.
• Rules 2.x (Drupal 7 only) features improved APIs, a new admin UI, support for all entity types, parameter configuration via simple data selection (i.e. just pass node:author as argument) and much more. See this blog post for more details.

Requirements

Drupal 6:

• To get token replacements in your actions, install the latest release(6.x-1.12 or later) of the Token module

Drupal 7:

• Entity API - Version 1.0 beta 9 or later!

Further resources

• Documentation & FAQ
• List of modules related to Rules, Manual list of modules supporting Rules
• Group for discussion and usage questions
• Issues for Rules integration with other modules
• fago's blog

To get started have a look at the documentation. Before asking questions read the FAQ.

Credits

The project has been sponsored by

• drunomics
• epiqo
• Google Summer of Code

Maintainer

• Wolfgang Ziegler (fago)

The maintainer provides consulting services and paid development, e.g. for implementing a specific feature. Help improving the module and get in contact!

Downloads