Events & Webhooks: A Practical Cookbook
Levi’s event and webhook system lets you connect your assistant to almost anything — CRMs, Slack, Zapier, Google Sheets, analytics platforms, or even your custom backend.
This guide serves as your cookbook for using Levi’s event triggers and webhooks to extend functionality, automate workflows, and build custom integrations.
🍳 What You’ll Learn
By the end of this guide, you’ll be able to:
Understand Levi’s event architecture
Create outgoing webhooks for any system
Receive external events back into Levi
Automate actions between tools like HubSpot, Slack, or Zapier
⚙️ Step 1 — Understand Levi Events
Everything in Levi generates an event. Think of these as moments that can trigger actions elsewhere.
Event Name | Description | Example Use |
|---|---|---|
lead.created | New lead captured from chat or form | Send notification to Slack |
lead.qualified | Lead meets qualification criteria | Create contact in CRM |
booking.scheduled | Appointment booked successfully | Add to Google Calendar |
booking.canceled | Appointment canceled by client | Trigger reschedule flow |
conversation.closed | Chat ended or conversation marked resolved | Send summary email |
💡 Tip: You can view live event activity in Developer → Event Logs.
🔗 Step 2 — Create an Outgoing Webhook
Go to Integrations → Webhooks → Create New.
Choose your event trigger (e.g.,
lead.created).Paste the endpoint URL where Levi should send the data.
Select POST as the method and choose data format — JSON is recommended.
Add custom headers (for example,
Authorization: Bearer <token>).Save and test — Levi will send a sample payload.
Example payload:
✅ Your webhook will now fire automatically whenever a new lead appears.
🧠 Step 3 — Receive External Events into Levi
Levi can also receive data from your external apps (for example, CRMs or analytics tools).
Go to Developer → Incoming Webhooks → Create Endpoint.
Copy the provided Levi Webhook URL.
From your external app (e.g., HubSpot, Stripe, Zapier), send a POST request to that URL with your payload.
Map incoming fields to Levi properties — e.g.,
email,status,source.
💬 Pro Tip: Add a secret header to authenticate external events securely.
🧩 Step 4 — Use Zapier or Make for No-Code Automations
If you’re not writing code, you can still connect Levi using Zapier or Make.
Example Recipes:
Goal | Trigger | Action |
|---|---|---|
Notify team in Slack |
| Post message to #sales-updates |
Add new lead to CRM |
| Create record in HubSpot |
Record every booking in Sheets |
| Append row to Google Sheet |
Trigger custom campaign |
| Send data to webhook URL |
💡 You can combine multiple Levi events to automate complex workflows — like automatically notifying the right salesperson based on lead location.
📊 Step 5 — Monitor and Debug Events
Use Developer → Event Logs to track performance.
Column | Description |
|---|---|
Event ID | Unique identifier for each trigger |
Status | Delivered, Pending, or Failed |
Attempts | Number of delivery retries |
Response Code | HTTP code returned by your endpoint |
Duration | Time it took to complete the request |
✅ Use the Retry button for failed deliveries or temporarily disable a webhook while testing.
🧩 Step 6 — Example: Slack Notification Workflow
Here’s a simple but powerful use case — notify your sales team in Slack every time a new lead is created.
Step | Tool | Action |
|---|---|---|
1 | Levi | Trigger event |
2 | Zapier | Receive webhook from Levi |
3 | Slack | Send message to #sales: “New lead {{name}} from {{source}}” |
Result: your team never misses a hot lead — all without writing a single line of code.
🧭 Summary
Step | Goal | Time |
|---|---|---|
1. Understand Events | Learn how Levi triggers actions | 5 min |
2. Create Outgoing Webhook | Send data to external apps | 10 min |
3. Receive External Events | Feed data into Levi | 10 min |
4. Use Zapier/Make | Build no-code automations | 10 min |
5. Monitor Logs | Debug and optimize | 5 min |
Total: 40 minutes to build your first end-to-end automation.