Tiny ERP Auth2 icon

Tiny ERP Auth2

Interact with Tiny ERP API v3 with OAuth2

Actions21

Contatos → Update

AI-generated

Overview

This node integrates with the Tiny ERP API v3 using OAuth2 authentication to perform operations on various resources within the ERP system. Specifically, for the Contatos resource and the Update operation, it updates an existing contact's information in the ERP database.

Typical use cases include:

  • Keeping contact records up-to-date by modifying details such as address, phone number, or email.
  • Automating synchronization of contact data from other systems into Tiny ERP.
  • Correcting or enriching contact information programmatically without manual entry.

For example, a user might update a contact’s phone number and email after receiving new information from a CRM system, ensuring that the ERP always has current contact details.

Properties

Name Meaning
ID The unique identifier of the contact to update.
Additional Fields Optional fields to update on the contact. Can include:
- Address (endereco)
- City (cidade)
- Document number (cpf_cnpj) — CPF or CNPJ
- Email (email)
- Name (nome)
- Phone (telefone)
- State (uf)
- ZIP Code (cep)

The "Additional Fields" collection allows specifying any subset of these properties to update on the contact.

Output

The node outputs JSON objects representing the updated contact data returned from the Tiny ERP API. Each output item corresponds to one updated contact record.

The structure of the json output field matches the contact resource schema as returned by the API, including all updated fields.

No binary data output is produced by this node.

Dependencies

  • Requires an OAuth2 API credential configured in n8n to authenticate with the Tiny ERP API.
  • Depends on the Tiny ERP API v3 being accessible and the authenticated user having permissions to update contacts.
  • The node uses an internal OperationFactory to handle resource-specific logic, but this is abstracted away from the user.

Troubleshooting

  • Common issues:

    • Invalid or missing contact ID will cause the update to fail.
    • Providing invalid field values (e.g., malformed email or document number) may result in API errors.
    • Authentication failures if the OAuth2 token is expired or misconfigured.
    • Network or API downtime can cause request failures.

  • Error messages:

    • "Unknown resource: contatos" — indicates a misconfiguration or typo in the resource name.
    • API error messages related to validation or permission issues are passed through; check the message for details.

  • Resolutions:

    • Ensure the contact ID exists and is correct.
    • Validate input fields before sending.
    • Refresh or reconfigure OAuth2 credentials if authentication errors occur.
    • Check network connectivity and API status.

Links and References

Discussion