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 job is created or completed.
- Notifying teams when customer details are updated or new messages arrive.
- Tracking invoice status changes such as when an invoice is sent or fully paid.
- Responding to staff shift changes or job site check-ins/outs.
Practical examples:
- Automatically sending a thank-you email when a customer review is submitted.
- Updating a CRM system when a new customer is added.
- Creating tasks in project management tools when a job is marked as completed.
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 JSON includes:
triggerEvent: The type of event that triggered the webhook (e.g., "job.created").createdAt: Timestamp indicating when the event was created.- Additional fields from the webhook body providing detailed information about the event.
This structured JSON can be used downstream in workflows for further processing or integration.
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, check, and delete webhook subscriptions automatically.
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 or invalid credentials. Verify API credentials and network connectivity.404 Not Found on Checking Webhook:
This indicates no existing webhook subscription found for the given URL and event. The node handles this gracefully by returning false.General API Errors:
Any unexpected errors from the ServiceM8 API calls will cause the node to fail. Check API limits, credentials, and ServiceM8 service status.