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 "Magnet Customer" node integrates with the Magnet Customer API to manage various CRM-related resources such as customers, deals, leads, prospects, organizations, tasks, staff, pipelines, and custom fields. Specifically, for the Customer resource with the Get Many operation, this node retrieves multiple customer records from the Magnet Customer system.
This node is beneficial in scenarios where you need to fetch bulk customer data for analysis, reporting, synchronization with other systems, or automation workflows. For example, you might use it to:
- Retrieve a list of all customers to update a marketing database.
- Fetch customers with pagination to process them in batches.
- Automatically pull customer data into a dashboard or CRM analytics tool.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: API Token, OAuth2. |
| Page | The page number of results to retrieve (used for pagination). |
| Limit | Maximum number of customer 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 "Life Cycle" and "Source" exist but are not user-configurable and serve internal purposes.
Output
The node outputs an array of JSON objects representing customer records retrieved from the Magnet Customer API. Each object contains customer data fields as provided by the API.
If the Resolve Custom Fields option is enabled, custom fields within each customer record will be expanded to show human-readable names and values rather than just IDs.
The node does not output binary data.
Dependencies
- Requires access to the Magnet Customer API.
- Requires either an API token credential or OAuth2 authentication configured in n8n.
- No additional external dependencies beyond the Magnet Customer API and proper credentials.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Requesting pages or limits outside valid ranges may result in empty responses or errors.
- If custom fields are not resolved correctly, ensure the "Resolve Custom Fields" option is enabled.
Error Messages:
- Authentication errors typically indicate invalid or expired API tokens or OAuth2 tokens. Re-authenticate or update credentials.
- Rate limiting or API quota exceeded errors require checking Magnet Customer API usage limits.
- Network or connectivity errors suggest verifying internet connection and API endpoint accessibility.
Links and References
- Magnet Customer API Documentation (example placeholder, replace with actual URL if known)
- n8n Documentation on Creating Custom Nodes
- OAuth2 and API Token Authentication best practices in n8n
This summary focuses on the "Customer" resource with the "Get Many" operation based on the provided source code and property definitions.