Actions22
- Chat Actions
- Channel Actions
- Message Actions
- Contact Actions
- OTP Code Actions
- OTP Link Actions
Overview
This node interacts with the CrunchzApp API to retrieve the profile picture of a specific contact by their Contact ID. It is useful in scenarios where you need to display or process the profile image associated with a contact, such as in customer support dashboards, CRM integrations, or messaging automation workflows.
For example, if you have a contact's unique identifier and want to fetch their profile picture to show it in your application or use it for further processing, this node provides a straightforward way to do so.
Properties
| Name | Meaning |
|---|---|
| Contact Id | The unique identifier of the contact whose profile picture you want to retrieve. Example: 6281357541790@c.us |
Output
The node outputs JSON data containing the profile picture information of the specified contact. The exact structure depends on the CrunchzApp API response but typically includes fields such as the image URL or base64-encoded image data.
If the node supports binary data output (not explicitly shown in the provided code), it would represent the actual image file content, allowing downstream nodes to handle or save the picture directly.
Dependencies
- Requires an active CrunchzApp API key credential configured in n8n.
- Depends on the CrunchzApp API endpoint at
https://api.crunchz.app/api. - The node sends requests with headers specifying JSON content type and expects JSON responses.
Troubleshooting
- Invalid Contact Id: If the Contact Id is incorrect or does not exist, the API may return an error or empty result. Verify the Contact Id format and existence.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is correctly set up.
- Network Issues: Connectivity problems to the CrunchzApp API endpoint can cause request failures. Check network access and API availability.
- Unexpected Response Format: If the API changes its response structure, the node might not parse the output correctly. Review API documentation for updates.
Links and References
- CrunchzApp API Documentation (assumed link based on baseURL)
- n8n Documentation on Creating Custom Nodes