Actions30
Overview
This node integrates with the SignifyCRM API to manage CRM data. Specifically, for the Case resource and the Delete operation, it deletes a case record in SignifyCRM by marking it as deleted via the API.
Typical use cases include automating the removal of outdated or resolved support cases from your CRM system directly within an n8n workflow. For example, after a customer issue is resolved and logged in another system, this node can be used to delete the corresponding case in SignifyCRM automatically.
Properties
| Name | Meaning |
|---|---|
| Case ID | The unique identifier of the case to delete |
Output
The node outputs JSON data representing the response from the SignifyCRM API after attempting to delete the case. This typically includes confirmation that the case was marked as deleted. The output structure mirrors the API's response format and contains fields such as status and any relevant metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the SignifyCRM API.
- The node uses HTTP POST requests to the
/set_entryendpoint of the SignifyCRM API. - Proper configuration of the SignifyCRM API credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing Case ID: Ensure the Case ID provided exists and is correct.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API downtime: Check connectivity and SignifyCRM service status.
Error messages:
- Errors returned from the API will be propagated. Common messages may indicate invalid IDs or permission issues.
- If the node is set to continue on fail, errors will be included in the output JSON under an
errorfield.
Links and References
- SignifyCRM API Documentation (general reference; specific endpoints used are
/set_entry) - n8n documentation on creating custom nodes