Actions104
- Custom Field Actions
- Custom Field Block Actions
- Custom Field Type Actions
- Customer Actions
- Deal Actions
- Lead Actions
- Meeting Actions
- Meeting Room Actions
- Meeting Type Actions
- Organization Actions
- Pipeline Actions
- Prospect Actions
- Staff Actions
- Task Actions
- Ticket Actions
- Treatment Actions
- Treatment Type Actions
- Workspace Actions
Pipeline → Get Many
AI-generatedOverview
This node operation retrieves multiple pipeline records from the Magnet Customer API. It supports fetching all pipelines or a limited number based on user-defined parameters such as pagination, filtering, and sorting. This operation is useful for scenarios where you need to list or analyze multiple sales or project pipelines, for example, to display them in a dashboard or to process them in bulk for reporting or automation.
Use Case Examples
- Retrieve all pipelines without limit to get a complete list of pipelines in the system.
- Fetch a limited number of pipelines with specific filters such as presence of emails or phones, and sort them by creation date in descending order.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use for API requests, either API Token or OAuth2. |
| Return All | Whether to return all pipeline results or only up to a specified limit. |
| Limit | Maximum number of pipeline results to return when 'Return All' is false. |
| Page | Page number for paginated results when 'Return All' is false. |
| Filters | Filters to apply to the pipeline results, such as search term and presence of emails, phones, or interactions. |
| Sort | Sorting options for the pipeline results, including field to sort by and sort direction. |
Output
JSON
_id- Unique identifier of the pipeline.title- Title or name of the pipeline.createdAt- Timestamp when the pipeline was created.stages- List of stages within the pipeline.otherProperties- Additional properties returned by the API for each pipeline.
Dependencies
- Magnet Customer API
Troubleshooting
- Ensure correct authentication method is selected and credentials are valid to avoid authentication errors.
- If no pipelines are returned, check filter criteria and pagination settings to ensure they match expected data.
- API rate limits or connectivity issues may cause request failures; verify network and API status.