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 node integrates with the Magnet Customer API to retrieve detailed information about organizations. Specifically, the "Get" operation for the "Organization" resource fetches data for a single organization by its unique ID. This is useful in scenarios where you need to enrich workflows with up-to-date organizational details from your CRM or customer management system.
Practical examples include:
- Fetching an organization's profile before creating a related deal or task.
- Retrieving organization data to personalize communications or reports.
- Using organization details to trigger conditional logic in automation workflows.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: "API Token" or "OAuth2". |
| Organization ID | The unique identifier of the organization to retrieve. Required for the "Get" operation. |
| Resolve Custom Fields | When enabled, custom fields returned as IDs are automatically resolved to their actual names and values. Defaults to false. |
Note: Several hidden properties related to "Life Cycle" and "Source" exist but are not relevant for this operation as they are hidden and have default fixed values.
Output
The output JSON contains the full details of the requested organization as returned by the Magnet Customer API. This includes standard organization fields plus any custom fields associated with it.
If the "Resolve Custom Fields" option is enabled, custom field IDs and option IDs within the organization data are replaced with their corresponding human-readable names and values, making the output easier to interpret.
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.
- No additional external dependencies beyond the API and credentials.
Troubleshooting
- Missing or invalid Organization ID: The operation requires a valid organization ID. Ensure the ID is correct and exists in the Magnet Customer system.
- Authentication errors: Verify that the API token or OAuth2 credentials are correctly set up and have sufficient permissions.
- Custom fields not resolving: If custom fields appear as IDs despite enabling "Resolve Custom Fields," check if the API user has access to custom field metadata.
- API rate limits or connectivity issues: Network problems or API limits may cause failures; retry or check API status.
Common error messages will typically indicate missing parameters, authentication failures, or resource not found errors. Resolving these involves verifying input parameters and credential configurations.
Links and References
- Magnet Customer API Documentation (example placeholder link)
- n8n documentation on Credentials
- n8n documentation on Creating Custom Nodes