Sales CRM
Configure event automation rules
Apply a controlled set of actions when a deal is created, its details are saved or its stage changes.
Where to start
Sales → Sales CRM setup → Event automations → Add automation
Fields and options
- Access needed
- Administrator
- Permission and scope
- Administrator
Before you begin
Open the correct company workspace and confirm Administrator. Review the original record before following these steps. Open the relevant entry under the native Sales menu; the workspace tabs use shorter labels such as Deals, Reports, Relationships and Sales setup.
Follow these steps
- Enter a rule name and choose Deal created, Deal details saved or Deal stage changed.
- Set a priority from 1 to 1000. Lower numbers are checked first; equal priorities use the order in which rules were created.
- Choose All conditions or Any condition and configure one to ten typed conditions.
- Add one to five actions and review their order. Start with Inactive while preparing the rule.
- Choose Active and save when the rule is ready for future events. Check its results on an appropriate deal after the selected event occurs.
Check the result
Reopen the configuration and confirm trigger, priority, availability, conditions and actions. Open the affected deal and expand its Automation activity entry to see each applied or skipped action.
If something does not look right
If another rule ran, check its priority and conditions. A broad high-priority rule can match before a more specific rule. An inactive rule never runs; changing a rule does not replay past events. If the rule did not match, check missing values and public-field availability. Use Has no value explicitly for empty fields.
Fields, rules and limits
- The workspace supports up to fifty rules, including inactive rules, with a maximum of ten active at a time.
- Only the first matching active rule for an event runs. Later matching rules are not combined, even if an action in the first rule is skipped.
- Deal details saved applies to the details save operation. Activity completion, routing, scoring changes, template configuration and archive controls do not independently trigger that event.
- A stage-change event runs when the stage actually changes, including an approved transition. Merely requesting stage approval does not execute a stage-change rule.
- Actions use the initiating staff member’s existing Edit permission. Rules do not grant permissions or recursively trigger other event rules.
- Only supported public fields are available to conditions. If a referenced field becomes private or retired, the rule cannot match.
Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.
Useful next steps
Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.