Easybill icon

Easybill

Interact with Easybill API

Actions13

Overview

The node integrates with the Easybill API to send documents, specifically invoices, via different delivery methods such as email, fax, or postal mail. It is designed to automate the distribution of invoice documents to recipients, streamlining billing and communication workflows.

Common scenarios where this node is beneficial include:

  • Automatically emailing invoices to customers after a sale.
  • Sending invoices via fax for clients who prefer that method.
  • Mailing physical copies of invoices through postal services with various mailing options.

Practical example:

  • After generating an invoice in your system, use this node to send the invoice as a PDF attachment by email to the customer’s email address, including a personalized message and subject line.

Properties

Name Meaning
Document Select the invoice document to send. Can be chosen from a searchable list or specified by ID.
Type Delivery method for sending the document: E-Mail, Fax, or Post.
To Recipient's email address (for email) or phone number (for fax). Required for email and fax types.
CC Optional CC email address for emails.
From Sender's email address or phone number depending on the send type. Required for email and fax.
Subject Email subject line. Required for email sending.
Message Content of the message body for email or fax. Required for email and fax.
Date Date and time when the document is sent. Required for all send types.
Send by Self Boolean flag indicating if the user sends the document themselves (true) or via Easybill (false).
Send with Attachment Whether to include attachments with the message. Defaults to true.
Document File Type Format of the document file to send. Options include Default, Zugferd1, Zugferd2, XRechnung variants.
Post Send Type Method of postal delivery (German Post options), e.g., Standard, Registered, Registered & Personal.

Note: The node currently supports only documents of type "Invoice".

Output

The node outputs a JSON array containing the response(s) from the Easybill API after attempting to send the document(s). Each item in the output corresponds to one send operation and includes details about the success or failure of the request.

If the node supports binary data (not explicitly shown here), it would typically represent the document files or attachments being sent, but this node focuses on sending existing documents via Easybill rather than returning raw files.

Dependencies

  • Requires an active Easybill account and API access.
  • Needs an API key credential configured in n8n for authentication with Easybill.
  • Relies on Easybill API endpoints to fetch document lists and perform send operations.
  • No additional external dependencies beyond the Easybill API and n8n environment.

Troubleshooting

  • Invalid Document ID: If the document ID does not match the expected numeric format, the node will reject it. Ensure the document ID is numeric.
  • Unsupported Document Type: Only invoices are supported. Attempting to send other document types may cause errors.
  • Missing Required Fields: For each send type, certain fields like recipient address, sender address, subject, and message are mandatory. Omitting these will result in errors.
  • API Authentication Errors: Incorrect or missing API credentials will prevent the node from communicating with Easybill.
  • Delivery Failures: Issues like invalid email addresses, fax numbers, or postal addresses can cause the send operation to fail. Verify recipient details.
  • Date Field: The send date must be valid; incorrect formatting might cause errors.

To resolve errors, verify all required parameters, ensure correct API credentials, and confirm the document exists and is of the supported type.

Links and References

Discussion