360 Secure SkillHub
360 安全技能中心

ActiveCampaign

该 Skill 通过 oo CLI 调用 OOMOL 托管的 ActiveCampaign 连接器：查询当前用户、联系人、自定义字段与邮件列表，并通过联系人同步接口创建或更新联系人。运行时先用 schema 命令获取动作输入输出结构，再以 JSON 载荷执行动作；写入类操作需先与用户确认。

oomol
oomol
热度 52.34
最近更新 2026-09-15 12:18:37
分类：营销依赖：代码执行 / 第三方 API应用场景：CRM / API 集成

安装技能

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

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

ActiveCampaign

Operate ActiveCampaign through your OOMOL-connected account. This skill calls the activecampaign 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 ActiveCampaign. 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 "activecampaign" --action "<action_name>"

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

oo connector run "activecampaign" --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

  • get_contact — Get one ActiveCampaign contact by identifier.
  • get_current_user — Get the current ActiveCampaign user associated with the API token.
  • list_contacts — List ActiveCampaign contacts with pagination, search, and filtering support.
  • list_fields — List ActiveCampaign custom contact fields.
  • list_lists — List ActiveCampaign mailing lists with pagination and optional name filtering.
  • upsert_contact — Create or update an ActiveCampaign contact using the official contact sync endpoint. [write]

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change ActiveCampaign 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 — ActiveCampaign 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=activecampaign

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

Resources