Human approval gates

DripPulse supports human-in-the-loop controls for both workflow execution and template-based agent deployment. This page explains when approvals are required, who can decide, and which APIs to use.

Two gate types

1) Workflow step approval gate

A workflow can include an approval step. When execution reaches that step, DripPulse creates an approval request and pauses the enrollment until approved, rejected, or expired.

2) Template deploy sign-off gate

A template can require sign-off before deployment. When enabled, spawning a template agent creates a pending deploy approval; OpenClaw deploy starts only after approval.

Who can approve

Approvers are team members in the same organization with role Admin or Approver.
Assignment can be narrowed by roles and/or specific user IDs.
If no assignees are configured, any org admin/approver can decide.

Workflow gate behavior

Explicit step: Add an approval step in the Workflow Builder logic section.
Default fallback: If you enable require_default_approval_gate on a workflow and the graph has no approval step, DripPulse prepends an implicit launch approval gate.
Status while waiting: enrollment moves to awaiting_approval.

Gap closed: teams can now enforce a baseline approval checkpoint even when a builder flow forgot to include an explicit approval step.

Approval step configuration

Field	Purpose
`approval_mode`	`any_approver`, `all_assignees`, or `quorum`
`required_count`	Minimum distinct approvers for quorum mode
`assignee_roles`	Role-based assignment, e.g. `approver`, `admin`
`assignee_user_ids`	Specific users who can decide
`sla_hours`	Optional timeout window
`on_reject`	`fail_enrollment`, `cancel_enrollment`, or `jump_to_step`
`on_timeout`	`auto_reject`, `escalate`, or `jump_to_step`

Template deploy sign-off behavior

Enable deploy_requires_approval on the template (admin-controlled setting).
Spawn returns a pending agent state (pending_approval) and a deploy approval request.
Approving deploy request starts OpenClaw deployment; rejecting keeps agent inactive.

If your org plan has an agent cap, new spawns may return 403 until capacity is available.

Approvals inbox and APIs

Users handle both gate types from the Approvals page in the dashboard.

Workflow approvals API

GET /api/v1/workflow_approvals
GET /api/v1/workflow_approvals/:id
POST /api/v1/workflow_approvals/:id/approve
POST /api/v1/workflow_approvals/:id/reject

Agent deploy approvals API

GET /api/v1/agent_deploy_approvals
GET /api/v1/agent_deploy_approvals/:id
POST /api/v1/agent_deploy_approvals/:id/approve
POST /api/v1/agent_deploy_approvals/:id/reject