SignifyCRM icon

SignifyCRM

Consume SignifyCRM API
Join our community

Actions30

Overview

This node integrates with the SignifyCRM API to manage CRM data. Specifically, for the Lead - Create operation, it allows users to create new lead records in the SignifyCRM system. This is useful in scenarios where you want to automate lead generation workflows, such as capturing leads from web forms, marketing campaigns, or other sources and pushing them directly into your CRM.

Practical examples include:

  • Automatically creating a lead when a visitor fills out a contact form on your website.
  • Importing leads from external marketing platforms into SignifyCRM.
  • Creating leads programmatically based on triggers from other business systems.

Properties

Name Meaning
Salutation The lead's salutation/title. Options include: (empty), Asst., Dr., K., Mr., Mrs., Ms., Prof., คุณ, ดร., นาง, นางสาว, นาย, รศ., ศจ.
First Name The lead's first name. This is a required field.
Status The current status of the lead. Options include: (empty), Assigned, Converted, Dead, In Process, New, Recycled, Registered.
Additional Fields A collection of optional fields to provide more details about the lead:
- Account Name Name of the associated account.
- Assigned To Name or ID User assigned to this lead. Can be selected from a list or specified by ID via expression.
- Campaign Name or ID Campaign associated with the lead. Selectable from a list or specified by ID via expression.
- Department Department name related to the lead.
- Description Additional description or notes about the lead.
- Email (Primary) Primary email address of the lead.
- Last Name Lead's last name.
- Lead Source Origin of the lead. Options include: (empty), Campaign, Cold Call, Conference, Email, Employee, Existing Customer, Other, Partner, Self Generated, Social Media, Trade Show, Web Site, Word of mouth.
- Mobile Mobile phone number of the lead.
- Office Phone Office phone number of the lead.
- Title Job title of the lead.

Output

The node outputs JSON data representing the response from the SignifyCRM API after attempting to create the lead. The structure typically includes:

  • Confirmation of the created lead entry.
  • Details of the lead record as stored in SignifyCRM.
  • Any metadata returned by the API regarding the creation process.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the SignifyCRM API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • Uses internal helper methods to fetch user IDs and make authenticated API calls.
  • Some input options (e.g., Assigned To, Campaign) dynamically load choices from the CRM via API calls.

Troubleshooting

  • Common Issues:

    • Missing required fields like "First Name" will cause the API request to fail.
    • Invalid or expired API credentials will result in authentication errors.
    • Providing invalid option values (e.g., unknown campaign ID) may cause the API to reject the request.
    • Network connectivity issues can prevent communication with the SignifyCRM API.

  • Error Messages:

    • Authentication errors: Check that the API key/token is correctly set up and has necessary permissions.
    • Validation errors: Ensure all required fields are provided and option values are valid.
    • API request failures: Review the error message for clues; verify network access and API endpoint availability.

  • Resolution Tips:

    • Double-check required inputs before execution.
    • Refresh or reconfigure API credentials if authentication fails.
    • Use expressions carefully to ensure dynamic values resolve correctly.
    • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion