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 manage custom field blocks, specifically supporting operations such as updating a custom field block. Custom field blocks are used to group related custom fields under a named section within features like contacts, deals, organizations, or staff. The "Update" operation allows users to modify properties of an existing custom field block, such as its name, position, feature association, and display settings.
Practical scenarios include:
- Reorganizing custom fields in a CRM by renaming or repositioning blocks for better clarity.
- Changing which feature (e.g., contact, deal) a custom field block belongs to.
- Adjusting whether a block is expanded by default or shown in summary views.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication: either "API Token" or "OAuth2". |
| Block ID | The unique identifier of the custom field block to update. |
| Name | The new name for the custom field block. |
| Feature | The feature this block belongs to; options are: "Contact", "Deal", "Organization", "Staff". |
| Position | Numeric position/order of the block relative to others. |
| Is Expanded | Boolean indicating if the block should be expanded by default in the UI. |
| Summary Display | Boolean indicating if the block should be displayed in summary views. |
Note: Several hidden properties related to "Life Cycle" and "Source" exist but are not user-configurable in this context.
Output
The node outputs JSON data representing the updated custom field block object returned from the Magnet Customer API. This typically includes the block's ID, name, feature, position, expansion state, and summary display flag, reflecting the changes made.
No binary data output is involved.
Dependencies
- Requires access to the Magnet Customer API.
- Requires valid credentials configured in n8n, either via an API token or OAuth2 authentication.
- The node depends on internal helper functions to make HTTP requests to the API endpoints corresponding to custom field blocks.
Troubleshooting
Common Issues:
- Invalid or missing Block ID will cause the update to fail.
- Insufficient permissions or invalid credentials will result in authentication errors.
- Providing invalid values for properties like "Feature" or "Position" may cause API validation errors.
Error Messages:
"error": "Block ID is required"— Ensure the Block ID property is set."error": "Authentication failed"— Verify API token or OAuth2 credentials."error": "Invalid feature value"— Use one of the allowed feature options.
Resolution Tips:
- Double-check all required fields before execution.
- Confirm that the API credentials have appropriate scopes/permissions.
- Review API documentation for valid property values and constraints.