Zapier and Make
Connect Trabalance to thousands of apps with one key — no code on either side.
Trabalance publishes an app for Zapier and one for Make. Neither is a separate integration: both run on the public API, with the same triggers, the same actions and the same guarantees you would get writing the calls yourself.
What they share
Settings → API keys & webhooks → New key. Grant the scopes your automation needs, and tick Allow webhook subscriptions so the app can manage its own listeners.
Turning an automation on creates an endpoint you can see under Settings → Webhooks, with its own delivery log. Turning it off removes it. Nothing polls.
An invoice created from an automation 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.
Both apps send an Idempotency-Key, so a platform retry replays the original response instead of creating a second document.
| Zapier | Make | |
|---|---|---|
| Triggers | Nine, one per event — each its own trigger | One instant trigger, with the event picked from a dropdown |
| Actions | Create customer · Create vendor · Create invoice · Record money received · Push statement lines | Create a customer · Create an invoice · Record money received |
| Searches | Find customer · Find vendor · Find item | Search customers |
| Connection test | `GET /customers?page_size=1` | `GET /customers?page_size=1` |
Every write wants a customer id and item ids. Put a find or search step in front of it — matching a party or an item on its name is how duplicates get created. Item identity is SKU or barcode.
Any other platform
Nothing here is special to these two. Any tool that can hold a bearer token and receive a POST can do the same thing: mint a key with the Webhooks option, call POST /api/v1/webhooks/endpoints with your listener URL, and call the resources directly.