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" (contact) data. Specifically, the Get Many operation retrieves multiple person records from the CRM system. It supports filtering, pagination, and sorting of results, making it useful for workflows that need to list or process batches of contacts.
Common scenarios include:
- Exporting a filtered list of contacts for marketing campaigns.
- Synchronizing contact data with other systems.
- Generating reports based on contact attributes or creation dates.
For example, you could use this node to fetch all contacts whose names contain "João Silva", ordered by creation date descending, retrieving 50 contacts per page.
Properties
| Name | Meaning |
|---|---|
| Options | A collection of parameters to control the query: |
| - Order By | Field to sort results by: ID, Name, Created At, or Updated At |
| - Order Direction | Sort direction: Ascending or Descending |
| - Page | Page number to retrieve (minimum 1) |
| - Per Page | Number of items per page (1 to 100) |
| - Search | Search term to filter persons by name or other searchable fields |
Output
The node outputs JSON data containing an array of person objects retrieved from the Agendor API. Each object represents a person/contact with their details as provided by the API.
The output structure typically includes fields such as:
id: Unique identifier of the person.name: Person's full name.- Other metadata fields like creation and update timestamps.
No binary data is output by this operation.
Dependencies
- Requires an API authentication token credential for the Agendor CRM API.
- The node sends requests to the base URL:
https://api.agendor.com.br/v3. - Proper configuration of the API token in n8n credentials is necessary.
Troubleshooting
- Empty results: Ensure the search term matches existing contacts or adjust pagination parameters.
- Invalid page or perPage values: Use valid numbers within allowed ranges (page ≥ 1, perPage between 1 and 100).
- Authentication errors: Verify the API token credential is correctly set and has sufficient permissions.
- API rate limits: If many requests are made rapidly, the API may throttle; implement delays or retries as needed.
- Malformed search queries: Avoid special characters or unsupported syntax in the search field.
Links and References
- Agendor API Documentation
- n8n Documentation on HTTP Request Nodes (for understanding API calls)
- Agendor CRM Official Website