SignifyCRM icon

SignifyCRM

Consume SignifyCRM API
Join our community

Actions30

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 Opportunity resource with the Get operation, it retrieves detailed information about a single opportunity record by its ID.

Typical use cases include:

  • Fetching details of a specific sales opportunity to display or process further in an automation workflow.
  • Integrating CRM data into other systems by retrieving opportunity information dynamically.
  • Triggering follow-up actions based on opportunity status or attributes.

Example: Given an Opportunity ID, the node fetches fields like name, account association, sales stage, amount, close date, probability, and assigned user, enabling workflows that react to changes or analyze sales pipelines.

Properties

Name Meaning
Opportunity ID The unique identifier of the opportunity to retrieve

Output

The node outputs JSON data representing the retrieved opportunity record. The structure includes fields such as:

  • id: Opportunity unique identifier
  • name: Name/title of the opportunity
  • account_id: Associated account's ID
  • opportunity_type: Type/category of the opportunity
  • lead_source: Origin of the lead
  • sales_stage: Current sales stage (e.g., Prospecting, Qualification)
  • currency_id: Currency used for the amount
  • amount: Monetary value of the opportunity
  • date_closed: Expected or actual close date
  • probability: Probability percentage of closing the deal
  • next_step: Next planned action
  • description: Additional notes or description
  • assigned_user_id: User responsible for the opportunity
  • campaign_id: Related marketing campaign ID

The output is a JSON array where each item corresponds to one opportunity record fetched.

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 such as /get_entry.
  • No additional external dependencies are required beyond proper API credentials and network access to the SignifyCRM service.

Troubleshooting

  • Common issues:

    • Invalid or missing Opportunity 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.
    • Request limits or permissions issues configured in the SignifyCRM account.

  • Error messages:

    • Errors returned from the API typically include messages indicating invalid IDs or authentication failures.
    • If the node throws an error about missing parameters, ensure the Opportunity ID property is set and non-empty.
    • For "continue on fail" enabled workflows, errors are captured per item and included in the output with an error message field.

  • Resolution tips:

    • Verify the Opportunity ID exists in the CRM system.
    • Check and update the API key credential in n8n settings.
    • Confirm network access and firewall rules allow outbound calls to the SignifyCRM API.
    • Review SignifyCRM user permissions related to reading opportunity records.

Links and References

Discussion