Cardinal by RAMCOREOpen Cardinal

Send on WhatsApp

AI agents and the runner. Connect your own WhatsApp number through n8n once, then send an invoice, quote or reminder to a client on WhatsApp.

The workspace owner can have Cardinal send invoices, quotes and payment reminders from a WhatsApp number. Cardinal posts each message to a workflow on your n8n server, which sends it from your number through WAHA and reports back. Nothing is sent without your click.

Before you start

  • Your server needs CONNECTION_KEYS and CARDINAL_PUBLIC_URL, and your workspace's id in CARDINAL_N8N_ORGS. Until then Comms › Sending setup says what is missing.
  • The WhatsApp number needs its own WAHA session, signed in by scanning the QR code on the phone (Linked devices).
  • In n8n, the Cardinal workflows are built and unpublished. Publish them only when you are ready, then send the test message.

Connect it in Cardinal

  1. On Comms › Sending setup, paste the n8n send link (the production URL of the Cardinal WhatsApp send workflow, over https) and the sending number, and press Save.
  2. Cardinal shows two keys once: the send key and the callback secret. Copy them now; the page never shows them again.
  3. In n8n, paste the send key into the credential called Cardinal send key (Header Auth, name X-Cardinal-Key). Set the callback secret as CARDINAL_WA_CALLBACK_SECRET on the n8n server.
  4. In the WAHA session and the n8n events workflow, use the callback URL Cardinal showed, ending in /api/comms/callback?org= and your workspace id.
  5. Press Send a test message, to your own number with This is my own number ticked. When n8n answers, the status changes to Ready and held messages are released.

New send key makes another send key and waits for the next test message. New callback secret makes another callback secret: the old one keeps working for 7 days, or until n8n sends an event signed with the new one.

Sending

Add each contact's WhatsApp number on the client page. The first time you send to a contact, tick that they agreed to WhatsApp and say where; Cardinal records it. Then use Send by WhatsApp on an invoice or quote, or Remind by WhatsApp on an overdue invoice. You see the exact message first. A client who replies STOP is never messaged again.

A new number starts slowly to protect it: 5 documents a day for the first week, 10 for the second, then 20, at most one a day to each contact, and no more than 3 a minute. Pause WhatsApp sending stops everything at once; Resume lets held messages go.

If something is wrong

  • n8n refused the send key: the page says so and messages wait. Press New send key, paste it into n8n, and send a test message.
  • No word from n8n for over 2 hours, or the WhatsApp session is signed out: Cardinal emails you at most once a day and shows WhatsApp needs attention on Today. Check the n8n workflows and scan the QR code again if asked.
  • A message shows Not delivered with a short code: the reason n8n gave. Retry it from Comms.

Remove forgets the link and send key. Replies and STOP are still recorded. Saving again turns it back on.

Meta's Cloud API

A server that has WHATSAPP_APP_SECRET and WHATSAPP_VERIFY_TOKEN also shows the Meta form, for sending approved templates through Meta instead. Only one of the two can be connected at a time: remove one before connecting the other.