One webhook. Everywhere your team already is.
reviewmy signs every event and posts it to an endpoint you control. Catch it in Zapier, Make or n8n and it lands in Slack, a task board, or a spreadsheet, without anybody opening another tab.
Examplereplayed from a real run
reviewmy
Contrast fails on the primary CTA
Zapieryour step, your accountSlack
Review finished for Northwind marketing site
reviewmy
Raise the primary CTA to 4.5:1. Now 1.4:1. Keep the radius and the type scale.
handed over MCP
Claude Code
> apply cb_3f7b edit tokens.css --cta-fg #F0EDE6 → #1A1A1D ✓ 12.6:1, passes AA
A vermillion mark means the card is ours. Zapier, Slack and Claude Code are your own tools, connected by you. The sequence above is a replay of one real run, not a live feed.
The proof
Nothing gets pasted between tools by hand.
x-reviewmy-event: review.completed x-reviewmy-timestamp: 1788230041 x-reviewmy-signature: t=1788230041,v1=9f2a1c6b8e... { "event": "review.completed", "occurredAt": "2026-08-31T09:14:01.482Z", "data": { "projectName": "Northwind marketing site", "findings": 7, "highestSeverity": "critical", "score": 68 } }
Recompute the HMAC over the timestamp and the raw body, compare it to v1=, and you know the request came from us and not from anybody who guessed your URL.
It is the same t= and v1= shape Stripe uses, so most integrators recognise it on sight and reuse the verification they already have.
Connectors
None ship. Thirteen are coming.
DeliveryIn progress. Four still to prove out on this deployment.
ZapierIn progress
MakeIn progress
n8nIn progressNotificationsIn progress. Three still to prove out on this deployment.
DiscordIn progressMicrosoft TeamsIn progressTask managementIn progress. Six still to prove out on this deployment.
LinearIn progress
AsanaIn progress
JiraIn progress
NotionIn progress
ClickUpIn progress
TrelloIn progressSetup
Connect once. Everything travels.
Point it somewhere
Paste an endpoint, or connect Zapier, Make or n8n. No code if you use an automation tool.
Pick your events
Seven fire today, or subscribe to all of them.
Get a test
We send a real event so you see the exact shape before you rely on it.
Capability
What each one does today.
Nothing has delivered on this deployment yet. Every connector below is built and waiting on its first successful delivery, which is what puts it in this table.
Behaviour
How connectors behave.
We sign every webhook payload, so you can prove it came from us. Slack, Discord and Teams messages are not signed: the channel URL is the secret.
No payload carries a credential: not yours, not a reviewer’s, and not a site’s access key.
A failed delivery retries with backoff, then stops and tells you.
We refuse private and internal addresses, and re-check on every redirect.
Connections are scoped to one account and revocable in one click.
Turning a connector off stops delivery immediately, not eventually.
Questions
Before you wire it up.
Why do Zapier, Make and n8n look identical
Because they are. All three receive the same signed POST that a plain webhook receives. The only difference is what you build downstream of it, which is why the capability table repeats itself rather than inventing distinctions.
Can I reach Slack today
Yes, directly, on any paid plan. Paste a Slack incoming webhook URL into a connector and the events you pick post to that channel as a formatted message. Discord and Microsoft Teams work the same way. You can also catch review.completed in Zapier, Make or n8n and post it from there.
What happens when a delivery fails
We retry with backoff. If the endpoint keeps refusing, we stop, mark the connector as failing, and tell you with the status code we got and the time of the next attempt. A connector never goes quietly broken.
Which events can I subscribe to
Seven fire today: review.completed, review.finding_created, review.regressed, comment.created, comment.resolved, request.marked_done and agent.run_failed. Two more are defined and cannot fire yet, and the setup docs say which.
Do you write to my repository
No. reviewmy reads a site and produces a change brief. Applying it is your coding agent’s job, in your repository, under your review. Nothing we ship has write access.
Point it at the last thing you shipped.
A review takes a few minutes. Wiring the first webhook takes about four.