Proofsource and Make: scenarios that start fixes
Make lets you build visual automations across thousands of apps, and one HTTP call from a scenario can start a Proofsource routine. A published post, a new row or a schedule can kick off a run that drafts an AI visibility fix and waits in Fix it for your approval, with the same limits as Run now.
Proofsource and Make, in short
The facts, ready to quote.
- Stage
- Live, on workspaces with routines turned on
- Connects with
- A Make HTTP module calling the routine's webhook URL; there is no Proofsource app in Make
- Access it needs
- The routine's secret, sent as a bearer token
- Safe by design
- Only a routine that is on starts, and any 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 Make
In the makers' own words, from their own pages. Proofsource builds on it, never around it.
A canvas you can see working
Make's visual builder lets you drag modules onto a canvas and watch automations and AI agents as they run, with execution history that shows which step needs attention.
From make.comThousands of apps to connect
Make offers more than three thousand five hundred applications, from CRM to development tools, so almost any tool can take part in a scenario.
From make.comTemplates in a few clicks
Make's template library offers prebuilt automations you can switch on with a few clicks, sorted by category and by the most popular.
From make.comHow Proofsource uses Make
Let a Make scenario start a Proofsource routine that drafts an AI visibility fix for your OK.
- Connect
One webhook per routine
Turn on a routine's webhook in Proofsource and copy the URL and its secret, shown once.
- Act
A scenario calls it
Add an HTTP module that sends a POST to the routine's URL whenever your scenario's trigger fires.
- Ship
A fix is drafted
The routine runs under the same limits as Run now, and the draft waits in Fix it.
- Prove
Approve, then measure
After your OK and the fix shipping, Proofsource re-checks whether the engines now name you.
Set up Make in 4 steps
Turn on the routine's webhook
In Routines, open a routine, go to its trigger and turn on webhook. Copy the URL and the secret.
Add an HTTP module in Make
In your scenario, add an HTTP make a request module with method POST and the routine's webhook URL.
Send the secret as a bearer token
Add the header Authorization with the value Bearer and your routine secret.
Run once to test
Run the scenario and watch a run appear under the routine, with its drafted fix in Fix it.
| Draft | Started by | Status |
|---|---|---|
| Northwind vs Trek commuter guide | Webhook (Make) | Waiting for your OK |
| Sizing guide FAQ | Run now | Approved |
See it at work
Drawn screens with sample data for an example brand.
What you unlock with Make
Any trigger, any scenario
A new row, a published post or a schedule in Make can begin a run.
Guarded by a secret
Only calls that carry the routine's secret can start it.
Your OK first
A drafted fix waits in Fix it until approved.
No double runs
Send a delivery id and a repeated call is reported as a duplicate, not a second run.
Same limits as Run now
Runs from Make follow the same usage limits and one-open-draft rule as Run now.
Scheduled or reactive
Use a Make schedule to run routines on your own rhythm.
Google AI OverviewsGoogle AI Mode
Questions about Proofsource and Make
Is there a Proofsource app in Make?
No. Make calls a routine through its HTTP module, which sends a POST to the routine's webhook URL. It is quick to set up and gives you the full trigger.
What does a Make scenario start?
A Proofsource routine, run the same way as Run now with the same limits on usage and open drafts. A fix it drafts waits in Fix it for your approval.
How is the call authenticated?
Send the routine's secret as the Authorization bearer token. The secret is shown once when you turn the webhook on, and you can make a new one at any time.
What happens if the routine is off?
It does not start, and the call returns a conflict. A trigger never turns a routine on.
Can a scenario retry start two runs?
Not if you send a delivery id in an Idempotency-Key or X-Proofsource-Delivery header. A repeated id is reported as a duplicate.
How do I disconnect Make?
Turn off the routine's webhook or make a new secret in Routines, and calls from Make stop starting runs. You can also switch off the scenario.
How does this help my AI visibility?
It ties fixes to your real events, such as a new page or product, so they start when they matter. Proofsource then measures across up to 10 engines, including ChatGPT, Perplexity, Gemini and Claude, whether the shipped fix moved your mentions.
Pairs well with Make
Put Make to work for your AI visibility.
Scan your brand, connect Make, and see what AI says about you on up to 10 engines.
Google AI OverviewsGoogle AI Mode