SearchOps + Zapier
Write every client's monthly report for you, open a deal when an account starts slipping, and keep a running log of the work you did.
Zapier connects SearchOps to the tools your agency already pays for. Pull a client's month (profile results, Map Pack coverage, ChatGPT visibility) into a Google Docs template, push confirmed Map Pack losses into your CRM as churn-risk deals, and log every completed task where clients and account managers can see it.
Monthly reports that write themselves
A Zap fills your Google Docs report template with each client's month and drops the document in their folder.
Churn risk in your CRM
A confirmed Map Pack loss becomes a deal or task in HubSpot or Pipedrive, so renewals don't surprise you.
A visible log of the work
Every task finished in SearchOps lands in the client's shared sheet or CRM timeline: no more "what are we paying for?".
Wins your sales team can use
Confirmed Map Pack gains collect in one sheet, ready for case studies and pitch decks.
Listing hijacks treated as emergencies
A lost verification or duplicate listing texts the account manager straight away.
One Zap, many clients
Paths route by location, so one webhook can serve the whole portfolio.
Recipes
What agencies build with Zapier
Each client's monthly report, written into Google Docs
GET /profile/performance, /ai-visibilityAgencies spending a day a month on reports
- 1Trigger: Schedule by Zapier, monthly on the 1st.
- 2API by Zapier: GET /api/v1/locations/{id}/profile/performance?months=1 for calls, website clicks, direction requests, action rate and the change on last month.
- 3API by Zapier: GET /api/v1/locations/{id}/ai-visibility?engine=chatgpt for how often ChatGPT named the client.
- 4Google Docs: Create Document from Template, filling your report's placeholders, saved to the client's Drive folder for a person to check and send.
Map Pack loss becomes a churn-risk deal
geo_grid.movedAgencies running renewals from a CRM
- 1Trigger: Webhooks by Zapier, Catch Hook, fed geo_grid.moved.
- 2Filter: Data Direction exactly matches down.
- 3Pipedrive (or HubSpot): Create Deal "{{Location Business Name}}: {{Data Keyword}} lost {{Data Points Lost}} grid points" in a Retention pipeline, with {{Data Keyword Url}} attached.
Proof-of-work log the client can open
task.completedRetainer clients who ask what they're paying for
- 1Trigger: Catch Hook fed task.completed.
- 2Paths by Zapier: one path per client, matching Location Business Name.
- 3Google Sheets: Create Spreadsheet Row in that client's shared log with the date, {{Data Title}} and {{Data Task Url}}.
Hijack alarm: lost verification or a duplicate listing
profile.changedAnyone responsible for client profiles
- 1Trigger: Catch Hook fed profile.changed.
- 2Filter: Data Kind exists (verification or duplicate).
- 3SMS by Zapier or Twilio to the account manager, plus a Slack message with {{Data Field Label}}, before and after.
Setup
Connect Zapier, step by step
- 1
Create a Zap with a Catch Hook
In Zapier, create a Zap. For event recipes choose Webhooks by Zapier, then Catch Hook, and copy the URL (use Catch Raw Hook only if you want to verify our signature in a Code step). For report recipes start with Schedule by Zapier instead.
- 2
Add the webhook in SearchOps
In SearchOps, open Developers, then Webhooks, and choose Add webhook. Paste the URL from Zapier, tick the events you want and, for a client-specific workflow, pick that client's locations. Save, and copy the signing secret somewhere safe: it is shown once.
- 3
Send a test event
Back in SearchOps, press Send test on the endpoint. The test event has the same envelope as real events but a short sample body. To map review or scan fields, wait for a real event of that type or replay one from Deliveries, then use that as your sample.
- 4
Find the test in Zapier
In the trigger's Test tab, choose Find new records. Zapier shows our nested fields with readable names, such as Data Points Lost and Location Business Name.
- 5
Call the SearchOps API
For reports, add API by Zapier, API Request, with a connection that sends the header Authorization: Bearer and your SearchOps API key (Developers, API & MCP Credentials). Base URL https://searchops.co/api/v1.
- 6
Route, act and turn it on
Add a Filter or Paths (by Type or by location), then your actions. Publish the Zap. Failed deliveries show in SearchOps under Deliveries, where you can replay them.
Field reference
The fields you'll map most
From the SearchOps webhook payload. Every event also carries type, id, created_at and the location's id and business name.
| Field | Use it for |
|---|---|
| type | Route by event: geo_grid.moved, scan.completed, profile.changed, task.created, task.planned, task.completed, review.created |
| location.business_name | Which client or branch it is about |
| data.direction | up or down: a grid move beyond normal re-run swing (geo_grid.moved) |
| data.points_gained / data.points_lost | How many grid points entered or left the top 3 (geo_grid.moved) |
| data.keyword / data.engine_label | The keyword and engine: Google Maps, Google Search or AI Mode |
| data.share / data.share_low / data.share_high | Share of answered grid points in the top 3 (or named, for AI Mode), with its likely range |
| data.keyword_url / data.scan_url | Open the keyword's grid history or the scan in SearchOps |
| data.field_label / data.before / data.after | What changed on the Business Profile (profile.changed) |
| data.changed_by | google or someone_else: who changed the profile |
| data.kind / data.severity | verification or duplicate, and how serious the change is |
| data.title / data.completed_at / data.task_url | A task and when it was done: your proof of work (task.created, task.planned, task.completed) |
What you need
- SearchOps Pro, Agency or Enterprise. Webhooks and the API are included; an owner or admin sets them up.
- Zapier: Webhooks by Zapier and Paths need a paid plan (Professional or above). API by Zapier is in beta and counts as a premium app.
- Each action after a trigger uses a Zapier task. Filters and Paths do not.
Steps checked against the vendor's own documentation on 12 October 2026. Tools change their menus often; if a step no longer matches, the help article has the latest.
Works well alongside
FAQ
SearchOps and Zapier
Can Zapier build client reports from SearchOps?
Yes. A monthly Schedule, two or three API by Zapier calls (profile results, AI visibility, grid history) and Google Docs Create Document from Template produce a draft report per client. A person checks it before it goes out.
Which Zapier plan do I need?
Webhooks by Zapier and Paths are on Professional and above. Task usage depends on how many actions run per event or report.
Is there a SearchOps app in the Zapier directory?
Not yet. Webhooks by Zapier receives every SearchOps event and API by Zapier calls any of the 29 read-only endpoints, which covers what an app would.
Can one Zap handle all my clients?
Yes. Send all locations to one webhook and use Paths on Location Business Name, or create one SearchOps webhook per client filtered to their locations.