SignifyCRM icon

SignifyCRM

Consume SignifyCRM API

Overview

This node integrates with the SignifyCRM API to manage CRM data programmatically. Specifically, for the Lead resource and the Delete operation, it allows users to delete a lead record by marking it as deleted in the CRM system.

Typical use cases include:

  • Automating lead cleanup workflows by removing outdated or invalid leads.
  • Integrating lead deletion into broader automation pipelines, such as after lead conversion or disqualification.
  • Synchronizing lead data between SignifyCRM and other systems by deleting leads that no longer exist elsewhere.

Example: You have a list of leads that failed qualification criteria, and you want to automatically delete them from SignifyCRM using this node.

Properties

Name Meaning
Lead ID The unique identifier (ID) of the lead to delete

Output

The node outputs JSON data representing the response from the SignifyCRM API after attempting to delete the lead. This typically includes confirmation details about the updated lead record, showing that the "Deleted" flag has been set to "1".

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the SignifyCRM API.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests.
  • The node uses the /set_entry endpoint of the SignifyCRM API to mark the lead as deleted.

Troubleshooting

  • Common issues:

    • Invalid or missing Lead ID: Ensure the Lead ID provided exists and is correct.
    • Authentication errors: Verify that the API credentials are valid and have sufficient permissions.
    • Network or API downtime: Check connectivity and SignifyCRM service status.
  • Error messages:

    • "Lead ID not found" or similar: Confirm the Lead ID is correct and the lead exists.
    • "Authentication failed": Recheck API credentials and update if necessary.
    • "API request failed": Inspect network settings, proxy configurations, or API limits.

Resolving these usually involves verifying input parameters, refreshing credentials, and ensuring stable network access.

Links and References

Discussion