Use supported operational alerts, reminders, and follow-up rules

Several Pryseflow workflows queue notifications, reminders, retries, and follow-up when a supported record reaches a defined state.

This is not a promise of a universal user-authored rules engine. Each published automation must name the implemented trigger, condition, action, recipient, channel, and failure behavior.

‍

‍

Available triggers and actions vary by domain and configuration. Review the exact workflow with Pryseflow before relying on an automated step.

• Send supported contract invitations, reminders, resends, and lifecycle notifications.
• Queue implemented order, shipping, pickup, delivery, and marketplace updates.
• Apply invoice due-date, recurring, and reminder behavior where configured.
• Use retry handling for supported queued delivery or connector work.
• Preserve the related record and status so staff can review the event.
• Confirm recipient, channel, timing, limits, and failure recovery for each workflow.