Linqer CRM icon

Linqer CRM

Integração com a API do CRM Linqer

Actions32

Overview

The node integrates with the Linqer CRM API to manage attachments related to sales opportunities. Specifically, the Upload operation under the Anexos (Attachments) resource allows users to upload files and associate them with a specific opportunity in the CRM.

This is useful in scenarios where you want to programmatically add documents, images, or other files to an opportunity record, such as contracts, proposals, invoices, or supporting materials. For example, after generating a PDF proposal in a workflow, you can use this node to upload that file directly to the corresponding opportunity in Linqer CRM.

Properties

Name Meaning
ID da Oportunidade The unique identifier of the opportunity to which the file will be attached.
Arquivo The file data or path for upload. This can be raw binary data from a previous node or a base64 string representing the file content.
Nome do Arquivo Optional filename for the uploaded file. If not provided, the filename will be extracted automatically.

Output

  • The output JSON contains the response from the Linqer CRM API after uploading the attachment.
  • Typically, this includes metadata about the uploaded file such as its ID, name, URL, size, and association details with the opportunity.
  • The node supports binary data input but does not output binary data; it only returns JSON metadata about the uploaded attachment.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests against the Linqer CRM API.
  • The node sends HTTP POST requests with multipart/form-data encoding to upload files.
  • The API endpoint used for uploading attachments is /v1/anexo/public/upload.

Troubleshooting

  • Common issues:

    • Providing an invalid or empty opportunity ID will cause the upload to fail.
    • Incorrectly formatted file data or missing binary data when expected may result in errors.
    • Network or authentication failures if the API key is missing, expired, or incorrect.

  • Error messages:

    • "Operação "upload" não suportada para anexos": This indicates an unsupported operation was requested on attachments. Ensure the operation parameter is set to "upload".
    • HTTP errors from the API (e.g., 401 Unauthorized, 400 Bad Request) usually indicate credential or data format problems.

  • Resolutions:

    • Verify the opportunity ID is correct and exists in Linqer CRM.
    • Confirm the file data is correctly passed, especially if using binary data from a previous node.
    • Check that the API key credential is properly configured and has necessary permissions.

Links and References

Discussion