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 deals and other CRM-related resources. Specifically, for the Deal - Delete operation, it deletes a deal identified by its unique ID from the Magnet Customer system.
Common scenarios where this node is useful include:
- Automating cleanup of outdated or invalid deals in your CRM.
- Integrating deal deletion into workflows triggered by external events (e.g., when a deal is lost or cancelled).
- Synchronizing deal data between Magnet Customer and other systems by removing deals no longer relevant.
Example: Automatically delete a deal when a related contract is terminated in another system, ensuring your CRM stays up-to-date without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: "API Token", "OAuth2". |
| Deal ID | The unique identifier of the deal to delete. This is required to specify which deal to remove. |
| Life Cycle | Hidden property indicating the life cycle stage of the contact (e.g., customer, lead, prospect). Not user-editable here. |
| Source | Hidden property indicating the source of the contact, defaulting to "n8n". Not user-editable here. |
Note: Multiple hidden properties named "Life Cycle" and "Source" appear due to internal configuration but are not exposed for user input.
Output
The node outputs JSON data representing the result of the delete operation for each processed item. Typically, this will be a confirmation of successful deletion or an error message if the deletion failed.
The output structure per item includes:
- A JSON object with details returned by the API after attempting to delete the deal.
- In case of failure and if "Continue On Fail" is enabled, an error object with the error message.
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 Magnet Customer API endpoints.
Troubleshooting
- Missing or invalid Deal ID: The operation requires a valid deal ID. Ensure the "Deal ID" property is correctly set and corresponds to an existing deal.
- Authentication errors: If the API token or OAuth2 credentials are incorrect or expired, the node will fail to authenticate. Verify credentials in n8n settings.
- API rate limits or connectivity issues: Network problems or API rate limiting can cause failures. Check network connectivity and Magnet Customer API status.
- Error messages from API: The node surfaces error messages returned by the API. Review these messages to understand issues like permission denied or deal not found.
- Enable "Continue On Fail" to allow processing multiple items even if some deletions fail, capturing errors in output for review.
Links and References
- Magnet Customer API Documentation (generic link, replace with actual if available)
- n8n documentation on HTTP Request Node for understanding API calls
- OAuth2 and API token setup guides within n8n credentials documentation