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
This node integrates with the Magnet Customer API to retrieve multiple organization records. The "Get Many" operation for the "Organization" resource fetches a list of organizations, supporting pagination and limiting the number of results returned. This is useful in scenarios where you want to bulk import or synchronize organization data from Magnet Customer into your workflow, such as generating reports, updating CRM systems, or triggering downstream automation based on organizational data.
Practical examples:
- Fetching all organizations to update a marketing database.
- Retrieving a limited set of organizations for batch processing or analysis.
- Automatically syncing organization data into another system on a schedule.
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 organization 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 in this context.
Output
The output is a JSON array where each item represents an organization object retrieved from the Magnet Customer API. Each organization object contains standard organization fields plus any custom fields. If "Resolve Custom Fields" is enabled, custom fields will be resolved to their human-readable names and values rather than just IDs.
No binary data is output by this node.
Dependencies
- Requires access to the Magnet Customer API.
- Requires either an API token or OAuth2 credentials configured in n8n for authentication.
- Pagination parameters ("Page" and "Limit") control how many records are fetched per execution.
Troubleshooting
- Empty Results: If no organizations are returned, verify that the account has organizations available and that pagination parameters are correct.
- Authentication Errors: Ensure the API token or OAuth2 credentials are valid and have sufficient permissions.
- Limit Too Low: The minimum limit is 15; setting lower may cause errors or unexpected behavior.
- Custom Field Resolution Issues: If enabling "Resolve Custom Fields" causes errors, check if custom fields exist and are accessible via the API.
Common error messages typically relate to authentication failures, invalid parameters, or API rate limits. Resolving these involves verifying credentials, adjusting input parameters, or consulting Magnet Customer API documentation.
Links and References
- Magnet Customer API Documentation (example link)
- n8n Documentation on Creating Custom Nodes
- OAuth2 and API Token Authentication best practices in n8n