Overview
This n8n node enables sending push notifications via Alibaba Cloud Push (Aliyun Push) service. It is designed to deliver messages or notifications to various targets such as devices, accounts, aliases, tags, or all devices registered with Aliyun Push. The node supports advanced configuration for both Android and iOS platforms, including scheduling, offline storage, notification channels, and custom payloads.
Common scenarios:
- Sending real-time alerts or updates to users' mobile devices.
- Broadcasting marketing or informational messages to a user base.
- Notifying specific users or groups based on device, account, alias, or tag.
- Scheduling push notifications for future delivery.
- Logging push events to an external OA system for auditing or analytics.
Practical examples:
- A retail app sends promotional notifications to all users during a sale.
- An IoT platform pushes critical device status updates to the relevant user's phone.
- An internal tool logs every push notification sent for compliance purposes.
Properties
| Name | Type | Meaning |
|---|---|---|
| AppKey | string | The unique identifier for your Aliyun Push application. Required for authentication. |
| 标题 (Title) | string | The title of the notification/message shown to the user. |
| 内容 (Body) | string | The content/body of the notification/message. |
| 推送类型 (Push Type) | options | Type of push: "消息" (MESSAGE) for message, "通知" (NOTICE) for notification. |
| 推送目标类型 (Target) | options | Target type: by device, account, alias, tag, or all devices. |
| 推送目标值 (Target Value) | string | The value(s) for the selected target type (comma-separated if multiple). |
| 扩展数据 (Ext Parameters) | json | Additional custom data to include in the notification payload. |
| 离线提醒 (Remind) | boolean | If true and the device is offline, auxiliary popup will be used for MESSAGE type pushes. |
| 推送设置 (Push Setting) | collection | Advanced settings: offline storage, send channel, scheduled time, job key, etc. |
| iOS推送设置 (iOS Push Setting) | collection | iOS-specific settings: APNS environment, badge number, etc. |
| Android推送设置 (Android Push Setting) | collection | Android-specific settings: notification type, open action, activity, URL, popup, channel, etc. |
Output
The node outputs a JSON object containing the response from the Aliyun Push API for each input item. The structure typically includes:
{
"RequestId": "...",
"MessageId": "...",
"ResponseCode": "...",
// ...other fields returned by Aliyun Push API
}
If OA logging is configured (via optional credentials), the node also attempts to log the push event to an external OA system, but this does not affect the main output.
If an error occurs and "Continue On Fail" is enabled, the output will include an error field with error details for the failed item.
Dependencies
- Aliyun Push API: Requires valid Aliyun Push API credentials (
accessKeyId,accessKeySecret). - OA System (optional): If OA logging is enabled, requires OA API credentials and endpoint.
- n8n Configuration: Credentials must be set up in n8n for both Aliyun Push and (optionally) OA API.
Troubleshooting
Common issues:
- Invalid Credentials: Errors due to incorrect or missing Aliyun Push API keys.
- Missing Required Fields: Omitting required properties like AppKey, Title, Body, Target, or Target Value will cause errors.
- API Limitations: Exceeding allowed number of target values may require splitting into multiple pushes.
- OA Logging Failures: If OA API credentials or endpoint are misconfigured, logging will fail but the main push may still succeed.
Error messages:
"Missing required parameter": Ensure all required fields are filled."Authentication failed": Check your Aliyun Push API credentials."Invalid target value": Verify that the target value matches the selected target type and format."OA logging failed": Check OA API credentials and endpoint configuration.