Tiny ERP icon

Tiny ERP

Consumir API do Tiny ERP
Join our community

Actions3

Overview

This node integrates with the Tiny ERP API to retrieve user data based on a provided username filter. It is designed to fetch information about users registered in the Tiny ERP system, allowing workflows to dynamically query and process user details.

Common scenarios where this node is beneficial include:

  • Automating user data retrieval for reporting or synchronization with other systems.
  • Filtering users by name to trigger specific workflow actions.
  • Integrating user information into broader business processes managed within n8n.

For example, you could use this node to get details of a user named "João Silva" from Tiny ERP and then update a CRM system with that information.

Properties

Name Meaning
Nome do Usuário User name to filter the search by (string). If left empty, it may return all users or no filter applied depending on API behavior.

Output

The node outputs JSON data containing the result of the user data request. The structure includes:

  • success: A boolean indicating if the request was successful.
  • message: A status message, e.g., "Obtendo usuário" (Obtaining user).
  • filtros: An object showing the filters used in the request, such as the username.

Example output JSON:

{
  "success": true,
  "message": "Obtendo usuário",
  "filtros": {
    "nome": "someUserName"
  }
}

Note: The current implementation returns a placeholder response with the filter info but does not perform an actual API call to fetch user data. This suggests the user data retrieval logic might be incomplete or requires further implementation.

Dependencies

  • Requires an API authentication token credential for the Tiny ERP API.
  • Makes HTTP GET requests to the Tiny ERP API endpoints.
  • Needs proper configuration of the API token credential in n8n to authenticate requests.

Troubleshooting

  • No real user data returned: The node currently returns only a success message with the filter parameters without fetching actual user data. Ensure the API endpoint and request logic for user data retrieval are correctly implemented.
  • API errors: If the API returns errors, they will be caught and included in the output under an error field with the error message and stack trace.
  • Credential issues: Make sure the API token credential is set up correctly; otherwise, requests will fail due to authentication errors.
  • Empty username filter: Providing an empty string as the username filter may lead to unexpected results depending on the API's handling of empty filters.

Links and References

Discussion