Overview
This node triggers workflows in n8n when an SMS message is received on a specified Kavenegar line number. It periodically polls the Kavenegar API to check for new incoming SMS messages that have not yet been read. The node supports filtering by sender phone number and by text content within the message, allowing users to trigger workflows only for relevant messages.
Common scenarios where this node is beneficial include:
- Automating responses or actions based on incoming SMS commands.
- Logging or processing SMS messages from specific senders.
- Filtering and triggering workflows only when certain keywords appear in SMS messages.
For example, a user could set up this node to monitor a customer support SMS line and automatically create support tickets when messages contain the word "help".
Properties
| Name | Meaning |
|---|---|
| Line Number | The Kavenegar phone line number to monitor for incoming SMS messages. |
| Poll Interval (Seconds) | How often (in seconds) the node checks for new SMS messages on the specified line. |
| Sender Filter | Optional filter to trigger only for SMS messages from this specific phone number. Leave empty to accept any sender. |
| Message Contains | Optional filter to trigger only if the SMS message contains this text (case-insensitive). Leave empty to accept all messages. |
Output
The node outputs an array of JSON objects, each representing an incoming SMS message that matches the filters. Each object includes:
sender: The phone number of the SMS sender.message: The text content of the SMS.messageId: Unique identifier of the SMS message.date: The date/time string when the SMS was received.lineNumber: The monitored Kavenegar line number.rawData: The full raw data object returned by the Kavenegar API for the SMS.timestamp: The ISO timestamp when the node processed the message.
The output is delivered as the main output of the node and can be used downstream in workflows for further processing.
Dependencies
- Requires a valid Kavenegar API key credential configured in n8n.
- Access to the Kavenegar SMS Receive API endpoint.
- Network connectivity to
https://api.kavenegar.com.
Troubleshooting
No credentials got returned!
This error indicates that the node could not find or access the required Kavenegar API key credential. Ensure the credential is properly set up and selected in the node configuration.Error fetching SMS: [error message]
This error occurs if the API request fails. Possible causes include invalid API key, network issues, or incorrect line number. Verify the API key validity, internet connection, and that the line number is correct.If no messages are triggering the workflow, check that the filters (
Sender FilterandMessage Contains) are correctly set or left empty to allow all messages.The polling interval should be set considering API rate limits and desired responsiveness.