Actions30
Overview
This node integrates with the SignifyCRM API to manage CRM data. Specifically, for the Contact - Get operation, it retrieves detailed information about a single contact by its unique ID. This is useful in scenarios where you need to fetch up-to-date contact details from your CRM system within an automated workflow.
Practical examples:
- Automatically retrieving contact details when a new support ticket is created.
- Fetching contact information to personalize email campaigns.
- Synchronizing contact data between SignifyCRM and other systems.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to retrieve. This is required to specify which contact's details should be fetched. |
Output
The output JSON contains the detailed fields of the requested contact record as returned by the SignifyCRM API. Typical fields included are:
id: Contact's unique ID.salutation: Formal greeting (e.g., Mr., Ms.).first_name: Contact's first name.last_name: Contact's last name.email1: Primary email address.title: Job title.phone_mobile: Mobile phone number.phone_work: Work phone number.department: Department name.birthdate: Date of birth.description: Additional notes or description.assigned_user_id: ID of the user assigned to this contact.
The node does not output binary data for 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 beyond the configured SignifyCRM API credentials.
Troubleshooting
Common issues:
- Invalid or missing Contact 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 and resolutions:
"Contact not found": Verify that the Contact ID exists in your SignifyCRM instance."Authentication failed": Check that the API key credential is correctly configured and valid.- Timeout or network errors: Ensure your server can reach the SignifyCRM API endpoint and retry.
Links and References
- SignifyCRM API Documentation (general reference for API endpoints)
- n8n documentation on creating custom nodes