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, enabling automation workflows to manage various CRM entities such as deals, organizations (companies), people, tasks, funnels, products, users, and system data. Specifically for the Empresa (Organization) resource with the Criar (Create) operation, the node allows you to create a new company record in Agendor.
Typical use cases include:
- Automatically adding new companies from lead capture forms or external databases into Agendor.
- Syncing company data from other systems into Agendor to maintain up-to-date CRM records.
- Enriching company profiles by adding additional details during creation.
For example, you could use this node to create a new company with its name, description, email, phone number, and custom value fields directly from an automated workflow triggered by a form submission.
Properties
| Name | Meaning |
|---|---|
| Nome | The name of the company to be created. |
| Campos Adicionais | Additional optional fields to enrich the company record: |
| - Descrição: Description of the company. | |
| - Valor: Monetary value in Brazilian reais (used mainly for deals but available here). | |
| - E-mail: Email address associated with the company. | |
| - Telefone: Phone number of the company. |
Output
The node outputs JSON data representing the newly created company record as returned by the Agendor API. This typically includes all the properties of the company such as its unique ID, name, description, contact details, and any other fields accepted by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Agendor CRM API via an API key credential configured in n8n.
- The node uses HTTP requests to Agendor endpoints; therefore, internet access and valid API credentials are mandatory.
- No additional external dependencies beyond the Agendor API and n8n's credential management.
Troubleshooting
Common issues:
- Missing required "Nome" property will cause the API request to fail.
- Invalid or expired API credentials will result in authentication errors.
- Network connectivity problems can prevent communication with the Agendor API.
- Providing invalid formats for fields like email or phone may cause validation errors.
Error messages and resolutions:
- Authentication failed: Check that the API key credential is correctly set up and has necessary permissions.
- Validation error: Ensure all required fields are provided and formatted correctly.
- Network timeout or unreachable host: Verify network connectivity and Agendor service status.
- Unexpected API response: Confirm that the API endpoint and payload conform to Agendor's current API specification.
Links and References
- Agendor API Documentation (official API docs for reference on endpoints and data structures)
- n8n Documentation (for general guidance on using credentials and nodes)