Evolution API icon

Evolution API

Complete WhatsApp automation with Evolution API
Join our community

Actions48

Overview

This node integrates with the Evolution API to manage WhatsApp contacts and perform various contact-related operations. Specifically, the Get Contact operation retrieves detailed information about a specific WhatsApp contact by their phone number.

Common scenarios where this node is beneficial include:

  • Fetching contact details for customer support or CRM integration.
  • Verifying contact information before sending messages.
  • Automating workflows that require up-to-date contact data from WhatsApp.

For example, you can use this node to get profile information of a user who just interacted with your WhatsApp business account, enabling personalized responses or logging contact details in your database.

Properties

Name Meaning
Additional Fields Optional extra parameters to customize the request:
- Delay: Delay in milliseconds before sending (not applicable here but available)
- Link Preview: Enable link preview in messages (not applicable here but available)
- Quoted Message ID: ID of message to quote/reply to (not applicable here but available)
- Mentions: Comma-separated list of numbers to mention (not applicable here but available)

Note: For the Get Contact operation, only the "Additional Fields" collection is available as input, but none of its options are used in the actual request.

Output

The node outputs JSON data containing the contact information retrieved from the Evolution API. The structure depends on the API response but typically includes fields such as:

  • Contact's WhatsApp number
  • Profile name
  • Profile picture URL (if available)
  • Status/about text
  • Other metadata related to the contact

The output is an array of items, each with a json property holding the contact data corresponding to the input item.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for the Evolution API, including base URL, API key, and instance name.
  • Optionally uses another API key credential for an internal validation service before making requests.
  • The node makes HTTP requests to the Evolution API endpoints.
  • Proper configuration of these credentials in n8n is necessary for successful execution.

Troubleshooting

  • Invalid subscription or API key error: If the internal validation request fails with 401 or 403 status, check that the API keys and subscriptions are valid and correctly configured.
  • Unknown resource or operation errors: These occur if unsupported resource or operation values are set; ensure "Contact" resource and "Get Contact" operation are selected.
  • Network or API errors: Could be due to incorrect base URL, instance name, or network issues; verify all connection details.
  • Empty or missing contact data: Confirm the phone number is correct and the contact exists on WhatsApp.

Links and References

Discussion