Overview
This node integrates with the Tellus API to send various types of messages and notifications. It supports sending emails, SMS, POPO messages (a messaging service), phone calls, WeChat messages, webhooks, and combinations thereof to individuals, groups, or alert groups. This node is useful in scenarios where automated communication is needed across multiple channels, such as alerting teams about incidents, sending marketing messages, or triggering workflows based on message delivery.
Practical examples:
- Sending an email notification to a DevOps team when a server goes down.
- Dispatching SMS alerts to all members of an alert group.
- Sending a POPO message to a specific user or group for internal communications.
- Combining email, SMS, and POPO messages to ensure critical alerts reach recipients via multiple channels.
Properties
| Name | Meaning |
|---|---|
| Send Message Type | The type of message to send. Options include: - 发送邮件 (Send Email) - 发送短信 (Send SMS) - 对单人发送 POPO 消息 (Send POPO message to individual) - 对群组发送 POPO 消息 (Send POPO message to group) - 拨打电话 (Make a phone call) - 对单人发送微信消息 (Send WeChat message to individual) - webhook - popo 服务号 (POPO service account) - popo 服务号按钮信息 (POPO service account button info) - popo 服务号选项信息 (POPO service account option info) - popo 服务号模版信息 (POPO service account template info) - 邮件和短信 (Email and SMS) - 邮件和 POPO 单人消息 (Email and POPO individual message) - 邮件，短信和 POPO 单人消息 (Email, SMS, and POPO individual message) - Various options for sending to alert groups and POPO groups combining emails, SMS, calls, and POPO messages (values 21 to 74). |
| Subject | The subject line of the message, typically used for emails. |
| Sender | The sender's address or identifier, defaulting to "grp.devops@corp.netease.com". |
| Receiver | The recipient(s) of the message. Can be one or multiple addresses or identifiers, entered as a string. |
| Message | The content/body of the message to be sent. |
Output
The node outputs JSON data representing the response from the Tellus API after attempting to send the message(s). The output structure corresponds directly to the API response and is returned as an array of JSON objects, each containing details about the message sending result for each input item.
If binary data were involved, it would represent attachments or media related to the messages, but this node only handles JSON responses.
Dependencies
- Requires access to the Tellus API.
- Needs an API authentication credential configured in n8n (an API key or token).
- The node uses an internal helper function
apiRequestto communicate with the Tellus API. - No other external dependencies are indicated.
Troubleshooting
- Empty or missing parameters: If required fields like "Receiver" or "Message" are empty, the API may reject the request or return errors. Ensure all necessary inputs are provided.
- Authentication errors: If the API key or credentials are invalid or missing, the node will fail to authenticate. Verify that the API credential is correctly set up in n8n.
- Unsupported message type: Selecting a message type not supported by your Tellus account or configuration might cause errors.
- API request failures: Network issues or API downtime can cause request failures. Check connectivity and API status.
- Large message content: Very large message bodies might be rejected or truncated by the API.
Common error messages usually relate to invalid parameters, authentication failure, or rate limiting. To resolve, verify input correctness, credential validity, and API usage limits.
Links and References
- Tellus API Documentation (Replace with actual URL if available)
- n8n documentation on Creating Custom Nodes
- General information on POPO Messaging Service (Replace with actual URL if available)