Pixie CRMHelp Centre
Sales & Marketing Hub · Feature guide

Set future-event workflow enrolment and re-enrolment rules

Start approved workflows from new CRM events while controlling eligibility, ownership and repeated enrolment.

Audience: authorised staffReviewed 13 November 2026

Use these steps in your selected Pixie CRM company workspace. The module, dependent tools and actions available to you follow its configuration and your permissions.

Where to start

Workflow draft → trigger, enrolment criteria and re-enrolment controls; published workflow → Automatic enrolment history

Permission

Manage automation resources; workflow owner must retain all required record and action permissions

Before you begin

Decide which new event should start the workflow and whether the same record should enter once or for each eligible event. Review the effect of repeated actions before enabling re-enrolment.

Follow these steps

  1. Edit the workflow and select Manual, Record created, Record updated, Profile updated or Activity recorded.
  2. Set the enrolment criteria and All/Any matching mode. Select Once or Each event for re-enrolment.
  3. Dry-test representative accessible records. Obtain independent approval and publish the current revision.
  4. Make a controlled new matching change through the supported CRM process, then allow the regular worker to evaluate it.
  5. Open Automatic enrolment history to review the trigger cursor and recent enrolled, skipped or blocked results.

Fields and options

Future events
Publication records a current event watermark. Events before publication are not backfilled.
Execution identity
Automatic enrolment evaluates access and action permissions as the resource owner, rather than the staff member who caused the event.
Once
A prior run for that workflow and record prevents another automatic enrolment. Each event permits another eligible event to create a run.

Rules and limits

  • Profile events generated by a running Hub workflow are excluded from automatic trigger dispatch, preventing a self-trigger loop.
  • Publishing a revised triggered workflow re-arms its current revision from new events; it does not replay all earlier skipped records.
  • Missing records or permissions can block an event. Temporary processing failures can remain retry-pending without advancing the cursor.

Check the result

  • Confirm the controlled future event produced the intended result and no historical batch was enrolled.
  • Inspect an ineligible example and confirm it was skipped rather than executed.

If something does not look right

  • If nothing starts, check the published revision, event type, owner access, criteria and CRM cron.
  • If Once skips a record, review its previous enrolment instead of changing the rule blindly.

Common questions

Will publishing enrol all existing leads?

No. Automatic triggers are future-only. Use deliberate manual enrolment for an existing accessible record.

Whose permissions apply?

The workflow owner’s current permissions and native record access apply to automatic enrolment.