TagOne Custom

Requisição customizada para API do ERP TagOne

TagOne Custom

AI-generated

Overview

This node performs custom HTTP requests to the TagOne ERP API using OData endpoints. It supports GET, POST, and DELETE methods, allowing users to query, create, or delete data in the TagOne system. Typical use cases include retrieving filtered data with OData queries, sending data payloads for creation or updates, and deleting records via the API.

Use Case Examples

  1. Retrieve a list of people whose names contain 'João' using a GET request with an OData filter.
  2. Create a new record by sending a JSON body in a POST request to a specific endpoint.
  3. Delete a record by specifying the endpoint and using the DELETE method.

Properties

Name Meaning
Método The HTTP method to be used for the request (GET, POST, DELETE).
Endpoint The OData API endpoint of the TagOne system to which the request is sent.
Query Odata The OData query in JSON format used to filter or manipulate the data for GET requests.
Body The JSON body sent with POST or PUT requests containing data to be created or updated.

Output

JSON

  • * - The JSON response from the TagOne API parsed into an array of objects, excluding the '@odata.context' property if present.

Dependencies

  • An API key credential for the TagOne API, including a cookie and base OData URL.

Troubleshooting

  • Invalid OData Query: This error occurs if the OData query JSON is malformed or does not conform to the expected schema. Ensure the query is valid JSON and matches the OData query schema.
  • Invalid JSON response: This error occurs if the API response is not valid JSON. Check the API endpoint and ensure it returns proper JSON.
  • Authentication errors: Ensure the TagOne API credentials (cookie and URL) are correctly configured and valid.

Links

Discussion