- Inbound — the Integration API. Third-party tools and your own code can create transactions and expenses in AI2Fin through an authenticated, scoped REST API.
- Outbound — webhooks. AI2Fin notifies your other tools (Zapier, Make, n8n, or any HTTPS endpoint) the moment a transaction is categorised, an expense is created, or a receipt is processed.
Open Automations
Create and manage your webhook automations in the AI2Fin dashboard.
Your privacy is built in. Only your manually created, CSV-imported, API-created and receipt data is ever sent to an outbound webhook. Data synced from connected bank feeds is never included in webhook payloads. The same principle applies across every outbound surface: the Integration API is write-only (no endpoint returns transaction data), and MCP tool responses exclude bank-feed data by default.
Automations (no code)
The fastest way to connect AI2Fin to Zapier or Make is a webhook automation.1
Get a webhook URL from your automation tool
In Zapier, create a Zap with the Webhooks by Zapier → Catch Hook trigger and copy the custom webhook URL. Make (Integromat) offers the same via a Custom webhook module.
2
Create the automation in AI2Fin
Open Automations, choose New automation, paste the URL, pick the events you want, and acknowledge the consent notice. AI2Fin shows your signing secret once — save it in your receiver.
3
Send a test
Use Send test on the automation to push a sample delivery, then confirm your Zap/Make scenario received it.
4
Let it run
From now on, matching activity is delivered automatically. Pause, resume, rotate the secret, or inspect the delivery log any time.
Webhook events
Payload shape
Every delivery is JSON with a stable envelope. Fields are minimised by default — only the fields below are sent unless you opt into more (e.g.description) when creating the automation.
source reflects where the record came from. On transaction.categorized deliveries it is manual, csv_import, or api; expense.created deliveries report manual; receipt.processed deliveries report receipt.
Verifying signatures
Each request carries an HMAC signature so your receiver can confirm it genuinely came from AI2Fin and was not tampered with.Delivery, retries & reliability
- Retries use exponential backoff (30s → 2m → 10m → 1h → 6h) before a delivery is marked dead.
- An automation that fails repeatedly is auto-paused and shown in your delivery log so you can fix the receiver and resume.
- Rotate your secret at any time; the previous secret keeps validating for 24 hours so you can roll it without dropped events.
- Deliveries are HTTPS-only and time-bounded; redirects are not followed.
Integration API (inbound)
Create transactions and expenses in AI2Fin from your own code or an automation tool.The Integration API lives at
https://api.ai2fin.com/api/integrations/v1 and is authenticated with an OAuth bearer token carrying the right scope. See MCP authentication for how AI2Fin issues OAuth tokens.Create a transaction
Create an expense
Idempotency
Send an
Idempotency-Key header (any stable string, ≤128 chars) on writes. Retrying with the same key never creates a duplicate — you get the original result back. Keys are scoped per user and expire after 24 hours.429 response, honour Retry-After and back off.
Xero, QuickBooks & other apps
AI2Fin does not need a native connector for every tool. Once your automation platform is receiving AI2Fin webhooks, its own app catalogue does the rest — for example, a Zapier Zap can take atransaction.categorized event and create a matching bill or expense in Xero or QuickBooks. No fund movement is involved; these flows move data and accounting entries only.
What’s coming
Native Zapier & Make apps
Branded triggers and actions in the Zapier and Make directories, so you won’t need the generic webhook step. In progress.
More events
Additional event types as the platform grows. Your existing automations keep working unchanged.
Related
CSV & PDF import
Bring in historical data and statements.
MCP server
Ask ChatGPT, Claude or Cursor about your real finances.
