How to send WhatsApp Message via API using QuickReply.ai?

Businesses often want to start a WhatsApp conversation automatically when something happens — like a user signs up, places an order, submits a form, requests a demo, etc.

QuickReply.ai makes this extremely easy for developers by letting them pass raw JSON payloads and processing everything inside QuickReply.ai's platform.

🔥 USE CASE EXAMPLE

Imagine you are a business that wants to trigger WhatsApp notifications whenever a visitor:

• Registers on website

• Requests a callback

• Downloads a guide

• Books a free session

In this guide, we will walk you through how to use QuickReply.ai’s Data Sources and Journeys to automatically send a welcome message with login details or access links the moment someone registers on your site.

---

Chapter 1 - The Premise – "SkillUp Academy"

To make this tutorial practical, let’s imagine a fictional EdTech platform called "SkillUp Academy."

The Use Case: SkillUp Academy offers free coding webinars. Users fill out a registration form on the landing page to book a spot.

The Problem: Users register, but the confirmation email goes to Spam/Promotions. They forget about the webinar and never show up.

The Solution: We want to trigger a WhatsApp Registration Success message containing the Zoom link immediately after the user hits "Sign Up" on the website.

The Workflow:

1. Website Event: User fills the "Save My Spot" form.

2. API Trigger: The website backend sends user data to QuickReply.ai via Webhook.

3. Journey: QuickReply.ai sends a message: "Hi Alice, you are registered for Python 101! Here is your joining link."

---

Chapter 2: Applying for the Template

Before coding, we need a Meta-approved message template.

1. Navigate to Templates:

   • Log in to QuickReply.ai.

   • Go to Templates > Create WhatsApp Template.

2. Define the Template:

   • Name: registration_welcome_v1

   • Type: Standard

   • Category: Utility (Best for confirmations).

   • Language: English.

3. Draft the Content as shown below

Body:

Hi {{1}}! 👋

Welcome to SkillUp Academy. You have successfully registered for {{2}}.
📅 Access your session by clicking on the button below on {{3}} at {{4}}.

See you there!

Button:

Join Session

1. Now Submit with sample values such as (e.g., "Alice", "Python Webinar", "25-Dec-2025", "04:00 PM", "https://zoom.us/...")

---

Chapter 3: Data Source, Webhook & Events

We need to create a "listener" on QuickReply.ai that waits for your website to send data. We will use Postman to simulate a user signing up on your website.

1

Create the Webhook

• Go to Data Sources on the left sidebar.

• Click Create New Data Source > Webhook.

• Name it: SkillUp Website.

• Copy the Webhook URL provided. (e.g., https://webhooks.quickreply.ai/v1/receivers/abc12345).

2

Triggering from Postman

1. Open Postman.

2. Create a POST request.

3. URL: Paste the Webhook URL.

4. Body: Select raw JSON. Paste this payload:

{
  "event_name": "user_signup",
  "phone": "919876543210",
  "name": "Alice Baker",
  "event_title": "Python Masterclass",
  "event_date": "25-Dec-2025",
  "event_time": "04:00 PM",
  "join_link": "https://skillup.com/live/8877"
}

A field containing phone number is mandatory. Always include the country code in the phone number.

1. Click Send. Ensure you get a success response.

3

Map the Event

1. Go back to Data Sources in QuickReply.ai.

2. Find the event log and click Map Event.

3. Event Name: Select event_name (Value: user_signup).

4. Map Attributes:

   • phone → Phone Number.

   • name → Name.

5. Click Save.

---

Chapter 4: Creating the Journey

Now we tell the system: When a user signs up, send the template.

1. Go to Journeys > Create Journey.

2. Trigger

   1. Source: SkillUp Website

   2. Event Name: SkillUp Webinar Registration.

3. Action: Add a Send WhatsApp Template node.

4. Select Template: Choose registration_welcome_v1.

5. Map Variables:

   • {{1}} : Select body.name.

   • {{2}}: Select body.event_title.

   • {{3}}: Select body.event_date.

   • {{3}}: Select body.event_time

   • {{3}}: Select body.join_link

6. Choose "Journey Complete" as the Goal.

7. Save and Publish.

---

Chapter 5: Going Live and Testing

1. Live Test:

   • Open Postman.

   • Change the phone to your personal WhatsApp number.

   • Change the name to your name.

   • Click Send.

2. Result: Check your WhatsApp. You should receive the personalized welcome message immediately.

---

Once you are able to send the first message, you can add wait nodes and followup messages or use conditional branching to create a segment wise user messaging experience.

---

Analytics & Engagement

Once this is live on your website, you can track performance in the Analytics tab:

• Read Rate: Are users actually seeing the message?

• CTR (Click-Through Rate): specific to the join_link.

• Failed Messages: Check if users are entering invalid phone numbers on your signup form

---

Why this is better than direct Send Template API?

Many businesses ask:

“Why can’t I just call the WhatsApp API from my backend? Why should I use QuickReply.ai Journeys?”

Here is the clear, practical answer.

1

Minimal Development Effort

With Journeys, you only send one event payload to QuickReply.ai. Everything else — selecting the template, sending the message, retries, fallbacks — is handled by the platform.

No more writing API calls, managing variables, handling failures, or redeploying code.

2

No-Code Editing of Templates & Flows

If tomorrow you want to:

• update wording

• change formatting or variable values

• add/remove fallback messages

• modify timing or flow logic

…you can do all of this from the UI, without involving engineering.

Example

Scenario: You want to change the template text from “Welcome to SkillUp” → “Get ready to learn!”

Solution: Just edit the template or the Journey step inside QuickReply.ai.

No developer needed. No code deployment needed.

3

Easy Follow-up Sequences

If your use case needs a sequence (example: send message → wait → reminder → conditional message), you can visually build it in the Journey builder.

No backend complexity.

4

Built-in A/B Testing

Journeys let you test different messaging approaches without touching code.

Example

Scenario: You want to test if sending a PDF immediately performs better than sending it after 1 hour.

Solution: Add an A/B Split + Wait node in the Journey builder.

No engineering. Just drag, drop, publish.

5

Auto-Scaling, Queuing & Retry Handling

If your system emits thousands of events at once, calling the Send Template API directly will likely start failing, and you’ll have to manually manage:

• rate limits

• retries

• failures

• batching/queuing

Journeys handle all of this automatically.

Events are queued, retried, and executed reliably at scale without data loss.

6

Centralized Journey Analytics

In Journeys, you get a complete visual dashboard:

• which events triggered

• which messages failed

• which messages got delivered

• what % of users progressed through which node

• what A/B test variant performed better

If you use the Send Template API directly, you have to build all this reporting yourself.

---

Summary Comparison

Feature	Send Template API (Direct)	QuickReply.ai Journeys
Development effort	High	Very low
Change templates	Requires code change	No-code edits
Follow-up logic	Build yourself	Drag & drop
A/B testing	Build logic manually	One-click
Scaling & retries	Developer-managed	Auto-managed
Analytics	Build dashboards yourself	Built-in
Speed to experiment	Slow	Instant

---

Final Takeaway

If you want:

• faster iterations

• fewer engineering dependencies

• higher reliability at scale

• built-in analytics

• drag-and-drop automation

…then Journeys is the superior approach vs. calling the Send Template API directly.