Actions55
- Client Actions
- General Actions
- Mission Actions
- Agent Actions
- Invoice Actions
- Contact Actions
- Alert Actions
- Walter Actions
- Notification Actions
- Webhook Actions
- Route Actions
- Export Actions
Overview
The node integrates with the Everest Transport Management System (TMS) to send SMS notifications. Specifically, the "Send SMS" operation under the "Notification" resource allows users to send text messages to one or multiple phone numbers. This is useful for alerting drivers, clients, or team members about mission updates or other important information.
Practical examples include:
- Sending a notification SMS to drivers when a new transport mission is assigned.
- Alerting clients about the status of their shipment using a mission reference.
- Broadcasting urgent messages to a list of phone numbers related to logistics operations.
Properties
| Name | Meaning |
|---|---|
| Phone Numbers | Comma-separated list of phone numbers to which the SMS will be sent. |
| Message Text | The content of the SMS message. Supports a placeholder [mission_ref] for dynamic text. |
| Mission Reference | A string to replace the [mission_ref] placeholder in the message text. |
Output
The node outputs a JSON array where each element corresponds to the result of sending an SMS message. The exact structure depends on the response from the Everest TMS API but generally includes confirmation of message delivery or error details if sending failed.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Everest TMS API.
- The node uses the Everest API endpoints internally to perform operations.
- Proper configuration of the Everest API credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing phone numbers can cause the SMS sending to fail.
- Incorrect API credentials or expired tokens will prevent communication with the Everest API.
- Using the
[mission_ref]placeholder without providing a corresponding mission reference may result in incomplete messages.
Error messages:
- Errors returned from the Everest API will be propagated. For example, "Invalid phone number format" indicates input formatting issues.
- Authentication errors suggest checking the configured API key or token.
Resolutions:
- Verify that phone numbers are correctly formatted and separated by commas.
- Ensure the API key credential is valid and has the required permissions.
- Provide a mission reference if using the
[mission_ref]placeholder in the message text.
Links and References
- Everest TMS official documentation (not provided here; consult your Everest TMS provider)
- n8n documentation on creating and configuring API credentials
- General SMS messaging best practices and formatting guidelines