DS DevShelfHub Projects · AI tools
Tutorials / CrewAI / Reference / Classes / InvokeCrewAIAutomationTool
Class tools

InvokeCrewAIAutomationTool: Reference Guide

By DevShelfHub

Invokes a deployed CrewAI AMP automation from another crew — composing automations across the platform.

See the CrewAI API reference index, CrewAI introduction, and core concepts for surrounding context.

What is InvokeCrewAIAutomationTool?

InvokeCrewAIAutomationTool is the AMP-native bridge that lets one deployed crew call another automation by ID, using the platform's auth and transport instead of hand-rolling HTTP. It is how teams shard large systems: a lightweight triage crew can forward heavy research or generation work to a specialized automation that already has its own rate limits, secrets, and observability dashboards.

Inputs and outputs follow the same structured patterns as other CrewAI tools — the caller supplies the automation_id (from AMP) and a payload dict matching what the downstream automation expects. Streaming support mirrors AMP capabilities so long-running delegations can still surface partial progress to the parent crew when enabled.

This tool is intentionally absent from pure open-source deployments: without AMP there is no managed automation registry or credential broker. Local development should stub the tool or gate it behind environment flags so pytest does not attempt real cross-tenant calls.

When to Use

Composing multiple AMP automations.

Use Cases

  • • AMP-to-AMP composition

Key Features

  • ✓ Auto-auth
  • ✓ Streaming support

When NOT to Use

Standalone OSS deployments.

Notes

Automation IDs are contracts

Renaming or deleting the downstream automation breaks callers. Store IDs in configuration per environment and validate during deploy.

Latency stacking

Nested AMP calls add network hops. Set aggressive timeouts on the parent crew and surface partial results when streaming is available.

Auth is platform-managed

Do not try to pass raw service account secrets through prompts — rely on AMP-scoped credentials issued to the automation.

Local testing

Mock InvokeCrewAIAutomationTool in unit tests or run against a dedicated sandbox automation to avoid billing production workloads.

Import

python 
from crewai_tools import InvokeCrewAIAutomationTool

Key Parameters

Parameter Type Default Purpose
automation_id str — Target automation id.

Code Examples

Delegate heavy research to another automation

python 
import os
from crewai import Agent
from crewai_tools import InvokeCrewAIAutomationTool

research_bridge = InvokeCrewAIAutomationTool(automation_id=os.environ['AMP_RESEARCH_AUTOMATION_ID'])

router = Agent(role='Router', goal='Delegate deep dives', backstory='Call AMP for long jobs.', tools=[research_bridge])

Minimal tool list

python 
from crewai_tools import InvokeCrewAIAutomationTool

tools = [InvokeCrewAIAutomationTool(automation_id='a1b2c3d4-e5f6-7890-abcd-ef1234567890')]

Pair with Serper for discovery + AMP for execution

python 
from crewai import Agent
from crewai_tools import InvokeCrewAIAutomationTool, SerperDevTool

agent = Agent(
    role='Operator',
    goal='Find URLs then invoke AMP enrichment',
    backstory='Keep AMP calls idempotent.',
    tools=[SerperDevTool(), InvokeCrewAIAutomationTool(automation_id='prod-enrichment')],
)

Common Mistakes

❌ Hard-coding production automation_id in source

✅ Load from environment or AMP config APIs per stage.

InvokeCrewAIAutomationTool FAQ

What is InvokeCrewAIAutomationTool in CrewAI?

Invokes a deployed CrewAI AMP automation from another crew — composing automations across the platform. InvokeCrewAIAutomationTool is the AMP-native bridge that lets one deployed crew call another automation by ID, using the platform's auth and transport instead of hand-rolling HTTP. It is how teams shard large systems: a lightweight triage crew can forward heavy research or generation work to a specialized automation that already has its own rate limits, secrets, and observability dashboards. Inputs and outputs follow the same structured patterns as other CrewAI tools — the c…

Which package defines the CrewAI class InvokeCrewAIAutomationTool?

DevShelfHub maps InvokeCrewAIAutomationTool to Python module crewai_tools (package path crewai_tools in this reference). Pin your installed crewai version and match imports to the snippet on this page.

When should I use InvokeCrewAIAutomationTool?

Composing multiple AMP automations.

When should I avoid using InvokeCrewAIAutomationTool?

Standalone OSS deployments.

How do I import InvokeCrewAIAutomationTool in Python?

from crewai_tools import InvokeCrewAIAutomationTool

Where can I explore more CrewAI API reference pages?

Open the CrewAI API reference index on DevShelfHub to search 58 classes, 30 methods, and 16 decorators, each with runnable examples, parameters, common mistakes, and cross-links.