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 an existing organization. It allows users to modify key details such as the organization's name, address, tax identifiers (CNPJ), website, and phone number. This operation is useful for keeping organizational data current in your CRM system, ensuring that contact and company records reflect the latest information.
Practical examples:
- Updating a company's address after relocation.
- Correcting or adding the official tax ID (CNPJ) of an organization.
- Changing the organization's website URL or phone number.
- Renaming the organization due to rebranding.
Properties
| Name | Meaning |
|---|---|
| Organization ID | The numeric ID of the organization to update (required). |
| Name | The new name of the organization (required). |
| Additional Fields | Optional extra fields to update, including: |
| - Address | Full address of the organization. |
| - CNPJ | Tax identification number of the organization (numbers only). |
| - Website | URL of the organization's website. |
| - Phone | Phone number of the organization. |
Output
The node outputs JSON data representing the updated organization object returned by the Agendor API. This typically includes all the organization's properties such as its ID, name, address, CNPJ, website, phone, and timestamps for creation and last update.
No binary data output is involved.
Dependencies
- Requires an API authentication token credential configured in n8n to authorize requests to the Agendor CRM API.
- The base URL for API requests is
https://api.agendor.com.br/v3. - The node sends HTTP PUT requests to the endpoint
/organizations/{organizationId}with the updated data in the request body.
Troubleshooting
- Missing or invalid Organization ID: The update will fail if the provided organization ID does not exist or is malformed. Ensure the ID is correct and corresponds to an existing organization.
- Required fields missing: The "Name" field is mandatory; omitting it will cause an error.
- API authentication errors: If the API token is invalid or missing, the request will be rejected. Verify that the API key credential is correctly set up.
- Validation errors on fields: For example, the CNPJ must contain only numbers; providing invalid formats may cause the API to reject the update.
- Network issues: Connectivity problems can prevent the node from reaching the Agendor API.
Links and References
- Agendor API Documentation (for detailed API endpoints and data models)
- n8n Documentation (for general usage of custom nodes and credentials)