SignifyCRM icon

SignifyCRM

Consume SignifyCRM API

Overview

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

Use cases include:

  • Fetching case details to display or process in workflows.
  • Integrating case data into other systems or automations.
  • Monitoring support tickets or customer issues tracked as cases.

Example: Retrieve a case by its ID to check its status, assigned user, related account, and important dates.

Properties

Name Meaning
Case ID The unique identifier of the case to retrieve

Output

The output is a JSON object representing the retrieved case's details. It includes fields such as:

  • id: The case's unique identifier.
  • subject: The subject/title of the case.
  • account_id: Identifier of the related account.
  • status: Current status of the case.
  • type: Type/category of the case.
  • request_date: Date when the case was requested.
  • due_date: Due date for the case resolution.
  • description: Additional description or notes.
  • contact_id: Related contact identifier.
  • opportunity_id: Related opportunity identifier.
  • assigned_user_id: User assigned to the case.

The data is returned inside an array of JSON objects, each corresponding to one input item processed.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the SignifyCRM API.
  • The node uses HTTP POST requests to the SignifyCRM endpoints /get_entry to fetch case data.
  • No additional external dependencies beyond the configured SignifyCRM API credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing Case ID will cause the API request to fail.
    • Authentication errors if the API key credential is incorrect or expired.
    • Network connectivity problems preventing access to the SignifyCRM API.
  • Error messages:

    • Errors from the API typically include messages indicating invalid IDs or permission issues.
    • If the node throws an error about missing parameters, ensure the Case ID property is set and not empty.
  • Resolutions:

    • Verify the Case ID exists in your SignifyCRM system.
    • Check and update the API authentication credentials.
    • Ensure network access to the SignifyCRM API endpoint.

Links and References

Discussion