Webhooks allow DMLY to send real-time data to your external systems whenever specific events happen inside your workspace.

Instead of manually exporting data, DMLY automatically pushes event notifications (like new messages, new contacts, tag updates, etc.) directly to your server endpoint.

What Are Webhooks and How to Set it up?

A webhook is a real-time HTTP request sent from DMLY to your server when an event occurs.

For example:

• A new WhatsApp message is received

• A contact is created

• A tag is added

• A message is sent

• A website live chat message arrives

DMLY immediately sends structured JSON data to your configured Server URL.

Method 1: Standard Webhook Integration (From Integrations Menu)

This is the easiest way to connect DMLY to your external system.

Step 1: Go to Webhooks

1. Navigate to Integrations

2. Click Webhooks

3. Click Connect

4. Click Add New Webhook

Step 2: Configure Your Webhook

You will see the Webhook Configuration screen.

Required Fields

Name

Give your webhook a descriptive name
Example:
CRM Sync
New Lead Automation

Server URL

Enter your server endpoint where DMLY should send data.

Example:

https://yourdomain.com/webhook-endpoint

This must be:

• Publicly accessible

• HTTPS recommended

Events

Select the events that should trigger the webhook.

Available events include:

• Incoming WhatsApp Messages

• Outgoing WhatsApp Messages

• Incoming Instagram Messages

• Outgoing Instagram Messages

• Incoming Messenger Messages

• Outgoing Messenger Messages

• Incoming Telegram Messages

• Outgoing Telegram Messages

• Incoming Website Messages

• Outgoing Website Messages

• Contact Created

• Contact Tag Added

• Contact Tag Removed

Active Toggle

Turn this ON to activate the webhook.

Headers (Optional but Recommended)

You can add custom headers such as:

Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json

Click Add Header to include API keys or secret tokens.

This improves security and verification on your server.

Save the Webhook

Click Save once completed.

Your webhook is now live and will start sending event data to your server.

Important Note

Webhooks are NOT triggered for:

• Data imported via CSV bulk import

• Outgoing messages sent via Broadcasts

Those need to be manually synced if required.

Method 2: Advanced Setup – Customized Payload via Automation

This method gives you full control over:

• Custom JSON payload structure

• Dynamic variables

• Custom headers

• Trigger conditions

• RESTful request control

Perfect for advanced integrations or custom backend systems.

Steps:

Go to Automations

Click Add Rule → Choose Create Rule from Scratch

Set the Trigger

Example triggers:

• When a Contact is Created

• When a Tag is Added

• When a Message is Received

(Optional) Add Conditions

Filter the trigger logic if needed.

Example:

• Only if tag = "Lead"

• Only if channel = WhatsApp

Add Action → Send Webhook

Choose:
Send Webhook

Configure the Webhook

Request Method

Select:

POST

URL

Enter your webhook endpoint:

https://yourdomain.com/api/leads

🔹 Payload

Customize your JSON body.

You can insert dynamic variables using #.

Example:

{
  "contact_name": "#contact.name#",
  "phone": "#contact.phone#",
  "channel": "#message.channel#",
  "message": "#message.body#"
}

🔹 Headers

Use default headers or click Add Header to add:

Authorization: Bearer YOUR_SECRET
X-Source: DMLY

6️⃣ Send Test Webhook

Click Send Test Webhook to validate your configuration.

Click Save

Your automation-powered webhook is now active.

How to Test Webhooks (Using RequestBin Flow)

Testing is critical before going live.

Step 1: Visit RequestBin

Go to:

https://requestbin.com

Sign up or log in.

Step 2: Create a Request Bin

Click Create Request Bin
This generates a temporary test webhook URL.

Step 3: Copy the Generated Request URL

Paste it into:

• Webhook → Server URL (Method 1), OR

• Automation → Webhook URL (Method 2)

Step 4: Trigger the Event

Examples:

• Create a new contact

• Send a message

• Add a tag

Step 5: Inspect Incoming Payload

Return to RequestBin and inspect:

• Headers

• JSON body

• Event structure

Verify data matches your expectations.

Step 6: Replace With Your Production Endpoint

Once confirmed:

• Replace the RequestBin URL with your real server endpoint

• Click Save

Best Practices for Webhooks

Security

• Always use HTTPS

• Add authentication headers

• Validate incoming requests on your server

• Use secret tokens

How to View Webhook Logs in DMLY

Webhook logs help you monitor deliveries, debug issues, and verify whether your external system is successfully receiving events from DMLY.

If a webhook is not working as expected, this should be your first troubleshooting step.

Where to Find Webhook Logs

1. Go to Integrations

2. Click Webhooks

3. On the top-right corner, click View Logs

This opens the webhook activity log panel.

What You’ll See in Webhook Logs

The logs provide detailed information for every webhook attempt, including:

• Date & Time of the request

• Target Server URL

• Payload sent (JSON body)

• Request headers

• HTTP Status Code returned by your server

• Error messages (if any)

• Success confirmations

Understanding Status Codes

Here’s how to interpret common responses:

If you’re not seeing 200 OK, the issue is likely on your server side.

How to Use Logs for Troubleshooting

If your webhook fails:

1. Click the specific log entry.

2. Review the payload that was sent.

3. Check the response returned by your server.

4. Verify:

   • Server URL is correct

   • Endpoint is active

   • Headers (Authorization tokens) are valid

   • Your server returns HTTP 200

Common Reasons Webhooks Fail

• Expired API token

• Wrong Authorization header

• Server endpoint not public

• Firewall blocking requests

• Incorrect JSON parsing

• SSL certificate issues