Magnet Customer icon

Magnet Customer

Consume Magnet Customer API

Deal → Get Many

AI-generated

Overview

This node interacts with the Magnet Customer API to retrieve multiple deal 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 means that instead of returning custom field IDs, it fetches and returns their actual names and values. This is useful for users who want detailed and human-readable deal information including custom fields.

Use Case Examples

  1. Retrieve a list of deals from the Magnet Customer system, specifying the page number and limit to control the number of deals returned.
  2. Fetch all deals and automatically resolve custom fields to get detailed deal information with custom field names and values instead of just IDs.

Properties

Name Meaning
Authentication Method of authentication to use for the API requests, either API Token or OAuth2.
Page The page number of results to retrieve when fetching multiple deals.
Limit The maximum number of deal results to return per request, with a minimum value of 15.
Resolve Custom Fields If enabled, custom fields in the deal data are resolved to their actual names and values instead of just returning their IDs.

Output

JSON

  • _id - Unique identifier of the deal.
  • title - Title or name of the deal.
    customField_ - Resolved custom fields with their actual names and values if 'Resolve Custom Fields' is enabled.
  • docs - Array of deal objects if the response is paginated.
  • data - Array of deal objects if the response is paginated.

Dependencies

  • Magnet Customer API

Troubleshooting

  • If the API authentication fails, check that the correct authentication method (API Token or OAuth2) is selected and that the credentials are valid.
  • If no deals are returned, verify that the page and limit parameters are set correctly and that there are deals available in the Magnet Customer system.
  • If custom fields are not resolved correctly, ensure that the 'Resolve Custom Fields' option is enabled and that the API has access to fetch custom field metadata.

Discussion