One key per workflow
Give each workflow its own API key with the read or write preset. Figa shows a key once; rotate it in workspace settings if it leaks.
Integrationsn8n
Your bill workflow,built in n8n.
Use the HTTP Request node and a Figa API key to keep recurring bills current: invoices confirmed, payments recorded, briefings sent. Run it on n8n cloud or your own server.
- HTTP Request node
- Header auth with x-api-key
- Cloud or self-hosted
Email trigger
Invoice from City Energy
city-energy-november.pdf
Extract From File + your parser
Reads the amount and billing period
€97 · Oct 12 – Nov 11
HTTP Request
Finds the matching bill
GET /api/v1/expenses/:id/bill
Figa
Electricity confirmed at €97
PUT /api/v1/expenses/:id/bill · estimate €94
Illustrative workflow. Endpoints are real Figa API endpoints.
Try it
Three workflows worth building.
Each one runs on its own once you trust it, and reports back where you already read messages.
Schedule Trigger
Every Monday at 8:00
A read-only key is enough
HTTP Request
Asks Figa for the month
GET /api/v1/insights/summary
Your team chat
“November: €2,364 planned”
Largest category: Housing, €1,250
Schedule Trigger
Every day at 7:00
Checks the current month
HTTP Request
Looks for unusually large expenses
GET /api/v1/insights/anomalies
Your team chat
“Water is far above its usual amount”
Water · €78 · usually about €35
Trigger
Your bank confirms a transfer
Rent · €1,250 · sent Nov 1
HTTP Request
Marks the matching bill paid
PUT /api/v1/expenses/:id/payment-status
Figa
Rent marked paid
No money moves: only the status changes
Illustrative workflow. Endpoints are real Figa API endpoints.
Setup
Connect in three steps.
n8n calls the Figa REST API with a workspace API key, sent as a header.
https://api.figa.cc - 1 Create an API key In Figa workspace settings under API & MCP, create a key: the read preset for briefings, the write preset for changes. Only owners and admins can.
- 2 Add a credential In n8n, create a header auth credential named x-api-key with your key. Test it with GET /api/v1/categories in an HTTP Request node.
- 3 Match, then write Match each event to the right bill before writing. Add a review step for unclear matches, then let the workflow run.
Details can change between versions. Source: n8n: HTTP Request node.
You stay in control
Access you decide.
No duplicates on retry
Reuse the same Idempotency-Key when a step retries. It covers 24 hours, so keep your own log of handled invoices for longer.
Paid means paid
Mark a bill paid only when the source confirms the payment. Figa records the status and never moves money.
Free to start on both sides.
n8n Community edition is free to self-host. Figa Free includes one API or MCP connection and 20 expenses a month. Pro includes 10 connections per workspace.
Keep reading
n8n and your bills
How to automate recurring bills with n8n
Bills are a good fit for n8n: the same few steps every month, with a decision in the middle that you want to control.
Why n8n fits bills
A monthly invoice needs more than one step: read the document, find the right bill, decide what to change, write it and check the result. n8n lets you build that as a workflow with branches, and run it on your own server if you prefer to keep invoices in house.
Figa holds the result: the confirmed amount, the billing period, the history and the payment status, next to every other bill you plan.
The invoice workflow, step by step
- Trigger: An email trigger picks up the invoice, or a schedule checks a folder.
- Extract: Extract From File pulls the text from the PDF; your parser or an AI node reads the amount, period and currency.
- Match: An HTTP Request lists the month and reads the candidate bill. A supplier name alone is not a reliable match.
- Write: Confirm the actual amount on that occurrence with PUT /api/v1/expenses/:id/bill.
- Verify: Read the bill back and store the invoice-to-bill mapping, so the next run skips it.
The PDF stays in n8n
Figa’s API does not accept PDF attachments or read your inbox. Reading the document, and deciding how long to keep it, belongs to your workflow. Figa receives only the structured result.
Retries without duplicates
Send a UUID Idempotency-Key with each write and reuse it when n8n retries the same operation. On a 429 response, wait for the time in Retry-After. If a write may or may not have landed, read the bill before sending another one.
The retry key covers 24 hours. For invoices, keep your own ledger of handled source IDs for longer.
From automation to insight
Once bills stay current, the Insights endpoints have real data to work with: a monthly summary, period comparisons, trends, forecasts and unusually large expenses. A scheduled workflow can send them wherever your household or team already reads messages.
Questions about Figa and n8n
Anything else is in Help, or one email away.
n8n setup in Help →Invoice workflow →Insights API → [email protected]
Is there an n8n node for Figa?
No dedicated node. Use the HTTP Request node with a header auth credential that sends your Figa API key as x-api-key.
Can Figa start an n8n workflow?
Not directly: Figa does not send webhooks. Start the workflow from an email or file trigger, or run it on a schedule.
Does Figa read the PDF?
No. n8n reads the document and sends Figa the amount, period and currency. Figa does not ingest attachments or watch an inbox.
What happens when I hit a rate limit?
Figa answers 429 with a Retry-After header. Wait that long, then retry with the same Idempotency-Key.
Can n8n pay my bills?
No. Marking a bill paid only records the payment. Figa never moves money.
Add your bills.
Know your month.
Start with rent. Every bill you add sharpens the months ahead.
Free plan · No card · No bank connection