Tiny ERP Auth2 icon

Tiny ERP Auth2

Interact with Tiny ERP API v3 with OAuth2

Actions21

Contatos → Create

AI-generated

Overview

This node integrates with the Tiny ERP API v3 using OAuth2 authentication to manage various resources within the ERP system. Specifically, for the Contatos (Contacts) resource with the Create operation, it allows users to add new contact entries into the ERP database.

Typical use cases include automating the creation of customer or supplier contacts from external systems, syncing contact data from CRM platforms, or bulk importing contacts into Tiny ERP. For example, a business could use this node to automatically create new client records when a lead is converted in their sales pipeline.

Properties

Name Meaning
Additional Fields A collection of optional fields to specify details about the contact:
- Address The contact's street address
- City The city where the contact is located
- Document CPF or CNPJ document number (Brazilian individual or company tax ID)
- Email Contact's email address
- Name Full name of the contact
- Phone Contact's phone number
- State State abbreviation (UF)
- ZIP Code Postal code (CEP)

These fields are all optional and can be provided as needed to enrich the contact record being created.

Output

The node outputs an array of JSON objects representing the newly created contact(s). Each output item contains the full response data returned by the Tiny ERP API for the created contact, including any assigned IDs or metadata.

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 create contacts.
  • The node uses an internal OperationFactory to handle different resources and operations dynamically.

Troubleshooting

  • Unknown resource error: If the node throws an error like Unknown resource: contatos, ensure that the resource name is correctly set to "contatos" and supported by the node version.
  • Authentication failures: Verify that the OAuth2 credentials are valid and have not expired. Re-authenticate if necessary.
  • API errors on create: If the API returns validation errors (e.g., missing required fields), check that the input properties meet the API requirements, especially mandatory fields like "nome" (Name).
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON under an error key.

Links and References

Discussion