message/sendText

When to Use

• Order status updates: An e-commerce workflow sends a plain-text confirmation to the customer's WhatsApp number the moment their order ships, including the tracking number and estimated delivery date.
• OTP and verification codes: An authentication workflow sends a one-time passcode to a user's WhatsApp number as a fast, high-deliverability alternative to SMS.
• Appointment reminders: A scheduling workflow sends a reminder 24 hours and 1 hour before a booking, including the appointment time, location, and a link to reschedule.
• Customer support replies: A support ticketing workflow sends a text reply to the customer on WhatsApp when an agent updates their ticket status.
• Internal team alerts: A monitoring workflow sends a text alert to a manager's WhatsApp when a critical threshold is crossed, such as a payment gateway error rate exceeding 5%.

Configuration

Connection

Operation

Sample Configuration

{
  "resource": "message",
  "operation": "sendText",
  "accessToken": "{{ $credentials.whatsAppToken }}",
  "phoneNumberId": "123456789012345",
  "to": "{{ $input.customerPhone }}",
  "text": "Hi {{ $input.customerName }}, your order #{{ $input.orderId }} has shipped! Track it here: https://track.example.com/{{ $input.trackingCode }}",
  "previewUrl": "true"
}

Validation Errors

Output

Success Port

Fires after Meta confirms the message was accepted for delivery. The messageId is the unique WhatsApp message ID (wamid) and should be stored if you need to send a reaction or delete the message later.

Error Port

Fires when Meta rejects the request or when the network call fails. Always connect the error port to a logging or alerting node in production workflows.

Sample Output

{
  "messageId": "wamid.HBgLMTQxNTU1NTI2NzEVAgARGBI2QzM4NjhGQTExMjQ3RDMAA",
  "phoneNumberId": "123456789012345",
  "to": "14155552671",
  "status": "sent",
  "errorCode": null,
  "errorMessage": null,
  "rawResponse": "{\"messaging_product\":\"whatsapp\",\"contacts\":[{\"input\":\"14155552671\",\"wa_id\":\"14155552671\"}],\"messages\":[{\"id\":\"wamid.HBgLMTQxNTU1NTI2NzEVAgARGBI2QzM4NjhGQTExMjQ3RDMAA\"}]}"
}

Expression Reference

Node Policies & GuardRails

Examples

OTP Verification Code

{
  "resource": "message",
  "operation": "sendText",
  "accessToken": "{{ $credentials.whatsAppToken }}",
  "phoneNumberId": "123456789012345",
  "to": "{{ $input.phoneNumber }}",
  "text": "Your BizFirstAI verification code is: {{ $input.otpCode }}\n\nThis code expires in 10 minutes. Do not share it with anyone.",
  "previewUrl": "false"
}

Sends a one-time passcode to the user's WhatsApp number during account verification. The workflow upstream generates a 6-digit code, stores it in the session with a 10-minute TTL, and passes it to this node via $input.otpCode.

Shipment Tracking Alert with Link Preview

{
  "resource": "message",
  "operation": "sendText",
  "accessToken": "{{ $credentials.whatsAppToken }}",
  "phoneNumberId": "123456789012345",
  "to": "{{ $input.customerPhone }}",
  "text": "Your order #{{ $input.orderId }} is on its way! Track your delivery: https://track.example.com/{{ $input.trackingId }}",
  "previewUrl": "true"
}

The previewUrl: true option causes WhatsApp to fetch and display a rich link card for the tracking URL, showing the page title and thumbnail. This increases click-through rate compared to a plain URL.

Dynamic Appointment Reminder

{
  "resource": "message",
  "operation": "sendText",
  "accessToken": "{{ $credentials.whatsAppToken }}",
  "phoneNumberId": "123456789012345",
  "to": "{{ $input.patientPhone }}",
  "text": "Reminder: You have an appointment with {{ $input.doctorName }} tomorrow at {{ $input.appointmentTime }}.\n\nLocation: {{ $input.clinicAddress }}\n\nReply YES to confirm or call {{ $input.clinicPhone }} to reschedule.",
  "previewUrl": "false"
}

A ScheduledTrigger node fires this workflow 24 hours before each appointment. Patient data is sourced from the CRM and passed as input variables. The free-form text format is valid here because appointment reminders fall within the 24-hour conversation window after the patient originally booked.