Submit by 11 PM IST
Week 1 · Day 1 of 14
Week 1
Day 1 ✓
Day 2 ✓
Day 3 ✓
Day 4 ✓
Day 5 ✓
Day 6 ✓
Week 2
Day 7 ✓
Day 8
Day 9
Day 10
Day 11
Day 12
Week 3
Day 13
Day 14
Day 15
Day 16
Day 17
Day 18
Week 4
Day 19
Day 20
Day 21
Day 22
Day 23
Day 24
Week 5
Day 25
Day 26
Day 27
Day 28
Day 29
Day 30
Week 6
Day 31
Day 32
Day 33
Day 34
Day 35
Day 36
Week 7
Day 37
Day 38
Day 39
Day 40
Day 41
Day 42
Week 8
Day 43
Day 44
Day 45
Day 46
Day 47
Day 48
⚡ Do This Right Now
1
Read the explainer
2
Pass the quiz (3/5)
3
Submit before 11 PM
🕚 Deadline: 11 PM IST
1
Read
2
Quiz 3/5
3
Submit
🕚 11 PM IST
🔒

This task is currently closed.

Day 1 is assigned to a specific date by the WSP team based on your batch start date.

📅 Check your confirmation email for your full task schedule.

Haven't received it? Email hello@wa.expert and we'll sort it out quickly.
📅 Week 1 · Monday
day-01

What is WA.Expert?.

Today you'll learn: what WA.Expert is and why businesses pay for it — explained so clearly you could teach it to your parents by tonight.

⏱ ~20 mins
📖 Read + Quiz + Submit
✅ Need 3/5 to unlock
🔒 Tuesday only
Week
Week 2 of 8
Day
1 of 14
Program
2-Week Program
📖 Read This First — About 8 Minutes

If you understand webhooks, you can connect WA.Expert to anything. That is not an exaggeration.

Webhooks are the integration mechanism that makes WA.Expert a platform rather than just a messaging tool. Understanding them — how they work, how to design them, and how to troubleshoot them — is the single technical skill that unlocks the most advanced implementations.

The good news: webhooks are conceptually simple. Event occurs → HTTP POST request fires → receiving system acts on the data. That is the whole thing.

🔔
A webhook is a doorbell. When the button is pressed (event), an electrical signal fires (HTTP POST), and the bell rings inside (receiving system acts). You don't keep checking the door — the bell tells you when something happened. That is webhook architecture.
📤
WA.Expert → external system
When a form is submitted in WA.Expert (chatbot input, Flow completion), WA.Expert fires a webhook to a URL you provide — delivering data as a JSON payload to your system.
📥
External system → WA.Expert
When an event happens in your external system (new order, payment received), your system fires a webhook to WA.Expert's API, which triggers the appropriate WhatsApp message.
📋
Payload design
JSON body should contain: event type, timestamp, unique identifier, relevant data fields. Minimise payload size — send only what the receiving system needs to act.
🔧
Error handling
Every webhook needs: retry logic (auto-retry 3x on failure), logging (every payload logged), dead letter queue (failed retries flagged for manual review). No data silently lost.

🔑 Non-coder's webhook toolkit: Make.com, Zapier, and n8n receive webhook payloads and route data between systems visually — no code required. For most client implementations, these are faster and more maintainable than custom code.

💡
Read the reference page below before taking the quiz.
🔗
Read: WhatsApp Webhook Guidewa.expert/pages/whatsapp-webhook-guide.html · Technical webhook guide · ~6 mins
🧠 Quiz — 5 Questions
🧠
Day 1 Quiz
Score 3 or more to unlock your submission. Retry as many times as you want — every wrong answer tells you why.
5 questions Need 3/5 Unlimited tries Instant feedback
Question 1 of 5
What is a webhook in plain terms?
A
A special type of WhatsApp message template
B
A notification that one software system sends to another when a specific event occurs — delivered as an HTTP POST request containing data as a JSON payload
C
A backup system for storing WhatsApp conversations
D
A tool for testing API connections
✅ Event → HTTP POST → data delivered to receiving URL → receiving system acts. Simple concept, very powerful application.
❌ A webhook is an event-triggered notification. Event occurs → POST fires → data arrives → receiving system acts. Conceptually simple, architecturally powerful.
Question 2 of 5
Shopify store wants every new order to trigger a WhatsApp confirmation. How does this work technically?
A
WA.Expert polls Shopify every minute
B
Shopify fires a webhook to WA.Expert's API when an order is created → payload contains phone, order ID, items, address → WA.Expert sends the confirmation template
C
Store owner manually triggers the WhatsApp for each order
D
Shopify sends an email that WA.Expert converts
✅ Shopify webhook → WA.Expert API → template sent. Event-driven, real-time, zero manual intervention at any order volume.
❌ Shopify webhook → WA.Expert API → WhatsApp template is the architecture. Event-driven, real-time, no human step.
Question 3 of 5
What should a well-designed webhook payload for a WA.Expert task submission include?
A
Only the user's phone number
B
Event type, timestamp in IST, unique submission ID, user identifier (WSP ID), task number, quiz score, answer text, and any other fields the receiving system needs to act
C
Full conversation history
D
User's browser fingerprint
✅ Event type + timestamp + unique ID + user identifier + relevant data fields. Everything the receiving system needs to act correctly. Nothing unnecessary.
❌ Minimum viable payload: event type, timestamp, unique ID, user ID, specific data fields. Keep payloads lean — only what the receiving system needs.
Question 4 of 5
A webhook fires but the receiving system is temporarily down. What should happen?
A
Data is lost permanently
B
Retry logic: send system retries 3 times at increasing intervals (1min, 5min, 30min). If all fail, payload goes to dead letter queue for manual review and reprocessing.
C
User is notified of the failure
D
The event is cancelled
✅ Retry + dead letter queue. Webhooks without retry logic lose data during outages. Dead letter queues ensure failed deliveries are never silently dropped.
❌ Retry + dead letter queue is the production pattern. 3 retries at increasing intervals, then manual review queue. No data silently lost.
Question 5 of 5
Non-technical client wants to connect WA.Expert to Google Sheets without writing code. Recommended approach?
A
Hire a developer
B
Use Make.com or Zapier — these no-code platforms receive WA.Expert webhooks and route data to Google Sheets visually, without writing a single line of code
C
Export data manually and paste into Sheets
D
Ask WA.Expert support to do the integration
✅ Make.com or Zapier. No-code webhook routing that connects WA.Expert to any tool visually. Most standard integrations can be built this way in 30 minutes.
❌ Make.com or Zapier is the answer. No-code webhook routing platforms. Standard integrations without custom code — accessible to non-technical teams.
of 5
Answer all 5 questions, then check your score.
✏️ Your Task
🔒

Score 3/5 to unlock this

Complete the quiz above first. The moment you score 3 or more, this section unlocks.

🏅

🎉 Day 1 — done!

Day 2 opens on your assigned Tuesday.

📝 Today's Task
Someone in your family runs a small business. In 3–4 sentences, explain WA.Expert to them like you're actually WhatsApp-ing them right now. Your own words — not copied from the page.
Start like this: "So there's this platform I was reading about — it's basically for businesses that get too many WhatsApp messages to handle manually. It lets them..."
0 / 800
From your registration confirmation email. Can't find it?
Submitting before 11 PM IST on your assigned Tuesday counts as Day 8 complete.
Week 1 · Coming Tomorrow
Day 2 — WhatsApp App vs Business API Opens Tuesday on your assigned date.
Day 2 →
WSP · WA.Expert Student Programs · wa.expert Help: hello@wa.expert
📋 Register a friend 🎁 Share your WSP ID