Skip to content
Claude for Operators

Multi-Tool Workflow Orchestration

Last verified: 14 February 2026 | Applies to: Pro, Max, Team, Enterprise

In 30 seconds

Section titled “In 30 seconds”

Most business workflows span multiple tools — check the CRM, update a spreadsheet, post a summary to Slack. Claude can chain these steps into a single command using MCP connectors and skills. Instead of tabbing between five apps, you describe the workflow once and Claude executes it end to end.

What it does

Section titled “What it does”

Workflow orchestration means Claude reads from one tool, processes the data, and writes to another — all within a single Cowork session. The building blocks are:

  • MCP connectors — the pipes that connect Claude to external tools (Slack, Google Sheets, Asana, HubSpot, Notion, etc.)
  • Skills — the instructions that tell Claude how to handle a specific workflow
  • Cowork — the execution environment where Claude can run multi-step operations autonomously

When you combine these, you get workflows like:

  • “Pull this week’s closed deals from HubSpot, calculate commission, and post the summary to the #sales Slack channel”
  • “Check Asana for overdue tasks, draft a nudge message for each owner, and send via Slack”
  • “Read the latest NPS responses from our survey tool, categorise by theme, update the tracking spreadsheet, and draft a summary for the team”

How to set it up

Section titled “How to set it up”

  1. Connect your tools

    Section titled “Connect your tools”

    Before you can orchestrate, you need connectors in place. In Claude Desktop, go to Cowork tab, then Connectors in the left sidebar.

    Install the connectors for the tools you want to chain. Common combinations:

    WorkflowConnectors needed
    Sales reportingCRM (HubSpot/Salesforce) + Spreadsheets (Google Sheets) + Messaging (Slack)
    Task managementProject management (Asana/Linear) + Messaging (Slack) + Calendar (Google Calendar)
    Customer opsCRM + Support tool (Zendesk/Intercom) + Spreadsheets
    Content pipelineCMS (Notion/Confluence) + Spreadsheets + Messaging

    Each connector requires authentication. Claude walks you through the OAuth flow for each tool.

  2. Build your first orchestrated workflow

    Section titled “Build your first orchestrated workflow”

    Start with a simple two-tool chain. Here’s an example that pulls data from a spreadsheet and posts to Slack:

    Read the "Weekly Metrics" sheet in my Google Sheets doc called "2026 KPIs". Summarise the key changes from last week in 3-4 bullet points. Then post that summary to the #operations channel in Slack with the heading "Weekly Metrics Update — [today's date]".

    Claude will:

    1. Use the Google Sheets connector to read the data
    2. Process and summarise the changes
    3. Use the Slack connector to post the formatted message

    Watch the Cowork activity panel — you’ll see each tool call logged as Claude executes the chain.

  3. Add conditional logic

    Section titled “Add conditional logic”

    Real workflows have branches. Claude handles natural-language conditions:

    Check Asana for any tasks assigned to me that are overdue. For each one:
    - If it's overdue by less than 2 days, move the due date to end of this week
    - If it's overdue by more than 2 days, draft a Slack DM to the task creator explaining the delay and asking if the priority has changed
    Show me the drafted messages before sending.

    The “show me before sending” part is important. For any workflow that sends external messages, include a review step until you trust the outputs.

  4. Save it as a reusable skill

    Section titled “Save it as a reusable skill”

    Once a workflow is working, encode it so you can run it with a short command:

    Save this workflow as a skill called "weekly-metrics-update". It should:
    1. Read the Weekly Metrics sheet from my KPIs spreadsheet
    2. Compare to last week's values
    3. Generate a summary with bullets for anything that changed more than 5%
    4. Post to #operations in Slack
    5. Add a row to the "Update Log" sheet with today's date and the summary
    

    Create a slash command: /weekly-metrics

    Next week, you just type /weekly-metrics and the whole chain runs.

  5. Chain more complex sequences

    Section titled “Chain more complex sequences”

    Once you’re comfortable with two-tool chains, build longer ones:

    Run my Monday morning operations check:
    1. Pull all open support tickets from Zendesk that are older than 24 hours
    2. Check if any of those customers have open deals in HubSpot worth more than $50K
    3. For high-value customers with old tickets, create an urgent task in Asana assigned to Sarah with the ticket details
    4. Post a summary to #ops-alerts in Slack: "[count] tickets older than 24h, [count] flagged as high-value"
    5. Add a row to the Monday Check Log in Google Sheets

How operators actually use it

Section titled “How operators actually use it”

A real three-tool chain:

An operations manager at a 20-person SaaS company runs this every Monday morning:

Run my Monday ops check:
1. Pull all deals that moved stages in HubSpot last week
2. For any deal over $25K that moved to "Negotiation" or "Closed Won", check if we have a support ticket from that account in Zendesk
3. Update the "Deal Tracker" Google Sheet with the new stage, date moved, and support ticket status
4. Post a summary to #revenue in Slack

Before orchestration: Open HubSpot, filter deals, export. Open Zendesk, search each account. Open Google Sheets, update manually. Open Slack, write summary. Total: 35-40 minutes, error-prone, often skipped.

After orchestration: One command, 2 minutes of execution, review the Slack post. Done.

Section titled “Related”

Something wrong or outdated? Let us know →

Get weekly workflows — subscribe to the newsletter.