Actions60
- General Actions
- Mission Actions
- Client Actions
- Agent Actions
- Invoice Actions
- Contact Actions
- Alert Actions
- Walter Actions
- Notification Actions
- Webhook Actions
- Route Actions
- Export Actions
Notification → Send Push Notification
AI-generatedOverview
This node sends a push notification to a specified agent within the Everest Transport Management System (TMS). It is useful for alerting agents about new missions or updates directly on their devices. For example, a dispatcher can notify an agent about a new mission assignment by sending a customized message that includes a mission reference.
Use Case Examples
- Sending a push notification to an agent with a message like 'You have a new mission ABC123XXX' where 'ABC123XXX' is dynamically replaced by the mission reference.
- Alerting an agent about urgent updates or changes in their schedule via push notifications.
Properties
| Name | Meaning |
|---|---|
| Agent ID | The unique identifier of the agent to whom the push notification will be sent. |
| Message Text | The content of the push notification message. It supports a placeholder [mission_ref] that can be replaced with a specific mission reference. |
| Mission Reference | A string to replace the [mission_ref] placeholder in the message text, allowing dynamic insertion of mission-specific information. |
Output
JSON
success- Indicates whether the push notification was sent successfully.message- The text content of the push notification sent.agent_id- The ID of the agent who received the push notification.
Dependencies
- Requires an API key credential for Everest TMS to authenticate and send requests.
Troubleshooting
- If the agent ID is invalid or does not exist, the node may throw an error indicating the agent could not be found.
- If the message text is empty or missing required placeholders, the notification may not be sent correctly.
- Network or authentication errors may occur if the Everest API credentials are incorrect or expired.