Tell Your Other Systems When a Job Is Done
FSM Navigator® runs your service business from first booking to renewals. Webhooks let the rest of your tools keep up: a signed message goes to your CRM, spreadsheet or reporting tool when a job is created, changes status or is completed, when an invoice is paid, and when a new customer or service request comes in.
Included in Enterprise with the REST API · A card is required at signup · Nothing is charged until the trial ends
The CRM is always three days behind
The install finished Tuesday. The invoice was paid Wednesday. On Friday your CRM still lists the customer as an open lead, and the "your installation is coming up" email goes out anyway.
Nobody did anything wrong. Someone was supposed to export the week's jobs, and it was a busy week. Any tool that depends on a person remembering to copy data across is a tool that's out of date.
Webhooks take the person out of that step. The moment the job is marked complete, FSM Navigator tells the systems you've pointed it at.
What FSM Navigator Sends
Events follow the customer through the whole lifecycle, from first request to paid invoice. Tick the ones each endpoint should receive.
Service Requests
A service request is received, from your booking page or the customer portal.
Customers
A new customer is added, whether someone typed it in, imported a spreadsheet or created it through the API.
Jobs
Created, details updated, status changed, completed, deleted and restored. A completed job sends its own event on top of the status change.
Invoices
An invoice becomes fully paid, by card, bank transfer or a payment your office records. It's sent again if a disputed payment comes back to you.
Each event carries a unique id, the time it happened and where the change came from: dashboard, mobile app, API, booking page or portal. Six things teams build on a job completed webhook.
Built So You Can Trust It
A webhook nobody checks is worse than an export, because it fails quietly. So every part of the delivery is visible.
Signed Requests
Every webhook is signed and time-stamped, so your system can confirm it came from FSM Navigator and ignore forged or replayed requests. Setup details are in the help docs.
A Secret Shown Once
The signing secret appears once, when you save the endpoint, and is stored encrypted. Make a new one any time: for 24 hours we sign with both, so your receiver doesn't miss a beat.
Retries With Growing Gaps
If your endpoint times out or answers with a server error, we try again, up to eight attempts in all over about 15 hours, starting a minute later and stretching to eight hours between tries.
A Log of Every Delivery
The delivery log shows each delivery's status, response code and timing, filtered by endpoint or status. Select Send again to resend one. It keeps 30 days of history.
Duplicate-Safe
The event id stays the same on every retry and every resend. Your receiver records the ids it has handled and skips repeats, so a customer never gets the same follow-up twice.
Switched Off, Not Forgotten
An endpoint that keeps failing is switched off, and the Owner and Managers get an email and an in-app notification. Turning it back on sends a test first.
Set Up in the Dashboard
The Owner and Managers open Webhooks from the side menu, add a public https address, tick the events it should get and save. Copy the signing secret into the receiving system, then select Send test to check the endpoint answers.
Addresses on a private or internal network are refused, and redirects are never followed.
Or Subscribe Through the API
Apps that follow the REST Hooks pattern subscribe and unsubscribe themselves with an Enterprise API key, for job and customer events. Revoke the key and its subscriptions go with it, so old endpoints don't pile up.
API subscriptions show up, read-only, on the Webhooks page under Connected through the API.
Using Zapier? Use Its Webhook Trigger
There's no FSM Navigator app in the Zapier directory, and we won't pretend otherwise. You don't need one. Start a Zap with the Webhooks by Zapier Catch Hook trigger, copy the URL Zapier gives you, and add it in FSM Navigator as an endpoint. Every event you tick starts the Zap, and from there you add the actions: a row in a spreadsheet, a message in team chat, a contact in your email tool.
Check that your Zapier plan includes Webhooks by Zapier before you start. The step-by-step, with the four things to watch for, is in how to send field service jobs to Zapier with webhooks.
What Teams Connect
Webhooks are how FSM Navigator reaches the tools you already pay for. You build these connections; there's no native connector for each product.
CRM
Open a lead when a service request arrives, mark it won when the job is completed and the invoice is paid.
Email Marketing
Add a new customer to a welcome sequence, or start a maintenance-plan offer a week after an install.
Team Chat
Post to the service channel when an emergency job changes status.
Commission Review
Add completed jobs to the sheet your payroll person checks. FSM Navigator doesn't run payroll; this feeds whatever you use.
Reporting
Stream completed jobs and paid invoices into your warehouse or BI tool, so morning reports don't wait on an overnight export.
Connect Your CRM
Exports, connectors, polling or webhooks: how to choose, and the three problems that trip people up.
Webhooks and the REST API Work Together
Each request is a JSON body with the event id, its type, when it happened and the record itself, using the same fields as the matching API response. The Enterprise REST API lets your systems read and write customers, jobs, assets, inventory and more.
Most teams use the webhook to learn that something changed and the API to fetch anything else they need. Your developer stops polling every few minutes, and your daily API allowance goes further. Events can arrive out of order, so each one carries the time it happened, and job events also carry a version number your receiver can compare.
The webhooks developer docs cover the payload, headers, signature checks with sample code, retries and REST Hooks calls.
Part of the Enterprise Plan
Webhooks sit beside the REST API, work orders, inventory and asset management. See what else a larger operation gets on the large teams page. Prefer to ask in plain words? The AI Connector lets the AI assistant you already use read your data directly, with your permissions.
Not in This Release
A published Zapier app, and built-in connectors for named CRM, payroll or marketing products. Webhooks send events out; they don't take changes in. For writes, use the REST API.
Webhook Questions
Which plans include webhooks?
Enterprise ($59.99 per user per month, or $47.99 billed annually), the same plan as the REST API. Webhooks are not on Free or Pro.
Which events can I receive?
Job created, job details updated, job status changed, job completed, job deleted and job restored; invoice paid; customer created; and service request received. You tick the events each endpoint should get.
Who can set up endpoints?
The account Owner and Managers, from the Webhooks page in the dashboard. Other roles do not see it. Apps can also subscribe through the REST API with an API key.
How do I know a webhook really came from FSM Navigator?
Every webhook is signed and time-stamped with a signing secret that only you and FSM Navigator know. Your system checks the signature to confirm the request came from FSM Navigator and to ignore old or replayed requests. The developer docs show how.
What happens if my endpoint is down?
If it times out, cannot be reached or answers with a server error, the delivery is tried again, up to eight attempts in all over about 15 hours, with gaps that grow from one minute to eight hours. Every attempt shows in the delivery log. If an endpoint keeps failing it is switched off, and the Owner and Managers get an email and an in-app notification.
Can I resend a delivery?
Yes. Pick it in the delivery log and select Send again. It goes out with the same event id, so a receiver that already handled it can skip it.
Do you have a Zapier app?
No, there is no FSM Navigator app in the Zapier directory. You can still send events to Zapier: start a Zap with the Webhooks by Zapier Catch Hook trigger and paste its URL into FSM Navigator as an endpoint. Check that your Zapier plan includes Webhooks by Zapier.
Does FSM Navigator integrate with my CRM?
Through webhooks. FSM Navigator sends the event, and your CRM, or an automation tool in between, acts on it. There is no built-in connector for a specific CRM.
How long is the delivery log kept?
30 days. After that, finished deliveries and their events are removed.
Is QuickBooks connected through webhooks?
No. QuickBooks Online sync is its own built-in connection on Pro and Enterprise. Webhooks are for the rest of your systems.
Stop Copying Jobs Into Your Other Systems
One app from first booking to renewals, and the rest of your tools hear about it as it happens.
14-day free trial · A card is required at signup · Nothing is charged until the trial ends