Actions30
Overview
This node integrates with the SignifyCRM API to manage CRM data. Specifically, for the Contact - Create operation, it allows users to create new contact records in the SignifyCRM system. This is useful in scenarios where you want to automate adding new contacts from various sources such as web forms, lead generation tools, or other databases into your CRM without manual entry.
Practical examples include:
- Automatically creating a new contact when a user submits a signup form.
- Importing contacts from an external marketing platform into SignifyCRM.
- Syncing contacts from another system into SignifyCRM as part of an automated workflow.
The node handles required fields and supports additional optional fields to enrich the contact record.
Properties
| Name | Meaning |
|---|---|
| Salutation | The contact's salutation/title. Options include: (empty), Asst., Dr., K., Mr., Mrs., Ms., Prof., คุณ, ดร., นาง, นางสาว, นาย, รศ., ศจ. |
| First Name | The contact's first name. This is a required field. |
| Additional Fields | A collection of optional fields to add more details about the contact: |
| - Assigned To Name or ID: User responsible for the contact (selectable from user list or by expression). | |
| - Birthdate: Contact's birth date (date/time). | |
| - Department: Department name (string). | |
| - Description: Additional notes or description (string). | |
| - Email (Primary): Primary email address (string). | |
| - Last Name: Contact's last name (string). | |
| - Mobile Number: Mobile phone number (string). | |
| - Office Phone: Work phone number (string). | |
| - Title: Job title or position (string). |
Output
The node outputs JSON data representing the response from the SignifyCRM API after attempting to create the contact. This typically includes details of the newly created contact record such as its unique ID and any other metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the SignifyCRM API via an API key credential configured in n8n.
- The node uses internal helper functions to fetch user lists dynamically for the "Assigned To" field.
- Network access to the SignifyCRM API endpoint is necessary.
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 values for options (e.g., an unrecognized salutation) may cause the API to reject the request.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors usually indicate incorrect or missing API keys; verify and update credentials.
- Validation errors from the API often specify which fields are missing or invalid; ensure all required fields are correctly filled.
- If the node returns empty or unexpected responses, check that the SignifyCRM service is operational and accessible.
Links and References
- SignifyCRM API Documentation (example placeholder, replace with actual URL if available)
- n8n Expressions Documentation — for using expressions in input fields such as "Assigned To".
If you need summaries for other operations or resources, feel free to ask!