WhatsApp node — dojobase

Output

WhatsApp the report link

Sends a WhatsApp message (usually a link to the result) when the job reaches this step. The first message to a contact must use a pre-approved template.

How it works

WhatsApp reaches customers where a lot of them already chat, and it shows delivered and read receipts. When a job completes, this node sends a WhatsApp message to the number you specify, commonly a link to open the finished report.

WhatsApp has a rule worth knowing up front: to start a conversation, businesses must use a message template that WhatsApp has approved in advance. So the first outbound message uses one of these approved templates, with your job values slotted into the blanks. This keeps WhatsApp's spam controls satisfied.

Sending requires a WhatsApp Business account. By default dojobase can send through its own managed business number so you do not have to set one up, while larger teams can connect their own account.

Common use cases

Real situations where this node earns its place in a flow.

Message on WhatsApp

Deliver an update on the channel much of the world uses day to day.

Send an approved template

Push a status or report link via a Meta-approved WhatsApp template.

Share a link with context

Send the report with a short accompanying message.

WhatsApp in a workflow

A simple example of where this node sits in a flow.

What you set up

Enter the recipient's WhatsApp number, or map it from a value the job captured.
Choose the pre-approved message template and map job values into its placeholders (name, link, reference).
Confirm which business account sends: dojobase's managed sender by default, or your own connected WhatsApp Business account.

Common questions

Why can't I just write any WhatsApp message I want?

To begin a conversation, WhatsApp only allows pre-approved templates. You fill in the blanks with job values, but the wording structure has to be an approved template first.

Do I need my own WhatsApp Business account?

Not to start. dojobase can send through its own managed business number by default. Larger senders can connect their own WhatsApp Business account instead.

Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.

Field	Type	Default	What it controls
`to`	string (phone)	—	Destination number; falls back to the confirmed relay recipient.
`sender`	enum: managed \| byo	—	Which sender identity to use; inferred from whether a key and from-number are set.
`from`	string (phone)	—	BYO sender number.
`apiKey`	string (secret)	—	BYO Telnyx API key; resolved from the org secret vault by reference.
`sendMode`	enum: template \| text	`template`	Send a Meta-approved template or a free-form text message.
`senderName`	string	`dojobase`	Display sender name for text mode.
`body`	string	—	Text-mode message body; falls back to a relay default then a built-in default.
`templateName`req	string	—	Meta-approved template name; required in template mode or the send fails.
`languageCode`	string	`en_US`	Template language code.
`bodyParams`	string	`{link}`	One template body parameter per line, each token-expanded.

to
Destination number; falls back to the confirmed relay recipient.
Type: string (phone)
sender
Which sender identity to use; inferred from whether a key and from-number are set.
Type: enum: managed | byo
from
BYO sender number.
Type: string (phone)
apiKey
BYO Telnyx API key; resolved from the org secret vault by reference.
Type: string (secret)
sendMode
Send a Meta-approved template or a free-form text message.
Type: enum: template | textDefault: template
senderName
Display sender name for text mode.
Type: stringDefault: dojobase
body
Text-mode message body; falls back to a relay default then a built-in default.
Type: string
templateNamereq
Meta-approved template name; required in template mode or the send fails.
Type: string
languageCode
Template language code.
Type: stringDefault: en_US
bodyParams
One template body parameter per line, each token-expanded.
Type: stringDefault: {link}

How this node appears inside a workflow's nodes[] array (the shape you see in the Developer export / import). A full workflow is { nodes: [...], edges: [...] }.

{
  "id": "whatsapp-out",
  "type": "card",
  "position": {
    "x": 160,
    "y": 120
  },
  "data": {
    "type": "whatsapp-out",
    "kind": "output",
    "title": "WhatsApp",
    "subtitle": "WhatsApp the report link",
    "config": {
      "to": "",
      "sender": "managed",
      "from": "",
      "apiKey": "",
      "sendMode": "template",
      "senderName": "dojobase",
      "body": "",
      "templateName": "",
      "languageCode": "en_US",
      "bodyParams": "{link}"
    }
  }
}