PRO Send WebPush - Captain
AI-generatedOverview
This node sends WebPush notifications to users as part of a campaign using a selected WebPush provider. It allows customization of the notification's title, body, images, icons, URLs, and action buttons. It supports dynamic content through expressions and can handle batch sending with optional waiting until all messages are sent. It also supports tag management for users and options to ignore certain conditions like FC (possibly frequency capping) and DND (Do Not Disturb). This node is useful for marketing campaigns, user engagement, and notification management.
Use Case Examples
- Sending a promotional WebPush notification to users of a specific campaign with customized title, body, and action buttons.
- Sending notifications with dynamic content based on previous node data, such as personalized messages.
- Managing user tags automatically when sending notifications to segment or track user engagement.
Properties
| Name | Meaning |
|---|---|
| Select a Campaign | Select a campaign from the list to associate the WebPush notifications with. |
| WebPush Provider | Select the WebPush provider from the list to send notifications through. |
| Webpush Name | Name of the WebPush notification. |
| WebPush Title | Title of the WebPush notification message. |
| WebPush Body | Body content of the WebPush notification. |
| WebPush Image Address | Image URL to display in the WebPush notification. |
| WebPush Icon Address | Icon URL to display in the WebPush notification. |
| WebPush Url | URL to open when the WebPush notification is clicked. |
| Action Btn1 Todo | Action to perform when the first action button is clicked (Open or Close). |
| Text of Action Btn1 | Text label for the first action button. |
| URL of Action Btn1 | URL to open when the first action button is clicked. |
| Action Btn2 Todo | Action to perform when the second action button is clicked (Open or Close). |
| Text of Action Btn2 | Text label for the second action button. |
| URL of Action Btn2 | URL to open when the second action button is clicked. |
| Wait Until All Messages Sent. | Boolean flag to wait until all WebPush messages are sent before continuing. |
| Tag Settings | Settings for managing user tags, including adding a tag if it does not exist and scheduling tag removal after a specified time. |
| Ignore FC | Boolean flag to ignore frequency capping (FC) when sending notifications. |
| Ignore DND | Boolean flag to ignore Do Not Disturb (DND) settings when sending notifications. |
| Users | User identifiers to send the WebPush notifications to. If left blank, users from the previous node are used. |
Output
JSON
response- Response from the WebPush sending API indicating the result of the send operation.
Dependencies
- Requires an API key credential for authorization to the external CDP API (environment variable UNEXO_API_KEY).
- Requires the base URL of the CDP API set in environment variable CDP_URL.
Troubleshooting
- Ensure environment variables CDP_URL and UNEXO_API_KEY are correctly set and accessible to the node.
- If the node fails to fetch campaigns or providers, check network connectivity and API key validity.
- If sending fails after retries, verify the API endpoint and payload correctness.
- Dynamic expressions in title or body must be correctly formatted; otherwise, placeholders may not be replaced properly.
- Waiting for all messages to be sent may cause delays; adjust the wait setting based on workflow needs.