什么是 Organizze API Skill？

Organizze API Skill 是 Openclaw Skills 生态系统中的专用工具，专为希望通过终端管理个人财务的开发者和高级用户设计。它提供了一个健壮的基于 Node.js 的命令行界面，与官方 Organizze REST API 进行交互，实现对财务资源的完整 CRUD 操作。

通过利用此技能，用户可以以编程方式处理银行账户、支出类别、信用卡账单和复杂的转账。它弥合了手动输入与自动化财务工作流之间的差距，确保您的财务数据始终可以通过简单的 shell 命令访问和操作。

下载入口:https://github.com/openclaw/skills/tree/main/skills/leaofelipe/organizze-skill

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

Organizze API Skill 应用场景

• 通过 Openclaw Skills 获取交易，自动化每月费用报告。
• 使用 CLI 脚本批量更新或迁移交易类别。
• 以编程方式监控信用卡账单周期和付款历史。
• 通过按特定时间段的标签对交易进行分组，生成自定义财务摘要。
• 使用创建和更新端点将外部财务数据同步到 Organizze 账户中。

1. 用户通过环境变量提供身份验证凭据，以与 Organizze REST API 交互。
2. 通过针对特定财务资源（如账户或交易）的 Node.js 脚本执行命令。
3. 该技能处理请求，向 Organizze 服务器发送适当的 HTTP 方法（GET, POST, PUT, DELETE）。
4. 接收并解析 API 响应，该技能提供本地增强功能，例如基于标签的分组。
5. 最终数据以美化的 JSON 格式输出到 stdout，以便进行管道处理或终端读取。

Organizze API Skill 配置指南

要将其集成到您的 Openclaw Skills 工作流中，请确保已安装 Node.js 18+ 并按照以下步骤操作：

# Clone the repository and install dependencies
npm install

# Configure your environment variables in a .env file
ORGANIZZE_EMAIL=your_email@example.com
ORGANIZZE_TOKEN=your_api_token
ORGANIZZE_USER_AGENT=OpenclawIntegration

Organizze API Skill 数据架构与分类体系

该技能遵循严格的数据分类法，以确保与 Organizze API 的兼容性：

name: organizze
description: >-
  Runs Organizze personal finance API operations via Node.js CLI scripts:
  accounts, categories, transactions (filters, tag grouping), credit cards
  (invoices, payments), and transfers. Use when the user works with Organizze,
  budgets, expenses, income, categories, bank accounts, credit card bills,
  transfers, or asks to query or change their Organizze data through the terminal.
credentials:
  - name: ORGANIZZE_TOKEN
    description: API token for authenticating with the Organizze REST API (used as HTTP Basic Auth password)
    required: true
env:
  - name: ORGANIZZE_EMAIL
    description: Email address associated with the Organizze account (used as HTTP Basic Auth username)
    required: true
  - name: ORGANIZZE_TOKEN
    description: API token for authenticating with the Organizze REST API
    required: true
  - name: ORGANIZZE_USER_AGENT
    description: Short string identifying the integration, required by the Organizze API
    required: true

Organizze API (CLI scripts)

Use the organizze-skill repository to read and write Organizze personal finance data through the official REST API. JSON is printed to stdout; errors go to stderr and the process exits non-zero on failure.

Working directory

Before every node command, set the shell working directory to the repository root — the directory that contains package.json.

Prerequisites

• Node.js 18 or newer
• From the repository root: npm install
• A .env file (copy from .env.example) with:
  • ORGANIZZE_EMAIL
  • ORGANIZZE_TOKEN
  • ORGANIZZE_USER_AGENT (required by the API; any short string identifying your integration)

Do not print or log credential values. Mask PII when summarizing API output for the user.

How to run

node src/routes/.js  [args]

is one of: accounts, categories, transactions, credit-cards, transfers.

Run a script with no arguments to see its full usage on stderr.

Output: pretty-printed JSON on stdout. Errors: message on stderr, exit 1.

Conventions

• amount_cents: integer cents. R$ 50.00 = 5000. Expenses are negative.
• Dates: YYYY-MM-DD.
• JSON arguments: pass as a single quoted shell argument.
• transactions list --group-by-tag: local grouping after the API response (not a native API feature). Returns [{ tag, total_cents, transactions }]. Transactions with multiple tags appear in each group; untagged ones go into "untagged".
• transfers list: returns two entries per transfer (debit and credit sides), not one merged object.

For field names and payloads not listed here, see: https://github.com/organizze/api-doc

accounts

node src/routes/accounts.js list
node src/routes/accounts.js get 12345

categories

delete accepts optional JSON with replacement_id to migrate existing references before removal.

node src/routes/categories.js list
node src/routes/categories.js delete 42 '{"replacement_id":18}'

transactions

delete accepts optional JSON for recurring/installment behavior: '{"update_future":true}' or '{"update_all":true}'.

node src/routes/transactions.js list --start-date=2025-04-01 --end-date=2025-04-30
node src/routes/transactions.js list --account-id=1 --group-by-tag
node src/routes/transactions.js delete 888 '{"update_future":true}'

credit-cards

node src/routes/credit-cards.js list
node src/routes/credit-cards.js list-invoices 3 --start-date=2025-01-01 --end-date=2025-12-31
node src/routes/credit-cards.js get-payments 3 1001

transfers

Typical create fields: credit_account_id, debit_account_id, amount_cents, date, paid. Confirm exact shape via the API doc or by inspecting existing transfers.

node src/routes/transfers.js list --start-date=2025-04-01 --end-date=2025-04-30
node src/routes/transfers.js get 55

End-to-end workflows

Balances

node src/routes/accounts.js list

Transactions for a period, filtered by account

# 1. get account id
node src/routes/accounts.js list

# 2. list transactions
node src/routes/transactions.js list --start-date=2025-04-01 --end-date=2025-04-30 --account-id=1

Create an expense

node src/routes/transactions.js create r
  '{"description":"Coffee","amount_cents":-1500,"date":"2025-04-03","category_id":10,"account_id":1}'

Use negative amount_cents. Get category_id and account_id from prior list calls. Adjust fields to match the API.

Spending by tag

node src/routes/transactions.js list --start-date=2025-04-01 --end-date=2025-04-30 --group-by-tag

Each group in the result has tag and total_cents.