Integration · Business plan

Zapier triggers and actions, built on the public API

The Claver Zapier app ships five triggers and two actions, riding the same public REST API you can call yourself. Pair it with signed outbound webhooks when you want events pushed the moment they happen. All of it is included on Business at $79/mo, with no connector fee.

Start for $1 → See all features

$1 for 14 days, then $19/mo. Card required. Cancel any time.

Zapier triggers, actions, and webhook events

What the Zapier app can watch for and what it can create, plus the events Claver can push straight to an endpoint you own.

Name	Type	What it does
New Customer	Trigger	Fires when a customer is added in Claver
New Job	Trigger	Fires when a job is created
Job Completed	Trigger	Fires when a job is marked complete
Quote Approved	Trigger	Fires when a customer approves a quote
Invoice Paid	Trigger	Fires when an invoice is paid in full
Create Customer	Action	Creates a customer record. Needs an API key with the write scope
Create Job	Action	Creates a job for an existing customer. Needs an API key with the write scope
Outbound webhooks	Push	job.created, job.updated, job.completed, customer.created, quote.approved, and invoice.paid, each signed with HMAC-SHA256

Triggers poll the REST API and deduplicate by record id. Webhooks push instead of polling, and retry on a backoff for up to five attempts.

How to connect Zapier

Zapier authenticates with a Claver API key that you mint yourself. Keys are shown once, scoped to read or write, and can be revoked at any time. You need to be the owner or an admin on a Business plan.

Open the API and Integrations screen. It is in the app sidebar under Settings, titled API and Integrations.
Click Create key. Name it for the tool that will hold it, for example Zapier integration, so a revoked key is easy to pick out later.
Choose the scopes. Read is enough for triggers. Add write only if you want Zapier to create customers or jobs in Claver.
Copy the key once. Claver stores only a hash of it, so the full key is shown a single time. Paste it into Zapier when it asks for your Claver API Key.
Turn on webhooks if you want push instead of poll. On the same screen, add an endpoint URL, tick the events you want, and verify the signature header on your side before you trust the payload.

Rate limits and scopes

API keys carry the prefix cl_live_ and are stored only as a hash, so a leaked key can be revoked but never recovered. Each key is limited to 60 requests a minute, and Zapier backs off cleanly when it hits that ceiling. You can hold up to ten active keys at once.

The read endpoints cover customers, jobs, quotes, and invoices, with search, status and date filters, and cursor paging. The write endpoints cover creating customers and jobs. There are no delete endpoints, on purpose.

Which plan includes it

The public API, the Zapier app, and outbound webhooks are Business features, $79/mo flat for up to 20 users. The gate is enforced on the server, so a key minted on a lower plan will not authenticate. Business also includes in-app calling, the AI receptionist, job costing, campaigns, and custom role permissions. See the pricing page for the full tier list.

Directory listing status

Straight answer: the Claver Zapier app is built and registered with Zapier, and its public directory listing is still in review. The triggers, the actions, and the API behind them are live today. If you want it before the listing clears, email [email protected] and we will get you connected. If you would rather not wait on a middleman at all, the REST API and the signed webhooks are available the moment your Business plan starts.

Zapier and API FAQ

What Zapier triggers and actions does Claver have?

Five triggers and two actions. The triggers are New Customer, New Job, Job Completed, Quote Approved, and Invoice Paid. The actions are Create Customer and Create Job, both of which need an API key with the write scope. Triggers poll the Claver REST API and deduplicate by record id, so a Zap fires once per record rather than once per poll.

How does Claver authenticate with Zapier?

With a Claver API key that you mint yourself in the app, under Settings and then API and Integrations. You name the key, pick read or write scopes, and copy it once, because Claver stores only a hash of it. Zapier asks for it as your Claver API Key and sends it as a bearer token. Each key is limited to 60 requests a minute and you can hold up to ten active keys.

Which Claver plan includes Zapier and the API?

Business, at $79/mo flat for up to 20 users. The limit is enforced on the server, so an API key created on Starter or Crew will not authenticate against the public API. Business also includes in-app calling, the AI receptionist, job costing, email and SMS campaigns, and custom role permissions. There is no separate connector or API add-on fee.

Can Claver send webhooks instead of using Zapier?

Yes, and it is the faster path. On Business you can register an HTTPS endpoint and subscribe it to job.created, job.updated, job.completed, customer.created, quote.approved, and invoice.paid. Each delivery carries the event name, a delivery id, a timestamp, and an HMAC-SHA256 signature so you can verify it came from Claver. Failed deliveries retry on a backoff, and an endpoint that keeps failing is deactivated rather than hammered.

Wire Claver into the rest of your stack.

Five triggers, two actions, a REST API, and signed webhooks, all included on Business at $79/mo. Start for $1 and upgrade when you need them.