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 "Person" resources, specifically enabling the creation of new person records in the CRM system. It is useful for automating contact management workflows, such as adding new leads or contacts collected from forms, other systems, or manual input into the CRM without manual data entry.
Practical examples include:
- Automatically creating a new contact when a lead form is submitted on a website.
- Syncing contacts from another database or application into Agendor CRM.
- Adding people programmatically during sales or marketing automation processes.
Properties
| Name | Meaning |
|---|---|
| Name | The full name of the person to be created (e.g., "João Silva"). |
| The email address of the person (must be a valid email format, e.g., "joao@empresa.com"). | |
| Additional Fields | A collection of optional fields to provide more details about the person: |
| - Address | Full address of the person (e.g., "Rua das Flores, 123 - São Paulo/SP"). |
| - CPF | Brazilian individual taxpayer registry identification number (only numbers). |
| - Organization ID | ID of the organization related to this person. |
| - Phone | Phone number of the person (e.g., "(11) 99999-9999"). |
Note: Some additional fields are shared with other resources but only relevant ones for "Person" are listed here.
Output
The node outputs JSON data representing the newly created person record as returned by the Agendor API. This typically includes the person's unique ID, name, email, and any other fields accepted by the API.
No binary data output is involved.
Dependencies
- Requires an API authentication token credential configured in n8n to access the Agendor CRM API.
- The node sends HTTP POST requests to
https://api.agendor.com.br/v3/peopleendpoint. - Proper network connectivity to the Agendor API service is necessary.
Troubleshooting
- Invalid Email Format: If the email does not match the required regex pattern, the node will reject the input before sending the request. Ensure emails are correctly formatted.
- Missing Required Fields: The "Name" field is mandatory. Omitting it will cause the API to return an error.
- Authentication Errors: If the API token is missing or invalid, the API will respond with an authorization error. Verify that the API key credential is correctly set up.
- API Rate Limits or Downtime: Temporary failures may occur if the Agendor API is down or rate limits are exceeded. Retry after some time or check API status.
- Incorrect Field Types: Providing non-string values where strings are expected may cause errors.
Links and References
- Agendor API Documentation (for detailed API endpoints and data models)
- n8n Documentation (for general usage of custom nodes and credentials)
This summary is based solely on static analysis of the provided source code and property definitions.