Nearby Now Integration – User Guide

Use this guide to:

• connect Nearby Now inside LaunchSMS
• understand which service integrations can send data to Nearby Now
• send Nearby Now checkin.created events into LaunchSMS
• turn those events into service-area pages
• show Nearby Now reviews and check-ins on AI Website Builder pages

---

Overview

Nearby Now touches three different areas in the app. They do different jobs:

Area	What it controls
Integrations → Nearby Now	API keys, webhook URL, automation filters, invoice/review rules
Integrations → Local Content Engine	Whether Nearby Now webhooks are allowed to generate service-area pages
AI Website Builder → Service Area Pages – Global Settings	URL pattern, page rendering, and Nearby Now widget display on the website

If one of these is skipped, the setup will feel incomplete.

---

What the integration can do

1. Create Nearby Now check-ins and review requests from automations

LaunchSMS can send supported completed-job automation payloads to Nearby Now.

2. Generate AI service-area pages from Nearby Now check-ins

LaunchSMS can receive Nearby Now checkin.created webhooks and use the job location to create or refresh city pages.

3. Render Nearby Now content on AI websites

AI Website Builder can display Nearby Now reviews and check-ins on:

• the service-area index page
• individual city/service-area pages

---

How Nearby Now works with other services

Nearby Now has two separate directions of data flow:

1. Outbound to Nearby Now: LaunchSMS sends job data from another service to Nearby Now to create a check-in and optionally send a review request.
2. Inbound from Nearby Now: Nearby Now sends checkin.created webhooks into LaunchSMS so Local Content Engine can create or refresh service-area content.

These are independent. A company can use one without the other.

Outbound automation support

The Nearby Now check-in automation action currently supports these trigger types:

Source service	Supported automation trigger	What LaunchSMS sends to Nearby Now	Notes
ServiceTitan	ServiceTitan job completed	Check-in plus optional review request	Uses ServiceTitan job notes/invoice summary for the reference text. Requires technician email. Check-in requires coordinates.
Housecall Pro	Housecall Pro job completed	Check-in plus optional review request	Supports Housecall Pro note selection and optional Housecall Pro image attachments. Requires technician email. Check-in requires coordinates.
Jobber	Jobber job closed	Check-in plus optional review request	Uses Jobber notes/summary for reference text. Check-in requires coordinates in the generic latitude/longitude payload fields.
Jobber	Jobber invoice created	Check-in plus optional review request	Same behavior as Jobber job closed, but triggered from invoice creation.

These services do not currently send outbound Nearby Now check-ins through the nearbynow_checkin automation action:

• Dispatch Scout
• ServiceTrade
• FieldPulse
• AccuLynx
• Angi, HomeAdvisor, Thumbtack, Google LSA
• Native FieldOps/Dispatch jobs

Those services may still participate in other automation actions, Google Business Profile posts, YouTube posts, or Local Content Engine workflows, but they are not outbound Nearby Now check-in sources unless the code adds them to the supported trigger list.

Inbound Nearby Now support

When Nearby Now sends a checkin.created webhook into LaunchSMS:

• LaunchSMS validates that the webhook belongs to the saved Nearby Now integration.
• LaunchSMS extracts the check-in location.
• If Local Content Engine is enabled and the Nearby Now provider is enabled, LaunchSMS can create or refresh service-area content from the check-in.
• AI Website Builder can render Nearby Now reviews/check-ins when the website settings enable the Nearby Now widget.

Inbound Nearby Now webhooks do not require ServiceTitan, Housecall Pro, Jobber, or any other field-service integration.

---

Prerequisites

Before starting, make sure you have:

• access to the Integrations module
• access to AI Website Builder
• your Nearby Now Agency API Key
• your Nearby Now Storefront API Key
• an AI Website Builder site already created for the company

Important:

• For AI Website Builder widget rendering, LaunchSMS only needs at least one Nearby Now API key.
• For automation-driven check-ins/review requests, LaunchSMS currently expects both the Agency API Key and the Storefront API Key to be saved.

---

Step 1: Connect Nearby Now in LaunchSMS

Go to Integrations → Nearby Now.

Enter:

• Agency API Key
• Store Front API Key

Optional settings on this page:

• Trigger Filter Phrase: only send jobs that include this phrase in notes, such as #ci
• Suppression Filter Phrase: skip jobs that include this phrase, such as #no
• Identification Filter Phrase: use the tagged note as the check-in text, such as #use
• Housecall Pro Note To Use: for Housecall Pro, choose whether the first or last job note becomes the Nearby Now reference when no identification phrase overrides it
• Include Housecall Pro Photos: attach a Housecall Pro image when the completed-job payload includes supported image attachments
• Housecall Pro Photo Sequence: choose first, last, or first and last photo candidates
• Require Paid Invoice: only send when the invoice is paid in full
• Do not send reviews: create check-ins only and skip review requests

Click Save Nearby Now Settings.

After saving, LaunchSMS generates a Webhook URL for the company.

---

Step 2: Add the LaunchSMS webhook inside Nearby Now

Copy the Webhook URL from Integrations → Nearby Now and add it inside Nearby Now as the destination for check-in events.

Use Nearby Now event type:

• checkin.created

LaunchSMS expects the webhook payload to include a usable location, especially:

• data.location.city
• data.location.state

If the payload does not contain a valid location, LaunchSMS will ignore it for service-area page generation.

---

Step 3: Allow Nearby Now to generate service-area pages

Go to Integrations → Local Content Engine.

Turn on:

• Enable Local Content Engine
• Use Queue Processing (Recommended)
• Nearby Now under Enabled Providers

This step matters because the Nearby Now webhook by itself does not control provider ingest. The Local Content Engine page is what allows Nearby Now events to create or refresh service-area pages.

---

Step 4: Connect Nearby Now to AI Website Builder

Go to AI Website Builder and open:

• Service Area Pages – Global Settings

Configure the service-area page settings you want for all providers, including Nearby Now:

• Service Area URL Pattern
• Enable AI mini-post cards on city pages
• Enable service area heat maps

The URL pattern supports:

• {service-slug}
• {city}
• {state}

Then turn on:

• Enable Nearby Now reviews/check-ins

If the company has a Nearby Now key saved, the builder will show the integration as connected.

Optional advanced Nearby Now widget settings:

• Include Google Reviews
• Review Count
• Check-in Count
• Map Zoom Level
• Facebook Like Button
• Map Scroll Wheel

Save the AI website changes. Publish the site if you want the live website to reflect the new settings immediately.

---

How AI Website Builder uses Nearby Now

When Nearby Now is enabled in the builder:

• the service-area index can render a general Nearby Now heatmap/review block
• city pages can render city/state-specific Nearby Now content

For city pages to render correctly, the page must have a city and state context. That normally comes from the Nearby Now webhook location data used to create the page.

---

Optional: Use Nearby Now in Automations

If you want LaunchSMS to send completed-job data to Nearby Now:

1. Go to Automations
2. Create or edit an automation using one of these trigger types:
   • ServiceTitan completed job
   • Housecall Pro completed job
   • Jobber closed job
   • Jobber invoice created
3. Add the Nearby Now check-in action
4. Choose whether to send a customer review request with the check-in

Notes:

• company-level Do not send reviews overrides the per-step review checkbox
• #noreview in the selected note, invoice summary, Jobber note, or Jobber summary suppresses the review request
• if contact info or address is incomplete, LaunchSMS falls back to check-in only
• if latitude/longitude are missing, LaunchSMS cannot create the check-in, but it can still attempt the review request when contact info and address are complete
• if technician email is missing, the action is skipped
• if Require Paid Invoice is enabled, the action is skipped unless the trigger payload indicates paid_in_full

What the automation sends

For a check-in, LaunchSMS sends:

• latitude
• longitude
• reference text
• technician/user email
• optional photo

For a review request, LaunchSMS sends:

• customer name
• customer email and/or SMS phone
• reference text
• service address
• technician/user email
• the created Nearby Now check-in ID when a check-in was created first
• optional photo

Reference text and filters

Nearby Now reference text comes from the trigger payload notes:

• Housecall Pro uses structured job notes when present. The Housecall Pro Note To Use setting chooses first or last.
• ServiceTitan and other non-Housecall triggers use the last available note by default.
• Jobber uses jobber_note or jobber_summary as fallback text when needed.

Filter behavior:

• Trigger Filter Phrase must appear in one of the available notes, or the action is skipped.
• Suppression Filter Phrase skips the action when it appears in one of the available notes.
• Identification Filter Phrase selects the matching note as the Nearby Now reference when present.
• The trigger phrase is removed from the final reference text before sending.

Housecall Pro photos

Housecall Pro photos are controlled by the Nearby Now integration settings, not by the automation step itself.

To send Housecall Pro photos:

1. Go to Integrations → Nearby Now.
2. Check Include Housecall Pro Photos.
3. Choose Housecall Pro Photo Sequence.
4. Save the Nearby Now settings.

Photo sequence behavior:

Setting	Behavior
First	Sends up to the first two image candidates
Last	Sends up to the last two image candidates
First and last	Sends the first image candidate and the last image candidate

Important details:

• This photo option currently applies only to Housecall Pro job-completed triggers.
• The Housecall Pro webhook payload must include image attachments under job.attachments.
• Attachments must have an image MIME type such as image/jpeg, or an image filename extension.
• Housecall Pro attachment URLs are temporary signed URLs. LaunchSMS stores selected image candidates under public/uploads/job_images/{company_id}/housecall/ during webhook processing and sends those stable URLs to Nearby Now.
• If Include Housecall Pro Photos is unchecked, LaunchSMS does not attach photos even when the Housecall Pro webhook payload contains images.
• ServiceTitan and Jobber image URLs may exist in automation payloads for other actions, but the Nearby Now photo attachment path is currently limited to Housecall Pro.

---

Recommended setup order

1. Save Nearby Now API keys in Integrations → Nearby Now
2. Copy the generated webhook URL into Nearby Now
3. Enable Local Content Engine and the Nearby Now provider
4. Turn on Enable Nearby Now reviews/check-ins in AI Website Builder
5. Save and publish the AI website
6. Send a test Nearby Now check-in

---

Testing checklist

Use this quick validation flow after setup:

1. Save the Nearby Now integration and confirm a webhook URL appears
2. Confirm Nearby Now is enabled under Local Content Engine → Enabled Providers
3. Confirm Enable Nearby Now reviews/check-ins is turned on in AI Website Builder
4. Trigger a Nearby Now checkin.created event with a valid city and state
5. Verify a service-area page is created or refreshed for that location
6. Open the service-area page preview or live page and confirm the Nearby Now block renders

If you are also using automations:

1. Run a supported completed-job automation
2. Confirm the job has the required notes, contact data, and coordinates
3. Confirm the assigned technician has an email address
4. For Housecall Pro photos, confirm Include Housecall Pro Photos is checked and the webhook includes job.attachments
5. Verify LaunchSMS sends the Nearby Now check-in or review request

---

Troubleshooting

Issue	Likely cause	Fix
No webhook URL is shown	Settings have not been saved yet	Save the Nearby Now integration once to generate the webhook key
Nearby Now widget does not appear in AI Website Builder	Nearby Now is not enabled in builder settings, or no API key is saved	Turn on Enable Nearby Now reviews/check-ins and confirm at least one API key is saved
City pages are not being generated	Local Content Engine or provider ingest is off	Enable Local Content Engine and the Nearby Now provider
Webhook is received but page is skipped	Payload does not contain a usable location	Confirm the Nearby Now payload includes data.location.city and data.location.state
Automation action does nothing	Both API keys are not saved	Save both the Agency API Key and Storefront API Key
Review request is skipped	Missing customer email/SMS or incomplete address, or reviews are suppressed	Add customer contact info and address, or disable review suppression
Check-in is skipped	Missing coordinates or technician email	Make sure the payload includes latitude, longitude, and technician email
Check-in is skipped but review request sends	Missing coordinates, but contact info and address are present	Add latitude/longitude to the source payload if a Nearby Now check-in is required
Housecall Pro photos do not attach	Include Housecall Pro Photos is unchecked, the payload has no image attachments, the image download failed, or the automation ran from a non-Housecall trigger	Check Include Housecall Pro Photos, confirm job.attachments contains image files, and review automation run events/logs for photo download warnings
Jobber action skips the check-in	Jobber payload lacks generic latitude/longitude fields	Map or enrich the trigger payload with coordinates before relying on Nearby Now check-ins
Dispatch Scout, ServiceTrade, or FieldPulse automation does not send to Nearby Now	These triggers are not supported by the Nearby Now check-in action	Use a supported trigger or add code support for that provider before configuring outbound Nearby Now check-ins

---

External Nearby Now References

• Check-in API docs: https://servicepros.nearbynow.co/plugins/api-integration/create-check-in/
• Review request docs: https://servicepros.nearbynow.co/plugins/api-integration/requesting-review/