Magnet Customer

Overview

This node integrates with the Magnet Customer API to manage various CRM-related resources, including pipelines. Specifically, for the Pipeline - Delete operation, it allows users to delete a pipeline by specifying its unique ID. This is useful in scenarios where obsolete or incorrect sales pipelines need to be removed from the system to maintain data accuracy and streamline sales processes.

Practical examples include:

• Automatically deleting a pipeline after a project completion.
• Removing test or duplicate pipelines created during data imports or testing phases.
• Cleaning up pipelines that are no longer relevant due to changes in business strategy.

Properties

Note: There are several hidden properties related to "Life Cycle" and "Source" in the provided JSON, but they are not relevant to the Pipeline Delete operation and appear to be related to other resources.

Output

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

The structure generally looks like:

[
  {
    "json": {
      // API response fields confirming deletion or error details
    },
    "pairedItem": {
      "item": <index_of_input_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 depends on internal helper functions to make HTTP requests to the API endpoints.

Troubleshooting

• Common Issues:

  • Invalid or missing Pipeline ID: Ensure the pipeline 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": "Pipeline not found": The specified pipeline ID does not exist. Double-check the ID.
  • "error": "Unauthorized": Authentication failed. Reconfigure credentials.
  • Other HTTP errors (e.g., 400, 500): Review API documentation and logs for more details.

To resolve these, confirm input parameters, reauthenticate if needed, and ensure the API service is operational.

Links and References

• Magnet Customer API Documentation (Assumed URL, replace with actual if known)
• n8n Documentation on Creating Custom Nodes
• OAuth2 and API Token Authentication best practices in n8n

If you need further details about other operations or resources, feel free to ask!