Magnet Customer icon

Magnet Customer

Consume Magnet Customer API

Actions68

Overview

This node integrates with the Magnet Customer API to manage prospects, specifically allowing deletion of a prospect by its ID. It is useful in scenarios where you want to automate the removal of outdated or incorrect prospect records from your CRM system. For example, if a lead has been disqualified or merged into another record, this node can programmatically delete that prospect entry.

Properties

Name Meaning
Authentication Method of authenticating API requests; options are "API Token" or "OAuth2".
Contact ID (prospectId) The unique identifier of the prospect to delete. This is required for the delete operation on the Prospect resource.

Note: Several hidden properties related to "Life Cycle" and "Source" exist but are preset internally and not exposed for user input in this operation.

Output

The output JSON contains the response from the Magnet Customer API after attempting to delete the specified prospect. Typically, this will include confirmation of deletion or an error message if the deletion failed.

If an error occurs and the node is set to continue on failure, the output will contain an error field with the error message for the corresponding 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 API endpoints.

Troubleshooting

  • Common Issues:

    • Invalid or missing prospect ID: Ensure the Contact ID property is correctly set to the ID of an existing prospect.
    • 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": "Prospect not found": The provided prospect ID does not exist. Confirm the ID is correct.
    • Authentication failures typically return 401 or 403 errors. Recheck credentials.
    • If the node throws an error and continueOnFail is disabled, the workflow will stop. Enable continueOnFail to handle errors gracefully.

Links and References

Discussion