Overview
This node is designed to send contact vCard messages via a Chat API. It allows users to provide vCard data and a display name for a contact, which the node then sends through the configured Chat API service. This is useful in scenarios where automated sharing of contact information is needed within chat conversations, such as customer support bots, CRM integrations, or messaging workflows that require exchanging contact details programmatically.
Practical examples include:
- Automatically sending a business card to new leads in a chat.
- Sharing contact details during a customer support interaction.
- Distributing team member contact info in group chats.
Properties
| Name | Meaning |
|---|---|
| Contact Vcard | The vCard data string representing the contact's detailed information to be sent. |
| Contact Name | The display name for the contact as it should appear in the chat message. |
Output
The node outputs JSON data containing the response from the Chat API after attempting to send the contact vCard message. The output structure includes all data returned by the API call, typically confirming success or providing error details.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Chat API.
- Needs the base URL and session identifier for the Chat API, provided via credentials.
- Uses the Axios HTTP client library internally to make POST requests to the Chat API endpoint
/v1/send/contactVcard.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrectly formatted vCard data may result in API errors or message rejection.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors typically indicate invalid or expired tokens; verify and update credentials.
- API response errors may include validation messages about the vCard format or missing fields; ensure the vCard string complies with expected standards.
- If the node throws an error referencing item index, it indicates which input item caused the failure, helping isolate problematic data.
To handle errors gracefully, the node supports continuing on failure if enabled, allowing partial processing of multiple inputs.
Links and References
- vCard Format Specification
- Axios HTTP Client Documentation
- (Chat API documentation would be linked here if publicly available)