tr Skip to content
Black Friday FlowMattic for life, 12 payments of $33.25 Or $399 once. Nothing added for splitting Ends in --Days --Hrs --Min --Sec See the deal

WordPress Approval Workflow: Human in the Loop by Email or Slack

FlowMattic Human in the Loop: a refund request waits for a manager's email approval before the order is refunded and the customer notified.

A WordPress approval workflow lets automation do the gathering and the follow-through while a person makes the call. FlowMattic’s Human in the Loop step sends an approval request by email or Slack, pauses the run until someone approves or rejects it, then continues on the answer, with a wait limit and a fallback if nobody responds.

It fits any decision you don’t want a workflow to make on its own: refunds above a threshold, AI-written content before it goes live, discounts a sales rep asks for, new accounts that look unusual. Everything before the approval runs as normal, and nothing after it runs until someone accountable has answered.

What is Human in the Loop?

Human in the Loop is a built-in app in the builder’s Flow Controls group. It has two action events:

  • Get Approval on Email: “Send approval request via email and wait for response.”
  • Get Approval on Slack: “Send approval request via Slack with interactive buttons.”

Each request is stored in your own WordPress database with a unique ID, its assignee, its status and a “valid until” time. A third way to approve lives in WP Tables: its Continue on Approve or Reject Button action pauses a run until someone clicks Approve or Reject on a table row. The Human in the Loop overview shows all three side by side.

How a WordPress approval workflow runs

  1. Ask. The Human in the Loop step sends the request: an email with Approve and Reject links and a link to the request details, or a Slack message with Approve and Reject buttons.
  2. Wait. The run pauses and shows as Waiting in Task History. The step’s output so far has approval_status set to waiting.
  3. Answer. The approver opens a link and confirms on the page that opens, or clicks a Slack button. On the request details page they can also add an optional message with Save Message.
  4. Continue or stop. On approval, the run continues at the next step, and approval_status becomes approved. On rejection, the run ends at the approval step; set Action on Reject to start another workflow for the rejection path.
FlowMattic Human in the Loop step showing Email Settings, Timeout Options and Assignee Management fields.
A Get Approval on Email step with the approval message, a two-day wait limit and a custom assignee.

Email links never act on their own. Opening an Approve or Reject link shows a confirmation page, and the decision is recorded only when the approver clicks the button there. That keeps email security scanners, which open links automatically, from approving or rejecting anything. Each request can be answered once: a second click reads “This request has already been processed”, and a link used after the wait limit reads “This approval request has expired”.

Get Approval on Email settings

GroupFieldWhat it does
Email SettingsSender Name, Email Subject (optional), Approval Message Headline, Approval MessageWhat the approver reads. All accept dynamic tags, so the request carries the order, amount or draft from earlier steps.
Timeout OptionsMax Wait Time, Timeout UnitHow long the request stays open, in Minutes, Hours or Days.
Timeout OptionsTimeout ActionSkip and Continue to Next Step, End Workflow Execution or Re-assign to Another User.
Timeout OptionsReassignment EmailWho gets the request when it is reassigned.
Assignee ManagementAssignee TypeCustom Assignee (an Assignee Email you type or map) or Round Robin – Based on User Role.
Assignee ManagementUser Role, User Meta Key, User Meta ValueFor round robin: the role to pick from, optionally narrowed by a user meta match.
Rejection HandlingAction on Reject, Select WorkflowDo Nothing, or Execute Workflow to run a workflow you choose when the request is rejected.
AuthenticationCheck User Logged InWhen Yes, the approver must be logged in to WordPress to view, approve or reject, and their email is recorded.

Round robin picks, from the users with the chosen role, the one whose last assignment is the oldest, so requests spread evenly across the team.

Get Approval on Slack settings

The Slack action uses a Slack connection from Connects. Send To chooses Channel (with a Channel ID) or Direct Message (with a User ID). The message settings and Rejection Handling match the email action. Timeout Action offers Skip and Continue to Next Step or End Workflow Execution; reassignment is email-only.

Button clicks reach your site through FlowMattic’s proxy service, so you don’t configure interactivity in a Slack app yourself. When someone answers, the Slack message updates in place to show the result, and an expired request is marked as expired.

What the approval step returns

  • approval_status: approved after an approval, or approved_with_timeout when the wait limit passed and the timeout action was Skip and Continue.
  • user_response: the message the approver saved, if any.
  • approved_by: the approver’s email, when Check User Logged In is Yes.
  • request_id, assignee, valid_until and, after a reassignment, reassigned_to and reassigned_count.

Use cases

Refunds above a threshold

Small refunds go through automatically; large ones wait for a manager. A rejection starts a separate workflow that emails the customer the manager’s note.

Form (refund request) → Filter (amount Greater than 100) → Get Approval on Email (manager, Action on Reject: Execute Workflow) → WooCommerce Change Order Status (Refunded) → Send Email to the customer

Editorial sign-off for AI drafts

An AI Agent drafts the post; an editor who must be logged in approves it before it is published.

Schedule (weekly) → AI Agent (draft post) → Get Approval on Email (editor, Check User Logged In: Yes) → WordPress New Post (publish) → Slack Send Channel Message

Discount requests approved in Slack

Sales reps request a discount through a form, the sales lead answers in Slack, and an approved request creates the coupon.

Form (discount request) → Get Approval on Slack (#sales-approvals) → WooCommerce Create Coupon → Send Email to the customer

Client approval before an agency sends a report

The client’s contact gets the draft report first. If they don’t answer within two days, it goes out anyway with a note.

Schedule (monthly) → Generate PDF from Template → Get Approval on Email (client contact, 2 Days, Skip and Continue to Next Step) → Send Email to the client's team

Review unusual sign-ups

A SaaS site holds new accounts from unknown domains for a quick check in a direct message to the admin.

WordPress New User → Filter (email Does not end with a known domain) → Get Approval on Slack (Direct Message) → WordPress Change User Role → FluentCRM welcome sequence

Spread expense approvals across a team

Internal ops route each expense claim to the next finance approver in turn, and reassign it if nobody answers within a day.

Form (expense claim) → Get Approval on Email (Round Robin, role: Editor, 1 Day, Re-assign to Another User) → WP Tables Update Record (approved) → Send Email to the claimant

Tips and gotchas

  • Rejection ends the run. Steps after the approval step only run for approvals (and for timeouts set to Skip and Continue). To act on a rejection, set Action on Reject to Execute Workflow; the chosen workflow, which must be switched on, receives the request details with approval_status set to rejected, the approver’s message, headline, message and assignee.
  • Tell timeouts apart. With Skip and Continue, the next steps run with approval_status set to approved_with_timeout. Add a Branch on that value if a timeout should be handled differently from a real approval.
  • Timeouts are checked every 10 minutes. A background job in FlowMattic’s own job table checks expired requests, so the timeout action can run up to about 10 minutes after the limit.
  • Reassignment has limits. A request with a Custom Assignee is reassigned once; with Round Robin, up to three times. The new approver is the Reassignment Email if you set one, otherwise the next user by round robin. When attempts run out, the workflow ends. Reassigned emails add “(Reassigned)” to the subject and headline.
  • Turning the workflow off settles waiting runs. If an answer arrives while the workflow is off, the run is closed instead of continuing.
  • Clean up old requests. Under FlowMattic Settings, Clean Human in the Loop Data? and Human in the Loop Cleanup (Days) delete requests whose expiry is older than the number of days you set.

Related features

  • WP Tables: approve from a table row with the Continue on Approve or Reject Button action.
  • Task History: see every run that is Waiting on an approval.
  • Branch: separate real approvals from timeouts after the approval step.

FAQ

How do I add an approval step to a WordPress workflow?

Add a Human in the Loop step where the decision belongs and choose Get Approval on Email or Get Approval on Slack. Fill in the message, the approver and the wait limit, then add the steps that should run after approval.

What happens if nobody approves the request?

When Max Wait Time passes, the Timeout Action runs: continue to the next step, end the workflow, or (for email) reassign the request to another user. The run stays Waiting until then.

Can the approver leave a comment?

Yes. The request details page has an optional Add a Message box. The saved message is returned as user_response, ready to use in an email or a table row.

Can I require the approver to be logged in?

Yes, for email approvals. Set Check User Logged In to Yes and only logged-in users can view, approve or reject the request. The approver’s email is then recorded on the step.

Human in the Loop is part of every FlowMattic plan, and every request and answer stays on your own server. Compare plans and put an approval in your next WordPress approval workflow.

More from the blog