Proofsource and Zapier: any trigger starts a routine
Zapier connects thousands of apps, and with one webhook it can start a Proofsource routine too. A new product launch, a closed deal or a weekly schedule in a Zap can kick off a run that drafts an AI visibility fix and leaves it in Fix it for your approval. It follows the same limits as Run now.
Proofsource and Zapier, in short
The facts, ready to quote.
- Stage
- Live, on workspaces with routines turned on
- Connects with
- Webhooks by Zapier calling the routine's webhook URL; there is no separate Proofsource app in Zapier
- Access it needs
- The routine's secret, sent as a bearer token or used to sign the body
- Safe by design
- Only a routine that is on starts, and its drafted fix waits for your approval
- Where it shows
- Routines, on a routine's trigger settings, and the run in Fix it
- Disconnect
- Turn off the routine's webhook or make a new secret
Why we love Zapier
In the makers' own words, from their own pages. Proofsource builds on it, never around it.
Thousands of apps, no code
Zapier connects more than ten thousand apps, so work can flow across your whole stack without writing code.
From zapier.comWebhooks without a server
Webhooks by Zapier lets you catch data from an app that has no native integration, or send it on to your own backend, without code or server setup.
From zapier.comReady-made automations
The template library offers prebuilt no-code automations, organized by team such as sales, marketing and support, so a good Zap is a few clicks away.
From zapier.comHow Proofsource uses Zapier
Let any Zap start a Proofsource routine, with the drafted fix waiting for your OK.
- Connect
One webhook per routine
Each Proofsource routine can have a webhook URL. You turn it on once and copy the URL and its secret, shown a single time.
- Act
A Zap calls it
A Zap sends a POST with Webhooks by Zapier whenever your trigger fires, such as a new blog post or a deal closing.
- Ship
The routine drafts a fix
Proofsource runs the routine under the same limits as Run now, and a drafted fix lands in Fix it.
- Prove
You approve, then it is measured
Nothing publishes without your OK. Once approved and shipped, Proofsource re-checks whether the engines now name you.
Set up Zapier in 4 steps
Turn on the routine's webhook
In Routines, open a routine, choose the trigger tab and turn on webhook. Copy the URL and the secret, which is shown once.
Add Webhooks by Zapier to a Zap
Pick your trigger, then add the Webhooks by Zapier action with POST to the routine's webhook URL.
Authenticate the call
Send the secret as an Authorization bearer token, or sign the body with it and send the signature in the X-Proofsource-Signature header.
Add a delivery id and test
Add an Idempotency-Key header so a retry does not start a second run. Test the Zap and watch the run appear.
| Draft | Started by | Status |
|---|---|---|
| Driffle vs Otter comparison page | Webhook (Zapier) | Waiting for your OK |
| Meeting notes FAQ refresh | Run now | Approved |
See it at work
Drawn screens with sample data for an example brand.
What you unlock with Zapier
Any trigger, any app
A new post, deal, ticket or schedule in a Zap starts a run.
Signed or bearer calls
Authenticate with the routine secret as a bearer token or an HMAC signature.
One run per delivery
A repeated delivery id returns a duplicate flag, not a second run.
Your OK comes first
A drafted fix waits in Fix it until someone approves it.
Same cap as Run now
Webhook runs follow the same usage limits and one-open-draft rule.
Scheduled or reactive
Pair with Zapier schedules to run routines on your own rhythm.
Questions about Proofsource and Zapier
Is there a Proofsource app in Zapier?
No. Zapier connects through its Webhooks by Zapier action, which calls the routine's webhook URL. That is simple to set up and gives you the full trigger with no extra install.
What does a Zap start?
A Proofsource routine. It runs the same way as Run now, with the same usage limits, and any fix it drafts waits in Fix it for your approval.
How do I authenticate the call?
Send the routine's secret as the Authorization bearer token, or sign the raw body with it and send the signature in X-Proofsource-Signature. The secret is shown once when you turn the webhook on, and you can make a new one at any time.
What if the routine is off?
A routine that is off does not start, and the call returns a conflict. A trigger never turns a routine on. Unknown or disabled webhooks return not found.
Can a retry start two runs?
Not if you send a delivery id in X-Proofsource-Delivery or Idempotency-Key. A repeated id returns a duplicate result. Calls are also rate limited, with a retry hint when you go over.
How do I disconnect Zapier?
Turn off the routine's webhook, or make a new secret, in Routines. Calls from the Zap then stop starting runs. You can also turn off the Zap itself.
How does this help my AI visibility?
It makes your fixes reactive to your business: a launch, a new page or a lost deal can start a run immediately. Proofsource then measures across up to 10 engines, including ChatGPT, Perplexity, Gemini and Claude, whether the shipped fix moved your mentions.
Pairs well with Zapier
Put Zapier to work for your AI visibility.
Scan your brand, connect Zapier, and see what AI says about you on up to 10 engines.
