Zapier and Make connect any CRM to RankUpside through our webhook. Build a Zap that triggers when a deal or job is won, then add a Webhooks by Zapier POST step to the client's RankUpside revenue URL with the site's key. In Make, use an HTTP request module the same way. Each deal then lands in the client's report.
What it doesn't do: There's no RankUpside app in the Zapier or Make directories. You use their generic webhook steps, which may need a paid Zapier plan.
Updated
Won deal → client report
One Zap per client site
For CRMs with no webhook of their own, such as many field-service tools, a Zap carries each won deal to the client's revenue webhook. Zapier and Make names are as their own docs show them on Oct 22, 2026. Webhook
The same fields for Zapier and Make. Names on the left must match exactly; values come from your CRM's trigger.
| Field | Map from | If missing |
|---|---|---|
| id | The deal or job ID | A stable id from the deal's contents |
| date | Close date, as 2026-10-14 | Today |
| amount | Deal or job value (value works too) | Rejected: amount is required |
| status | won | Won |
| landing_page | The landing page field on the lead | Listed as unmatched |
| source | The lead source field | Counted and flagged |
| phone, email | Customer phone or email | Optional, to match calls |
{
"id": "D-1042",
"amount": 4200,
"status": "won",
"landing_page": "https://copperlinegutters.example/",
"source": "organic"
}In Make, add the HTTP app's Make a request module after your CRM's won-deal trigger. Set the method to POST, add the Authorization header, choose a JSON body and map the same fields.
| Setting | Value |
|---|---|
| URL | https://rankupside.com/api/hooks/revenue |
| Method | POST |
| Header | Authorization: Bearer rk_•••• |
| Body | JSON, with the fields above |
For a call tracker without a webhook of its own, post each call to the generic lead webhook instead, with the same key.
POST https://rankupside.com/api/hooks/leads?provider=generic
Authorization: Bearer rk_••••
{ "id": "...", "date": "...", "type": "call", "landing_page": "...", "source": "...", "duration": 157 }Recent deals in Client settings › Leads & revenue lists the last 15 received, so a test from the Zap shows up there.
More on this:Webhook referenceOr upload a CSVHubSpotWebhook docsRevenue by search
Recent deals
Received by Zapier · Copperline Gutters
The first report builds from 13 weeks of Search Console history as soon as you connect. Start with 3 client sites.
Weekly search report · Copperline Gutters
Sep 14 – Oct 11, 2026 vs the 4 weeks before
Copperline Gutters got 27 clicks from named buyer searches in the last 4 weeks, up 23% from the 4 weeks before. Google hides the search terms behind 84% of all 289 search clicks. Rankings rose across the site: pages that steadily show up are up about 2.4 positions.