Overview
The node performs operations related to managing contacts in the Autocust system. Specifically, for the Get Single Contact operation, it retrieves detailed information about a single contact either by their unique Contact ID or by their email address.
This operation is useful when you need to fetch specific contact details for further processing, such as updating records, sending personalized communications, or integrating contact data into other workflows.
Practical examples:
- Retrieve a contact's profile by their ID after a form submission.
- Look up a contact by email to verify if they exist before adding them to a marketing campaign.
- Fetch contact details to enrich customer support tickets with relevant information.
Properties
| Name | Meaning |
|---|---|
| Search By | Choose whether to search for the contact by Contact ID or Contact Email. |
| Contact ID | The numeric ID of the contact to retrieve (required if searching by Contact ID). |
| Contact Email | The email address of the contact to retrieve (required if searching by Contact Email). |
Output
The output contains a JSON object representing the retrieved contact's data. This typically includes all available fields and attributes associated with that contact in the Autocust system, such as name, email, phone number, and any custom attributes.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Autocust service.
- The node depends on the Autocust API being accessible and properly configured within n8n.
- No additional external dependencies are required beyond the provided API authentication.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Contact ID or email will result in no contact found or an error response from the API.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity problems can prevent successful API calls.
Error messages and resolutions:
"The operation 'getSingleContact' is not known!"— This indicates an internal misconfiguration; ensure the operation parameter is correctly set to "Get Single Contact".- Errors indicating "contact not found" suggest verifying the Contact ID or email input values.
- Authentication errors require checking the API key credential setup in n8n.
Links and References
- Autocust API Documentation (example placeholder link)
- n8n Expressions Documentation
- n8n Credential Setup Guide