Notify admins or external systems when workflows need approval, complete, or fail.
Updated 5 June 2026·Task guide
Outcome
Workflow stakeholders receive email or webhook notifications when a workflow needs attention, finishes successfully, or fails.
Video walkthrough
▶
Video walkthrough coming soon.
The YouTube embed will appear here.
Risk level
Low. Low direct risk. Test delivery before relying on notifications for production approvals.
Before you start
The workflow has clear step labels.
Approval gates are configured where manual review is required.
Email recipients or webhook destinations are known.
Webhook URLs are stored securely if used.
Steps
Open the workflow editor Edit the workflow that should send notifications.
Choose events Enable notifications for approval required, completed, failed, or other supported workflow events.
Choose delivery method Use email, webhook, or both depending on the team workflow.
Add useful approval messages Tell reviewers exactly what to inspect before approving.
Test with a dry run or low-risk workflow Confirm notifications arrive before relying on them for production releases.
Screenshots
Open Workflow Settings
{n "event": "approval_required",n "workflow_id": "wf_123",n "message": "Approval required before pushing to production."n}
Labels reduce confusion
WPChangeSync now falls back to Step 1, Step 2, etc. for unlabeled approval steps, but explicit labels make notifications much easier to act on.
Verify and recover
After enabling notifications, run a low-risk workflow and confirm the expected email or webhook delivery arrives. If messages do not arrive, check the workflow event settings, recipient or webhook URL, Activity entries, and server mail/webhook logs.