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 to manage "Pessoa" (Person) records, specifically supporting the Atualizar (Update) operation. It allows users to update existing person records in Agendor by specifying the record ID and any fields to modify.
Typical use cases include:
- Updating contact details such as email or phone number for a person.
- Modifying descriptive information or custom values related to a person.
- Keeping CRM data synchronized with other systems by updating person records programmatically.
For example, you might use this node to update a person's email address after receiving new contact information from a form submission or another database.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the person record to update in Agendor. |
| Campos Adicionais | Additional fields to update on the person record. Options include: |
| - Descrição: Description of the person record. | |
| - Valor: Numeric value in Brazilian reais (used for business-related data). | |
| - E-mail: Email address of the person. | |
| - Telefone: Phone number of the person. |
Output
The node outputs JSON data representing the updated person record as returned by the Agendor API. This typically includes all fields of the person after the update, reflecting the changes made.
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 ID: The update operation requires a valid person ID; ensure it is correct and exists in Agendor.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Field validation errors: Ensure additional fields conform to expected formats (e.g., numeric values for "Valor", valid email format).
Error messages:
"error": "Not Found": The specified person ID does not exist."error": "Unauthorized": API key is invalid or missing."error": "Bad Request": One or more fields have invalid values or are malformed.
To resolve these, double-check input parameters, confirm API credentials, and review field formats.
Links and References
- Agendor API Documentation (official API docs for reference)
- n8n Documentation (for general usage of nodes and credentials)