How I Track Website Demo Requests with Omnismith (and Instant Telegram Alerts)

Learn how I configured our own Book a Demo workflow on omnismith.io using dynamic schemas, REST endpoints, and instant Telegram automations.

When launching a product or publishing a landing page, capturing prospective customer inquiries and notifying your team immediately is essential for quick follow-ups.

Teams often face a compromise: either pay for rigid, costly CRM subscriptions or spend valuable engineering hours creating backend database tables and custom email scripts.

When building the Book a Demo page for Omnismith, I chose a third option: using Omnismith itself to collect submissions, store structured records, and trigger real-time team alerts.

Here is how I set up our complete end-to-end lead tracking workflow in just a few minutes.

---

Workflow Overview

The setup connects a public website form to a team Telegram channel in three straightforward steps:

1. Visitor Submits Form: A prospective customer fills out the "Book a Demo" form on the website.
2. Omnismith Stores Lead: Omnismith receives the data and saves it directly into your organized leads table.
3. Team Gets Notified: An automation rule instantly formats and pushes the lead details to your team's Telegram chat.

---

1. Defining the Data Model

First, I defined the fields needed to store incoming lead details. Rather than writing database migrations or configuring fixed tables, I used Omnismith's built-in AI Assistant to scaffold the structure:

Hi! I want to start tracking demo requests from my website form. It collects Full Name, Work Email, Company Name, Phone Number, Primary Use Case, and "How can Omnismith help your team?" (named as "Message"). All attributes as string. Could you help me set that up?

Within seconds, the assistant created the Demo Request template populated with the six string attributes:

Because attributes in Omnismith are dynamic, new fields can be added or updated later without schema lock-in or downtime.

---

2. Ingesting Form Submissions via REST API

Our public Book a Demo page presents a clean, responsive contact form:

When a visitor submits the form, an extremely simple serverless function (like a Cloudflare Worker or API route) receives the form data and sends an HTTP POST request directly to the Omnismith /v1/entities endpoint, mapping form fields to attribute slugs:

POST /v1/entities
Content-Type: application/json

{
  "template_slug": "demo_request",
  "attribute_values": [
    { "attribute_slug": "full_name", "value": "Jane Doe" },
    { "attribute_slug": "work_email", "value": "[e-mail]" },
    { "attribute_slug": "company_name", "value": "Acme Corp" },
    { "attribute_slug": "phone_number", "value": "[phone]" },
    { "attribute_slug": "primary_use_case", "value": "Dynamic EAV Backend" },
    { "attribute_slug": "message", "value": "We would like to test integrating our website forms with Omnismith." }
  ]
}

Upon receipt, Omnismith assigns a unique record identifier, validates attribute values, and writes the entry into storage.

---

3. Centralized Lead Records Dashboard

All submitted demo requests immediately populate the Omnismith dashboard under the Demo Request records view:

From here, team members can search, filter, and inspect incoming inquiries in real time without accessing raw database tools or navigating complex CRM menus.

---

4. Configuring Real-Time Telegram Alerts

Prompt response times make a huge difference in lead conversion. To ensure our team is notified instantly, I configured an automated Telegram alert in three simple steps:

Step A: Register the Telegram Notification Channel

In the Omnismith console under Automations > Notification Channels, I added a new channel using our Telegram Bot token:

Step B: Create the Automation Rule

Next, I defined an automation rule triggered whenever a new entity is created under the demo_request template:

Step C: Format the Alert Message

I structured the alert payload template using variable placeholders to map record fields directly into the Telegram message:

---

The Outcome: Instant Notifications for Every Lead

Whenever a visitor submits the demo form, our team receives a clear, formatted notification in our internal Telegram channel within seconds:

---

Key Implementation Considerations

• Authentication & Proxying: To prevent exposing API access tokens on public frontend clients, requests can be routed through a lightweight serverless handler or backend proxy.
• Input Validation: Basic form validation (such as email formatting and required fields) should be enforced on the client side before submitting the payload to the API.

---

Summary

By leveraging Omnismith's dynamic schema engine and event-driven automations, I built a reliable lead capture and notification pipeline in minutes—eliminating the need for custom database migrations or dedicated CRM software subscriptions.