HITL Workflows

​

HITL Approaches in CrewAI

​

Flow-Based HITL with Enterprise Platform

​

Key Benefits

• External responders: Anyone with an email can respond, even non-platform users
• Dynamic assignment: Pull assignee email from flow state (e.g., account_owner_email)
• Simple configuration: Email-based routing is easier to set up than user/role management
• Deployment creator fallback: If no routing rule matches, the deployment creator is notified

​

Setting Up Webhook-Based HITL Workflows

1

Configure Your Task

Set up your task with human input enabled:

2

Provide Webhook URL

When kicking off your crew, include a webhook URL for human input:

3

Receive Webhook Notification

Once the crew completes the task requiring human input, you’ll receive a webhook notification containing:

• Execution ID
• Task ID
• Task output

4

Review Task Output

The system will pause in the Pending Human Input state. Review the task output carefully.

5

Submit Human Feedback

Call the resume endpoint of your crew with the following information:

Critical: Webhook URLs Must Be Provided Again: You must provide the same webhook URLs (taskWebhookUrl, stepWebhookUrl, crewWebhookUrl) in the resume call that you used in the kickoff call. Webhook configurations are NOT automatically carried over from kickoff - they must be explicitly included in the resume request to continue receiving notifications for task completion, agent steps, and crew completion.

Example resume call with webhooks:

Copy

Ask AI

curl -X POST {BASE_URL}/resume \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "execution_id": "abcd1234-5678-90ef-ghij-klmnopqrstuv",
    "task_id": "research_task",
    "human_feedback": "Great work! Please add more details.",
    "is_approve": true,
    "taskWebhookUrl": "https://your-server.com/webhooks/task",
    "stepWebhookUrl": "https://your-server.com/webhooks/step",
    "crewWebhookUrl": "https://your-server.com/webhooks/crew"
  }'

Feedback Impact on Task Execution: It’s crucial to exercise care when providing feedback, as the entire feedback content will be incorporated as additional context for further task executions.

This means:

• All information in your feedback becomes part of the task’s context.
• Irrelevant details may negatively influence it.
• Concise, relevant feedback helps maintain task focus and efficiency.
• Always review your feedback carefully before submission to ensure it contains only pertinent information that will positively guide the task’s execution.

6

Handle Negative Feedback

If you provide negative feedback:

• The crew will retry the task with added context from your feedback.
• You’ll receive another webhook notification for further review.
• Repeat steps 4-6 until satisfied.

7

Execution Continuation

When you submit positive feedback, the execution will proceed to the next steps.

​

Best Practices

• Be Specific: Provide clear, actionable feedback that directly addresses the task at hand
• Stay Relevant: Only include information that will help improve the task execution
• Be Timely: Respond to HITL prompts promptly to avoid workflow delays
• Review Carefully: Double-check your feedback before submitting to ensure accuracy

​

Common Use Cases

• Quality assurance and validation
• Complex decision-making scenarios
• Sensitive or high-stakes operations
• Creative tasks requiring human judgment
• Compliance and regulatory reviews

​

Learn More