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 Tarefa (Task) resource with the Atualizar (Update) operation, the node updates an existing task record in Agendor by sending updated field values.
Typical use cases include:
- Automating task updates based on external triggers or events.
- Synchronizing task information from other systems into Agendor.
- Modifying task details like description, email, phone, or value programmatically.
For example, you might update a task’s description and contact email after receiving new information from a customer support system.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the task record to update. |
| Campos Adicionais | Additional fields to update on the task. Options include: |
| - Descrição: Description of the task. | |
| - Valor: Monetary value in Brazilian reais (used mainly for deals but available here). | |
| - E-mail: Email address associated with the task. | |
| - Telefone: Phone number associated with the task. |
Output
The node outputs JSON data representing the updated task object returned from the Agendor API. This typically includes all current properties of the task after the update, such as its ID, title, description, contact info, and any other relevant fields.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Agendor CRM API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node uses internal helper functions to make HTTP requests to Agendor endpoints.
Troubleshooting
Common issues:
- Invalid or missing task ID will cause the update to fail.
- Providing unsupported or incorrectly formatted additional fields may result in API errors.
- Network or authentication failures can prevent communication with Agendor.
Error messages:
- Errors from the Agendor API are propagated; typical messages include "Not Found" if the task ID does not exist, or "Unauthorized" if credentials are invalid.
- To resolve, verify the task ID is correct, ensure required fields are provided, and confirm that API credentials are properly set up in n8n.
Links and References
- Agendor API Documentation (official API docs for reference)
- n8n Documentation (for general usage of custom nodes and credentials)