OpenClaw Integration

OpenClaw works best when your tool schema mirrors Figa API constraints and validates user intent before execution.

1. 1

   Create dedicated workspace API key using read/write preset (use write for mutations and payments).

2. 2

   Configure OpenClaw tool endpoint to call Figa API with x-api-key header.

3. 3

   Expose read operations first (categories, recipients, expenses, insights, notifications).

4. 4

   Enable write operations: create, update, delete expenses + manage payments.

5. 5

   Add skill-level guardrails for amount format, required fields, and Idempotency-Key on POST mutations.

6. 6

   Use context endpoint to check workspace plan limits before write operations.

Recommended skill blocks

• Category resolver: map natural language labels to categoryInput.
• Amount validator: convert user money format to integer cents.
• Date normalizer: produce Unix timestamp for expenseDate.
• Expense lifecycle: create → update → pay → delete through chat commands.
• Insights reporter: fetch spending summaries, comparisons, trends, and forecasts.
• Idempotency handler: generate deterministic Idempotency-Key from source IDs for retry safety.

Available operations

OpenClaw skills can leverage the full Figa API surface:

• Read: categories, recipients, expenses (by month), expense detail, history, payments, monthly totals, recurring templates.
• Write: create/update/delete expenses, bulk actions (markAsPaid), manage categories & recipients.
• Payments: add/remove payments on expenses.
• Insights: spending summary, period comparison, trends, anomalies, forecast.
• Context: workspace metadata, plan tier, limits, notifications.

See the Developer API page for the full endpoint reference and permission model.