CrunchzApp icon

CrunchzApp

Interact with CrunchzApp API
Join our community

Actions22

Overview

This node interacts with the CrunchzApp API to retrieve detailed information about a specific contact by their unique Contact ID. It is useful in scenarios where you need to fetch up-to-date contact details from CrunchzApp within an automated workflow, such as syncing contact data, verifying contact existence, or enriching customer profiles.

For example, if you have a contact ID like 6281357541790@c.us, this node can query CrunchzApp and return all available information related to that contact, enabling further processing or decision-making in your automation.

Properties

Name Meaning
Contact Id The unique identifier of the contact to retrieve details for (e.g., 6281357541790@c.us).

Output

The node outputs JSON data containing the detailed information of the requested contact. This typically includes fields such as the contact's name, phone number, status, profile picture URL, and other metadata provided by the CrunchzApp API.

If the API supports binary data (e.g., profile pictures), it may be included as binary output, but based on the provided code and properties, the primary output is structured JSON contact information.

Dependencies

  • Requires an active CrunchzApp API key credential configured in n8n.
  • Depends on the CrunchzApp REST API endpoint at https://api.crunchz.app/api.
  • The node uses standard HTTP headers for JSON communication (Accept: application/json and Content-Type: application/json).

Troubleshooting

  • Invalid Contact ID: If the provided Contact Id is malformed or does not exist, the API may return an error or empty response. Verify the Contact Id format matches expected patterns (e.g., including domain suffix like @c.us).
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the CrunchzApp API key is correctly set up in n8n credentials.
  • Network Issues: Connectivity problems to the CrunchzApp API endpoint will result in request failures. Check network access and API availability.
  • API Rate Limits: Excessive requests might trigger rate limiting; handle such errors by implementing retries or backoff strategies.

Links and References

Discussion