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 retrieve multiple deals (business opportunities) from the system. The "Get Many" operation under the "Deal" resource allows users to list deals with various filtering and sorting options. This is useful for scenarios where you want to fetch a paginated list of deals, optionally filtered by search terms, and ordered by specific fields.
Practical examples include:
- Retrieving all deals created or updated recently to analyze sales pipeline status.
- Fetching deals matching a customer name or keyword to generate reports.
- Paginating through large deal datasets for batch processing or synchronization with other systems.
Properties
| Name | Meaning |
|---|---|
| Options | Collection of optional parameters to customize the retrieval of deals: |
| - Order By | Field to order results by: ID, Name, Created At, Updated At |
| - Order Direction | Direction of ordering: Ascending or Descending |
| - Page | Page number to retrieve (minimum 1) |
| - Per Page | Number of items per page (minimum 1, maximum 100) |
| - Search | Search term to filter deals by (e.g., customer name or keywords) |
Output
The node outputs JSON data containing an array of deal objects retrieved from the Agendor API. Each deal object includes details such as its ID, title, value, related organization and person IDs, creation and update timestamps, and other relevant metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token credential for the Agendor CRM API.
- The node sends HTTP GET requests to the endpoint
/dealson the base URLhttps://api.agendor.com.br/v3. - Query parameters are used to pass pagination, ordering, and search filters.
Troubleshooting
- Empty Results: If no deals are returned, verify that the search term and filters are correct and that there are deals matching those criteria in your Agendor account.
- Invalid Pagination: Ensure the "Page" and "Per Page" values are within allowed ranges (Page ≥ 1, Per Page between 1 and 100).
- Authentication Errors: Confirm that the API token credential is valid and has sufficient permissions.
- API Rate Limits: If many requests are made rapidly, the API might throttle; implement retries or delays if needed.