The screen states that a published Zapier app is not offered. You can still connect Zapier yourself.

• A Zapier account.
• A VisionScaper access key with Set up alerts (needed by Zapier) ticked, plus whatever you want to read or add.

1. In VisionScaper, make a key named “Zapier” (see Creating access keys and choosing scopes).
2. In a Zap, add a step with Webhooks by Zapier and choose Custom Request.
3. For a read (an action), use GET .../api/v1/customers with header Authorization: Bearer YOUR_KEY.
4. To add a lead, send a POST to .../api/v1/leads with JSON.

Use Zapier’s Visual Builder or Platform CLI.
1. For the login test, call GET zap/me.
2. For instant triggers, call POST zap/subscribe with event and target_url (Zapier’s hookUrl is accepted too). Needs the alerts scope. The reply includes the alert id and a secret.
3. When the Zap is turned off, call POST zap/unsubscribe with { "id": ... }.
4. For polling triggers and for test samples, call GET zap/poll/{event}.

The addresses to copy are on the Zapier tab: Subscribe address, Unsubscribe address, and Sample address (add the event name).

lead.created, customer.created, quote.sent, quote.accepted, job.completed, invoice.paid.

• Subscribing twice with the same event and address returns the same alert. Nothing is doubled.
• A subscription made this way is marked From Zapier in the alert list.
• zap/poll/{event} returns a plain list of the newest real records (up to 25), newest first, each with an id. If you have none yet, it returns one clearly marked sample.
• A Zapier alert switches off when Zapier answers 410.

• Add a lead: POST api/v1/leads.
• Add or update a customer: POST api/v1/customers, PATCH api/v1/customers/{id}.
• Search customers: GET api/v1/customers?email=....

• Test each trigger with the sample address before turning the Zap on.
• Alerts that are not from the instant route may arrive up to about 5 minutes late.
• Keep the Zapier key’s scopes small.

• 403 on subscribe: the key lacks the alerts scope.
• 422 invalid_event: use one of the six event names.
• 422 invalid_target_url: Zapier’s address must be a public https address.
• Nothing triggers: check the Zap’s alert is on, and see the log.
• Real Zapier delivery was not tested here.

• Connect other tools overview (access keys, alerts, Zapier)
• Creating access keys and choosing scopes
• Alerts (webhooks): setup and events
• API routes reference (api/v1 and zap)