Actions36
Overview
This node integrates with the Magnet Customer API to manage various CRM resources, including prospects. Specifically, for the Prospect - Delete operation, it deletes a prospect record identified by its unique ID. This is useful in scenarios where you want to programmatically remove outdated or incorrect prospect entries from your CRM system.
Practical examples:
- Automatically deleting prospects that have unsubscribed or are no longer valid leads.
- Cleaning up test or duplicate prospect data as part of an automated workflow.
- Removing prospects after they have been converted or disqualified.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: "API Token" or "OAuth2". |
| Contact ID (prospectId) | The unique identifier of the prospect to delete. This is required to specify which prospect to remove. |
| Life Cycle | Hidden property indicating the life cycle stage of the contact; preset to "prospect". |
| Source | Hidden property indicating the source of the contact; preset to "n8n". |
Note: Several hidden properties like lifeCycle and source are preset internally and not exposed for user modification during 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 relevant status information.
If an error occurs (e.g., invalid ID), the output will contain an error message describing the issue.
No binary data is produced by 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 corresponding to prospects.
Troubleshooting
Common issues:
- Providing an invalid or non-existent prospect ID will result in an error from the API.
- Missing or incorrect authentication credentials will cause authorization failures.
- Network connectivity issues can prevent successful API calls.
Error messages:
"error": "Invalid prospect ID"— Check that the provided prospect ID is correct."error": "Unauthorized"— Verify that the API token or OAuth2 credentials are properly set up."error": "Network Error"— Ensure your server has internet access and the API endpoint is reachable.
To resolve errors, confirm the input parameters, especially the prospect ID and authentication method, and ensure the API credentials are valid and active.
Links and References
- Magnet Customer API Documentation (general reference for API endpoints and authentication)
- n8n documentation on creating custom nodes