API
Connect Zapier¶
Send remake events to your Zap, so a change in your numbers can add a sheet row, post a message or open a ticket.
Before you start¶
- A Zapier account: you build your Zap there.
- The account owner's sign-in: you need it, because viewer seats can't add channels.
- A schedule: your events come from scheduled runs. Set one up on Budget & Spending.
Catch the hook in Zapier¶
- In your Zapier account, create a Zap.
- For the trigger, pick Webhooks by Zapier and the Catch Hook event.
- Copy the hook URL Zapier gives you. It starts with
https://hooks.zapier.com/.
Add the hook to remake¶
- Open Integrations.
- On the Connections tab, find Zapier under Automations.
- Click Connect. The Connect Zapier dialog opens on its first step, Hook.
- Paste your hook URL and click Next.
- On the Connect step, click Add webhook.
Your hook is now a webhook channel. It hears events for every brand on your account.
Send a test¶
- On the Test step, click Send test. The dialog shows Test sent.
- In Zapier, press Test trigger. Zapier shows you the test event and its fields.
- Pick the action you want, such as a new sheet row or a Slack message.
- Publish your Zap, then click Done in remake.
Your test event's payload holds only test. The fields of a real event's payload reach your Zap when that event first arrives.
What arrives¶
Every event is a JSON POST with the same 6 top-level fields. Map these in your Zap.
{
"event": "visibility.moved",
"title": "Visibility up 15 pts",
"detail": "40% of answers named you last run; 55% this run (11 of 20 answers).",
"domain": "samsung.com",
"occurred_at": "2026-10-07T07:08:51+00:00",
"payload": {"prev_rate": 40, "rate": 55, "delta": 15, "mentions": 11, "asked": 20}
}
event |
When it arrives | payload fields |
|---|---|---|
visibility.moved |
Your Visibility differs from the last scheduled run, by any amount | prev_rate, rate, delta, mentions, asked |
score.moved |
Your Overall score rose or fell by 5 points or more | prev_score, score, delta |
rival.top3 |
A rival entered the top 3 recommended, one event per rival | name |
ai_model.first |
An AI model named you this run, after naming you in none of its answers the run before | ai_model, label, mentions, asked |
scan.failed |
A scheduled run failed | scan_id, error |
scan_complete |
A Run now started through the API or MCP finished or failed | scan_id, token, status, score, error |
fix.verified |
A fix re-check finished | live, total, scan_id, domain |
test |
You clicked Send test | test |
Rates are whole percentages. A few rules decide what you hear:
- Which runs: only scheduled runs and Run now send change or failure events.
- First run: a brand's first scheduled run sends no change events. There is nothing to compare it with.
- At most 4: one run sends 4 change events at most.
- Hidden rivals: a rival you hid never triggers
rival.top3.
Only a Run now started through the API or MCP sends scan_complete when it ends. To follow any other run, poll it through the API, as Webhooks shows.
Check it worked¶
- The Zapier tile reads Connected, and its button reads Manage.
- On the Alerts tab, your hook is listed with an active pill.
- The Delivery log shows a
testrow with the status sent. - In Zapier, your trigger step holds the test sample.
FAQ¶
Why didn't my Zap start after a run finished?¶
Events fire when a number moved, a run failed or a fix re-check finished.
A Run now started through the API or MCP also sends scan_complete. A brand's first scheduled run never sends a change event. Check the Delivery log on the Alerts tab to see what reached your hook.
Can the Zap hear only one brand?¶
Yes. Add your hook on the Alerts tab instead of through the dialog. Pick the brand in the scope menu, which starts on All brands, then click Add channel.
Why does my channel say paused?¶
Your hook failed 5 deliveries in a row, so remake paused it. Each delivery is tried 3 times first. Remove the channel, then add your hook again.
Can a Zap start a run in remake?¶
Not with a ready-made action. Your Zap can call the API with a key, the way Make does.