NotificaMe Hub icon

NotificaMe Hub

Integração com NotificaMe Hub API

Actions31

Overview

This node integrates with the NotificaMe Hub API to send files via WebChat. Specifically, the "Enviar Arquivo" operation allows users to send a file (document, image, or video) to a specified recipient within a WebChat channel by providing the channel ID, recipient ID, and a public URL of the file.

Common scenarios include:

  • Sending documents such as PDFs or Word files to customers during support chats.
  • Sharing images or videos for marketing or informational purposes in customer interactions.
  • Automating file delivery in chat workflows without manual intervention.

Practical example:
A customer support automation sends a user a PDF invoice or product brochure directly in the WebChat after a purchase or inquiry.

Properties

Name Meaning
ID Do Canal The unique identifier of the WebChat channel where the file will be sent.
ID Do Destinatário The unique identifier of the recipient within the WebChat channel who will receive the file.
Tipo De Arquivo The type of file being sent. Options: Documento (document), Imagem (image), Vídeo (video).
URL Do Arquivo The publicly accessible URL of the file to be sent.
Nome Do Arquivo Optional name of the file to be displayed or referenced when sending.

Output

The node outputs JSON data representing the result of the file sending operation. This typically includes confirmation details such as message IDs, status, timestamps, or error information if the operation failed.

If binary data is involved (not indicated here), it would represent the actual file content or related media, but in this case, the file is sent via a URL, so no binary output is expected.

Dependencies

  • Requires an active connection to the NotificaMe Hub API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The file to be sent must be accessible via a public URL.

Troubleshooting

  • Common issues:

    • Invalid or missing channel ID or recipient ID can cause failures in delivering the file.
    • Providing a non-public or inaccessible file URL will prevent the file from being sent.
    • Incorrect file type selection may lead to unexpected behavior or rejection by the API.

  • Error messages:

    • Authentication errors indicate missing or invalid API credentials; verify and update credentials.
    • "File not found" or similar errors suggest the file URL is incorrect or not publicly reachable.
    • Validation errors on IDs mean the provided channel or recipient identifiers are invalid or do not exist.

Resolving these usually involves verifying input parameters, ensuring the file URL is correct and publicly accessible, and confirming that API credentials are properly set up.

Links and References

Discussion