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 various CRM-related resources, including custom field blocks. Specifically, the Delete operation on the Custom Field Block resource allows users to remove a custom field block by its ID. This is useful when you want to clean up or reorganize your CRM data structure by deleting obsolete or unused custom field blocks.
Practical scenarios include:
- Automating cleanup of custom field blocks that are no longer needed.
- Managing CRM schema dynamically based on business rules.
- Integrating with workflows that require removal of specific custom field blocks after certain events.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: "API Token" or "OAuth2". |
| Block ID | The unique identifier of the custom field block to delete. |
Note: There are several hidden properties related to "Life Cycle" and "Source" in the provided JSON, but they are not relevant for this operation as per the code and are likely used internally or for other operations.
Output
The output is a JSON array where each item corresponds to the result of the delete operation for each input item. Typically, the output will contain confirmation of deletion or any returned data from the API about the deleted custom field block.
If an error occurs during deletion and "Continue On Fail" is enabled, the output will include an error object with the message describing the failure for that particular item.
No binary data output is involved in this operation.
Dependencies
- Requires access to the Magnet Customer API.
- Requires either an API token or OAuth2 credentials configured in n8n for authentication.
- The node uses internal helper functions to make HTTP requests to the Magnet Customer API endpoints.
Troubleshooting
Common issues:
- Invalid or missing Block ID: Ensure the Block ID provided exists and is correct.
- Authentication errors: Verify that the API token or OAuth2 credentials are valid and have sufficient permissions.
- Network or API downtime: Check connectivity and Magnet Customer API status.
Error messages:
"error": "Block ID not found"(example): Means the specified custom field block does not exist; verify the ID.- Authentication failures: Usually indicate invalid credentials; reconfigure the API key or OAuth2 token.
- Rate limiting or permission denied errors: May require adjusting API usage or user permissions.
Enabling "Continue On Fail" allows the workflow to proceed even if some deletions fail, returning error details in the output.
Links and References
- Magnet Customer API Documentation (generic placeholder link)
- n8n documentation on Creating Custom Nodes
- OAuth2 and API Token authentication setup guides in n8n
This summary is based solely on static analysis of the provided source code and property definitions.