Bills from Zapier,planned in Figa.

Zapier and your bills

How to automate bills with Zapier and Figa

Zapier is good at noticing things: a new row, an email, a form. Figa is where those things become a plan for the months ahead.

Who does what

Zapier watches your other apps and runs a step when something happens. Figa keeps your recurring bills, estimates and payments. A Zap connects the two by calling the Figa REST API.

Figa does not send webhooks of its own, so a Zap always starts somewhere else: an event in another app, or a schedule. For reports, a scheduled Zap that reads from Figa is the usual pattern.

Start with a read

Before any change, check the key with a simple read: list your categories or read the workspace context. It confirms the key, the workspace and the currency in one step, and costs nothing if something is wrong.

New expense or existing bill?

A monthly invoice usually belongs to a bill that already exists in Figa. Find that occurrence and confirm the actual amount on it, so the estimate becomes the real number and the history stays in one place. Create a new expense only when nothing matches.

• New expense: POST /api/v1/expenses with name, amount, currency and date.
• Invoice for a known bill: Read GET /api/v1/expenses/:id/bill, then confirm with PUT on the same path.
• Payment: PUT /api/v1/expenses/:id/payment-status, only when the source confirms it.

Amounts, keys and retries

Amounts are integer cents: €42.50 is 4250, not 42.50. Always send the currency with the amount.

Zapier can retry a step. Send a UUID Idempotency-Key with each write and reuse it on the retry, so Figa saves the change once. The key covers 24 hours; for invoices, keep a list of the ones you already handled, for example in a sheet, so a late duplicate is skipped.

Keep a person in the loop

Start with a review step for anything ambiguous: two bills from the same supplier, an unusual amount, a missing period. Once the matches are reliable, let the Zap run on its own for the suppliers you trust.