Route new Calendly bookings into the right Flodesk nurture and log to Notion

Build me an agent workflow that routes new Calendly bookings into the right Flodesk nurture and logs the meeting in my Notion CRM before the call.

Trigger: a Calendly webhook for the invitee.created event. Whenever someone books a meeting through one of my event types, the workflow should fire immediately.

Step 1. Pull the booking details from Calendly. Use Calendly Get Event Invitee with the invitee URI from the webhook payload and read out the invitee's email, first and last name, event type name, scheduled start time, and any intake question answers they submitted at booking.

Step 2. Decide which Flodesk segment fits. Read the intake answers and pick the best segment for this lead from my Flodesk account, for example Discovery Call, Demo Requested, or Free Consult. If the answers are sparse or ambiguous, default to a general Booked Calls segment so nobody falls through the cracks. Briefly note why you picked that segment so I can review the call later.

Step 3. Get the lead into Flodesk. Call Flodesk Create or Update Subscriber with the invitee's email, first name, and last name so we either create a new subscriber or update the existing one. Then call Flodesk Add Subscriber to Segments with the segment you chose so they are tagged correctly. Then call Flodesk Add Subscriber to Workflow with the matching pre-meeting nurture workflow so they immediately start receiving the right warm-up emails.

Step 4. Log the booking in Notion. Call Notion Create a Page in my CRM database with the invitee's name as the page title and the following details in the page body or properties: meeting time, event type, invitee email, the Flodesk segment you picked, and a one-line summary of why you picked that segment based on their intake answers. I want this record to exist before the meeting starts so I can read it during prep.

Notes for the agent. Match the Flodesk segment by name, not ID, in your reasoning so the choice is human-readable. If a segment or workflow named in my list does not exist in Flodesk, list the closest match using List All Segments or List Workflows and continue with that. Keep the Notion summary to one or two sentences.

Additional information

What does this prompt do?

Catches every new Calendly booking the moment it happens and pulls the invitee's name, email, event type, and intake form answers.
Reads the intake answers and picks the right Flodesk segment for the lead, for example Discovery Call, Demo Requested, or Free Consult.
Adds or updates the subscriber in Flodesk, tags them in the matching segment, and drops them into the right pre-meeting nurture so they get warmed up before the call.
Creates a fresh page in your Notion CRM database with the meeting time, event type, and a one-line summary of why the agent routed them where it did.

What do I need to use this?

A Calendly account with at least one event type that collects intake questions.
A Flodesk account with the segments and pre-meeting workflows you want to route leads into already set up.
A Notion workspace with a CRM database for tracking booked meetings, and your General Input connection shared into that database.

How can I customize it?

Change the list of Flodesk segments and nurture workflows the agent can choose from, and the rules it uses to pick between them.
Adjust which intake questions matter most when deciding the segment, for example weighting team size or use case over budget.
Edit the Notion page template to capture extra fields like deal stage, lead source, or call owner.

Frequently asked questions

Does this work with Flodesk's free trial or do I need a paid plan?

You need a Flodesk plan that supports API access, segments, and workflows. The free trial generally works while it is active, but the long-term plan needs to include subscriber and workflow features.

What if the agent picks the wrong Flodesk segment for a booking?

Open the workflow and tighten the instructions. You can add example intake answers, list the segments more explicitly, or tell the agent to default to a specific segment when it is unsure.

Can I send the lead to more than one Flodesk segment at once?

Yes. The workflow can add a subscriber to multiple segments in one step. Just tell the agent which combinations make sense, for example a general Booked Calls segment plus the specific event segment.

Will it update an existing Flodesk subscriber or create duplicates?

Flodesk matches subscribers by email, so an existing person gets updated in place. The agent uses Create or Update Subscriber, which is safe to run on repeat bookers.

How do I make sure the Notion page lands in the right database?

Share your CRM database with your General Input Notion connection from the database's Connections menu, then point the workflow at that database. Without sharing, Notion will return an empty result and the page will not appear.