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 perform various operations on different resources related to customer relationship management. Specifically, for the Custom Field Block resource with the Get operation, it retrieves details of a custom field block by its ID. This is useful when you want to fetch metadata or configuration about a group of custom fields defined in the Magnet Customer system.
Practical scenarios include:
- Fetching the structure of a custom field block to dynamically build forms or UI elements.
- Retrieving custom field block information to synchronize or audit CRM configurations.
- Using the block data to map or transform data between systems during automation workflows.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: "API Token" or "OAuth2". |
| Block ID | The unique identifier of the custom field block to retrieve. |
| Life Cycle | (Hidden) The life cycle stage of the contact; preset values like "customer", "lead", etc. |
| Source | (Hidden) The source of the contact; defaulted to "n8n". |
Note: The properties Life Cycle and Source are hidden and preset internally, likely used for internal API request context but not exposed for user input.
Output
The node outputs JSON data representing the retrieved custom field block. The structure typically includes the block's metadata such as its ID, name, description, and the list of custom fields it contains. Each custom field may have attributes like type, label, options, and validation rules.
If the node supports binary data output (not indicated here), it would be summarized accordingly, but this node primarily returns structured JSON data.
Dependencies
- Requires an active connection to the Magnet Customer API.
- Needs either an API token credential or OAuth2 authentication configured in n8n.
- No additional external dependencies beyond the Magnet Customer API.
Troubleshooting
Common issues:
- Invalid or missing Block ID will cause the API call to fail.
- Authentication errors if API credentials are incorrect or expired.
- Network connectivity problems preventing access to the Magnet Customer API.
Error messages:
"error": "Invalid Block ID"— Verify that the Block ID is correct and exists."error": "Authentication failed"— Check API token or OAuth2 credentials.- Timeout or network errors — Ensure n8n server has internet access and Magnet Customer API is reachable.
Resolution tips:
- Double-check the Block ID input.
- Re-authenticate or refresh credentials.
- Test API connectivity outside n8n to isolate network issues.
Links and References
- Magnet Customer API Documentation (replace with actual URL)
- n8n documentation on Creating Custom Nodes
- OAuth2 and API Token authentication setup guides in n8n official docs.