Actions14
- Client Actions
- Email Actions
- Job Actions
- Search Actions
- SMS Actions
Overview
The node integrates with the ServiceM8 platform, specifically enabling sending SMS messages via the "Send SMS" operation under the "SMS" resource. It allows users to send text messages to specified phone numbers and optionally link these messages to jobs within ServiceM8, so they appear in the job diary.
This node is beneficial in scenarios where automated SMS notifications or updates need to be sent to clients or staff directly from workflows, such as appointment reminders, job status updates, or alerts related to specific jobs.
Example use cases:
- Sending a confirmation SMS to a client after booking an appointment.
- Notifying a technician about a new job assignment.
- Sending follow-up messages linked to a particular job for record-keeping.
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, and messages longer than 153 characters will consume multiple 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. If omitted, the message is unlinked. |
Output
The node outputs a JSON array containing the response from the ServiceM8 API for each SMS sent. Each item in the output corresponds to one input item processed and includes details about the sent SMS message as returned by the API.
There is no binary data output; all information is provided in JSON format.
Dependencies
- Requires an API key credential for authenticating with the ServiceM8 API.
- The node makes HTTP POST requests to the ServiceM8 SMS endpoint (
https://api.servicem8.com/platform_service_sms). - Proper configuration of the API credentials in n8n is necessary for successful communication.
Troubleshooting
Common issues:
- Invalid or improperly formatted phone numbers (must be in E.164 format with "+" prefix).
- Messages containing unsupported special characters may fail or cause unexpected behavior.
- Omitting the "To" or "Message" fields will likely result in errors from the API.
- Providing an invalid or non-existent job UUID in "Regarding Job UUID" will cause the message not to link to any job.
Error messages:
- Errors from the ServiceM8 API typically indicate issues with authentication, invalid parameters, or rate limits.
- If the node throws an error about missing fields, ensure that the required properties ("To" and "Message") are correctly set.
- Network or connectivity errors should be checked by verifying API credentials and internet access.