Overview
The node is a trigger for ServiceM8 events, designed to listen for specific occurrences within the ServiceM8 platform and initiate workflows in n8n when those events happen. It is useful for automating processes based on real-time updates from ServiceM8, such as new job creation, customer updates, invoice payments, or staff shift changes.
Common scenarios include:
- Automatically sending notifications or emails when a new job is created.
- Updating CRM records when customer details are updated.
- Triggering follow-up actions after a proposal is viewed by a customer.
- Logging or processing form responses submitted through ServiceM8.
This node listens via webhooks and outputs event data whenever the selected event occurs.
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 selected event occurs. The output includes:
triggerEvent: The type of event triggered (e.g., "job.created", "company.updated").createdAt: Timestamp of when the event was created.- Additional fields as provided by the ServiceM8 webhook payload, which vary depending on the event type.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the ServiceM8 API.
- Needs a publicly accessible HTTPS URL for receiving webhook calls from ServiceM8.
- The node interacts with the ServiceM8 API endpoints to manage webhook subscriptions.
Troubleshooting
- Webhook URL must be HTTPS: The node enforces that the webhook URL starts with HTTPS. Using HTTP or URLs starting with "www." without HTTPS will cause errors.
- Webhook subscription management errors: If the node cannot create, check, or delete webhook subscriptions, verify that the API credentials are correct and have sufficient permissions.
- 404 errors when checking webhook existence: This may indicate that no webhook subscription exists yet for the given URL and event.
- Missing or malformed webhook payloads: Ensure that ServiceM8 is correctly configured to send webhook events to the URL provided by the node.