Skip to content

Conditions#

All CRM conditions live in the CRM category in the ECA modeller. Every condition can be negated.

User and contact fields accept a token name, a bracketed token such as [crm_contact], or a numeric entity ID. See Tokens.

CRM: user has mapped contact#

Plugin ID: eca_crm_user_has_mapped_contact

True when the given user has a mapped person contact.

Field Description
User User entity token or user ID

CRM: contact is mapped to a user#

Plugin ID: eca_crm_contact_is_mapped

True when the given contact is mapped to a user.

Field Description
Contact Contact entity token or contact ID

CRM: contact bundle#

Plugin ID: eca_crm_contact_bundle

True when the contact's type matches the selected bundle (person, organization, household, or any other CRM contact type on the site). Default bundle is person.

Field Description
Contact Contact entity token or contact ID
Bundle Contact type ID (token-selectable)

If the contact cannot be resolved, the condition is false (before negate).

Plugin ID: eca_crm_contacts_related

True when the two contacts share a relationship of the selected type. Contact order does not matter: either contact may be A or B on the relationship.

Field Description
Contact A First contact token or ID
Contact B Second contact token or ID
Relationship type CRM relationship type (token-selectable)
Active relationships only When checked (default), only published relationships (status = 1) are considered

If either contact cannot be resolved or the type is empty, the condition is false (before negate).

CRM: contact method exists#

Plugin ID: eca_crm_contact_method_exists

True when at least one contact method of the given type already stores the value. This is a global lookup, not limited to one contact.

Field Description
Method type email or telephone (token-selectable)
Value Email address or telephone number