Webhooks
Managing Webhooks
Goal: Set up and manage webhooks to send real-time nativeMsg event data to your own systems. Estimated Time: 5–10 minutes
What's a webhook?
A webhook is a simple, automated message sent from nativeMsg to your system when a specific event occurs. It’s a way for your tools (like CRMs, analytics, or databases) to receive instant updates — no manual refresh required.
⚙️ When triggered, nativeMsg makes an HTTP POST request to the URL(s) you’ve set in your account.
🧭 Where to Manage Webhooks
Go to Settings → Webhooks in your nativeMsg dashboard.
You’ll see a list of all existing webhooks — inbound and outbound.
Each webhook shows:
URL endpoint
Event type(s)
Secret key
Edit/Delete options
🧱 Types of Webhooks
Inbound
Triggered when data enters nativeMsg (e.g., a message received, user action).
User sends a new message to a bot.
Outbound
Triggered when data leaves nativeMsg (e.g., a message sent, a status change).
Bot sends a message or completes an interaction.
💡 You can add multiple webhooks for different systems or event types — each with its own secret key.
🧩 Creating a New Webhook
Go to Settings → Webhooks.
Click Create New Hook.
In the dialog box, fill in the fields:
URL
The endpoint where nativeMsg will POST data. Must include https:// (e.g., https://yourdomain.com/webhook).
Events
Select one or more events you want to trigger this webhook. Examples: message.received, message.sent, user.created.
Click Create.
✅ The new webhook is created with a unique secret key for verification and security.
🔒 Keep your secret key private — it’s used to validate that webhook payloads are coming from nativeMsg.
✏️ Editing a Webhook
Go to Settings → Webhooks.
Find the webhook you want to update.
Click Edit.
Change the URL or Events as needed.
Click Update.
✅ The webhook will continue running with the new configuration immediately.
🗑️ Deleting a Webhook
Go to Settings → Webhooks.
Click Delete next to the webhook.
Confirm Yes to remove it.
⚠️ Once deleted, events will no longer send to that endpoint.
🧠 Pro Tips for Success
Always use HTTPS
Ensures secure communication. Plain HTTP is not supported.
Verify your secret key
Authenticate incoming requests to prevent spoofing.
Log incoming payloads
Helps debug or replay webhook data if needed.
Filter events by importance
Avoid unnecessary traffic — subscribe only to what you need.
Test before going live
Use a tool like Webhook.site or Postman to preview data.
⚙️ Common Use Cases
CRM Integration
Send new lead info or chat interactions to HubSpot, Salesforce, etc.
Analytics Tracking
Log message delivery and engagement events in your BI tool.
Automation Triggers
Launch workflows (e.g., via Zapier or n8n) when users engage with your bot.
Custom Reporting
Store conversation data in your internal database.
💬 Webhooks make nativeMsg part of your larger automation ecosystem.
🧩 Example JSON Payload
🧠 Use the
signatureheader to verify authenticity using your secret key.
✅ Quick Recap
You can:
Create secure webhook URLs for inbound/outbound events
Edit or delete existing hooks anytime
Use webhooks to integrate nativeMsg data with your own systems
🔗 Webhooks are your real-time bridge between nativeMsg and everything else in your tech stack.
Last updated
Was this helpful?

