Installs in ~2 min· 4 assets · 9 steps

Stop letting demo requests go cold before anyone books

A demo request never goes cold: booked, confirmed, chased, and tracked without a rep touching a spreadsheet.

A prospect fills in the demo request form. They get a Calendly link straight away, sales gets notified, and the moment they book, TinyCommand matches the booking back to their original request and updates everything itself. If they go quiet, the reminders go out on their own.

Free · no credit card · you connect your own apps

The blueprint
Trigger
Demo Request Form is submitted
Every run starts from one submission.
Action
Send Booking Link
Action
Notify Sales
Trigger
Calendly Booking Listener
Action
Booking Reminder
What gets built

4 things appear in your workspace.

Installing provisions each one, wired together and ready to run.

FormDemo Request Form

form capturing name, company, and email address. Every submission creates a lead row with the status Requested. Publishing it auto-creates the Demo Requests sheet, the single system of record for every lead and its status.

WorkflowNew Demo Request

Fires on every new lead in the Demo Requests sheet: marks the lead Requested, emails the prospect a thank-you with a Calendly booking link, and notifies the sales team.

WorkflowBooking Listener

Sends the confirmation email with the Calendly link, notifies sales, listens for Calendly bookings and matches them by email address, updates status and stores the meeting time, and sends reminders to prospects who haven't booked.

WorkflowBooking Reminder

A daily job finds leads still marked Requested after a configurable number of days and emails them a friendly reminder with the Calendly booking link.

What you connect

The apps this recipe needs.

You connect your own accounts. Swap any app that offers an alternative at install.

Scheduling
Calendly *

Listens for new Calendly bookings (invitee-created) and fetches each scheduled event so leads can be matched and updated automatically.

Prospect Email
Gmail *

Sends the booking-link confirmation, the post-booking confirmation, and reminder emails to the prospect. Swap for Brevo.

Rep Notification
Slack *

Notifies the sales team of every new demo request with the prospect's details. Swap for Telegram, Discord, or Google Chat.

How it works

Step by step, once it is running.

  1. 01
    A Prospect Requests a Demo

    They submit the Demo Request Form, built with form.

  2. 02
    The Lead Is Stored Immediately

    Their name, company, email address, and submission date land in TinyTables with an initial status of Requested.

  3. 03
    They Get a Booking Link

    Right Away An automated confirmation email thanks them for their interest and hands them a Calendly booking link, while their interest is still warm, not three days later when a rep gets to their inbox.

  4. 04
    Sales Is Notified

    The team receives an email or Slack notification about the new demo request the moment it arrives.

  5. 05
    TinyCommand Watches Calendly

    It listens for new meeting bookings on your connected Calendly account.

  6. 06
    The Booking Is Matched Back to the Request

    Whenever a meeting is booked, TinyCommand matches the invitee's email address against the records in TinyTables. If it finds a matching record still marked Requested, it updates the status to Meeting Scheduled, stores the scheduled date and time, and sends the prospect a confirmation email with any additional information or preparation material. Nobody cross-references two systems by hand.

  7. 07
    Quiet Prospects Get a Nudge

    If a prospect hasn't booked within a configurable number of days, TinyCommand automatically sends one or more reminder emails encouraging them to schedule.

  8. 08
    The Rep Closes the Loop After the Demo

    Once the demo takes place, the sales representative updates the status in TinyTables (Demo Completed, Won, or Lost) and carries on with their sales process.

  9. 09
    One Table Is the Pipeline

    TinyTables serves as the central sales pipeline: every demo request, booking status, scheduled meeting, and follow-up, tracked from one dashboard.

What you walk away with
FAQ

Questions about Product Demo Booking.

How does it know a prospect actually booked?
TinyCommand watches Calendly. The Booking Listener picks up the invitee-created event, fetches the scheduled meeting, and matches it back to the original request by email, so the pipeline row updates itself.
What happens to prospects who never book?
They get a nudge. After the number of quiet days you set in reminder_days, the Booking Reminder emails leads still marked Requested with the booking link again. That single follow-up is where most recovered demos come from.
What do I need to connect?
Calendly, Gmail and Slack, and all three are required. Calendly detects the booking, Gmail sends the confirmations and reminders, and Slack alerts sales on every new request. Telegram, Discord, Google Chat and Brevo are supported swaps.
Does this use AI credits?
No. There are no AI steps in this recipe, so nothing draws on your workspace credits. It is scheduling, routing and follow-up rather than generation.
Where is the pipeline?
Publishing the Demo Request Form auto-creates the Demo Requests sheet, and that one table is the pipeline: contact details, submission date, status, scheduled meeting time and follow-up history on a single row per lead.
More recipes

Install it, then make it yours.

Everything it creates is an ordinary form, table and workflow in your workspace. Edit any of it after install. Nothing is locked.