Back to Details

make-automation

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Make Automation via Rube MCP

通过Rube MCP实现Make自动化

Automate Make (formerly Integromat) operations through Composio's Make toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/make
通过Composio的Make工具包，借助Rube MCP自动化Make（原Integromat）的操作。
工具包文档：composio.dev/toolkits/make

Prerequisites

前提条件

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Make connection via 
    RUBE_MANAGE_CONNECTIONS
    with toolkit 
    make
  • Always call 
    RUBE_SEARCH_TOOLS
    first to get current tool schemas
  • 必须已连接Rube MCP（需提供RUBE_SEARCH_TOOLS）
  • 通过
    RUBE_MANAGE_CONNECTIONS
    激活Make连接，工具包选择
    make
  • 请始终先调用
    RUBE_SEARCH_TOOLS
    获取最新的工具架构

Setup

设置步骤

Get Rube MCP: Add 
https://rube.app/mcp
as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
  1. Verify Rube MCP is available by confirming 
    RUBE_SEARCH_TOOLS
    responds
  2. Call 
    RUBE_MANAGE_CONNECTIONS
    with toolkit 
    make
  3. If connection is not ACTIVE, follow the returned auth link to complete Make authentication
  4. Confirm connection status shows ACTIVE before running any workflows
获取Rube MCP：在客户端配置中添加
https://rube.app/mcp
作为MCP服务器。无需API密钥 —— 只需添加端点即可使用。
  1. 通过确认
    RUBE_SEARCH_TOOLS
    能正常响应，验证Rube MCP是否可用
  2. 调用
    RUBE_MANAGE_CONNECTIONS
    并指定工具包为
    make
  3. 如果连接未处于ACTIVE状态，请按照返回的认证链接完成Make认证
  4. 在运行任何工作流之前，确认连接状态显示为ACTIVE

Core Workflows

核心工作流

1. Get Operations Data

1. 获取操作数据

When to use: User wants to retrieve operation logs or usage data from Make scenarios
Tool sequence:
  1. MAKE_GET_OPERATIONS
    - Retrieve operation records [Required]
Key parameters:
  • Check current schema via RUBE_SEARCH_TOOLS for available filters
  • May include date range, scenario ID, or status filters
Pitfalls:
  • Operations data may be paginated; check for pagination tokens
  • Date filters must match expected format from schema
  • Large result sets should be filtered by date range or scenario
适用场景：用户希望从Make场景中检索操作日志或使用数据
工具序列:
  1. MAKE_GET_OPERATIONS
    - 检索操作记录 [必填]
关键参数:
  • 通过RUBE_SEARCH_TOOLS查看当前架构，获取可用的筛选条件
  • 可包含日期范围、场景ID或状态筛选器
注意事项:
  • 操作数据可能会分页；请检查分页令牌
  • 日期筛选器必须符合架构规定的格式
  • 对于大型结果集，应按日期范围或场景进行筛选

2. List Available Languages

2. 列出可用语言

When to use: User wants to see supported languages for Make scenarios or interfaces
Tool sequence:
  1. MAKE_LIST_ENUMS_LANGUAGES
    - Get all supported language codes [Required]
Key parameters:
  • No required parameters; returns complete language list
Pitfalls:
  • Language codes follow standard locale format (e.g., 'en', 'fr', 'de')
  • List is static and rarely changes; cache results when possible
适用场景：用户希望查看Make场景或界面支持的语言
工具序列:
  1. MAKE_LIST_ENUMS_LANGUAGES
    - 获取所有支持的语言代码 [必填]
关键参数:
  • 无必填参数；返回完整的语言列表
注意事项:
  • 语言代码遵循标准区域设置格式（例如：'en'、'fr'、'de'）
  • 列表为静态数据，极少变更；如有可能请缓存结果

3. List Available Timezones

3. 列出可用时区

When to use: User wants to see supported timezones for scheduling Make scenarios
Tool sequence:
  1. MAKE_LIST_ENUMS_TIMEZONES
    - Get all supported timezone identifiers [Required]
Key parameters:
  • No required parameters; returns complete timezone list
Pitfalls:
  • Timezone identifiers use IANA format (e.g., 'America/New_York', 'Europe/London')
  • List is static and rarely changes; cache results when possible
  • Use these exact timezone strings when configuring scenario schedules
适用场景：用户希望查看用于调度Make场景的支持时区
工具序列:
  1. MAKE_LIST_ENUMS_TIMEZONES
    - 获取所有支持的时区标识符 [必填]
关键参数:
  • 无必填参数；返回完整的时区列表
注意事项:
  • 时区标识符采用IANA格式（例如：'America/New_York'、'Europe/London'）
  • 列表为静态数据，极少变更；如有可能请缓存结果
  • 在配置场景调度时，请使用列表中的精确字符串值

4. Scenario Configuration Lookup

4. 场景配置查询

When to use: User needs to configure scenarios with correct language and timezone values
Tool sequence:
  1. MAKE_LIST_ENUMS_LANGUAGES
    - Get valid language codes [Required]
  2. MAKE_LIST_ENUMS_TIMEZONES
    - Get valid timezone identifiers [Required]
Key parameters:
  • No parameters needed for either call
Pitfalls:
  • Always verify language and timezone values against these enums before using in configuration
  • Using invalid values in scenario configuration will cause errors
适用场景：用户需要使用正确的语言和时区值配置场景
工具序列:
  1. MAKE_LIST_ENUMS_LANGUAGES
    - 获取有效的语言代码 [必填]
  2. MAKE_LIST_ENUMS_TIMEZONES
    - 获取有效的时区标识符 [必填]
关键参数:
  • 两个调用均无需参数
注意事项:
  • 在配置中使用语言和时区值之前，请始终对照这些枚举进行验证
  • 在场景配置中使用无效值会导致错误

Common Patterns

常见模式

Enum Validation

枚举验证

Before configuring any Make scenario properties that accept language or timezone:
1. Call MAKE_LIST_ENUMS_LANGUAGES or MAKE_LIST_ENUMS_TIMEZONES
2. Verify the desired value exists in the returned list
3. Use the exact string value from the enum list
在配置任何接受语言或时区的Make场景属性之前：
1. 调用MAKE_LIST_ENUMS_LANGUAGES或MAKE_LIST_ENUMS_TIMEZONES
2. 验证所需值是否存在于返回的列表中
3. 使用枚举列表中的精确字符串值

Operations Monitoring

操作监控

1. Call MAKE_GET_OPERATIONS with date range filters
2. Analyze operation counts, statuses, and error rates
3. Identify failed operations for troubleshooting
1. 调用MAKE_GET_OPERATIONS并传入日期范围筛选器
2. 分析操作数量、状态和错误率
3. 识别失败的操作以进行故障排除

Caching Strategy for Enums

枚举缓存策略

Since language and timezone lists are static:
1. Call MAKE_LIST_ENUMS_LANGUAGES once at workflow start
2. Store results in memory or local cache
3. Validate user inputs against cached values
4. Refresh cache only when starting a new session
由于语言和时区列表是静态的：
1. 在工作流启动时调用一次MAKE_LIST_ENUMS_LANGUAGES
2. 将结果存储在内存或本地缓存中
3. 对照缓存值验证用户输入
4. 仅在启动新会话时刷新缓存

Operations Analysis Workflow

操作分析工作流

For scenario health monitoring:
1. Call MAKE_GET_OPERATIONS with recent date range
2. Group operations by scenario ID
3. Calculate success/failure ratios per scenario
4. Identify scenarios with high error rates
5. Report findings to user or notification channel
用于场景健康监控：
1. 调用MAKE_GET_OPERATIONS并传入近期日期范围
2. 按场景ID对操作进行分组
3. 计算每个场景的成功/失败比率
4. 识别错误率高的场景
5. 将结果报告给用户或通知渠道

Integration with Other Toolkits

与其他工具包集成

Make workflows often connect to other apps. Compose multi-tool workflows:
1. Call RUBE_SEARCH_TOOLS to find tools for the target app
2. Connect required toolkits via RUBE_MANAGE_CONNECTIONS
3. Use Make operations data to understand workflow execution patterns
4. Execute equivalent workflows directly via individual app toolkits
Make工作流通常会连接到其他应用。构建多工具工作流：
1. 调用RUBE_SEARCH_TOOLS查找目标应用的工具
2. 通过RUBE_MANAGE_CONNECTIONS连接所需的工具包
3. 使用Make操作数据了解工作流执行模式
4. 通过单个应用工具包直接执行等效的工作流

Known Pitfalls

已知注意事项

Limited Toolkit:
  • The Make toolkit in Composio currently has limited tools (operations, languages, timezones)
  • For full scenario management (creating, editing, running scenarios), consider using Make's native API
  • Always call RUBE_SEARCH_TOOLS to check for newly available tools
  • The toolkit may be expanded over time; re-check periodically
Operations Data:
  • Operation records may have significant volume for active accounts
  • Always filter by date range to avoid fetching excessive data
  • Operation counts relate to Make's pricing tiers and quota usage
  • Failed operations should be investigated; they may indicate scenario configuration issues
Response Parsing:
  • Response data may be nested under 
    data
    key
  • Enum lists return arrays of objects with code and label fields
  • Operations data includes nested metadata about scenario execution
  • Parse defensively with fallbacks for optional fields
Rate Limits:
  • Make API has rate limits per API token
  • Avoid rapid repeated calls to the same endpoint
  • Cache enum results (languages, timezones) as they rarely change
  • Operations queries should use targeted date ranges
Authentication:
  • Make API uses token-based authentication
  • Tokens may have different permission scopes
  • Some operations data may be restricted based on token scope
  • Check that the authenticated user has access to the target organization
工具包功能有限:
  • Composio中的Make工具包目前功能有限（仅支持操作、语言、时区相关工具）
  • 如需完整的场景管理（创建、编辑、运行场景），请考虑使用Make的原生API
  • 请始终调用RUBE_SEARCH_TOOLS检查是否有新工具可用
  • 该工具包可能会逐步扩展；请定期重新检查
操作数据:
  • 对于活跃账户，操作记录的数量可能很大
  • 请始终按日期范围筛选，避免获取过多数据
  • 操作数量与Make的定价层级和配额使用情况相关
  • 应调查失败的操作；它们可能表明场景配置存在问题
响应解析:
  • 响应数据可能嵌套在
    data
    键下
  • 枚举列表返回包含code和label字段的对象数组
  • 操作数据包含有关场景执行的嵌套元数据
  • 解析时应带有防御性，为可选字段设置回退方案
速率限制:
  • Make API对每个API令牌有速率限制
  • 避免快速重复调用同一端点
  • 缓存枚举结果（语言、时区），因为它们极少变更
  • 操作查询应使用针对性的日期范围
认证:
  • Make API使用基于令牌的认证
  • 令牌可能具有不同的权限范围
  • 某些操作数据可能会根据令牌范围受到限制
  • 请检查已认证用户是否有权访问目标组织

Quick Reference

快速参考

TaskTool SlugKey Params
Get operationsMAKE_GET_OPERATIONS(check schema for filters)
List languagesMAKE_LIST_ENUMS_LANGUAGES(none)
List timezonesMAKE_LIST_ENUMS_TIMEZONES(none)
任务工具标识关键参数
获取操作数据MAKE_GET_OPERATIONS(查看架构获取筛选条件)
列出语言MAKE_LIST_ENUMS_LANGUAGES(无)
列出时区MAKE_LIST_ENUMS_TIMEZONES(无)

Additional Notes

补充说明

Alternative Approaches

替代方案

Since the Make toolkit has limited tools, consider these alternatives for common Make use cases:
Make Use CaseAlternative Approach
Trigger a scenarioUse Make's native webhook or API endpoint directly
Create a scenarioUse Make's scenario management API directly
Schedule executionUse RUBE_MANAGE_RECIPE_SCHEDULE with composed workflows
Multi-app workflowCompose individual toolkit tools via RUBE_MULTI_EXECUTE_TOOL
Data transformationUse RUBE_REMOTE_WORKBENCH for complex processing
由于Make工具包功能有限，针对常见的Make使用场景，可考虑以下替代方案：
Make使用场景替代方案
触发场景直接使用Make的原生Webhook或API端点
创建场景直接使用Make的场景管理API
调度执行使用RUBE_MANAGE_RECIPE_SCHEDULE构建组合工作流
多应用工作流通过RUBE_MULTI_EXECUTE_TOOL组合单个工具包工具
数据转换使用RUBE_REMOTE_WORKBENCH进行复杂处理

Composing Equivalent Workflows

构建等效工作流

Instead of relying solely on Make's toolkit, build equivalent automation directly:
  1. Identify the apps involved in your Make scenario
  2. Search for each app's tools via RUBE_SEARCH_TOOLS
  3. Connect all required toolkits
  4. Build the workflow step-by-step using individual app tools
  5. Save as a recipe via RUBE_CREATE_UPDATE_RECIPE for reuse
Powered by Composio
无需仅依赖Make的工具包，直接构建等效的自动化流程：
  1. 确定Make场景中涉及的应用
  2. 通过RUBE_SEARCH_TOOLS搜索每个应用的工具
  3. 连接所有所需的工具包
  4. 使用单个应用工具逐步构建工作流
  5. 通过RUBE_CREATE_UPDATE_RECIPE将工作流保存为可复用的模板
由 Composio 提供支持