Overview
This node acts as a trigger for ServiceM8 events, allowing workflows to start automatically when specific events occur in the ServiceM8 system. It listens for webhook notifications from ServiceM8 and triggers the workflow with the event data.
Common scenarios where this node is beneficial include:
- Automating follow-up actions when a new customer or job is created.
- Notifying teams or updating systems when job statuses change or are completed.
- Responding to customer interactions such as quote acceptance, form submissions, or reviews.
- Tracking staff activities like shift start/end or job site check-ins/outs.
For example, you could use this node to start a workflow that sends a thank-you email whenever a customer review is submitted or to update an internal dashboard 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. 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 corresponding to the event's data payload as provided by ServiceM8.
This output can be used downstream in the workflow to perform actions based on the event details.
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 from ServiceM8.
- The node interacts with the ServiceM8 API endpoints to manage webhook subscriptions (create, check existence, delete).
Troubleshooting
- Webhook URL must be HTTPS: If the webhook URL starts with "http://" or "www.", the node will throw an error indicating the URL is invalid. Ensure your webhook URL uses HTTPS.
- Webhook subscription errors: Failure to create or delete webhook subscriptions may occur due to network issues or invalid credentials. Verify API credentials and network connectivity.
- 404 on checking webhook existence: This may indicate no existing webhook subscription; it is handled gracefully by returning false.
- Missing or incorrect event selection: Make sure to select a valid event from the options list to receive the correct webhook notifications.