SignifyCRM icon

SignifyCRM

Consume SignifyCRM API
Join our community

Actions30

Overview

This node integrates with the SignifyCRM API to manage "Case" records within the CRM system. Specifically, the Get Many operation for the Case resource retrieves multiple case records from SignifyCRM. It supports fetching either all available cases or a limited number of them based on user input.

Typical use cases include:

  • Synchronizing case data from SignifyCRM into other systems.
  • Generating reports or dashboards that require bulk case information.
  • Automating workflows that depend on retrieving multiple case records at once.

For example, a user might want to fetch all open support cases to analyze workload distribution or retrieve the latest 50 cases for review.

Properties

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

Output

The output is an array of JSON objects representing case records retrieved from SignifyCRM. Each object contains fields such as:

  • id: Unique identifier of the case.
  • name: Name/title of the case.
  • account_id: Associated account identifier.
  • opportunity_type, lead_source, sales_stage, currency_id, amount, date_closed, probability, next_step, description, assigned_user_id, campaign_id: Various metadata fields related to the case.

Note: The actual fields returned are defined in the request's select_fields parameter and may include additional case-related attributes depending on the API response.

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 SignifyCRM REST API endpoints /get_entries_count and /get_entry_list to count and retrieve case records.
  • No additional external dependencies beyond the configured SignifyCRM API credentials.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Requesting too many records without setting "Return All" properly may result in truncated data.
    • Network connectivity issues can prevent successful API calls.

  • Error Messages:

    • Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
    • Rate limiting or quota exceeded errors suggest too many requests in a short time; implement retries or reduce request frequency.
    • Invalid parameter errors may occur if unsupported values are provided for properties like "Limit"; ensure values meet expected constraints.

Links and References

Discussion