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 sales funnels. Specifically, the "Funnel" resource with the "Get Many" operation allows users to retrieve a list of sales funnels from their Agendor account. This is useful for scenarios where you want to display, analyze, or process multiple sales funnels programmatically.
Practical examples include:
- Fetching all sales funnels to generate reports on pipeline stages.
- Synchronizing funnel data with other systems like marketing automation or analytics platforms.
- Filtering and sorting funnels based on creation date or name to prioritize sales efforts.
Properties
| Name | Meaning |
|---|---|
| Options | Collection of parameters to customize the retrieval of funnels: |
| - Order By | Field to sort the results by. Options: ID, Name, Created At, Updated At |
| - Order Direction | Direction of sorting. Options: Ascending, Descending |
| - Page | Page number to retrieve (pagination) |
| - Per Page | Number of items per page (max 100) |
| - Search | Search term to filter funnels by name or other searchable fields |
Output
The node outputs JSON data containing an array of funnel objects retrieved from the Agendor API. Each funnel object typically includes properties such as its unique ID, name, creation date, update date, and possibly other metadata related to the sales funnel.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token credential for Agendor CRM.
- The node makes HTTP GET requests to the Agendor API endpoint
/funnels. - Proper configuration of the API token in n8n credentials is necessary for successful requests.
Troubleshooting
Common Issues:
- Invalid or missing API token will cause authentication errors.
- Requesting pages beyond available data may return empty results.
- Using invalid values for "Order By" or "Order Direction" could lead to API errors.
Error Messages:
- Authentication failures usually indicate issues with the API token; verify and update credentials.
- Rate limiting errors from the API suggest too many requests in a short time; implement delays or retries.
- Validation errors on query parameters mean some options are incorrectly set; check property values.
Links and References
- Agendor API Documentation (official API docs for further details)
- n8n Documentation (for general usage of nodes and credentials)