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, enabling automation workflows to manage various CRM entities such as deals, organizations, people, tasks, funnels, products, users, and system data. Specifically for the Negócio (Deal) resource and the Atualizar (Update) operation, the node updates an existing deal record in Agendor by its unique ID.
Typical use cases include:
- Automatically updating deal information based on external triggers or data changes.
- Synchronizing deal details from other systems into Agendor.
- Enriching deal records with additional fields like description, value, email, or phone number.
For example, a sales automation workflow could update the value and description of a deal when a new quote is generated in another system.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the deal record to update. |
| Campos Adicionais | Additional optional fields to update on the deal: |
| - Descrição: Description of the deal. | |
| - Valor: Monetary value of the deal in Brazilian reais. | |
| - E-mail: Email address associated with the deal. | |
| - Telefone: Phone number associated with the deal. |
Output
The node outputs the updated deal data as JSON. The output structure corresponds to the updated deal object returned by the Agendor API after the update operation. It includes all standard and custom fields that were updated or present on the deal.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Agendor CRM API via an API key credential configured in n8n.
- The node uses HTTP requests to Agendor endpoints to perform operations.
- Proper permissions on the API key are necessary to update deal records.
Troubleshooting
Common issues:
- Invalid or missing deal ID will cause the update to fail.
- Insufficient API permissions can result in authorization errors.
- Providing invalid field values (e.g., non-numeric value for "Valor") may cause request rejection.
- Network connectivity problems can prevent API communication.
Error messages and resolutions:
"Not Found"or similar indicates the deal ID does not exist; verify the ID."Unauthorized"or"Forbidden"suggests API credentials lack required permissions; check API key scopes.- Validation errors from the API usually specify which field is incorrect; adjust input accordingly.
- Timeout or network errors require checking internet connection and API availability.
Links and References
- Agendor API Documentation (official API docs for reference)
- n8n Documentation (for configuring credentials and using nodes)