TagOne Custom

Requisição customizada para API do ERP TagOne

Overview

This node enables making custom HTTP requests to the TagOne ERP system's OData API. It allows users to specify the HTTP method, the API endpoint, and an OData query to manipulate or filter data. This flexibility is useful when you need to interact with various parts of the TagOne ERP API that are not covered by predefined nodes, such as retrieving filtered lists of entities, creating new records, or deleting existing ones.

Practical examples:

  • Fetching a list of customers whose names contain "João" using a GET request with an OData filter.
  • Creating a new record in a specific entity by sending a POST request to the appropriate endpoint.
  • Deleting a record by specifying its identifier in the endpoint and using the DELETE method.

Properties

Name Meaning
Método The HTTP method to use for the request. Options: GET, POST, DELETE.
Endpoint The specific API endpoint path on the TagOne OData API (e.g., /Pessoa).
Query Odata A JSON object representing the OData query parameters to manipulate/filter the data.

Output

The node outputs an array of JSON objects corresponding to the response from the TagOne API. Each item represents the parsed JSON response from the API call, with the internal @odata.context property removed for clarity.

If the API returns binary data, it is not handled explicitly by this node; only JSON responses are processed and returned.

Dependencies

  • Requires valid credentials for the TagOne API, including at least a cookie-based authentication token and the base OData URL.
  • The node expects these credentials to be configured in n8n prior to execution.
  • No additional external dependencies beyond the TagOne API and n8n's built-in HTTP request helper.

Troubleshooting

  • Invalid Odata Query: error parsing JSON
    Occurs if the OData query input is not valid JSON. Ensure the query is correctly formatted JSON before running the node.

  • Invalid Odata Query: [validation message]
    Happens when the OData query JSON does not conform to expected schema rules. Review the query structure and correct any mistakes.

  • Invalid JSON response: error parsing JSON
    Indicates the API response was not valid JSON. This could be due to server errors or unexpected response formats. Verify the endpoint and method used, and check the TagOne API status.

  • Authentication errors
    If the credentials are missing or invalid, the request will fail. Confirm that the API credentials are properly set up in n8n.

Links and References

Discussion