# Make (Workflow Automation) MCP for AI Agents AI Agent Connect

> Make (Workflow Automation) MCP lets you manage your Make.com scenarios, logs, and data stores directly through your AI agent. Stop digging through complex dashboards to find why a workflow failed or to check a scenario's logic. This Connector gives your agent the eyes to see your entire automation footprint, allowing you to audit connections, inspect team structures, and debug execution errors using plain English commands.

## Overview
- **Category:** growth-engine
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_r2CLvTcOALOF2OpiXX677eGYLrooDXLwGaSUPk6K/ai-agent-connect
- **Tags:** workflow-orchestration, api-integration, execution-logs, data-mapping, automation-debugging

## Description

When you're running dozens of automated workflows, things get messy fast. You end up with a mountain of scenarios, and when one breaks, you're stuck clicking through nested menus to find the right log or see which module actually tripped. This Connector changes that by letting you talk to your Make account like it's a team member. Instead of hunting for a specific organization ID or trying to remember which connection is actually active, you can just ask your agent to show you the layout. You can pull up the history of a failed run to see exactly what data went wrong or check your internal data stores to see what's currently sitting in your tables. It's about moving from manual dashboard hunting to direct, conversational management. By connecting this to your setup via the Vinkius catalog, you turn your AI into a dedicated automation operator. You can audit your entire infrastructure, verify authentication hooks, and map out complex team environments without ever leaving your chat window. It's for the people who need to see the big picture of their automation footprint without the friction of a heavy UI. You get the ability to verify logic, inspect metadata, and monitor persistent data across your entire workspace without the manual overhead of navigating a dense interface.

## Tools

### list_scenarios
Check the list of active Make scenarios. Use this to get an overview of what's running in your account.

### get_scenario
Get the specific details of a single Make scenario. This is useful for looking at module mappings and trigger settings.

### list_teams
List the teams inside a specific organization. This helps you map out your team structure for complex auditing.

### list_scenario_logs
Get execution logs for a specific scenario. This is the fastest way to debug errors and see data processing volumes.

### list_data_stores
List your Make data stores. Use this to monitor the persistent data used across your workflows.

### list_connections
List all Make connections linked to an organization. Use this to see which apps are currently authenticated.

### list_organizations
List the organizations for your current user. This helps you identify the right workspace for your automation tasks.

## Prompt Examples

**Prompt:** 
```
Which connections are currently active in my 'Marketing' organization?
```

**Response:** 
```
I've checked the connections for your 'Marketing' organization. Here is the current status:

| App | Status |
| :--- | :--- |
| **Google Sheets** | ✅ Verified |
| **Slack** | ✅ Verified |
| **Airtable** | ❌ Expired |
| **HubSpot** | ✅ Verified |

It looks like the Airtable connection needs to be re-authenticated.
```

**Prompt:** 
```
Show me the logs for scenario 'Lead-Gen-Sync' from this morning.
```

**Response:** 
```
Retrieving logs for **Lead-Gen-Sync**... 

Here are the last 3 runs from today:
- **Run ID: 98765** | 09:15 AM | ✅ Success
- **Run ID: 98766** | 10:30 AM | ✅ Success
- **Run ID: 98767** | 11:45 AM | ❌ Failed

**Error Detail:** 
`401 Unauthorized` on the Slack module. The API token appears to have expired or been revoked.
```

**Prompt:** 
```
List all my data stores and tell me which ones are linked to my sales flow.
```

**Response:** 
```
I've found 3 data stores in your Make account:

1. **Sales_Leads_Temp** (Key-Value)
2. **Customer_Archive** (Key-Value)
3. **System_Logs_Internal** (Key-Value)

Based on your scenario configurations, **Sales_Leads_Temp** is the primary store linked to your sales flow.
```

## Capabilities

### Retrieve execution logs
Get the history of a specific scenario run to see success messages or error details.

### Audit organization structure
List all your organizations and teams to get a clear view of your workspace footprint.

### Verify active connections
Check which apps are currently linked and authenticated within a specific organization.

### Inspect data stores
View your internal Make data stores to see the persistent data used by your workflows.

### Map scenario logic
Pull detailed scenario configurations including module mappings and trigger settings.

### List all scenarios
Get a full list of every managed scenario in your account to see what's currently active.

## Use Cases

### Debugging a failed production flow
A production flow stops working. Ask the agent to check list_scenario_logs for the last 5 runs to find the specific error payload.

### Auditing security for a new client
You need to see what third-party apps have access. Call list_connections to get a full list of authenticated hooks in one view.

### Mapping out a complex workspace
You need to know which teams are in an organization. Use list_teams to map out the structure for a downstream API project.

### Verifying data store contents
You're unsure what data is being saved. Use list_data_stores to see which key-value tables are being populated by your active flows.

## Benefits

- Stop hunting for errors by using list_scenario_logs to see exactly why a run failed in seconds.
- Audit your entire footprint by using list_organizations and list_teams to see every workspace you manage.
- Verify your auth status quickly with list_connections to ensure your apps stay connected.
- Get instant visibility into your persistent data by calling list_data_stores on demand.
- Simplify scenario design by using get_scenario to pull module mappings and trigger settings into your chat.

## How It Works

The bottom line is you get a conversational interface for your entire Make automation infrastructure.

1. Subscribe to the Connector and grab your Make API token.
2. Provide your Make API token and your specific Zone (like us1 or eu1) to your AI client.
3. Ask your agent to list scenarios, check logs, or audit your connections.

## Frequently Asked Questions

**Can the Make (Workflow Automation) MCP help me debug errors?**
Yes, it allows your agent to pull execution logs directly. You can ask it to find specific failures and see the exact error message without opening the Make dashboard.

**Can I see my Make organizations with this Connector?**
Yes, you can list all organizations associated with your account. This is great for getting a high-level view of your entire automation footprint.

**Does the Make (Workflow Automation) MCP support multiple teams?**
Yes, it can list the teams inside any of your organizations. This helps you manage and audit complex team structures across your workspace.

**How do I use the Make (Workflow Automation) MCP to check my data stores?**
You can simply ask your agent to list your data stores. It will show you the persistent data tables you're using across your various workflows.

**Can I manage my Make connections through the agent?**
While you can't create new connections, you can list all active connections to see which apps are linked and check if any have expired.

**Is the Make (Workflow Automation) MCP good for auditing?**
It's perfect for auditing. You can quickly verify connections, list teams, and inspect scenario metadata to ensure your automation infrastructure is set up correctly.

**Can I see the modules and filters used in a Make scenario through my agent?**
Yes. Use the `get_scenario` tool with a specific Scenario ID. Your agent will retrieve the complete design structure, exposing the modules, mapping variables, and any logic filters configured in the flow.

**How do I find out why a Make scenario failed recently?**
The `list_scenario_logs` tool allows your agent to extract the execution history for a given scenario. You'll be able to see exactly when the failure occurred and retrieve the error message to assist with debugging.

**Can my agent list all active connections in my Make organization?**
Absolutely. Use the `list_connections` tool with your Organization ID. Your agent will report all configured auth hooks, helping you audit which services are currently linked to your Make account.