BUDHOSP Moph Notify icon

BUDHOSP Moph Notify

ส่งข้อความแจ้งเตือนผ่าน BUDHOSP Moph Notify API

Overview

This node integrates with the BUDHOSP Moph Notify API to send notification messages. It is designed to send alert or informational messages programmatically, which can be useful in scenarios such as system monitoring alerts, user notifications, or automated reminders.

A practical example would be sending a notification message to users or administrators when a specific event occurs in an automation workflow, such as completion of a data processing task or detection of an error condition.

Properties

Name Meaning
Client Key A required client key string used for authentication with the notification service.
Secret Key A required secret key string used alongside the client key for authentication (password type).
ข้อความแจ้งเตือน (Message) The notification message text that you want to send.
Alt Text (Title) The alt text or title of the notification message, serving as a brief heading or summary.

Output

The node outputs JSON objects for each input item processed. Each output JSON contains:

  • success: Boolean indicating if the notification was sent successfully.
  • response: The full response object returned from the BUDHOSP Moph Notify API on success.
  • error: Error message string if the operation failed.
  • timestamp: ISO 8601 timestamp of when the operation was performed.

No binary data output is produced by this node.

Dependencies

  • Requires an API credential containing:
    • Base URL of the BUDHOSP Moph Notify API.
    • Bearer token for authorization.
    • Optional CSRF token header.
  • The node uses HTTP POST requests to the endpoint /api/v1/moph/notify.
  • Proper configuration of these credentials in n8n is necessary for successful operation.

Troubleshooting

  • Missing Required Fields: The node throws errors if any of the required fields (Client Key, Secret Key, message, or Alt Text) are empty or missing. Ensure all required inputs are provided.
  • Authentication Errors: If the API keys or tokens are invalid or expired, the request will fail. Verify the correctness and validity of your API credentials.
  • API Endpoint Issues: Network issues or incorrect base URL configuration may cause request failures. Confirm the API base URL and network connectivity.
  • Error Handling: If the node is set to continue on failure, errors will be captured in the output JSON under the error field; otherwise, execution will stop on the first error.

Links and References

Discussion