Magnet Customer

Overview

This node integrates with the Magnet Customer API to manage various CRM-related resources, including custom fields. Specifically, for the Custom Field resource with the Delete operation, it allows users to delete a custom field by specifying its ID. This is useful in scenarios where you want to programmatically remove obsolete or incorrect custom fields from your CRM system to keep data clean and relevant.

Practical examples:

• Automatically deleting custom fields that are no longer needed after a data migration.
• Cleaning up test or temporary custom fields created during automation workflows.
• Managing custom fields lifecycle as part of a larger CRM maintenance process.

Properties

Note: The provided properties JSON includes some hidden properties related to "lifeCycle" and "source" which are not relevant for this operation and appear duplicated; they do not affect the Delete operation on Custom Field.

Output

The output of the node is a JSON array containing the response from the Magnet Customer API after attempting to delete the specified custom field. Typically, this will include confirmation of deletion or an error message if the deletion failed.

The json output field structure depends on the API response but generally contains status information about the deletion request.

This node does not output binary data.

Dependencies

• Requires access to the Magnet Customer API.
• Requires user to provide valid credentials via either an API token or OAuth2 authentication.
• The node uses internal helper functions to make HTTP requests to the Magnet Customer API endpoints.
• No additional external dependencies beyond the configured API credentials.

Troubleshooting

• Common issues:

  • Providing an invalid or non-existent Custom Field ID will result in an error from the API.
  • Insufficient permissions or invalid credentials can cause authentication failures.
  • Network connectivity issues may prevent successful API calls.

• Error messages and resolutions:

  • "Custom Field not found": Verify the Custom Field ID is correct and exists in the system.
  • "Authentication failed": Check that the API token or OAuth2 credentials are valid and have necessary permissions.
  • "Request timed out" or network errors: Ensure stable internet connection and that the Magnet Customer API endpoint is reachable.

• To handle errors gracefully, enable the node's "Continue On Fail" option to allow workflow execution to proceed even if deletion fails for some items.

Links and References

• Magnet Customer API Documentation (generic placeholder link)
• n8n documentation on Creating Custom Nodes
• OAuth2 and API Token authentication best practices

If you need details on other operations or resources, please provide their names.