Actions68
- Custom Field Actions
- Custom Field Block Actions
- Custom Field Type Actions
- Customer Actions
- Deal Actions
- Lead Actions
- Organization Actions
- Pipeline Actions
- Prospect Actions
- Staff Actions
- Task Actions
- Workspace Actions
Overview
The "Deal - Get Many" operation in this node allows users to retrieve multiple deal records from the Magnet Customer API. This is useful for scenarios where you want to fetch a list of deals, such as generating reports, syncing deal data with other systems, or displaying deal pipelines in dashboards.
Practical examples include:
- Fetching all deals within a certain page or limit to analyze sales performance.
- Retrieving deals to update CRM records or trigger follow-up workflows.
- Extracting deal information for integration with marketing automation tools.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: "API Token", "OAuth2". |
| Page | The page number of results to retrieve (pagination). |
| Limit | Maximum number of deal records to return. Minimum value is 15. |
| Resolve Custom Fields | When enabled, custom fields are returned with their actual names and option values instead of IDs. |
Note: Several hidden properties related to "lifeCycle" and "source" exist but are not user-configurable in this operation context.
Output
The output is a JSON array where each item represents a deal object retrieved from the Magnet Customer API. Each deal includes standard deal fields and, optionally, resolved custom fields if the "Resolve Custom Fields" option is enabled.
If custom fields are not resolved, they appear as IDs rather than human-readable names or values.
The node does not output binary data.
Dependencies
- Requires access to the Magnet Customer API.
- Requires either an API token or OAuth2 credentials configured in n8n for authentication.
- Pagination support depends on the "page" and "limit" input parameters.
- Optional resolution of custom fields may require additional API calls internally.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Setting a "limit" below 15 might result in unexpected behavior or errors.
- If many custom fields exist, enabling "Resolve Custom Fields" could slow down execution due to extra API requests.
Error messages:
- Authentication errors typically indicate invalid or expired credentials; verify and update your API key or OAuth2 token.
- Rate limiting or API quota exceeded errors suggest too many requests; consider adding delays or reducing request frequency.
- Invalid parameter errors may occur if unsupported values are provided for "page" or "limit"; ensure these are valid numbers.
Links and References
- Magnet Customer API Documentation (example link)
- n8n documentation on creating custom nodes
- n8n community forums for troubleshooting and tips