360 Secure SkillHub
360 安全技能中心

Make

封装 OOMOL 的 make 连接器，通过 oo 命令行以 JSON 载荷执行 Make 动作：查询当前用户与授权、列出团队和场景、查看场景详情及近 30 天用量，并激活、停用或单次运行场景。凭据由 OOMOL 服务端注入；写和破坏性动作需先与用户确认。

oomol
oomol
热度 45.69
最近更新 2026-09-20 11:41:10
分类：自动化依赖：代码执行 / 第三方 API应用场景：工作流 / 自动化脚本

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add oo-make
Metadata
name
oo-make
description
Make (make.com). Use this skill for ANY Make request — reading, creating, updating, and deleting data. Whenever a task involves Make, use this skill instead of calling the API directly.
allowed-tools
["Bash(oo *)"]
metadata
{"title":"Make","author":"OOMOL","version":"1.0.3","services":["make"],"icon":"https://static.oomol.com/logo/third-party/make.png"}

Make

Operate Make through your OOMOL-connected account. This skill calls the make connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Make. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "make" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "make" --action "<action_name>" --data '<json>' --json
  • --data takes a JSON object string or @path/to/file.json; omit it to send {}.
  • The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

  • activate_scenario — Activate a Make scenario. [write]
  • deactivate_scenario — Deactivate a Make scenario. [destructive]
  • get_current_authorization — Get the current Make credential authorization details and scopes.
  • get_current_user — Get the authenticated Make user profile.
  • get_scenario — Get details for one Make scenario.
  • get_scenario_usage — Get daily usage for a Make scenario over the previous 30 days.
  • list_scenarios — List Make scenarios for one team or organization.
  • list_teams — List Make teams visible to the authenticated credential.
  • run_scenario_once — Run a Make scenario once on demand. [write]

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change Make state — confirm the exact payload and effect with the user before running.
  • Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux

    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login

  • scope_missing / credential_expired / app_not_ready / app_not_found — Make is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

    https://console.oomol.com/app-connections?provider=make

  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources