ServiceM8 icon

ServiceM8

ServiceM8 Node

Actions11

Overview

This node integrates with the ServiceM8 platform to send SMS messages. It allows users to send text messages directly through ServiceM8's SMS service, linking messages optionally to specific jobs within ServiceM8 for better tracking and context.

Common scenarios where this node is beneficial include:

  • Notifying customers or clients about job updates or reminders via SMS.
  • Sending quick alerts or confirmations related to scheduled work.
  • Automating communication workflows by integrating SMS notifications into broader automation sequences.

For example, a field service company could use this node to automatically send an SMS reminder to a client about an upcoming appointment, linking the message to the relevant job in ServiceM8 so that all communication history is centralized.

Properties

Name Meaning
To Phone number of the message recipient in E.164 format, including the "+" prefix, country code, and area code.
Message Content of the SMS message. Note that special characters are not supported. Messages longer than 153 characters will consume multiple SMS credits.
Regarding Job UUID UUID of the job that this message is regarding. Linking the SMS to a job causes it to appear in the job diary within ServiceM8. Optional property.

Output

The node outputs a JSON array containing the response from the ServiceM8 API after sending the SMS. This typically includes details about the sent message such as status, message ID, timestamps, and any metadata returned by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an active ServiceM8 account with API access.
  • Needs an API key credential configured in n8n for authenticating requests to ServiceM8.
  • The node makes HTTP POST requests to the ServiceM8 SMS endpoint (https://api.servicem8.com/platform_service_sms).

Troubleshooting

  • Invalid phone number format: Ensure the "To" phone number is in correct E.164 format (e.g., +1234567890). Incorrect formatting may cause the API to reject the request.
  • Message too long or contains unsupported characters: SMS messages exceeding 153 characters will consume multiple credits; special characters might be rejected. Validate message content accordingly.
  • Missing required fields: Both "To" and "Message" fields should be provided. Omitting these may result in errors.
  • API authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
  • Job UUID linkage issues: If the "Regarding Job UUID" is invalid or does not exist, the message will still send but won't link to any job in ServiceM8.

If the node throws errors related to request failures, check network connectivity and API rate limits.

Links and References

Discussion