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
Prospect → Get Many
AI-generatedOverview
This node interacts with the Magnet Customer API to retrieve multiple prospect records. It supports pagination and limiting the number of results returned, making it useful for scenarios where you need to fetch a list of prospects for further processing or analysis. For example, a user might use this node to pull a batch of prospects to update a CRM system or to analyze prospect data in bulk.
Use Case Examples
- Fetching the first 15 prospects from the Magnet Customer system.
- Retrieving a specific page of prospects to process in a workflow.
Properties
| Name | Meaning |
|---|---|
| Authentication | Selects the authentication method to use for the API requests, either API Token or OAuth2. |
| Page | Specifies the page number of the prospect list to retrieve, useful for pagination. |
| Limit | Sets the maximum number of prospect records to return in one request, with a minimum value of 15. |
| Resolve Custom Fields | If enabled, custom fields in the prospect data are resolved to their actual names and values instead of just IDs, providing more readable and meaningful data. |
Output
JSON
_id- Unique identifier of the prospect.name- Name of the prospect.email- Email address of the prospect.customFields- Custom fields associated with the prospect, resolved to actual names and values if the option is enabled.
Dependencies
- Magnet Customer API
- API Token or OAuth2 credentials
Troubleshooting
- Ensure the API credentials are correctly configured and have the necessary permissions to access prospect data.
- If the 'Resolve Custom Fields' option is enabled but custom fields do not resolve correctly, verify that the custom fields exist and the API supports resolving them.
- Pagination parameters (Page and Limit) must be valid numbers; otherwise, the API request may fail.