Overview
The ServiceM8 Trigger node listens for specific events occurring within the ServiceM8 platform and triggers workflows in n8n when those events happen. It is designed to integrate ServiceM8's webhook system with n8n, enabling automation based on real-time updates from ServiceM8.
Common scenarios where this node is beneficial include:
- Automating follow-up actions when a new customer or job is created.
- Notifying teams when job statuses change or jobs are completed.
- Triggering workflows upon receipt of payments, quotes, proposals, or form responses.
- Responding to staff shift changes or site check-ins/outs.
- Handling incoming messages or notes related to jobs.
For example, you could use this node to automatically send a thank-you email when a customer review is submitted or update your CRM when a new job is added.
Properties
| Name | Meaning |
|---|---|
| Event | The specific ServiceM8 event to listen for. Options include: - Badge Added to Job - Badge Removed From Job - Customer Accepted the Quote - Customer Details Updated - Customer Review Submitted - Form Response Submitted - Full Payment Received for Invoice - Invoice Sent to Customer - Job Added to Queue - Job Details Modified - Job Marked as Completed - Job Status Changed - New Customer Added - New Job Created in the System - New Message Received in Inbox - Note Added to Job - Photo Attached to Job - Proposal Sent to Customer - Proposal Viewed by Customer - Quote Sent to Customer - Staff Member Arrived at Job Site - Staff Member Ended Shift - Staff Member Left Job Site - Staff Member Started Shift - Video Attached to Job |
Output
The node outputs JSON data representing the webhook payload received from ServiceM8 when the specified event occurs. The output structure includes:
triggerEvent: The type of event that triggered the webhook (e.g., "job.created").createdAt: Timestamp indicating when the event occurred.- Additional fields: All other properties included in the webhook body sent by ServiceM8, which vary depending on the event type.
This output allows downstream nodes in the workflow to access detailed information about the event and perform further processing.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the ServiceM8 API.
- Needs a publicly accessible HTTPS URL for receiving webhooks (the node validates that the webhook URL uses HTTPS).
- Uses ServiceM8's webhook subscription API to register, verify, and delete webhook subscriptions dynamically.
Troubleshooting
Invalid Webhook URL Error:
If the webhook URL does not start withhttps://, the node will throw an error indicating the URL is invalid. Ensure your webhook URL is publicly accessible over HTTPS.Webhook Subscription Failures:
Errors during webhook creation or deletion may occur due to network issues, invalid credentials, or API limits. Verify your API key and network connectivity.404 Not Found on Checking Webhook:
This indicates no existing webhook subscription was found for the given URL and event. The node treats this as the webhook not existing and attempts to create it if needed.Unexpected Payload Structure:
Since the output depends on the webhook payload from ServiceM8, changes in their API or event schema might affect downstream processing. Always validate the output structure after updates.