Actions16
- Contact Actions
- Contact Tagging Actions
- Data Field Actions
- Opt-In Process Actions
- Tag Actions
Overview
This node is designed to retrieve detailed information about a specific contact from the connected service. It is useful in scenarios where you need to fetch and use contact data within your workflow, such as personalizing emails, updating records, or integrating contact details with other systems.
For example, you might use this node to get a contact's profile by their unique ID before sending them a targeted marketing message or to verify contact information during a customer support process.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact you want to retrieve. This is a required string input where you enter the contact's ID. |
Output
The node outputs a JSON object containing the retrieved contact's details. The structure typically includes fields representing the contact's attributes such as name, email, subscription status, and any custom fields defined in the service.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the contact, but based on the provided code and properties, the output is focused on JSON data describing the contact.
Dependencies
- Requires an active connection to the external contact management service.
- Needs appropriate API credentials or authentication tokens configured in n8n to access contact data.
- The node relies on internal methods and routing logic bundled in its dependencies to perform the retrieval operation.
Troubleshooting
- Missing or invalid Contact ID: Ensure that the Contact ID property is correctly set and corresponds to an existing contact in the system.
- Authentication errors: Verify that the API credentials or authentication tokens are valid and have sufficient permissions to read contact data.
- Network issues: Check connectivity to the external service if requests time out or fail.
- Unexpected response structure: If the output does not match expectations, confirm that the contact exists and that the service's API has not changed.
Links and References
- Refer to the external service's official API documentation for details on contact data structure and retrieval endpoints.
- Consult n8n documentation on how to configure API credentials and use custom nodes effectively.