Actions19
- Negócio Actions
- Empresa Actions
- Pessoa Actions
- Tarefa Actions
- Produto Actions
- Usuário Actions
- Sistema Actions
Overview
This node integrates with the Agendor CRM platform, allowing users to perform various operations on different resources such as deals, organizations (companies), people, tasks, funnels, products, users, and system data. Specifically for the Empresa (Organization) resource with the Atualizar (Update) operation, the node updates an existing company record in Agendor.
Typical use cases include automating updates to company information within a CRM workflow, such as modifying contact details, descriptions, or financial values associated with a company. For example, when a company's phone number or email changes, this node can update those fields automatically based on input data from other systems or triggers.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the company record to update. |
| Campos Adicionais | Additional optional fields to update on the company record: |
| - Descrição | Description of the company. |
| - Valor | Monetary value in Brazilian reais related to the company (e.g., business value). |
| Email address associated with the company. | |
| - Telefone | Phone number of the company. |
Output
The node outputs JSON data representing the updated company record as returned by the Agendor API. This typically includes all the fields of the company after the update, reflecting the new state.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Agendor CRM API.
- Needs an API authentication credential configured in n8n to authorize requests to Agendor.
- The node uses internal helper functions to make HTTP requests to Agendor endpoints.
Troubleshooting
Common issues:
- Invalid or missing company ID will cause the update to fail.
- Incorrect API credentials or expired tokens will result in authentication errors.
- Providing invalid field formats (e.g., non-numeric value for "Valor") may cause request rejection.
Error messages:
"ID do registro" is required— Ensure the company ID is provided.- Authentication errors — Verify API key or token validity and permissions.
- Validation errors from Agendor API — Check that additional fields conform to expected types and constraints.
Resolving these usually involves verifying input parameters, ensuring correct credentials, and confirming API access rights.
Links and References
- Agendor API Documentation (official API docs for reference on endpoints and data structures)
- n8n Documentation (for general guidance on using and configuring nodes)