NotificaMe Hub icon

NotificaMe Hub

Integração com NotificaMe Hub API

Actions31

Overview

The NotificaMe Hub node for n8n, when configured with the Telegram resource and the Enviar Arquivo (Send File) operation, allows you to send various types of files (documents, photos, or videos) to a specified Telegram channel or recipient. This is useful for automating notifications, sharing media, or distributing documents via Telegram as part of your workflow.

Practical examples:

  • Automatically sending invoices or reports to a Telegram group.
  • Sharing images or promotional videos with subscribers.
  • Sending alerts with attached files to team members.

Properties

Below are the input properties relevant to the "Telegram" resource and "Enviar Arquivo" operation:

Display Name Type Description
ID Do Canal String The Telegram channel ID where the file will be sent.
ID Do Destinatário String The Telegram recipient's user ID.
Tipo Do Arquivo Options The type of file to send:
- Documento: Any document
- Foto: Image/photo
- Vídeo: Video file
URL Do Arquivo String Public URL of the file to be sent.
Legenda String Optional caption for the file.

Output

The node outputs a json object containing the result of the file-sending operation. While the exact structure depends on the Telegram API response, it typically includes:

  • message_id: Unique identifier for the sent message.
  • chat: Information about the target chat/channel.
  • date: Timestamp of when the message was sent.
  • document/photo/video: Details about the sent file (type, size, file_id, etc.).
  • caption: The caption text, if provided.

Example output:

{
  "message_id": 123,
  "chat": {
    "id": -1001234567890,
    "title": "My Channel",
    "type": "channel"
  },
  "date": 1712345678,
  "document": {
    "file_name": "report.pdf",
    "mime_type": "application/pdf",
    "file_id": "ABC123...",
    "file_size": 102400
  },
  "caption": "Monthly Report"
}

Note: If a photo or video is sent, the corresponding field (photo, video) will be present instead of document.

If binary data is involved, it represents the file that was sent.

Dependencies

  • External Service: Requires access to the NotificaMe Hub API, which acts as an intermediary to Telegram.
  • API Credentials: You must configure the notificamehubApi credential in n8n.
  • Environment: Ensure the file URL is publicly accessible by the NotificaMe Hub service.

Troubleshooting

Common issues:

  • Invalid Channel or Recipient ID: If the IDs are incorrect, the message will not be delivered. Double-check the values.
  • File URL Inaccessible: If the file URL is not public or is invalid, the operation may fail.
  • Missing Permissions: The bot/user must have permission to post in the target channel or chat.
  • API Key Issues: Incorrect or missing NotificaMe Hub API credentials will prevent the node from working.

Possible error messages:

  • "400 Bad Request": Usually due to invalid parameters (e.g., wrong channel/recipient ID, unsupported file type).
  • "401 Unauthorized": Check your NotificaMe Hub API credentials.
  • "404 Not Found": The file at the provided URL could not be found or accessed.

How to resolve:

  • Verify all input fields, especially IDs and URLs.
  • Ensure the NotificaMe Hub API key is correctly set up in n8n.
  • Make sure the Telegram bot has the necessary permissions.

Links and References

Discussion