Zapier automation for the tools you already use
Belvak works with Zapier today. Start a Zap from a Belvak event with a Catch Hook, and read or write your data from Zapier with an API key. No code on either side. Available on the Professional plan.
33
Belvak events that can start a Zap
2
Zapier steps you use: Catch Hook and API by Zapier
0
lines of code, on either side
11
record types you can read and write from a Zap
Capabilities
Two building blocks, and you are automated
There is no directory app to install. You use Zapier's own Webhooks and API steps, pointed at a Belvak webhook and an API key, so events flow out and a Zap can read and write back.
Start with an API key and a webhook
In Settings, open Integrations and create an API key, then register a webhook. Zapier connects to both: the webhook sends Belvak events out, and the key lets a Zap read and write your data. No native directory app to install, just Zapier's own building blocks.
Triggers: start a Zap from a Belvak event
Add a Webhooks by Zapier trigger, choose Catch Hook, and paste its URL into a Belvak webhook. Pick the events you care about or send them all. Every matching event posts to the Catch Hook and runs your Zap, signed so Zapier can trust it.
Actions and lookups: read and write Belvak
Use an API by Zapier request to call the Belvak API. Save your API key once as an Authorization header, then create a client, raise an invoice, record a payment, or look a record up by its public id, all from inside a Zap.
On the Professional plan
API keys and webhooks are a Professional plan feature in Belvak, set up by an admin. On Zapier's side, the Webhooks by Zapier and API by Zapier steps are part of Zapier's own paid plans.
A closer look
Events out, reads and writes back
The webhook is how Belvak tells Zapier something happened. The API key is how a Zap reaches back into Belvak. Together they cover both directions, without a line of code.
Triggers
Belvak events, straight into Zapier
Add a Webhooks by Zapier trigger, choose Catch Hook, and Zapier gives you a URL. Register that URL as a Belvak webhook and pick the events that should start the Zap. From then on, every matching event runs your workflow, and each delivery is signed so Zapier only acts on genuine Belvak events.
- Add a Webhooks by Zapier trigger and choose Catch Hook
- Copy the Catch Hook URL into a Belvak webhook, from Settings or the API
- Choose which events fire the Zap, or send them all
- Belvak signs every delivery, so your Zap only acts on real Belvak events
Actions and lookups
Read and write Belvak from a Zap
Use an API by Zapier request to call the Belvak API. Save your API key once as an Authorization header and the Zap can create a client, raise an invoice, record a payment, or look a record up by its public id. Storing the key as a header keeps it out of view for anyone else editing the Zap.
- Use API by Zapier to call the Belvak API for reads and writes
- Save your API key once as an Authorization header, so collaborators on the Zap cannot read it
- Create a client, raise an invoice, or look one up by its public id
- Custom Request works too, but anyone who can edit the Zap sees the credentials you type into it
How it works
Four steps from key to running Zap
01
Create an API key
In Settings, open Integrations and add an API key under API & Webhooks. One time, admin only, on the Professional plan.
02
Add a Catch Hook trigger
In Zapier, start a Zap with Webhooks by Zapier, choose Catch Hook, and register its URL as a Belvak webhook.
03
Add an API by Zapier action
Save your API key as an Authorization header, then call the Belvak endpoint you need to read or write data.
04
Turn the Zap on
Belvak sends every matching event to Zapier and answers every request, so your workflow runs on its own.
FAQ
Common questions about connecting Zapier
Is there a Belvak app in the Zapier directory?
Not yet. Today you connect Belvak to Zapier with Zapier's own building blocks: Webhooks by Zapier for triggers and API by Zapier for actions and lookups. A native Zapier app is on our roadmap, and these public docs are a step toward it. Nothing here depends on a directory listing.
Which plan do I need?
API keys and webhooks are a Professional plan feature in Belvak, and an admin sets them up. On Zapier's side, the Webhooks by Zapier and API by Zapier steps are part of Zapier's paid plans, so you need a Zapier plan that includes them.
How does Zapier trigger on a Belvak event?
Add a Webhooks by Zapier trigger, choose Catch Hook, and register its URL as a Belvak webhook. Pick the events that should fire the Zap. When one happens, Belvak posts to the Catch Hook and your Zap runs, with the event name and a link back to the record.
Can a Zap create or update records in Belvak?
Yes. Use an API by Zapier request with your API key in the Authorization header to create a client, raise an invoice, record a payment, and more. Reads work the same way, so a Zap can also look a record up by its public id before acting.
Is it safe to put my API key in Zapier?
Save it as a stored Authorization header in the API by Zapier step, where collaborators on the Zap cannot read it. Avoid typing it into a Custom Request, since anyone who can edit that Zap can see it. You can rotate or revoke a key from Settings at any time, and the change takes effect immediately.
What can I read and write?
The Belvak API covers clients, projects, invoices, payments, proposals, suppliers, purchases, employees, maintenance contracts, referrals, and notes. Time entries, users, and roles are not part of the API yet. See the developer reference for the full list of fields and events.
Keep exploring
Built on the Belvak API and webhooks
Zapier is one way to use the platform. The same API keys and webhooks power Make, n8n, Pipedream, and your own systems, all documented in the developer reference.
Automate the busywork
Create an API key, register a webhook, and let Zapier move your Belvak data where it needs to go.