Connect Zapier & Make

PreStartGo doesn't (yet) publish official Zapier or Make marketplace apps. You don't need one — both platforms can trigger workflows off any HTTPS webhook, and PreStartGo's webhook system already delivers signed, retried event notifications for every event below. This guide walks through wiring either platform up as a webhook receiver.

What you can automate

Every event PreStartGo emits can fire a Zapier Zap or Make scenario — compliance alerts in Slack, ticket creation in your CMMS, syncing completed checks into a spreadsheet, and similar. The current event catalogue:

See the Webhooks guide for the full payload shape and the * wildcard subscription.

Prerequisites

You need an API key with the webhooks:write scope (webhooks:read too, if you want to pull delivery history into your automation). API keys are created by an Administrator or the Account Owner (org role MANAGER or OWNER) from Developer → API Keys in the admin console — see Authentication for scopes, key prefixes, and rotation.

Zapier: catch a webhook

1. Create a Zap with the Webhooks by Zapier trigger, event Catch Hook. Zapier gives you a unique catch URL — copy it.

2. Register that URL as a PreStartGo webhook subscription:

   bashCopy

   curl -s -X POST https://api.prestartgo.com/api/v1/webhooks \
     -H "Authorization: Bearer psg_live_..." \
     -H "X-Org-Id: <uuid>" \
     -H "Idempotency-Key: $(uuidgen)" \
     -H "Content-Type: application/json" \
     -d '{
       "url": "https://hooks.zapier.com/hooks/catch/…/…/",
       "events": ["defect.reported", "check.completed"],
       "description": "Zapier integration"
     }'
   

   The response includes a secret — copy it now, it isn't shown again (see Verifying signatures below).

3. Fire a sample delivery so Zapier can record the payload shape for the rest of the Zap:

   bashCopy

   curl -s -X POST https://api.prestartgo.com/api/v1/webhooks/<webhook-id>/test \
     -H "Authorization: Bearer psg_live_..." \
     -H "X-Org-Id: <uuid>" \
     -H "Idempotency-Key: $(uuidgen)"
   

4. In Zapier, click Test trigger to pull in the sample payload, then build the rest of the Zap (filters, actions) against its fields.

Make: custom webhook module

1. Add a Webhooks → Custom webhook module as the scenario's trigger and click Add, which generates a receiving URL.
2. Register it the same way as above — POST /api/v1/webhooks with Make's URL in url and the events you want in events.
3. Use the same test-delivery call (POST /api/v1/webhooks/<webhook-id>/test) to send a sample event so Make can determine the payload's data structure for downstream modules.

Verifying signatures

Both platforms deliver the raw request to your Zap/scenario without verifying it came from PreStartGo. If your workflow acts on the payload (rather than just logging it), verify the X-PSG-Signature header before trusting the body — the scheme is documented in the Webhooks guide's Signature verification section. In Zapier or Make this typically means adding a Code / Custom function step that recomputes the HMAC before your real actions run.

Retries and delivery history

PreStartGo retries failed deliveries automatically — you don't need to build retry logic into the Zap or scenario. See the Webhooks guide's Delivery semantics section for the retry schedule, at-least-once guarantees, and how to query delivery history via GET /api/v1/webhooks/{id}/deliveries.