Actions36
- Activity Actions
- Contact Actions
- Customer Actions
- Data Proxy Actions
- Document Actions
- Employer Actions
- Lead Actions
- Meeting Actions
- Meeting Summary Actions
- Report Actions
- Workflow Actions
Lead → Delete a Lead
AI-generatedOverview
The node interacts with the Surense API to perform various operations on different resources. Specifically, for the "Lead" resource and the "Delete a Lead" operation, it deletes a lead identified by its unique ID (UUID). This is useful in scenarios where you need to programmatically remove outdated or incorrect lead records from your system.
Practical examples include:
- Automatically deleting leads that have been marked as invalid or duplicates.
- Cleaning up leads after a certain workflow or campaign has completed.
- Integrating with other systems to synchronize lead data by removing leads no longer relevant.
Properties
| Name | Meaning |
|---|---|
| מזהה ליד | The lead ID in UUID format to delete. Example: 123e4567-e89b-12d3-a456-426614174000 |
Output
The output of the node is an array of JSON objects corresponding to each input item processed. For the delete operation, the output typically contains confirmation of the deletion or any error messages if the deletion failed.
If an error occurs during deletion and the node is set to continue on failure, the output will include an object with an error field describing the issue.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential for authenticating with the Surense API.
- The node depends on the Surense API being accessible and properly configured.
- Pagination fields are available but not directly relevant for the delete operation.
- No additional external services are required beyond the Surense API.
Troubleshooting
Common issues:
- Providing an invalid or malformed lead ID (not in UUID format) will cause the operation to fail.
- Network connectivity problems or incorrect API credentials will prevent successful deletion.
- Attempting to delete a lead that does not exist may result in an error response from the API.
Error messages:
"error": "Lead not found"— The specified lead ID does not exist; verify the ID."error": "Unauthorized"— Check that the API authentication token is valid and has necessary permissions."error": "Invalid UUID format"— Ensure the lead ID matches the UUID format.
To resolve errors, verify the lead ID, check API credentials, and ensure network connectivity.
Links and References
- Surense API Documentation (hypothetical link)
- UUID Format Specification