SignifyCRM icon

SignifyCRM

Consume SignifyCRM API
Join our community

Actions30

Overview

This node integrates with the SignifyCRM API to perform various operations on CRM resources such as Leads, Accounts, Contacts, Opportunities, Cases, and Tasks. Specifically for the Lead - Get operation, it retrieves detailed information about a single lead by its ID.

Common scenarios where this node is beneficial include:

  • Fetching lead details to enrich workflows with up-to-date customer data.
  • Automating follow-ups or notifications based on lead status or attributes.
  • Integrating lead data into other systems or reports.

For example, you can use this node to get a lead's contact information and status by providing the Lead ID, then use that data to trigger personalized email campaigns or update sales dashboards.

Properties

Name Meaning
Lead ID ID of the lead to retrieve

The node requires the Lead ID as input to fetch the corresponding lead record from SignifyCRM.

Output

The output JSON contains the detailed lead information returned by the SignifyCRM API. The structure includes fields such as:

  • id: Unique identifier of the lead.
  • salutation, first_name, last_name: Personal name details.
  • status: Current status of the lead.
  • account_name: Associated account name if any.
  • email1: Primary email address.
  • title, phone_work, phone_mobile, department: Contact details.
  • description: Additional notes or description.
  • lead_source: Origin of the lead.
  • assigned_user_id: User assigned to the lead.
  • campaign_id: Campaign associated with the lead.

The node does not output binary data; all data is returned in JSON format representing the lead's properties.

Dependencies

  • Requires an API key credential for authenticating with the SignifyCRM API.
  • The node makes HTTP POST requests to SignifyCRM endpoints such as /get_entry.
  • No additional external dependencies are required beyond the configured API credentials.

Troubleshooting

  • Invalid Lead ID: If the provided Lead ID does not exist or is incorrect, the API may return an error or empty result. Verify the Lead ID before running the node.
  • Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to access lead data.
  • API Rate Limits: Excessive requests might be throttled by the SignifyCRM API. Implement retry logic or reduce request frequency.
  • Network Issues: Connectivity problems can cause request failures. Check network settings and firewall rules.

If errors occur, the node will throw exceptions unless "Continue On Fail" is enabled, in which case it returns error messages in the output.

Links and References

Discussion