Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions daprdocs/content/en/developing-applications/crewai/_index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
---
type: docs
title: "CrewAI"
linkTitle: "CrewAI"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yaron2 would it make sense to make a new section in the documentation tree that aligns with Dapr Agents & Dapr for Agents?

Developing applications/
| - AI Agents/
|   | - Dapr Agents/
|       | - Introduction/
|       | - ../
|   | - Dapr for Agents/
|       | - CrewAI/
|       | - ../
|       | - LangGraph/
|       | - ../
|       | - Strands Agents/
|       | - ../

This would also align with the storyline of dapr agents + dapr for agents

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. How would prefer to make agents more visible at a higher level section called AI

Developing applications/
AI/
| - AI Agents/
|   | - Dapr Agents/
|       | - Introduction/
|       | - ../
|   | - Dapr for Agents/
|       | - CrewAI/
|       | - ../
|       | - LangGraph/
|       | - ../
|       | - Strands Agents/
|       | - ../

weight: 25
description: "Dapr first-class integrations with CrewAI Agents"
---

### What is the Dapr CrewAI integration?

Dapr provides APIs for developers looking to build CrewAI agents that scale and operate reliably in production. Dapr provides first class integrations that range from agent session management to connecting agents via pub/sub and orchestrating agentic workflows.
Original file line number Diff line number Diff line change
@@ -0,0 +1,204 @@
---
type: docs
title: "CrewAI Workflows"
linkTitle: "CrewAI Workflows"
weight: 25
description: "How to run CrewAI agents with durable, fault-tolerant execution using Dapr Workflows"
---

## Overview

Dapr Workflows make it possible to run CrewAI agents **reliably**, **durably**, and **with built-in resiliency**.
By orchestrating CrewAI tasks with the Dapr Workflow engine, developers can:

- Ensure long-running CrewAI work survives crashes and restarts
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Ensure long-running CrewAI work survives crashes and restarts
- Ensure long-running CrewAI work survives crashes and restarts.

- Get automatic checkpoints, retries, and state recovery
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Get automatic checkpoints, retries, and state recovery
- Get automatic checkpoints, retries, and state recovery.

- Run each CrewAI task as a durable activity
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Run each CrewAI task as a durable activity
- Run each CrewAI task as a durable activity.

- Observe execution through tracing, metrics, and structured logs
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Observe execution through tracing, metrics, and structured logs
- Observe execution through tracing, metrics, and structured logs.


This guide walks through orchestrating multiple CrewAI tasks using Dapr Workflows, ensuring each step is run *exactly once* even if the process restarts.

## Getting Started

Initialize Dapr locally to set up a self-hosted environment for development. This process installs the Dapr sidecar binaries, provisions the workflow engine, and prepares a default components directory. For full details, see the official [guide on initializing Dapr locally]({{% ref install-dapr-selfhost.md %}}).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Initialize Dapr locally to set up a self-hosted environment for development. This process installs the Dapr sidecar binaries, provisions the workflow engine, and prepares a default components directory. For full details, see the official [guide on initializing Dapr locally]({{% ref install-dapr-selfhost.md %}}).
Initialize Dapr locally to set up a self-hosted environment for development. This process installs the Dapr sidecar binaries, provisions the workflow engine, and prepares a default components directory. For full details, see [guide on initializing Dapr locally]({{% ref install-dapr-selfhost.md %}}).


Initialize Dapr:

```bash
dapr init
```

Verify that daprio/dapr, openzipkin/zipkin, and redis are running:

```bash
docker ps
```

### Install Python

{{% alert title="Note" color="info" %}}
Make sure you have Python already installed. `Python >=3.10`. For installation instructions, visit the official [Python installation guide](https://www.python.org/downloads/).
{{% /alert %}}

### Install Dependencies

```bash
pip install dapr dapr-ext-workflow crewai
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This puts a LOT of packages onto your machine. This never actually completed for me, with this stuck message that never finished.

  Preparing metadata (setup.py) ... done
INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime. See https://pip.pypa.io/warnings/backtracking for guidance. If you want to abort this run, press Ctrl + C.

```

### Create a Python Virtual Environment (recommended)

```bash
python -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
```

### Create a Workflow to Run CrewAI Tasks

Create a file named crewai_workflow.py and paste the following:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Provide an overview explanation of what this application does, to prepare reading the code


```python
from dapr.ext.workflow import (
WorkflowRuntime,
DaprWorkflowContext,
WorkflowActivityContext,
DaprWorkflowClient,
)
from crewai import Agent, Task, Crew
import time

wfr = WorkflowRuntime()

# ------------------------------------------------------------
# 1. Define Agent, Tasks, and Task Dictionary
# ------------------------------------------------------------
agent = Agent(
role="Research Analyst",
goal="Research and summarize impactful technology updates.",
backstory="A skilled analyst who specializes in researching and summarizing technology topics.",
)

tasks = {
"latest_ai_news": Task(
description="Find the latest news about artificial intelligence.",
expected_output="A 3-paragraph summary of the top 3 stories.",
agent=agent,
),
"ai_startup_launches": Task(
description="Summarize the most impactful AI startup launches in the last 6 months.",
expected_output="A list summarizing 2 AI startups with links.",
agent=agent,
),
"ai_policy_updates": Task(
description="Summarize the newest AI government policy and regulation updates.",
expected_output="A bullet-point list summarizing the latest policy changes.",
agent=agent,
),
}

# ------------------------------------------------------------
# 2. Activity — runs ONE task by name
# ------------------------------------------------------------
@wfr.activity(name="run_task")
def run_task_activity(ctx: WorkflowActivityContext, task_name: str):
print(f"Running CrewAI task: {task_name}", flush=True)

task = tasks[task_name]

# Create a Crew for just this one task
temp_crew = Crew(agents=[agent], tasks=[task])

# kickoff() works across CrewAI versions
result = temp_crew.kickoff()

return str(result)

# ------------------------------------------------------------
# 3. Workflow — orchestrates tasks durably
# ------------------------------------------------------------
@wfr.workflow(name="crewai_multi_task_workflow")
def crewai_workflow(ctx: DaprWorkflowContext):
print("Starting multi-task CrewAI workflow", flush=True)

latest_news = yield ctx.call_activity(run_task_activity, input="latest_ai_news")
startup_summary = yield ctx.call_activity(run_task_activity, input="ai_startup_launches")
policy_updates = yield ctx.call_activity(run_task_activity, input="ai_policy_updates")

return {
"latest_news": latest_news,
"startup_summary": startup_summary,
"policy_updates": policy_updates,
}

# ------------------------------------------------------------
# 4. Runtime + Client (entry point)
# ------------------------------------------------------------
if __name__ == "__main__":
wfr.start()

client = DaprWorkflowClient()
instance_id = "crewai-multi-01"

client.schedule_new_workflow(
workflow=crewai_workflow,
input=None,
instance_id=instance_id
)

state = client.wait_for_workflow_completion(instance_id, timeout_in_seconds=60)
print(state.serialized_output)
```

### Create the Workflow Database Component

Dapr Workflows persist durable state using any [Dapr state store]({{% ref supported-state-stores %}}) that supports workflows.
Create a components directory, then create the file workflowstore.yaml:

```yaml
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: statestore
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
name: statestore
name: workflowstatestore

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we keep these names consistent. Mostly we use workflowstatestore in the quickstarts? Also I could not find the reference to this component in the code, so how does it get used? This should be set by the 'DaprWorkflowClient'

spec:
type: state.redis
version: v1
metadata:
- name: redisHost
value: localhost:6379
- name: redisPassword
value: ""
- name: actorStateStore
value: "true"
```
This component stores:
* Checkpoints
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Checkpoints
* Code execution checkpoints

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Put periods at the end of these sentences

* Execution history
* Deterministic resumption state
* Final output data
### Set a CrewAI LLM Provider
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Provide little more guidance here, always good to be explicit, best with an example.
It looks like the minimum for openAI would be this. Is this correct?

MODEL=model-id # e.g. gpt-5o
OPENAI_API_KEY=sk-...

CrewAI needs an LLM configuration or token to run. See instructions [here](https://docs.crewai.com/en/concepts/llms#setting-up-your-llm).
### Run the Workflow
Launch the CrewAI workflow using the Dapr CLI:
```bash
dapr run \
--app-id crewaiwf \
--dapr-grpc-port 50001 \
--resources-path ./components \
-- python3 ./crewai_workflow.py
```

As the workflow runs, each CrewAI task is executed as a durable activity.
If the process crashes, the workflow resumes exactly where it left off.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If the process crashes, the workflow resumes exactly where it left off.
If the process crashes, the workflow resumes exactly where it left off. You can try this by killing the process after the first activity and then rerunning that command line above with the same application ID.

Does that work (this comment above) or do you need to also provide the instance ID? It would be good to show how someone can try this out and see it in action.


Open Zipkin to view workflow traces:

```
http://localhost:9411
```
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could not get this code to work, first due to the component discovery. Let's check the steps.

Loading