SignifyCRM icon

SignifyCRM

Consume SignifyCRM API
Join our community

Actions30

Overview

This node integrates with the SignifyCRM API to create a new Case record in the CRM system. It allows users to specify key details about a case such as its subject, associated account, status, type, request and due dates, and additional optional fields like description or assigned user. This node is useful for automating customer support workflows, tracking issues, or managing service requests by programmatically creating cases based on incoming data or triggers.

Practical examples:

  • Automatically create a support case when a customer submits a form on your website.
  • Generate a case from an email trigger to track reported bugs or inquiries.
  • Create cases from other systems to centralize issue management within SignifyCRM.

Properties

Name Meaning
Subject Name The title or subject of the case being created.
Account Name or ID The account related to this case. You can select from a list of accounts or provide an account ID via expression.
Status The current status of the case. Options include: New, Approved, Assigned, Closed, Duplicate, Onsite, Pending Input, Pending Test, Rejected, Resolved.
Type The category or type of the case. Options include: Change Request, Consulting Service, Data Update / Archive, Defect, Infrastructure, KM Document, Project, Question, Remove Subscription, User Security, Server Down, Setup Problem, Add Subscription.
Request Date The date and time when the case was requested. Defaults to the current date/time if not specified.
Due Date The deadline or due date for resolving the case.
Additional Fields A collection of optional extra fields that can be added to the case:
- Description: Text description of the case.
- Contact Name or ID: Related contact for the case, selectable from a list or via expression.
- Opportunity Name or ID: Related opportunity, selectable from a list or via expression.
- Assigned To Name or ID: User assigned to handle the case, selectable from a list or via expression.

Output

The node outputs JSON data representing the response from the SignifyCRM API after creating the case. This typically includes details of the newly created case record such as its unique ID and all submitted fields.

No binary data output is produced by this node.

Dependencies

  • Requires an active connection to the SignifyCRM API using an API authentication token configured in n8n credentials.
  • Uses internal helper methods to fetch user IDs and load options dynamically for fields like accounts, contacts, opportunities, and users.
  • The node sends HTTP POST requests to the /set_entry endpoint of the SignifyCRM API to create the case.

Troubleshooting

  • Common issues:

    • Missing required fields such as Subject Name, Account ID, Request Date, or Due Date will cause the API call to fail.
    • Invalid or expired API credentials will result in authentication errors.
    • Providing invalid IDs for related entities (account, contact, opportunity, assigned user) may cause the creation to fail or link incorrectly.

  • Error messages:

    • Authentication errors: Check that the API key credential is correctly set up and has necessary permissions.
    • Validation errors from the API: Ensure all required fields are provided and valid.
    • Network or connectivity errors: Verify network access to the SignifyCRM API endpoint.

  • Resolution tips:

    • Double-check all required input parameters.
    • Use expressions carefully to ensure they resolve to valid IDs.
    • Confirm API credentials and permissions.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully during batch processing.

Links and References

Discussion