Actions30
Overview
This node integrates with the SignifyCRM API to manage "Account" records within the CRM system. Specifically, the Create Account operation allows users to add new accounts by specifying key details such as the account's name, type, industry, status, and assigned user. This is useful for automating the creation of customer or partner accounts directly from workflows, enabling seamless data entry and synchronization between systems.
Practical examples:
- Automatically creating a new customer account in SignifyCRM when a form is submitted on a website.
- Adding partner or supplier accounts based on data received from external business applications.
- Creating prospect accounts during lead generation campaigns to track potential clients.
Properties
| Name | Meaning |
|---|---|
| Name | The name of the account to be created. |
| Type | The category of the account. Options include: Customer, Others, Partner, Prospect, Supplier. |
| Industry | The industry sector the account belongs to. Options include: Agro, Automobile, Construction Materials, Consumption, e-Commerce, Education, Electronics, Energy, Engineering, Fashion, Finance, Food, Government, Health, Home, Hotel, ICT, Insurance, Machine, Non-Profit, Other, Packaging, Petrochemical, Pharmaceutical, Printing, Property, Restaurant, Retail, Tourism, Transportation. |
| Status | The current status of the account. Options include: Active, Approved, Collection, Inactive, Pending, Rejected, Suspend. |
| Assigned To Name or ID | The user responsible for this account. Can be selected from a list or specified via an expression. |
| Additional Fields | Optional extra fields to provide more information about the account. Includes: Email (Primary), Office Phone, Description. |
Output
The node outputs JSON data representing the response from the SignifyCRM API after attempting to create the account. This typically includes confirmation details of the newly created account record, such as its unique identifier and any other metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication credential configured in n8n to connect to the SignifyCRM API.
- The node uses internal helper functions to fetch user lists dynamically for the "Assigned To" field.
- Network connectivity to the SignifyCRM API endpoint is necessary.
Troubleshooting
Common issues:
- Missing required fields such as "Name", "Type", "Industry", "Status", or "Assigned To" will cause the API request to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Providing invalid option values outside the predefined lists may cause validation errors.
Error messages and resolutions:
- Authentication failed: Verify that the API key or token is correctly set up and has not expired.
- Missing required parameter: Ensure all mandatory properties are filled before execution.
- Invalid value for field: Check that the selected options for Type, Industry, and Status match the allowed values.
- Network errors: Confirm network access to the SignifyCRM API and retry.
Links and References
- SignifyCRM API Documentation (example link; replace with actual if available)
- n8n Expressions Documentation – for using expressions in input fields such as "Assigned To Name or ID".