Zapier
Triggers on your books' events and actions that create through the same producers the app uses.
The Trabalance Zapier app runs entirely on the public API: one key, REST-hook triggers the app subscribes for you, and actions that are each exactly one POST to a verified resource.
Connecting
Settings → API keys & webhooks → New key. Grant the scopes your Zaps need — customers, invoices, receipts, items, bank feeds — and tick Allow webhook subscriptions so triggers can listen. See Mint an API key.
The connection test lists one customer (GET /customers?page_size=1). A wrong or under-scoped key fails with the API's own message, so you find out at connect time rather than mid-Zap.
Triggers
Each trigger is a REST hook: turning the Zap on creates an endpoint under Settings → Webhooks; turning it off removes it.
| Trigger | Event |
|---|---|
| New Invoice | `invoice.created` |
| Invoice Paid | `invoice.paid` |
| Money Received | `receipt.created` |
| New Bill | `bill.created` |
| Bill Paid | `bill.paid` |
| Money Paid | `payment.created` |
| New Customer | `customer.created` |
| New Vendor | `vendor.created` |
| Statement Lines Arrived | `bank_feed.received` |
The event id is the deduplication key, not the document id — a single invoice fires several events over its life, and each one is a distinct thing that happened. The document id is still on the record, as document_id.
Actions and searches
| Kind | What it does |
|---|---|
| Create Customer / Create Vendor | Adds a party. Name required. |
| Create Invoice | Posts a sales invoice — customer id, date, and line items with item id, qty and rate. |
| Record Money Received | A customer receipt against open invoices — customer id, date, bank/cash account id, and the allocations. |
| Push Statement Lines | Sends one statement line to a bank account's reconciliation worklist. |
| Find Customer / Find Vendor / Find Item | Turns a name or email into the id an action needs. |
Actions carry an Idempotency-Key, so a Zapier retry does not create a second invoice.
Create Invoice wants a customer id and item ids. Put a Find Customer and a Find Item step in front of it — matching on a name is exactly the mistake that creates a duplicate party. Item identity is SKU or barcode, never the name.
An invoice created from a Zap is numbered, journalled and put through the same approval thresholds as one keyed by hand. A receipt is applied by settlement order. A bank line is deduplicated against what is already on the account.
Related
- Make — the same capabilities, as a Make app
- Subscribe an endpoint — the endpoints Zapier calls on your behalf
- Mint an API key