Review before it writes
Set the agent’s approval policy before any unattended writes. The skills tell it to show matches and amounts first.
IntegrationsOpenClaw
Install the Figa agent skills and connect OpenClaw by MCP or the REST API. Five workflows teach it how Figa works: reading, writing, organizing, recurring bills and automations.
Two invoices match bills in November:
Confirm both? Payment status stays as it is.
Both confirmed. Electricity and water are still unpaid.
Illustrative conversation. Tool names are real Figa MCP tools.
Try it
Each one maps to a Figa skill, so the agent follows the same careful steps every time.
€954 is still unpaid in November:
The estimate is electricity, until its invoice arrives.
Gas uses the last confirmed amount today. Seasonal would compare December with the same period in earlier years and put it at about €142.
Switch to seasonal?
Done. Future gas estimates follow seasonal history. Confirmed amounts stay as they are.
I can run that as a daily task: read the new invoices, match each one to a bill and send you the proposed amounts. Nothing is saved until you approve, and I keep a list of handled invoices so none is saved twice.
Illustrative conversation. Tool names are real Figa MCP tools.
Setup
Install the skills, then give OpenClaw a connection to Figa.
cp -R figa-agent-skills/figa-* ./skills/ Details can change between versions. Source: OpenClaw: skills.
You stay in control
Set the agent’s approval policy before any unattended writes. The skills tell it to show matches and amounts first.
MCP reaches the workspaces you choose, read only or read and write. A REST key is limited to its workspace and preset.
Figa never moves money and has no bank connection. Recording a payment only updates the status.
Works on Figa Free.
The skills are a free download. Figa Free includes one MCP or API connection and 20 expenses a month. Pro includes 10 connections per workspace.
Keep reading
Agents and your bills
A connection gives an agent tools. A skill gives it a method: which tool to use, in what order, and what to check before it writes.
Connected to Figa, an agent can list expenses, confirm a bill or end a series. Whether it does those things well depends on what it knows: that an invoice belongs on the existing bill, that an estimate is not a confirmed amount, that a retry must reuse the same request ID.
The Figa agent skills write that knowledge down as standard SKILL.md instructions, with references and optional helpers, so the agent follows the same steps every time.
If your OpenClaw setup supports remote MCP with OAuth, add the Figa MCP URL, sign in and pick the workspaces. Otherwise configure HTTP tools for the REST API with a workspace API key. MCP uses OAuth, not the key.
Only the optional Python helpers need Python 3.10 or newer, and they read their settings from your runtime’s secrets.
Start with one read and check the workspace, the dates and the currency. Then try one change you asked for and read it back. Only after that, set the approval policy for the jobs you want to run on their own, such as a daily invoice check.
The skills are not tied to OpenClaw. Hermes and other agents that load skills can use them too; check each runtime’s skill format and tool support. Without a skill loader, give the agent the instructions as task context.
Anything else is in Help, or one email away.
Agent skills →OpenClaw setup in Help →Invoice workflow → contact@getfiga.com
Five SKILL.md workflows with references and optional helpers that teach an agent how to read, write and organize Figa data safely.
No. Any agent that loads skills can use them, such as Hermes. Check your runtime’s skill format and tool support.
Only for the optional REST helpers, which need Python 3.10 or newer. The skills themselves are instructions.
No. Your agent reads the documents you give it access to. Figa stores the amounts and bill data it sends.
No. Recording a payment only updates the status. Figa never moves money.
Start with rent. Every bill you add sharpens the months ahead.
Free plan · No card · No bank connection