Actions28
- Deal Actions
- Person Actions
- Company Actions
- Activity Actions
- Note Actions
- Case Actions
- Product Actions
- Supplementary Actions
Overview
This node integrates with Didar CRM to fetch various types of supplementary base information. The "Get Base Info" operation under the "Supplementary" resource allows users to retrieve foundational datasets such as deal pipelines, case pipelines, activity types, user lists, custom fields, and product categories. This is useful for populating dropdowns, configuring workflows, or synchronizing reference data within n8n automations.
Practical examples include:
- Fetching all deal pipelines to dynamically build a sales funnel visualization.
- Retrieving user lists to assign tasks or activities programmatically.
- Getting product categories to categorize inventory items in an automated process.
Properties
| Name | Meaning |
|---|---|
| Dataset | Choose which base information to fetch. Options: Deal Pipelines, Case Pipelines, Activity Types, User List, Custom Fields List, Product Categories |
Output
The node outputs JSON data containing the requested base information dataset. The structure depends on the selected dataset but generally includes arrays of objects representing entities like pipelines, users, or categories with their relevant attributes.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Didar CRM service.
- The node depends on the Didar CRM API being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Selecting an unsupported dataset value may result in empty or error responses.
- Network connectivity issues can prevent successful API calls.
Error Messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- API response errors might suggest rate limits or permission restrictions; check API usage policies.
- Timeout or connection errors require checking network access and Didar CRM service status.
Links and References
- Didar CRM official API documentation (refer to your Didar CRM provider for exact URL)
- n8n documentation on creating and using API credentials
- General REST API troubleshooting guides