Actions28
- Deal Actions
- Person Actions
- Company Actions
- Activity Actions
- Note Actions
- Case Actions
- Product Actions
- Supplementary Actions
Overview
The node provides integration with Didar CRM, supporting multiple resources and operations. Specifically for the Supplementary resource with the Popup Caller ID operation, it triggers a caller ID popup based on a phone number and user extension. This is useful in call center or telephony environments where agents need immediate contextual information about incoming calls.
Typical use cases include:
- Displaying caller details automatically when a call arrives.
- Enhancing customer support by showing relevant CRM data linked to the caller.
- Reducing manual lookup time by automating caller identification popups.
Properties
| Name | Meaning |
|---|---|
| CallerId's APIKey | Dedicated API key for authenticating requests to the Caller ID popup endpoint (separate from main API key). |
| Phone Number | The phone number of the caller to look up and display information for. |
| User Extension | The internal extension number of the user receiving the call, used to route or identify the popup context. |
Output
The node outputs JSON data containing the response from the Caller ID popup endpoint. This typically includes caller information retrieved based on the provided phone number and user extension.
If the node supports binary data output (not explicitly shown here), it would represent any associated media or files related to the caller ID popup, but this is not indicated in the provided code.
Dependencies
- Requires a dedicated API key credential specifically for the Caller ID popup endpoint.
- Depends on Didar CRM’s supplementary API service that handles caller ID popup requests.
- No additional environment variables or external services are explicitly required beyond the API key.
Troubleshooting
- Invalid API Key: If the CallerId's APIKey is incorrect or missing, the node will fail to authenticate. Ensure the correct dedicated API key for the Caller ID popup endpoint is used.
- Incorrect Phone Number Format: Providing an improperly formatted phone number may result in no data found or errors. Validate the phone number format before execution.
- User Extension Missing or Incorrect: The internal extension must be valid; otherwise, the popup may not trigger correctly.
- Network Issues: Connectivity problems to the Didar CRM API endpoint can cause request failures.
- API Endpoint Changes: If Didar CRM updates their API, the node might require updates to maintain compatibility.
Links and References
- Didar CRM official documentation (for API keys and endpoints) — [Link not provided in source]
- General best practices for telephony integrations and caller ID popups.