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 Contacts, Accounts, Leads, Opportunities, Cases, and Tasks. Specifically, for the Contact resource with the Get Many operation, it retrieves multiple contact records from the CRM system.

The node supports fetching either all contacts or a limited number of contacts based on user input. This is useful in scenarios where you want to synchronize contact lists, generate reports, or automate workflows that require bulk access to contact information.

Practical example:
You might use this node to pull all contacts from your CRM into another system for marketing campaigns or to update a mailing list regularly.

Properties

Name Meaning
Return All Boolean option to return all contact records or limit the number of results returned.
Limit Maximum number of contact records to return when "Return All" is set to false (minimum 1).

Output

The output is a JSON array where each item represents a contact record retrieved from SignifyCRM. Each contact object includes fields such as:

  • salutation
  • first_name
  • last_name
  • email1
  • title
  • phone_mobile
  • phone_work
  • department
  • birthdate
  • description
  • assigned_user_id

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the SignifyCRM API.
  • The node makes HTTP POST requests to SignifyCRM endpoints like /get_entry_list and /get_entries_count.
  • 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 API calls.

  • Error messages:

    • Errors related to authentication typically indicate incorrect API keys or expired tokens; verify and update credentials.
    • If the node throws errors about query limits or timeouts, try reducing the "Limit" property or enabling pagination via "Return All".
    • Unexpected empty results may occur if there are no contacts matching the criteria or if the account has no contacts.

Links and References

Discussion