mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-02 13:48:09 +00:00
* feat: adopt directory-based docs versioning with Edge channel Switch docs.crewai.com from navigation-only versioning (every version selector entry rendered the same docs/<lang>/* source files) to Mintlify's directory-based versioning so each version selector entry renders its own snapshot. Add an "Edge" channel under docs/edge/<lang>/* that always reflects main HEAD for unreleased work, eliminating pre-release leakage onto frozen release labels. External links to canonical /<lang>/* URLs are preserved via wildcard redirects that always land on the current default version. Layout: - docs/edge/<lang>/* rolling source (you edit here) - docs/edge/enterprise-api.*.yaml - docs/v<X.Y.Z>/<lang>/* frozen, immutable snapshots - docs/v<X.Y.Z>/enterprise-api.*.yaml - docs/images/ shared, append-only - docs/docs.json nav + redirects URLs follow the Mintlify-idiomatic shape: /edge/<lang>/<page> for Edge, /v<X.Y.Z>/<lang>/<page> for every frozen snapshot. The wildcard redirects /<lang>/:slug* -> /<default>/<lang>/:slug* keep stale links working, and every freeze rewrites them (plus all per-section/per-page redirects) so destinations always resolve to the current default without depending on a second redirect hop. Release flow integration (devtools release): - New module crewai_devtools.docs_versioning.freeze() materialises docs/v<X.Y.Z>/ from docs/edge/, rewrites openapi: refs inside the snapshot, inserts the version into every language block in docs.json, and refreshes all redirect destinations. - _update_docs_and_create_pr() in cli.py now calls that freeze during Phase 2 of devtools release. Edge changelogs are updated first (so the snapshot freeze picks them up), then the snapshot is staged alongside docs.json, branched as docs/freeze-v<X.Y.Z>, and the PR is titled [docs-freeze] docs: snapshot and changelog for v<X.Y.Z> — the title prefix the new CI guard reads. - The PR still gates tag, GitHub release, PyPI publish, and the enterprise release as before; no new PRs are added. - Pre-releases (1.X.YaN, 1.X.YbN, ...) skip the snapshot — they ride Edge — and the docs PR title omits the [docs-freeze] prefix. - docs_check (AI-generated docs scaffolding) writes to docs/edge/<lang>/* so newly-generated unreleased docs land in Edge and never accidentally touch a frozen snapshot. Migration scripts (one-shot): - scripts/docs/freeze_historical_versions.py reconstructs all 16 historical snapshots (v1.10.0 .. v1.14.7) from git tags via git archive | tar, rewriting openapi: MDX refs so each snapshot reads its own enterprise-api YAML rather than the live one. - scripts/docs/prefix_version_paths.py one-shot-migrates docs.json: rewrites every page path in 16 versioned blocks to point under docs/v<X.Y.Z>/, inserts a new Edge entry per language, tags v1.14.7 as Latest (default), prunes pages whose target file doesn't exist in the snapshot (e.g. docs/ar/ didn't exist before v1.12.0), and writes the wildcard + per-section redirects. - scripts/docs/freeze_current_edge.py is now a thin CLI wrapper around docs_versioning.freeze for manual one-off freezes (e.g. retroactively snapshotting a forgotten release). CI guards (.github/workflows/docs-snapshots.yml): - Frozen snapshots under docs/v[0-9]*/ are immutable; only PRs whose title contains [docs-freeze] (i.e. release-cut PRs generated by devtools release or the manual wrapper) may modify them. - Images under docs/images/ are append-only since snapshots share a single image directory. Deleting or renaming an image breaks every historical snapshot that still references it. Restored docs/images/crewai-otel-export.png from PR #3673; it was deleted in PR #4908 but v1.10.0 / v1.10.1 snapshots still reference it. Restoring instead of editing the snapshots preserves historical rendering fidelity and validates the new append-only rule retroactively. Tests: - lib/devtools/tests/test_docs_versioning.py covers the freeze: file copy, openapi rewrite, version insertion, default demotion, redirect upserts, per-section redirect rewriting, idempotency, and invalid inputs. Verified locally with mintlify broken-links: 0 broken links across the full site (Edge + 16 frozen versions, 4 locales). AGENTS.md (repo root) is the contributor guide for the new model; RELEASING.md is the release-cut runbook; README's Contribution section links to both. Co-authored-by: Cursor <cursoragent@cursor.com> * style: resolve linter issues --------- Co-authored-by: Cursor <cursoragent@cursor.com>
277 lines
9.7 KiB
Plaintext
277 lines
9.7 KiB
Plaintext
---
|
|
title: CrewAI Run Automation Tool
|
|
description: Enables CrewAI agents to invoke CrewAI Platform automations and leverage external crew services within your workflows.
|
|
icon: robot
|
|
---
|
|
|
|
# `InvokeCrewAIAutomationTool`
|
|
|
|
The `InvokeCrewAIAutomationTool` provides CrewAI Platform API integration with external crew services. This tool allows you to invoke and interact with CrewAI Platform automations from within your CrewAI agents, enabling seamless integration between different crew workflows.
|
|
|
|
## Installation
|
|
|
|
```bash
|
|
uv pip install 'crewai[tools]'
|
|
```
|
|
|
|
## Requirements
|
|
|
|
- CrewAI Platform API access
|
|
- Valid bearer token for authentication
|
|
- Network access to CrewAI Platform automation endpoints
|
|
|
|
## Usage
|
|
|
|
Here's how to use the tool with a CrewAI agent:
|
|
|
|
```python {2, 4-9}
|
|
from crewai import Agent, Task, Crew
|
|
from crewai_tools import InvokeCrewAIAutomationTool
|
|
|
|
# Initialize the tool
|
|
automation_tool = InvokeCrewAIAutomationTool(
|
|
crew_api_url="https://data-analysis-crew-[...].crewai.com",
|
|
crew_bearer_token="your_bearer_token_here",
|
|
crew_name="Data Analysis Crew",
|
|
crew_description="Analyzes data and generates insights"
|
|
)
|
|
|
|
# Create a CrewAI agent that uses the tool
|
|
automation_coordinator = Agent(
|
|
role='Automation Coordinator',
|
|
goal='Coordinate and execute automated crew tasks',
|
|
backstory='I am an expert at leveraging automation tools to execute complex workflows.',
|
|
tools=[automation_tool],
|
|
verbose=True
|
|
)
|
|
|
|
# Create a task for the agent
|
|
analysis_task = Task(
|
|
description="Execute data analysis automation and provide insights",
|
|
agent=automation_coordinator,
|
|
expected_output="Comprehensive data analysis report"
|
|
)
|
|
|
|
# Create a crew with the agent
|
|
crew = Crew(
|
|
agents=[automation_coordinator],
|
|
tasks=[analysis_task],
|
|
verbose=2
|
|
)
|
|
|
|
# Run the crew
|
|
result = crew.kickoff()
|
|
print(result)
|
|
```
|
|
|
|
## Tool Arguments
|
|
|
|
| Argument | Type | Required | Default | Description |
|
|
|:---------|:-----|:---------|:--------|:------------|
|
|
| **crew_api_url** | `str` | Yes | None | Base URL of the CrewAI Platform automation API |
|
|
| **crew_bearer_token** | `str` | Yes | None | Bearer token for API authentication |
|
|
| **crew_name** | `str` | Yes | None | Name of the crew automation |
|
|
| **crew_description** | `str` | Yes | None | Description of what the crew automation does |
|
|
| **max_polling_time** | `int` | No | 600 | Maximum time in seconds to wait for task completion |
|
|
| **crew_inputs** | `dict` | No | None | Dictionary defining custom input schema fields |
|
|
|
|
## Environment Variables
|
|
|
|
```bash
|
|
CREWAI_API_URL=https://your-crew-automation.crewai.com # Alternative to passing crew_api_url
|
|
CREWAI_BEARER_TOKEN=your_bearer_token_here # Alternative to passing crew_bearer_token
|
|
```
|
|
|
|
## Advanced Usage
|
|
|
|
### Custom Input Schema with Dynamic Parameters
|
|
|
|
```python {2, 4-15}
|
|
from crewai import Agent, Task, Crew
|
|
from crewai_tools import InvokeCrewAIAutomationTool
|
|
from pydantic import Field
|
|
|
|
# Define custom input schema
|
|
custom_inputs = {
|
|
"year": Field(..., description="Year to retrieve the report for (integer)"),
|
|
"region": Field(default="global", description="Geographic region for analysis"),
|
|
"format": Field(default="summary", description="Report format (summary, detailed, raw)")
|
|
}
|
|
|
|
# Create tool with custom inputs
|
|
market_research_tool = InvokeCrewAIAutomationTool(
|
|
crew_api_url="https://state-of-ai-report-crew-[...].crewai.com",
|
|
crew_bearer_token="your_bearer_token_here",
|
|
crew_name="State of AI Report",
|
|
crew_description="Retrieves a comprehensive report on state of AI for a given year and region",
|
|
crew_inputs=custom_inputs,
|
|
max_polling_time=15 * 60 # 15 minutes timeout
|
|
)
|
|
|
|
# Create an agent with the tool
|
|
research_agent = Agent(
|
|
role="Research Coordinator",
|
|
goal="Coordinate and execute market research tasks",
|
|
backstory="You are an expert at coordinating research tasks and leveraging automation tools.",
|
|
tools=[market_research_tool],
|
|
verbose=True
|
|
)
|
|
|
|
# Create and execute a task with custom parameters
|
|
research_task = Task(
|
|
description="Conduct market research on AI tools market for 2024 in North America with detailed format",
|
|
agent=research_agent,
|
|
expected_output="Comprehensive market research report"
|
|
)
|
|
|
|
crew = Crew(
|
|
agents=[research_agent],
|
|
tasks=[research_task]
|
|
)
|
|
|
|
result = crew.kickoff()
|
|
```
|
|
|
|
### Multi-Stage Automation Workflow
|
|
|
|
```python {2, 4-35}
|
|
from crewai import Agent, Task, Crew, Process
|
|
from crewai_tools import InvokeCrewAIAutomationTool
|
|
|
|
# Initialize different automation tools
|
|
data_collection_tool = InvokeCrewAIAutomationTool(
|
|
crew_api_url="https://data-collection-crew-[...].crewai.com",
|
|
crew_bearer_token="your_bearer_token_here",
|
|
crew_name="Data Collection Automation",
|
|
crew_description="Collects and preprocesses raw data"
|
|
)
|
|
|
|
analysis_tool = InvokeCrewAIAutomationTool(
|
|
crew_api_url="https://analysis-crew-[...].crewai.com",
|
|
crew_bearer_token="your_bearer_token_here",
|
|
crew_name="Analysis Automation",
|
|
crew_description="Performs advanced data analysis and modeling"
|
|
)
|
|
|
|
reporting_tool = InvokeCrewAIAutomationTool(
|
|
crew_api_url="https://reporting-crew-[...].crewai.com",
|
|
crew_bearer_token="your_bearer_token_here",
|
|
crew_name="Reporting Automation",
|
|
crew_description="Generates comprehensive reports and visualizations"
|
|
)
|
|
|
|
# Create specialized agents
|
|
data_collector = Agent(
|
|
role='Data Collection Specialist',
|
|
goal='Gather and preprocess data from various sources',
|
|
backstory='I specialize in collecting and cleaning data from multiple sources.',
|
|
tools=[data_collection_tool]
|
|
)
|
|
|
|
data_analyst = Agent(
|
|
role='Data Analysis Expert',
|
|
goal='Perform advanced analysis on collected data',
|
|
backstory='I am an expert in statistical analysis and machine learning.',
|
|
tools=[analysis_tool]
|
|
)
|
|
|
|
report_generator = Agent(
|
|
role='Report Generation Specialist',
|
|
goal='Create comprehensive reports and visualizations',
|
|
backstory='I excel at creating clear, actionable reports from complex data.',
|
|
tools=[reporting_tool]
|
|
)
|
|
|
|
# Create sequential tasks
|
|
collection_task = Task(
|
|
description="Collect market data for Q4 2024 analysis",
|
|
agent=data_collector
|
|
)
|
|
|
|
analysis_task = Task(
|
|
description="Analyze collected data to identify trends and patterns",
|
|
agent=data_analyst
|
|
)
|
|
|
|
reporting_task = Task(
|
|
description="Generate executive summary report with key insights and recommendations",
|
|
agent=report_generator
|
|
)
|
|
|
|
# Create a crew with sequential processing
|
|
crew = Crew(
|
|
agents=[data_collector, data_analyst, report_generator],
|
|
tasks=[collection_task, analysis_task, reporting_task],
|
|
process=Process.sequential,
|
|
verbose=2
|
|
)
|
|
|
|
result = crew.kickoff()
|
|
```
|
|
|
|
## Use Cases
|
|
|
|
### Distributed Crew Orchestration
|
|
- Coordinate multiple specialized crew automations to handle complex, multi-stage workflows
|
|
- Enable seamless handoffs between different automation services for comprehensive task execution
|
|
- Scale processing by distributing workloads across multiple CrewAI Platform automations
|
|
|
|
### Cross-Platform Integration
|
|
- Bridge CrewAI agents with CrewAI Platform automations for hybrid local-cloud workflows
|
|
- Leverage specialized automations while maintaining local control and orchestration
|
|
- Enable secure collaboration between local agents and cloud-based automation services
|
|
|
|
### Enterprise Automation Pipelines
|
|
- Create enterprise-grade automation pipelines that combine local intelligence with cloud processing power
|
|
- Implement complex business workflows that span multiple automation services
|
|
- Enable scalable, repeatable processes for data analysis, reporting, and decision-making
|
|
|
|
### Dynamic Workflow Composition
|
|
- Dynamically compose workflows by chaining different automation services based on task requirements
|
|
- Enable adaptive processing where the choice of automation depends on data characteristics or business rules
|
|
- Create flexible, reusable automation components that can be combined in various ways
|
|
|
|
### Specialized Domain Processing
|
|
- Access domain-specific automations (financial analysis, legal research, technical documentation) from general-purpose agents
|
|
- Leverage pre-built, specialized crew automations without rebuilding complex domain logic
|
|
- Enable agents to access expert-level capabilities through targeted automation services
|
|
|
|
## Custom Input Schema
|
|
|
|
When defining `crew_inputs`, use Pydantic Field objects to specify the input parameters:
|
|
|
|
```python
|
|
from pydantic import Field
|
|
|
|
crew_inputs = {
|
|
"required_param": Field(..., description="This parameter is required"),
|
|
"optional_param": Field(default="default_value", description="This parameter is optional"),
|
|
"typed_param": Field(..., description="Integer parameter", ge=1, le=100) # With validation
|
|
}
|
|
```
|
|
|
|
## Error Handling
|
|
|
|
The tool provides comprehensive error handling for common scenarios:
|
|
|
|
- **API Connection Errors**: Network connectivity issues with CrewAI Platform
|
|
- **Authentication Errors**: Invalid or expired bearer tokens
|
|
- **Timeout Errors**: Tasks that exceed the maximum polling time
|
|
- **Task Failures**: Crew automations that fail during execution
|
|
- **Input Validation Errors**: Invalid parameters passed to automation endpoints
|
|
|
|
## API Endpoints
|
|
|
|
The tool interacts with two main API endpoints:
|
|
|
|
- `POST {crew_api_url}/kickoff`: Starts a new crew automation task
|
|
- `GET {crew_api_url}/status/{crew_id}`: Checks the status of a running task
|
|
|
|
## Notes
|
|
|
|
- The tool automatically polls the status endpoint every second until completion or timeout
|
|
- Successful tasks return the result directly, while failed tasks return error information
|
|
- Bearer tokens should be kept secure and not hardcoded in production environments
|
|
- Consider using environment variables for sensitive configuration like bearer tokens
|
|
- Custom input schemas must be compatible with the target crew automation's expected parameters
|