---
title: "n8n Integration"
description: "Integrate Figa with n8n using API keys."
canonical_url: "https://getfiga.com/help/developers/integrations/n8n/"
---

# n8n Integration

Use n8n when you need custom orchestration and branch logic between internal tools and Figa.

1.  Create an API key in Workspace settings → API & MCP (owner/admin only).
2.  In n8n, define credential as HTTP Header Auth: x-api-key = et\_...
3.  Add HTTP Request node to GET /api/v1/categories and verify connectivity.
4.  Read context, match the source event to an existing record, then create or update the intended expense.
5.  Reuse the operation UUID on supported retries. Inspect 403/409 codes; wait on Retry-After for 429, and resolve uncertain writes before a new operation.

Use `https://api.figa.cc` as the API origin. Configure UUID `Idempotency-Key` for POST mutations and supported bill PUTs; keep a durable source-event ledger. API keys share integration slots with MCP connections.

For monthly invoices, [match and confirm the existing recurring bill](https://getfiga.com/help/developers/invoice-workflow). PDF extraction and the event trigger belong to your n8n workflow. Use the create below only for a genuinely new record.

## Minimal create payload

```
{
  "name": "Invoice #481",
  "amount": 129900,
  "categoryInput": "Software",
  "recipientInput": "Acme Corp",
  "expenseDate": 1739577600
}
```

**Choose access and approval**

Start with a read request. Configure review for ambiguous matches before unattended writes. Saving an amount alone preserves status; marking Paid does not transfer money.