Dougs icon

Dougs

Manipulate Dougs data

Actions5

Overview

This node integrates with the Dougs platform to manipulate various Dougs data resources. Specifically, for the Invoice - Upload operation, it allows users to upload invoice files (either incoming or outgoing) associated with a specified company. This is useful in automating the process of adding invoices into the Dougs system directly from n8n workflows, eliminating manual uploads and improving accounting data management.

Practical examples include:

  • Automatically uploading scanned incoming invoices received via email.
  • Sending outgoing invoice PDFs generated by your system to Dougs for record keeping.
  • Associating uploaded invoices with the correct company entity within Dougs.

Properties

Name Meaning
Company The target company to which the invoice will be uploaded. Can be selected from a list or specified by ID.
FileName The name to assign to the uploaded invoice file.
Binary Field Name The name of the binary data field in the input that contains the actual invoice file content.
Invoice Type Specifies whether the invoice is "Incoming Invoice" or "Outgoing Invoice".

Output

The node outputs JSON data representing the result of the upload operation. This typically includes metadata about the uploaded invoice such as its identifier, status, and any relevant response details from the Dougs API.

If the node handles binary data, it expects the invoice file content to be provided in a binary field specified by the user, but the output itself is JSON describing the upload outcome rather than returning binary data.

Dependencies

  • Requires an active connection to the Dougs platform via an API authentication credential (an API key or token).
  • The node uses the Dougs REST API endpoint at https://app.dougs.fr.
  • Proper configuration of the credential in n8n is necessary to authenticate requests.
  • The node depends on internal resource handlers defined in the bundled code (handlerByOperationByResource), which map operations to their implementation logic.

Troubleshooting

  • Missing Handler Error: If you see an error like Handler missing for resource "invoice" and operation "upload", it indicates the node's internal mapping does not have an implementation for this combination. Ensure you are using a supported version of the node and that the resource and operation names are correct.
  • Authentication Failures: Errors related to authorization usually mean the API credential is invalid or expired. Verify the API key/token configured in n8n.
  • File Not Found or Binary Field Issues: If the binary field name is incorrect or the input data does not contain the expected binary file, the upload will fail. Double-check the binary field name matches the input data.
  • Invalid Company ID: Providing an incorrect or non-existent company ID will cause the upload to fail. Use the list mode to select valid companies or verify the ID manually.

Links and References

Discussion