SignifyCRM icon

SignifyCRM

Consume SignifyCRM API
Join our community

Actions30

Overview

This node integrates with the SignifyCRM API to manage CRM data entities such as Leads, Accounts, Contacts, Opportunities, Cases, and Tasks. Specifically, for the Lead resource with the Get Many operation, it retrieves multiple lead records from the CRM system.

The node supports fetching either all leads or a limited number of leads based on user input. This is useful in scenarios where you want to bulk retrieve lead information for reporting, synchronization, or further automation workflows.

Practical examples:

  • Retrieve all leads to export them into another system.
  • Fetch a limited number of recent leads for quick analysis or display.
  • Use the retrieved lead data to trigger follow-up actions or notifications.

Properties

Name Meaning
Return All Whether to return all lead records or only up to a specified limit.
Limit The maximum number of lead records to return when "Return All" is set to false.

Output

The output is an array of JSON objects representing lead records. Each lead object contains fields such as:

  • id
  • salutation
  • first_name
  • last_name
  • status
  • account_name
  • email1
  • title
  • phone_work
  • phone_mobile
  • department
  • description
  • lead_source
  • assigned_user_id
  • campaign_id

These fields correspond to the standard attributes of a lead in SignifyCRM.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the SignifyCRM API.
  • The node uses the /get_entry_list endpoint of the SignifyCRM API to fetch lead entries.
  • Proper configuration of the SignifyCRM API credentials within n8n is necessary.

Troubleshooting

  • Common issues:

    • Authentication failures due to invalid or missing API credentials.
    • Exceeding API rate limits if requesting too many records at once.
    • Network connectivity problems preventing access to the SignifyCRM API.

  • Error messages:

    • Errors returned from the API will typically include messages about invalid parameters or authentication errors.
    • If the node throws an error related to the limit parameter, ensure it is a positive integer.
    • If no leads are returned, verify that there are leads available in the CRM and that the query parameters are correct.

  • Resolutions:

    • Double-check and update the API key credential in n8n.
    • Adjust the "Return All" and "Limit" settings to comply with API constraints.
    • Ensure network connectivity and firewall rules allow outbound requests to the SignifyCRM API.

Links and References

Discussion