What Is a Webhook? Simple Guide to Webhooks in ZazzyAgent
A webhook lets another application send information to ZazzyAgent automatically when something happens.
Instead of repeatedly asking another system whether something changed, the other system can send the information to ZazzyAgent as soon as the event occurs.
That makes webhooks useful for real-time automation.
A simple example
Imagine you have an ecommerce store.
A customer places an order.
Your store sends the order information to a ZazzyAgent webhook.
ZazzyAgent receives:
Customer name
Phone number
Order number
Order information
Other available data
Your workflow can then use that information to send a WhatsApp message.
For example:
Hi Rahul, your order #12345 has been received.
Everything can happen automatically.
Webhook explained simply
Think of a webhook as a delivery address.
Your external application says:
Something happened.
Then it sends the relevant information to the webhook URL.
ZazzyAgent receives that information and can use it in the configured workflow.
API vs webhook
These two concepts are related but work in different directions.
API
ZazzyAgent or another application asks:
Give me this information.
Webhook
Another application says:
Here is information about something that just happened.
A useful way to remember it:
API = request
Webhook = notification
When should I use a webhook?
Webhooks are useful when you want automation to start because something happened in another system.
Examples:
New order
New lead
Form submission
Payment received
Appointment created
Cart abandoned
Customer registered
Shipment updated
Example: Website lead
A visitor fills out:
Name: Rahul Phone: +91XXXXXXXXXX Requirement: WhatsApp automation
Your website sends that information to a ZazzyAgent webhook.
Your workflow can then:
Receive the data.
Map the fields.
Send a WhatsApp template.
Save customer information.
Apply a label.
Trigger another workflow.
Example: Shopify order
A customer completes an order.
Shopify sends the event to ZazzyAgent.
The workflow receives the order information.
It can then send a WhatsApp notification using the appropriate template.
What is a webhook URL?
A webhook URL is the address that another application sends its data to.
When you create a supported webhook workflow in ZazzyAgent, the workflow provides a webhook URL.
You copy that URL into the external application.
What happens when data reaches ZazzyAgent?
A typical process looks like this:
External Application
↓
Webhook URL
↓
ZazzyAgent receives data
↓
Capture sample data
↓
Map fields
↓
Run workflow
↓
WhatsApp message / action
What is webhook data?
Webhook data is normally structured information sent by the external system.
It may look conceptually like:
{
"name": "Rahul",
"phone": "+919999999999",
"order_id": "12345"
}
The actual structure depends entirely on the application sending the webhook.
Why do you need to capture sample data?
External systems don't all use the same field names.
One application may send:
customer.first_name
Another may send:
billing.first_name
Another may send:
name
Capturing a sample payload lets you see the actual fields being received and select the correct values during mapping.
Mapping webhook data
Suppose the incoming data contains:
customer.first_name
customer.phone
order.id
You can map:
Customer Name → customer.first_name
Phone → customer.phone
Order Number → order.id
Those values can then be used in the workflow.
Webhook data can be transformed
Sometimes the value you receive isn't immediately suitable for WhatsApp.
Examples:
Phone number contains unwanted characters.
Name has unnecessary spaces.
Amount needs formatting.
Date needs a different format.
Where supported, data formatting tools can be applied before the value is used.
Webhook-triggered WhatsApp messages
A common workflow is:
External Event
↓
Webhook
↓
Capture data
↓
Map customer phone
↓
Map customer name
↓
Select WhatsApp template
↓
Send message
For business-initiated messaging, make sure the selected WhatsApp template meets the applicable WhatsApp requirements.
Webhook workflows don't have to be simple
You can build more advanced workflows using the received data.
For example:
Order created
↓
Check order value
↓
If order value > ₹10,000
→ Add VIP label
Otherwise
→ Standard flow
You can combine webhooks with other automation tools where supported.
Inbound vs outbound webhooks
There are two useful directions.
Incoming webhook
Another application sends data to ZazzyAgent.
Example:
Shopify → ZazzyAgent
Outbound webhook
ZazzyAgent sends information to another application.
Example:
ZazzyAgent → Zapier
The direction determines which system starts the request.
Common webhook problems
Webhook receives nothing
Check:
Correct webhook URL
External system actually sends the event
Webhook is enabled
Correct event selected
External application's webhook configuration
Data arrives but fields are empty
Capture a fresh sample payload.
Then check the field mapping.
Phone number is incorrect
Check the exact phone value being sent.
You may need to format the number correctly before sending a WhatsApp message.
Workflow runs but message isn't sent
Check:
WhatsApp account
Template
Template approval
Recipient number
Messaging eligibility
Message status
When not to use a webhook
You don't need a webhook for every integration.
If ZazzyAgent already has a native integration for what you're trying to accomplish, that may be easier.
Use webhooks when:
You need real-time event-based automation.
Your application supports webhooks.
You need a custom integration.
You need data from an external application that doesn't have a native connection.
The easiest way to remember webhooks
A webhook answers:
"Tell ZazzyAgent when something happens."
An API answers:
"Let ZazzyAgent ask another system for information or send it an instruction."
Once you understand that difference, building external integrations becomes much easier.