This taxonomy term is used for modules that integrate with Rules (

Jira REST Rules

The module provides an integration between Jira (via the jira_rest module) and rules.

In the current limited form the module provides a rules action for creating simple, basic issues in Jira.

You must configure the jira_rest module with username and password at admin/config/services/jira_rest.

In the rules action you can configure:


Rules Date Check

What it does

This is a small Rules module providing some date and time comparisons and formatting.

Why it exists

This module provides the ability to compare the current time to a given hour or day, for use in building conditions like "if it is after 6am on Tuesday..." Since multiple conditions can be applied, conditions like "before 9am between Tuesday and Thursday" can be created.

It is particularly useful for cron-triggered rules.

Commerce Coupon Rules

Provides individual white list and black list rules for individual coupons (from Commerce coupons), allowing the site builder or developer to easily customize conditions for each coupon instead of manually creating and organizing a bunch of rules in the standard rules UI.

Shibboleth Rules integration

Provides Rules integration for the Shibboleth Authentication module.

Right now, it just adds the event "User is logged in via Shibboleth", but new features will be available soon (like a new condition to compare Shibboleth attribute values).

Developed and maintained by FISQUA; Sponsored by RNP.


Update Rules

This module provides rules events, actions, and conditions related to Drupal project update statuses.

Drupal core offers a simple email notification when the site needs core/module updates. Unfortunately those emails do not contain any information about the projects or the releases, and you're at the mercy of the standard update notification configuration. This module solves this problem, and gives you all of the capabilities (actions, conditions, etc.) of Rules for handling update statuses. Imagine being able to send an email to your task management app with the server name, project name, and release info every time a security update is needed. This is a simple example, but was the exact goal I was shooting for when I wrote this module.

Security implications: please exercise caution when handling the status of the modules on your sites. You should not make public which security updates your sites need. I've added a "guid" to this module that you can use as a unique identifier for a specific project release. You can read about it in the README.txt file.



Integration with chat system.

Uses the Glip API for 'integrations' to allow Drupal to post messages to a discussion thread of your choice.

Via watchdog:

Configured through your logging settings at /admin/config/development/logging , you can tell glip to only notify you of events of a certain severity or type.

Via Rules:

You can add a glip message as a rules action to be triggered and configured according to conditions of your choosing.


Subscribe with RSS Subscribe to RSS - Rules