Actions34
- Activity Actions
- Deal Actions
- Funnel Actions
- Organization Actions
- Person Actions
- Product Actions
- Tag Actions
- User Actions
Overview
This node integrates with the Agendor CRM API to update information about a person (contact) in the CRM system. It allows users to modify existing person records by specifying the person's ID and updating fields such as name, email, and other optional details like phone number or CPF (Brazilian individual taxpayer registry identification).
Common scenarios where this node is beneficial include:
- Keeping contact information up-to-date automatically from other systems.
- Enriching CRM data with additional details collected elsewhere.
- Correcting or modifying contact details based on new inputs.
Practical example:
- After receiving updated contact info from a web form, use this node to update the corresponding person record in Agendor CRM by providing the person ID and new values for name, email, and other fields.
Properties
| Name | Meaning |
|---|---|
| Person ID | The unique numeric identifier of the person to update. |
| Name | The full name of the person. |
| The person's email address. Must be a valid email format. | |
| Additional Fields | Optional extra fields to update: |
| - Address | Full address of the person. |
| - CPF | Brazilian individual taxpayer registry number (only digits). |
| - Phone | Phone number of the person. |
| - Organization ID | ID of the organization related to the person. |
| - Description | Additional descriptive text about the person. |
| - Website | URL of the person's website (if applicable). |
Note: Some additional fields are shared with other resources but only relevant ones for "Person" resource are listed above.
Output
The node outputs JSON data representing the updated person object as returned by the Agendor API after the update operation. This typically includes all current fields of the person record, reflecting the changes made.
No binary data output is involved.
Dependencies
- Requires an API authentication token credential for Agendor CRM.
- The node makes HTTP PUT requests to the Agendor API endpoint
/people/{personId}. - The base URL used is
https://api.agendor.com.br/v3. - Proper API credentials must be configured in n8n for successful authentication.
Troubleshooting
- Invalid Person ID: If the provided person ID does not exist, the API will likely return a 404 error. Verify the ID is correct.
- Invalid Email Format: The email field has regex validation; entering an invalid email will cause validation errors before sending the request.
- Missing Required Fields: The person ID and name are required. Omitting these will prevent the request from being sent.
- Authentication Errors: Ensure the API token credential is correctly set up and has sufficient permissions.
- API Rate Limits: Frequent updates may hit API rate limits; handle such errors by retrying after some delay.