SignifyCRM icon

SignifyCRM

Consume SignifyCRM API
Join our community

Actions30

Overview

This node integrates with the SignifyCRM API to update contact records in the CRM system. It allows users to modify existing contact details such as salutation, first name, and various additional fields like last name, email, phone numbers, department, and title.

Typical use cases include:

  • Automating updates to contact information based on external data sources.
  • Synchronizing contact details from other systems or forms.
  • Bulk updating contacts with new attributes or corrections.

For example, you could use this node to update a contact’s phone number and department after receiving updated information from a customer support form.

Properties

Name Meaning
Contact ID The unique identifier of the contact to update (required).
Salutation The contact's salutation/title. Options include: "", Asst., Dr., K., Mr., Mrs., Ms., Prof., and several Thai honorifics like คุณ, ดร., นาง, นางสาว, นาย, รศ., ศจ.
First Name The contact's first name.
Additional Fields A collection of optional fields to update, including:
- Assigned To Name or ID: User assigned to the contact (selectable from a list or via expression).
- Birthdate: Contact's birth date (date/time).
- Department: Department name (string).
- Description: Text description or notes about the contact.
- Email (Primary): Primary email address.
- Last Name: Contact's last name.
- Mobile Number: Contact's mobile phone number.
- Office Phone: Contact's office phone number.
- Title: Job title or position.

Output

The node outputs JSON data representing the response from the SignifyCRM API after attempting to update the contact. This typically includes confirmation of the update and the updated contact record details.

The output structure is an array of objects corresponding to each input item processed, containing the API response under the json property.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the SignifyCRM API.
  • The node uses internal helper functions to make HTTP POST requests to the SignifyCRM endpoints.
  • No additional external dependencies are required beyond the configured SignifyCRM API credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing Contact ID will cause the update to fail.
    • Providing empty or invalid values for required fields may result in API errors.
    • Network or authentication failures can prevent successful API calls.

  • Error messages:

    • Errors returned from the SignifyCRM API will be propagated. Typical messages might indicate missing parameters, invalid IDs, or permission issues.
    • If "continue on fail" is enabled, errors for individual items will be included in the output with an error message field.

  • Resolution tips:

    • Ensure the Contact ID corresponds to an existing contact in the CRM.
    • Verify that the API credentials are valid and have sufficient permissions.
    • Use expressions carefully to provide dynamic values and avoid empty strings where not allowed.

Links and References

Discussion