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 user information. It allows you to modify details of an existing user by specifying their User ID and any additional fields you want to change. This is useful in scenarios where user data needs to be kept current, such as updating contact information, roles, or other user-specific attributes within your CRM system.
Practical examples include:
- Updating a user's phone number or email address after receiving new contact info.
- Changing user roles or permissions stored as custom fields.
- Correcting typos or adding missing details to user profiles.
Properties
| Name | Meaning |
|---|---|
| User ID | The numeric identifier of the user to update (required). |
| Additional Fields | A collection of optional fields to update for the user. These can include: |
| - Address | Full address (only applicable if resource is "people" or "organizations"). |
| - CNPJ | Organization's CNPJ number (numeric only, for organizations). |
| - CPF | Person's CPF number (numeric only, for people). |
| - Deal ID | ID of a related deal (not applicable for users directly, more for activities). |
| - Description | Additional descriptive text about the user. |
| - Organization ID | ID of the organization related to the user (varies by resource context). |
| - Person ID | ID of a person related to the user (varies by resource context). |
| - Phone | Phone number of the user (for people or organizations). |
| - Website | Website URL (for organizations). |
Note: For the "User" resource specifically, the main required property is the User ID. The "Additional Fields" collection is generic and may contain fields relevant to other resources; for updating users, typically only fields supported by the API for users should be included.
Output
The node outputs JSON data representing the updated user object returned from the Agendor API. This JSON includes all user properties after the update, reflecting the changes made.
No binary data output is involved.
Dependencies
- Requires an API authentication token credential configured in n8n to access the Agendor API.
- The base URL for API requests is
https://api.agendor.com.br/v3. - The node sends HTTP PUT requests to
/users/{userId}endpoint to perform updates.
Troubleshooting
- Missing or invalid User ID: The update operation requires a valid numeric User ID. Ensure this is provided and correctly formatted.
- API authentication errors: If the API token is missing or invalid, the request will fail. Verify that the API key credential is set up properly.
- Invalid field values: Sending unsupported or incorrectly formatted fields in "Additional Fields" may cause API errors. Refer to the Agendor API documentation for valid user fields.
- Network issues: Connectivity problems can prevent successful API calls. Check network settings and proxy configurations if applicable.
Common error messages might include:
- Unauthorized (401): Check API token validity.
- Not Found (404): User ID does not exist.
- Bad Request (400): Invalid input data format.
Links and References
- Agendor API Documentation (official API docs for reference on user update fields and endpoints)
- n8n Documentation (for general guidance on using credentials and HTTP request nodes)