Actions11
- Job Actions
- Client Actions
- Email Actions
- SMS Actions
Overview
The node integrates with the ServiceM8 platform, specifically enabling sending SMS messages linked optionally to jobs within ServiceM8. It is useful for automating communication workflows where SMS notifications or updates need to be sent to clients or staff directly from n8n. For example, a business can automatically notify customers about appointment confirmations, reminders, or job status updates by sending SMS messages that are also logged in the related job diary in ServiceM8.
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 this message relates to. Linking the SMS to a job causes it to appear in the job diary in ServiceM8. If omitted, no linkage occurs. |
Output
- The output is a JSON array containing the response from the ServiceM8 API after sending the SMS.
- Each item in the output corresponds to one SMS send operation.
- The structure typically includes details confirming the message was sent, such as message ID, status, timestamps, or error information if applicable.
- 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 service endpoint (
https://api.servicem8.com/platform_service_sms).
Troubleshooting
- Invalid phone number format: Ensure the "To" field uses the E.164 format (e.g., +1234567890). Incorrect formatting may cause the API to reject the request.
- Message too long or contains unsupported characters: Messages exceeding 153 characters consume multiple credits; special characters are not supported and may cause errors or unexpected behavior.
- Missing or invalid job UUID: If linking to a job, ensure the UUID is correct; otherwise, the SMS will not appear in any job diary.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network or API downtime: Temporary connectivity issues or ServiceM8 API outages can cause failures; retry or check ServiceM8 status.
Common error messages usually relate to validation failures on input fields or authentication problems. Reviewing the error details returned by the API helps identify the exact cause.