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 people, deals, organizations, tasks, products, and more. Specifically for the Pessoa (Person) resource with the Criar (Create) operation, the node allows users to create a new person record in Agendor by providing essential details like the person's name and optional additional fields.
Typical use cases include:
- Automatically adding new contacts collected from web forms or other sources into Agendor.
- Creating person records as part of lead generation or customer onboarding workflows.
- Enriching CRM data by programmatically inserting detailed contact information.
Example: When a new lead fills out a signup form, this node can create a corresponding person entry in Agendor with their name, email, phone number, and description.
Properties
| Name | Meaning |
|---|---|
| Nome | The full name of the person to be created. |
| Campos Adicionais | Additional optional fields to enrich the person record. Includes: |
| - Descrição: Description or notes about the person. | |
| - Valor: Monetary value associated (in reais), typically for business context. | |
| - E-mail: Email address of the person. | |
| - Telefone: Phone number of the person (numbers only). |
Output
The node outputs JSON data representing the newly created person record as returned by the Agendor API. This includes all fields sent during creation plus any additional data assigned by the system (such as unique IDs).
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Agendor CRM API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node uses internal helper functions to make HTTP requests to Agendor endpoints.
Troubleshooting
Common issues:
- Missing required "Nome" property will cause the API request to fail.
- Invalid or expired API credentials will result in authentication errors.
- Providing invalid formats for fields like phone or email may cause validation errors from the API.
Error messages:
- Authentication failures: Check that the API key credential is correctly set up and valid.
- Validation errors: Ensure required fields are filled and optional fields conform to expected formats.
- Network errors: Verify network connectivity and that the Agendor API endpoint is reachable.
Links and References
- Agendor API Documentation (official API docs)
- n8n Documentation (for general usage of custom nodes and credentials)