Overview
This node acts as a trigger for receiving SMS messages via the Sinch Engage webhook. It listens for incoming SMS events and triggers workflows when an SMS is received. This is useful for automating responses, logging messages, or integrating SMS communication into broader workflows.
Use Case Examples
- Automatically respond to incoming SMS messages.
- Log incoming SMS details to a database or spreadsheet.
- Trigger notifications or alerts based on received SMS content.
Properties
| Name | Meaning |
|---|---|
| Event Type | The type of event that triggers the workflow, currently supports 'Incoming SMS' which triggers when an SMS is received. |
Output
JSON
messageId- Unique identifier of the received message.from- Phone number that sent the SMS.to- Phone number that received the SMS.message- Content of the received SMS message.receivedAt- Timestamp when the SMS was received.metadata- Additional metadata associated with the message.raw- Raw data of the received message event.
Dependencies
- Requires an API key credential for MessageMedia API to manage webhooks and receive SMS events.
Troubleshooting
- Webhook creation failure due to network or authentication issues. Check API credentials and network connectivity.
- Webhook deletion errors, possibly due to webhook already being deleted or network issues. The node attempts cleanup in such cases.
- If no webhook ID is stored, the node will not find or delete webhooks, ensure the webhook is created successfully before triggering.
Links
- Sinch Engage Webhooks Documentation - Official documentation for setting up and managing Sinch Engage webhooks for messaging.