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
Customer → Get Many
AI-generatedOverview
This node interacts with the Magnet Customer API to retrieve multiple customer records. It supports pagination and allows users to specify the number of results per page. Additionally, it offers an option to resolve custom fields, which by default are returned as IDs, into their actual names and values for better readability. This node is useful for scenarios where bulk customer data retrieval is needed, such as syncing customer databases, generating reports, or integrating customer data into other systems.
Use Case Examples
- Retrieve a list of customers with a limit of 15 per page.
- Fetch all customers and automatically resolve custom fields to their names and values.
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 results to retrieve when getting multiple customers. |
| Limit | Sets the maximum number of customer records to return per request, with a minimum value of 15. |
| Resolve Custom Fields | If enabled, custom fields returned as IDs are automatically resolved to their actual names and option fields to their actual values for better clarity. |
Output
JSON
_id- Unique identifier of the customer.fullname- Full name of the customer.email- Email address of the customer.phone- Phone number of the customer.
customField_ - Custom fields associated with the customer, resolved to their actual names and values if the resolveCustomFields option is enabled.
Dependencies
- Magnet Customer API
Troubleshooting
- Common issues include authentication failures due to incorrect API tokens or OAuth2 credentials. Verify credentials and permissions.
- If the resolveCustomFields option is enabled but custom fields fail to resolve, it may be due to API changes or missing custom field definitions. Check API responses and update custom field mappings accordingly.
- Pagination parameters (page and limit) must be set correctly to avoid empty or incomplete data sets.