Integrations

Your card, connected to everything you already use

Chat on your website, messages from your other systems and replies back — bundled in one message center. Plus webhooks for your automations, a REST API and calendar sync.

Start for free View plans
All inquiries in one place

One message center for card, website and tools

No matter where someone writes to you — on your card, in the chat on your website or through a connected system: the message lands in the same place, and you reply from there.

Your cardLive chat at your card address
Your websitesThe same chat via a code snippet — on as many pages as you like
Your systemsForms, n8n, Make, Zapier, messenger bridges — via channels
Message center Queue, history, push to your phone, save as contact request
Your replyIn the chat straight to the visitor — via a channel signed back to your system
Overview

What connects with what

Live chat on your websiteBeta

A code snippet brings your card's chat to your website, your shop or landing pages. Every inquiry shows which page it came from.

Pro

Channels: receive messages via webhookBeta

One secret address per channel: whatever another system sends there appears as a conversation in the message center — with a conversation ID so follow-up messages land in the same thread.

Pro

Send replies back via webhookBeta

If you enter a reply address, every reply from the message center goes back to your system, signed. You can see on each message whether it arrived, and resend it.

Pro

Event webhooks

New contact requests, appointment requests, orders, reservations and chat transcripts go in real time to n8n, Make, Zapier or your CRM — signed with HMAC-SHA256.

Pro

REST API

Read and maintain cards, links and statistics from your own systems with a key — with read-only keys for reporting.

Add-on ab Pro

Calendar sync

Booked appointments land automatically in your Google Calendar or a CalDAV calendar (e.g. Nextcloud); busy times are taken into account when booking.

Pro

Reviews on your website

Approved reviews of your card as a widget you embed on your own website.

Pro

Reservations for AI assistantsBeta

An open interface (JSON and MCP) lets AI assistants query free times and submit reservation requests — the guest always confirms personally.

Pro

QR, NFC, vCard & Wallet

The bridges to the offline world: QR code for print, NFC tags to tap, vCard for the address book and a Google Wallet pass.

Channels in three steps

How messages from other systems come in

1. Create channel

In the dashboard under "Integrations": give it a name, choose a card, optionally enter a reply address. You get the secret channel address.

2. Connect your system

Send a POST to the channel address from n8n, Make, Zapier or your own script — only the "message" field is required.

3. Reply

The message appears in the message center. Your reply goes, signed, to the reply address — your system forwards it.

curl -X POST "https://vizitcard.de/api/kanal/v1/vzk_…" \
  -H "Content-Type: application/json" \
  -d '{"thread":"kunde-4711","name":"Erika Muster","message":"Hi, are you open on Saturday?"}'
Secure & data-minimal

Built by the same rules as the whole platform

  • HTTPS only: replies go exclusively encrypted to publicly reachable addresses — internal networks are blocked.
  • Signed: replies and events carry an HMAC-SHA256 signature; channels can be set to accept signed calls only.
  • Stored encrypted: channel keys and signing secrets are never stored in plain text in the database.
  • No IP addresses: we store neither the IP address nor the browser ID of calling systems.
  • Limited: rate limits per channel, duplicate detection via the message ID, automatic deletion after 90 days without a new message.

More on the Security & trust page and in the privacy policy. We process messages from channels on behalf of the card owner (DPA).

FAQ

Frequently asked questions

Do I need to know how to code?
No. For the chat on your website you copy a single code snippet. You set up channels in the dashboard with a few clicks; the easiest way to connect other systems is n8n, Make or Zapier — an HTTP module with the channel address is enough.
What is the difference between channels and event webhooks?
Event webhooks send something OUT as soon as something happens on your card — such as a new contact request or reservation. A channel is the way IN: messages from other systems land as a conversation in your message center, and your replies can go back to the other system.
Can I connect WhatsApp, Telegram or email?
Via a tool like n8n, Make or Zapier that connects these services: it forwards incoming messages to your channel and sends your replies back from the reply address. We do not offer a direct, ready-made connection to these services.
How secure are the webhooks?
The channel address contains a long random key; if you wish, a channel only accepts calls with an HMAC-SHA256 signature. We send replies exclusively via HTTPS to publicly reachable addresses and sign them as well. Keys and secrets are stored encrypted; we do not store IP addresses of calling systems.
How long are messages stored?
Conversations from channels are deleted automatically 90 days after the last message — the same period as ended live chats. You can delete them earlier at any time or save them as a contact request.

Ready to connect everything?

Try Vizitcard for free — each tile shows which plan includes the integration.

Start for free