Actions5
- Message Actions
- Contact Actions
- Session Actions
Overview
This node integrates with the Sendtick API to interact with WhatsApp messaging services. Specifically, for the Contact - Get operation, it retrieves detailed information about a single contact by its unique ID. This is useful in scenarios where you need to fetch up-to-date contact details from your WhatsApp contact list managed via Sendtick.
Practical examples include:
- Fetching contact information before sending personalized messages.
- Synchronizing contact data between Sendtick and other systems.
- Displaying contact details in workflows for decision-making or logging.
Properties
| Name | Meaning |
|---|---|
| Contact ID | ID of the contact to retrieve |
Output
The output is a JSON object containing the contact's details as returned by the Sendtick API. The structure typically includes all available fields related to the contact, such as name, phone number, tags, groups, and any metadata maintained by Sendtick.
No binary data is output by this operation.
Example output snippet (structure depends on Sendtick API response):
{
"id": "contact-id",
"name": "Contact Name",
"phone": "+1234567890",
"tags": ["tag1", "tag2"],
"groups": ["group1"],
...
}
Dependencies
- Requires an active Sendtick API key credential configured in n8n.
- The node makes authenticated HTTP requests to the Sendtick API endpoint at
https://sendtick.co/api/v1. - Proper network access to Sendtick API is necessary.
Troubleshooting
Common issues:
- Missing or invalid Contact ID will cause the request to fail.
- Network connectivity problems can prevent API calls.
- Invalid or expired API credentials will result in authentication errors.
Error messages:
"Unsupported resource/operation": Indicates that the selected resource or operation is not implemented; ensure you select "Contact" as resource and "Get" as operation.- API errors returned from Sendtick will be passed through; check the error message for details like "Contact not found" or "Unauthorized".
Resolutions:
- Verify the Contact ID is correct and exists in Sendtick.
- Confirm API credentials are valid and have required permissions.
- Check internet connectivity and firewall settings.
Links and References
- Sendtick API Documentation (for detailed API endpoints and data structures)
- n8n documentation on Creating Custom Nodes