Send Notification
AI-generatedOverview
This node, named "Bark Push," allows users to send custom push notifications directly to their iOS devices using the Bark notification service. It is particularly useful for automating alerts, reminders, or status updates that need to be delivered instantly to an iPhone or iPad. For example, you could use this node to notify yourself when a long-running workflow completes, alert on system errors, or send daily summaries.
The "Send Notification" operation sends a notification with customizable title, body, and advanced settings such as notification level, badge count, sound, icon, URL redirection, and grouping. This flexibility makes it suitable for various notification scenarios, from urgent alerts that wake the device screen to passive messages that quietly accumulate in the notification center.
Properties
| Name | Meaning |
|---|---|
| Title | The main title of the notification (required). |
| Body | The content/body text of the notification. |
| Is Archive | Whether to archive this message or not (boolean). |
| Level | Notification priority level: - Active: Turns on the screen when received. - TimeSensitive: Shows even in Focus mode. - Passive: Adds to notification list only without turning on the screen. |
| Badge | Number displayed next to the app icon (0 to 999999). |
| Auto Copy | Automatically copy notification content to clipboard (only works on iOS versions below 14.5). |
| Sound | Custom notification sound name. |
| Icon | Custom notification icon URL or identifier. |
| URL | Redirect URL supporting URL Scheme & Universal Link. |
| Group | Custom notification group identifier. |
Output
The node outputs the response from the Bark server API in the json field of the output data. This typically includes confirmation of the notification being sent or any error messages returned by the server.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Bark notification service.
- Needs the base URL of the Bark server configured in the credentials.
- The node performs HTTP requests to the Bark server endpoints (
/push,/ping,/info).
Troubleshooting
- Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect base URL configuration may lead to connection errors.
- Sending notifications with invalid parameters (e.g., unsupported sound or icon) might result in server errors.
- Error messages:
- HTTP errors from the Bark server are passed through due to
ignoreHttpStatusErrorsbeing true; check the response JSON for details. - If the notification fails to send, verify all required fields (especially the Title) are correctly set.
- HTTP errors from the Bark server are passed through due to
- Resolution tips:
- Double-check API credentials and base URL.
- Validate input property values against allowed options.
- Review Bark server logs if accessible for more detailed error information.
Links and References
- Bark GitHub Repository – Official Bark notification service source and documentation.
- iOS Notification Programming Guide – Apple’s guide on notification levels and behaviors.
- n8n Documentation on HTTP Request Node – For understanding how HTTP requests are made within n8n nodes.
