# Agent orchestration
Agent orchestration enables your genies to work autonomously within recipes. Recipes assign tasks to genies without user input. Genies process tasks while the recipe job pauses, then return responses and metadata to the recipe. The recipe resumes with the returned data.
You can track Agent orchestration workflows on the Conversations page. Each task assigned to a genie appears as a new conversation.
Agent orchestration uses the Assign task to genie action.
The Assign task to genie action lets you assign a task to your genie. You must provide a clear task description to ensure that your genie understands how to handle the task.
VERIFIED USER ACCESS and USER CONFIRMATION CONNECTIONS AREN'T SUPPORTED
The Assign task to genie action can't be used with genies that have verified user access skills or that require user confirmations with Business approvals.
# Assign task to genie action
You can use the Assign task to genie action to assign a task to a genie. This enables your genie to trigger a recipe autonomously, perform the assigned task, and return a response.
Complete the following steps to configure the Assign task to genie action:
Go to the skill recipe where you plan to assign a task to a genie.
Click the Select an app and action step in the recipe.
Search for and select Workato Genie.
Select the Assign task to genie action.
Assign task to genie action
Use the Genie drop-down menu to select the genie you plan to use.
Set up the Assign task to genie action
Enter detailed instructions in the Task description to genie field. Write clear, self-contained tasks to ensure your genie handles them correctly. Include all required data.
BEST PRACTICES FOR TASK DATA
Write clear task instructions and include all required data you plan for your genie to process to design reliable and autonomous orchestration workflows.
- Keep tasks self-contained and use Conversation ID for continuity.
- Use structured output for downstream mapping with predictable fields, such as status, result, and URLs.
- Delegate across genies by splitting large or multi-domain tasks.
- Monitor and evaluate by reviewing tasks on the Conversations page.
For example:
Review the customer onboarding form and extract the following:
- Company name and size
- Industry category
- Required integrations
Also retrieve their enterprise compliance requirements from Salesforce if the company size is over 500 employees. Return all data in JSON format with fields: company_name, company_size, industry, integrations (array), enterprise_requirements (object or null).
Alternatively, you can provide a structured description format to improve outcomes. For example:
<instructions>
Perform the following steps for the following task data
- [Step 1]
- [Step 2]
If you hit errors or need clarification
- [Error handling instructions]
</instructions>
Use the following context to handle the task
<data>
[Map any datapills or provide the task data so your genie can handle it]
</data>
Optional. Expand the Additional context for genie section and provide up to ten files as context for the task.
Optional. Click Show optional fields and select Configure genie output for usage in this recipe if you plan to enable your genie to respond with a structured output rather than a plain text response. This allows you to use the output datapills in downstream steps in your recipe.
Optional. Click Show optional fields and select Conversation ID to pass context from a previous task. Map the ID to assign a task that builds on the earlier conversation.
Click Save.
# Agent orchestration example use cases
Agent orchestration lets genies run multi-step tasks autonomously within recipes. This enables workflows that require decision-making, data gathering, or document handling to run without user input. Refer to the following example use cases to determine how Agent orchestration can be applied to your workflows:
- Autonomous task processing: Genies perform complete tasks while the recipe job is suspended. For example:
- Invoice reconciliation: Compare invoices and POs, and then return JSON summary of matches and discrepancies.
- Contract summarization: Extract key clauses, such as termination, renewal, and payment from contracts.
- Support triage: Categorize tickets and suggest priority level or assignee.
- Knowledge-based decision-making: Genies use internal knowledge bases to guide deterministic workflows. For example:
- Policy Q&A: Genies answer questions within a recipe using internal SOPs or wikis.
- Documentation lookup: A support genie retrieves relevant product documents and URLs.
- File and data processing: Genies parse, validate, or enrich structured and unstructured data.
For example:
- Document classification: Identify document type and metadata.
- Data extraction: Parse spreadsheets or CSVs and enrich data through API interaction.
- Evidence upload: Collect and upload audit files to Google Drive or SharePoint.
- Testing and evaluation: Genies autonomously test workflows or other genies. For example:
- Response testing: Compare genie outputs against expected answers.
- Genies in channels: Genies process background tasks while keeping conversational context in combination with Workbot for Slack or Teams. For example:
- Persistent Conversation ID: Maintains multi-turn conversations using the same Conversation ID.
- Cross-agent collaboration: Genies delegate subtasks to each other with the Assign task to genie action to form multi-agent workflows. For example:
- Compliance audit: Audit Genie delegates evidence collection to another genie to compile results.
- Procurement: Finance genie validates a budget, and then Procurement genie proceeds to onboarding.
- Project updates: Product Manager genie summarizes Jira issues, and then Communications genie drafts updates.
# Compliance audit example use case
A compliance audit triggers on a schedule and the Audit genie autonomously initiates evidence collection. The Audit genie uses an API endpoint skill to call a recipe that assigns the evidence collection task to the Evidence Collection genie.
The Evidence Collection genie autonomously collects required compliance documentation from multiple systems and uploads the files to Google Drive and returns the file URLs to the Audit genie, which then uploads the evidence to the governance, risk, and compliance tool.
Workflow outline
Trigger: Scheduled recipe triggers the Audit genie to begin compliance evidence collection.
API call: The Audit genie uses a skill to call an API endpoint recipe.
Assign task to genie: The API endpoint recipe uses the Assign task to genie action to send the evidence collection task to the Evidence Collection genie and suspends the recipe job.
Autonomous task processing: The genie references the task instructions to understand how to process the task.
Sends response: The genie sends the response and metadata back to the recipe when the task is complete.
Resume recipe: The API endpoint recipe resumes and returns the genie's response to the Audit genie.
Complete workflow: The Audit genie uses the Google Drive URLs to access and upload the files to the governance, risk, and compliance tool using another skill.
Last updated: 11/10/2025, 5:41:40 PM