Choose and order automation actions
Schedule an activity, set the next step, update a forecast category or start a cadence from a matching deal event.
Where to goSales CRM → Sales setup → Configure automation → Apply these actions
Before you start
Use your own authorised staff account in the intended Pixie CRM workspace. The Sales CRM module must be available and your role must include the permissions stated above. Existing leads, customers, communications and customer portal pages retain their normal access rules.
Follow these steps
- Choose Schedule activity to add a call reminder, meeting, task or email reminder. Enter its title, instructions and a delay from zero to ninety days.
- Choose Set next step to write the follow-up instruction shown on the deal.
- Choose Set forecast category to select Pipeline, Commit, Best case or Omitted.
- Choose Start cadence and select an available template when the deal should enter a structured follow-up process.
- Use Add action for further actions, review the top-to-bottom order and save the rule.
Behavior and limits
- Schedule activity calculates its due time from the triggering event and assigns the current deal owner. It does not execute the communication or task.
- Set next step and Set forecast category update those deal fields. They do not change stage, probability, value or owner. If repeated, the last value for the same field takes effect.
- Actions are configured as a simple ordered list. Conditions are evaluated once for the event; field changes do not cause another rule evaluation.
- Start cadence requires an active template, an open non-archived deal, an eligible owner and no active or paused run. Otherwise that action is recorded as skipped.
- A runtime validation failure in one action is recorded with a reason; other configured actions may still apply. A database failure rolls back the event’s changes rather than reporting a successful partial save.
- Changing next-step or forecast information cancels an outstanding stage approval so that a reviewer is not asked to approve obsolete deal details.
Check it worked
- Check each action result in Automation activity, not just the rule’s overall history entry.
- Confirm a generated reminder’s owner and due time and check any changed next-step or forecast value.
Troubleshooting
- A cadence action can be skipped because a run already exists or its template was retired. Review that condition before triggering a new event.
- A staff member with Create permission but no Edit permission can create a permitted deal, but automation actions are recorded as skipped.
- Rules never silently replace a paused cadence. Stop it explicitly before starting a different process.