Zapier Integration

Use Webhooks by Zapier for an HTTP workflow with the Figa REST API. API keys share the plan’s integration slots with MCP connections.

1. Generate API key in Figa workspace settings.
2. Create Zap trigger (for example: new invoice in your source app).
3. Read context and match the invoice first. For a new record, POST to https://api.figa.cc/api/v1/expenses.
4. Pass x-api-key and a saved UUID Idempotency-Key for this create; map amount as integer minor units and include currency.
5. Test and publish Zap with error handling branch.

For an existing recurring bill, follow the invoice matching and confirmation recipe instead of creating a duplicate. Keep a durable source-event ledger beyond the 24-hour retry window. Only mark Paid when the source confirms the expense was paid.

Headers for a new expense

x-api-key: et_...
Content-Type: application/json
Idempotency-Key: <saved UUID for this operation>