Contents
- What Local Services Ads Gives You Natively
- What the Google Ads API Returns for Each Lead
- Options to Get LSA Leads Into a CRM
- The Build: Poll, Dedupe, File, Alert
- Consent and Google's Terms
- Worked Example: A Plumber With 50 LSA Leads a Month
- What Breaks and How to Notice
- When Not to Bother
- Time to Build and Running Cost
- Want It Built?
- FAQ
What Local Services Ads Gives You Natively
Google's help page Manage leads and jobs (checked 17 November 2026) describes three lead types: phone calls through a forwarding number Google assigns, message requests, and booking leads if you opt in. You can be notified by email, SMS or both, and SMS notifications are only available in the United States. You reply to a message lead in the conversation box, and Google routes those messages through an anonymised alias. Message leads are not available for health care verticals or tax specialists.
That is the whole native workflow: a notification, and an inbox inside Google. Nothing in the help page mentions a CRM, a CSV export of leads or a webhook.
Some field service tools connect directly. ServiceTitan's LSA integration article (checked 17 November 2026) says it captures Get Quote message leads into CRM or Bookings, notes that the phone number is a Google tracking number, and offers an auto-reply message inside Google's thread. If you run ServiceTitan, use that first.
What the Google Ads API Returns for Each Lead
Google's developer guide, Local Services campaigns, describes local_services_lead and local_services_lead_conversation as read-only report resources. The guide does not mention webhooks or push notifications; leads are read with queries. Field details below come from the LocalServicesLead and ContactDetails references, all checked 17 November 2026.
| Data | Available by API? | Catch |
|---|---|---|
| Lead ID | Yes | Use it as your dedupe key |
| Lead type (phone, message, booking) | Yes | The guide says coupon leads are supported from v26 |
| Category and service | Yes | Codes such as xcat:service_area_business_hvac, map them to plain names |
| Consumer name | Sometimes | Only if the consumer gave it on a message or booking form |
| Phone number | Yes | "can be a real phone number or a tracking number", plus an extension when it is a tracking number |
| No | The guide says ContactDetails.email was removed in v25 | |
| Lead status, charged or not, credit state | Yes | Contact details are null when the status is WIPED_OUT |
| Message text, call duration, recording URL | Yes, from the conversation resource | Filter by lead; recordings need a signed-in user with account access |
| Healthcare category leads | No | The guide says this data is not available |
| Sending a reply | No | The API offers lead feedback, not messaging |
Access needs a Google Ads developer token. Google's access levels page says Explorer access works on production accounts with 2,880 operations a day, and Basic raises that to 15,000 after brand verification. You apply from the Overview page in the API Center.
Options to Get LSA Leads Into a CRM
| Option | Speed | What you get | Running cost | Effort |
|---|---|---|---|---|
| Native CRM integration (for example ServiceTitan) | Vendor-dependent | Message leads, plus an auto-reply in Google's thread | Included in that tool | Low |
| Parse the notification email | Minutes | Whatever the email contains; test it, Google does not document the format | Email parser or Zapier | Low, but fragile |
| Poll the Google Ads API from n8n | Every 2 to 5 minutes | Every field in the table above, all lead types | n8n hosting; API itself has no fee | Medium |
| Poll the API from Zapier | Every 5 minutes | Same data | Each check is a task: about 8,640 a month at 5 minutes | Medium, and costly |
| A third-party LSA responder | Vendor claims | Vendor-dependent | Subscription | Low |
The Zapier row is why we build this in n8n. A schedule that runs every 5 minutes is 288 runs a day. Under Zapier's task rules each successful action uses a task, so the API call alone burns roughly 8,640 tasks a month before a single lead is filed. Self-hosted n8n does not charge per run. See polling vs webhook for why this matters.
The Build: Poll, Dedupe, File, Alert
This is the n8n version for one Google Ads account that holds the Local Services campaign.
- Get access. Create a Google Cloud project with the Google Ads API enabled, an OAuth client, and a developer token at Explorer level or above. If the account sits under a manager account, note the manager's customer ID for the login-customer-id header.
- Trigger: n8n Schedule Trigger every 5 minutes. Add business-hours logic later if you want.
- Query: an HTTP Request node posting to the Google Ads API search endpoint for your customer ID, with a query like the one in Google's guide:
Test the WHERE clause against your API version before relying on it; if it is rejected, pull recent leads and let the dedupe step do the work.SELECT local_services_lead.id, local_services_lead.lead_type, local_services_lead.category_id, local_services_lead.contact_details, local_services_lead.lead_status, local_services_lead.creation_date_time, local_services_lead.lead_charged FROM local_services_lead WHERE local_services_lead.creation_date_time >= '[today minus 1 day]' - Dedupe: for each row, look up the lead ID in a small table (Postgres, a sheet, or n8n's data store). Skip known IDs. Save new ones.
- Enrich message leads: query
local_services_lead_conversationfiltered to that lead to get the message text. - Create the CRM record: name if present, phone, extension if present, category in plain words, lead type, source "Google LSA", and the message text as a note. In GoHighLevel that is the contacts API or an Inbound Webhook workflow trigger, which HighLevel bills as a premium execution after 100 free lifetime runs.
- Alert a person now: text or Slack the on-call person: "New LSA [type]: [name], [category], [phone + ext]. Reply in the LSA inbox."
- Error branch: if the API call fails twice in a row, alert someone. A silent token expiry is the most common failure.
What the build deliberately does not do: text the lead automatically. If phone_number_extension is filled, the number is a tracking number, and an SMS to it may not reach the person. For message leads, the fastest real reply is still inside Google's conversation box. For phone leads, it is a call back.
Consent and Google's Terms
We did not find a Google page that states what you may do with LSA lead contact details beyond answering the request. Read your current Local Services terms, and ask a lawyer before adding LSA leads to any marketing sequence. Filing the lead and answering it is the conservative use. See opt-in.
Worked Example: A Plumber With 50 LSA Leads a Month
Illustrative numbers, not a client. A plumber receives 50 LSA leads a month: 35 calls, 12 messages, 3 bookings.
- API usage: 288 polls a day plus about 15 conversation lookups a month. That sits far below Explorer's 2,880 operations a day.
- n8n: about 8,640 scheduled runs a month. Free of per-run charges if self-hosted; on n8n Cloud, check that against your plan's execution allowance.
- Office time saved: if copying each lead into the CRM took 3 minutes, that is 150 minutes a month, and the record now exists for every lead, including the ones nobody would have typed in.
- Charged-lead check: with
lead_chargedin the CRM, you can count what you paid for against what you booked each month.
The bigger number is the unanswered message lead. If even one message lead a month that would have been missed becomes a $400 job, the build pays back fast. That is an assumption; compare booked jobs from LSA before and after.
What Breaks and How to Notice
- OAuth refresh token revoked when someone changes a password or removes access. Alert on two failed polls.
- API version sunset. Google retires versions; field names change (email was removed in v25). Put the version in one variable and check Google's release notes each quarter.
- Missing names. Many call leads have no consumer name. Use "LSA caller" plus the category as a placeholder.
- Tracking numbers in your CRM. Store the extension with the number or the record is useless. Do not let other automations text these numbers.
- Wiped-out leads. Contact details become null. File what remains and flag it.
- Second account or location. Each Google Ads customer ID needs its own query.
When Not to Bother
- You use ServiceTitan or another tool with a native LSA connection that covers your lead types.
- You get fewer than 15 LSA leads a month and someone answers every notification within minutes.
- Your leads fall in a healthcare category. Google's guide says that data is not available through the API.
Time to Build and Running Cost
Market-typical as of November 2026, not a quote: one to three days for a builder who has used the Google Ads API before, longer if the developer token application takes time. Prices for a build like this commonly run from about one to a few thousand dollars. Running cost is n8n hosting plus any CRM premium executions, usually under $30 a month at small volume. Our build cost page and self-hosted n8n cost guide give the detail. For the same idea with other lead sources, see Thumbtack leads without a Zapier app and our HVAC and plumbing automation page.
Want It Built?
We handle the developer token, the polling flow, the CRM mapping and the alerts, and send a monthly summary of LSA leads filed, charged and booked. Start with the free automation audit and we will tell you if a native integration already covers you.
FAQ
- Does Google Local Services Ads have a webhook?
- Google's Local Services API guide describes read-only lead resources that you query and mentions no webhook or push delivery (checked 17 November 2026). The webhook you may have seen is for lead form assets in regular Google Ads, a different product.
- Is there a Zapier app for Local Services Ads?
- We found none on 17 November 2026. You can poll the Google Ads API from Zapier with a schedule, but every check uses a task, so n8n or another tool without per-run fees is cheaper.
- Does the API give me the customer's real phone number?
- Sometimes. Google's reference says the phone number can be a real number or a tracking number. When it is a tracking number, an extension is included and is needed to reach the right consumer.
- Can I get the customer's email from LSA leads?
- No. Google's guide says ContactDetails.email was removed in API version 25.
- Can I reply to LSA message leads automatically through the API?
- No. The lead resources are read-only and the API offers lead feedback, not messaging. Reply in the conversation box. Some CRMs, such as ServiceTitan, offer an auto-reply through their own integration.
- What Google Ads API access do I need?
- A developer token. Explorer access works on production accounts with 2,880 operations a day, which covers polling every 5 minutes for one account. Basic raises the limit to 15,000 after brand verification.
- Are healthcare leads available through the API?
- No. Google's guide says data from leads in a healthcare category is not available, and its help page says message leads are not offered for health care verticals.
If this resonated
Module 02 is the long version of this post.
Eval set, refusal pattern, kill switch. Build it in a weekend.
