NotificaMe Hub icon

NotificaMe Hub

Integração com NotificaMe Hub API

Overview

This node allows you to send an email with file attachments via the NotificaMe Hub API. It is designed for scenarios where you need to automate sending emails that include both HTML content and one or more files, such as sending reports, invoices, or notifications with supporting documents directly from your n8n workflows.

Practical examples:

  • Sending a welcome email with a PDF guide attached.
  • Delivering automated invoices or receipts to customers.
  • Sharing project files or updates with team members via email.

Properties

Below are the supported input properties for the "Email" resource and "Enviar Email (Com Arquivos)" operation:

Display Name Type Description
ID Do Canal String ID do canal de Email (the email channel identifier).
Email Do Destinatário String Endereço de email do destinatário (recipient's email address). Example: nome@exemplo.com
Assunto String Assunto do email (subject line of the email).
Template HTML String Conteúdo HTML do email (HTML body of the email).
Anexos Collection (multiple) List of attachments to include in the email. Each attachment requires:
- URL Do Arquivo (String): Public URL of the file to attach.
- Nome Do Arquivo (String): The filename as it will appear in the email.

Output

The node outputs a json object containing the result of the email sending operation. While the exact structure depends on the NotificaMe Hub API response, typical fields may include:

{
  "success": true,
  "messageId": "string",
  "status": "sent",
  "details": { /* additional info if provided by API */ }
}
  • success: Indicates if the email was sent successfully.
  • messageId: Unique identifier for the sent message.
  • status: Status of the email (e.g., "sent", "queued").
  • details: Any additional information returned by the API.

Note: This node does not output binary data; all responses are in JSON format.

Dependencies

  • External Service: Requires access to the NotificaMe Hub API.
  • API Key: You must configure the notificamehubApi credential in n8n.
  • Environment: No special environment variables are required beyond standard n8n setup.

Troubleshooting

Common issues:

  • Invalid Channel ID: If the "ID Do Canal" is incorrect, the API may return an error indicating the channel was not found.
  • Recipient Email Errors: Invalid or improperly formatted recipient email addresses can cause delivery failures.
  • Attachment Issues: If the file URL is inaccessible or invalid, the email may be sent without attachments or fail entirely.
  • Authentication Errors: Missing or incorrect API credentials will prevent the node from sending emails.

Common error messages and resolutions:

  • "401 Unauthorized": Check your NotificaMe Hub API credentials in n8n.
  • "404 Channel not found": Verify the "ID Do Canal" property.
  • "400 Bad Request": Ensure all required fields are filled and attachments have valid URLs and filenames.

Links and References

Discussion