# Workato MCP MCP

> Workato helps you manage your enterprise automation workflows by giving your AI agent full visibility into complex integration platforms. Monitor every recipe, audit job runs across multiple applications, and verify that all app connections are healthy—all without logging into a giant dashboard.

## Overview
- **Category:** growth-engine
- **Price:** Free
- **Tags:** ipaas, workflow-automation, integration-platform, recipe-management, job-monitoring, enterprise-automation

## Description

You can connect your Workato account to any AI client and treat the platform like an extension of your chat window. Instead of manually digging through complex iPaaS dashboards just to check if a scheduled workflow ran successfully, you talk to your agent. Your agent becomes your automation analyst, letting you list every active recipe or dive deep into a single job's execution history to spot errors immediately.

It lets you verify that the connections between critical apps—like Salesforce or NetSuite—are still up and running. You can also get a full inventory of all available connectors and see exactly which APIs are exposed for use in new workflows. This visibility is huge. Because every interaction with this MCP runs on Vinkius, your AI agent gets a cryptographically signed audit trail for everything that happens. So when you check job statuses or connection health, you know exactly what data flowed through and how the budget was spent. It’s pure oversight, without the manual clicking.

## Tools

### get_api_collections
Lists every API collection that Workato exposes to other systems.

### get_recipe_details
Retrieves the setup details for a single, specific Workato workflow recipe.

### list_app_connections
Lists and checks the status of all third-party application connections configured in your account.

### list_automation_recipes
Retrieves a list of every active workflow recipe in your Workato environment.

### list_managed_connectors
Displays all the integration blocks and services available for use within your account.

### list_recipe_jobs
Provides a record of recent job executions, including success status and timestamps, for one recipe.

### list_workato_folders
Shows the organizational folder structure used to manage recipes and assets within your account.

## Prompt Examples

**Prompt:** 
```
List all active recipes in my Workato account.
```

**Response:** 
```
I found 8 active recipes: 1. 'Salesforce to Slack Sync' (ID: 12345), 2. 'NetSuite Invoice Automation' (ID: 67890), 3. 'Zendesk Ticket Triage' (ID: 11223), and 5 others. Which one would you like to audit?
```

**Prompt:** 
```
Show me the last 5 jobs for the 'Salesforce to Slack Sync' recipe.
```

**Response:** 
```
Retrieving jobs for recipe 12345… The last 5 jobs all completed successfully (Status: SUCCESS). The most recent run was 15 minutes ago and processed 12 records. No errors detected.
```

**Prompt:** 
```
Are all my app connections healthy?
```

**Response:** 
```
Checking connections… Your Salesforce, Slack, and NetSuite connections are 'ACTIVE'. However, your Jira connection is 'DISCONNECTED'. Would you like me to pull the connection details to help you re-authenticate?
```

## Capabilities

### Inventory all automation recipes
Get a complete list of every workflow recipe running in your Workato account.

### Audit specific job runs
Review the history and status of recent executions for any individual workflow to check for errors or successes.

### Check app connection health
List every third-party application connection configured in your tenant and confirm they are active.

### Map the platform structure
Browse the folder hierarchy or list available managed connectors to understand how your recipes are organized.

### Examine API endpoints
List all exposed API collections so you know exactly what data points other systems can access via REST.

## Use Cases

### A critical workflow failed overnight
The support team finds an alert about a failing sync. Instead of logging into Workato and digging through folder structures, they ask the agent to run list_recipe_jobs for that specific recipe. The agent replies immediately, showing the last five runs were successful until 3 AM when it failed due to bad credentials.

### Planning a new multi-app integration
An architect needs to know what services are available. They start by calling list_managed_connectors and then get_api_collections to see if the required data endpoints exist before writing any code or building any recipes.

### Verifying platform setup post-migration
The ops team needs a full picture of what exists. They run list_workato_folders first, then use list_automation_recipes to catalog every single workflow that needs testing after the migration.

### Pre-emptively checking dependencies
Before starting development on a new service, the Product Owner asks the agent if all major app connections are healthy. The agent runs list_app_connections and reports immediately that the Jira connection is stale and needs re-authentication.

## Benefits

- Check connection health immediately. Instead of manually navigating to the 'Connections' tab, you simply ask your agent if the Salesforce or NetSuite links are active using list_app_connections.
- Deep dive into specific workflow logic. Use get_recipe_details to pull up a recipe's exact triggers and actions without leaving chat.
- Audit job failures instantly. Need to know why yesterday’s sync failed? Running list_recipe_jobs gives you the full history for that one workflow, pointing straight to the error.
- Understand your scope. You can run list_managed_connectors to see every integration block available, helping Product Owners plan future automation steps.
- Know what's accessible. Using get_api_collections lets you quickly surface all API endpoints so development teams don't waste time searching for data sources.

## How It Works

The bottom line is you get deep operational visibility into your entire integration layer using simple chat commands.

1. You subscribe this MCP and provide your Workato API Token and Base URL.
2. Your AI agent uses natural conversation to request specific information, like 'Show me the jobs for X recipe' or 'Are all my apps connected?'
3. The system runs the query against Workato and sends back a clean report detailing the status, IDs, or history.

## Frequently Asked Questions

**How do I check connection status using list_app_connections?**
You simply ask your agent to run list_app_connections. The system will return a clear report for every connected service, showing if it's 'ACTIVE,' 'INACTIVE,' or 'DISCONNECTED.' This lets you know which apps need immediate attention.

**What is the difference between listing recipes and checking job runs with list_automation_recipes vs list_recipe_jobs?**
list_automation_recipes gives you a catalog—a list of *what* workflows exist. You use list_recipe_jobs when you need to audit a specific workflow's performance, seeing the actual timestamps and success/failure status of its runs.

**Can I find out what APIs are available using get_api_collections?**
Yes. This tool lists all API collections exposed by Workato. If you're building a new integration, this is the first place to check to see exactly which data endpoints are accessible.

**Do I need to know folder IDs for list_workato_folders?**
No. You just ask your agent to run list_workato_folders, and it will show you the entire hierarchical structure of your account's assets, helping you find where specific recipes are stored.

**How can I check which integration blocks are available using list_managed_connectors?**
It lists every managed connector type in your instance. This tells you exactly what kind of integrations and automation capabilities Workato supports for your account.

**What specific steps or triggers make up a workflow when I use get_recipe_details?**
The tool provides deep details about the recipe's internal structure. You can see the exact sequence of actions, what events trigger it, and the targets involved in each step.

**If a job failed, how do I find the error logs using list_recipe_jobs?**
You monitor recent execution jobs for specific recipes. By checking the status fields, you can filter down to only the failed or errored runs to start troubleshooting.

**When listing all my automations with list_automation_recipes, how do I get the unique ID for a recipe?**
The output of this tool provides a comprehensive list that includes the unique ID for every active recipe. This identifier lets you reference or audit the workflow later without ambiguity.