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 manage organizations data. Specifically, the "Organization - Create" operation allows users to create a new organization record in their Agendor CRM account by providing essential details such as the organization's name and optional additional information.
Common scenarios where this node is beneficial include:
- Automating the creation of new client or partner organizations when onboarding through other systems.
- Synchronizing organization data from external databases or forms into Agendor CRM.
- Streamlining sales or customer management workflows by programmatically adding organizations.
Practical example:
- When a new company fills out a contact form on your website, you can use this node to automatically create an organization entry in Agendor CRM with the provided company name, address, CNPJ (Brazilian company registration number), phone, and website.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the organization to be created. Example: "Empresa ABC Ltda" |
| Additional Fields | Optional extra fields to provide more details about the organization. These include: |
| - Address | Full address of the organization. Example: "Rua das Flores, 123 - São Paulo/SP" |
| - CNPJ | Brazilian company registration number (only digits). Example: "12345678000199" |
| - Description | Additional descriptive details about the organization |
| - Phone | Phone number of the organization. Example: "(11) 99999-9999" |
| - Website | URL of the organization's website. Example: "https://www.exemplo.com.br" |
Note: Some additional fields like CPF, Deal ID, Person ID, User ID are defined but not applicable for the Organization resource's create operation.
Output
The node outputs JSON data representing the newly created organization object as returned by the Agendor API. This typically includes the organization's unique ID, name, and any other properties stored in Agendor after creation.
No binary data output is involved in this operation.
Dependencies
- Requires an API authentication token credential for Agendor CRM.
- The node makes HTTP POST requests to the Agendor API endpoint
/organizations. - The base URL used is
https://api.agendor.com.br/v3. - Proper configuration of the API token credential in n8n is necessary for successful authentication.
Troubleshooting
- Missing Required Fields: If the "Name" property is empty, the API will reject the request. Ensure the organization name is provided.
- Invalid CNPJ Format: The CNPJ field must contain only numbers; including letters or special characters may cause errors.
- Authentication Errors: If the API token is invalid or missing, the node will fail with authorization errors. Verify the API key credential setup.
- API Rate Limits: Excessive requests might lead to rate limiting by Agendor API. Implement retries or delays if needed.
- Network Issues: Connectivity problems can cause request failures. Check network access to
api.agendor.com.br.
Links and References
- Agendor API Documentation (official API docs)
- Agendor CRM Website