Calendly + Paminga: Route Follow-ups by Meeting Booked

Paminga's new Calendly integration creates or updates a Contact every time a Calendly event is booked — and lets you fire a different Action Set per Event Type, so the right follow-up runs automatically the moment someone books the meeting.

This is the integration I'm proudest of from this release.

Calendly is where a huge chunk of B2B intent shows up — demos, intro calls, support sessions. Until now, you had to glue that signal into your marketing automation with Zapier or hope your CRM caught it. No more.

What the Integration Does

• Syncs every Calendly Event Type as a Third-Party Form in Paminga
• Creates or updates a Paminga Contact every time someone books (matched on email)
• Fires a per-Event-Type Action Set so your automation reacts to the specific meeting that was booked — not just "a meeting"

That last point is the one that matters. If you've read my post on Action Sets, you already know — pick one Action Set, the entire chain of Actions (with Conditional branching) runs.

Setup, Briefly

1. Have a Calendly admin establish the connection — that lets Paminga sync Event Types for the whole team
2. Open the Integrations page in Paminga and click "Connect Paminga to Calendly"
3. Every Event Type from your Calendly account is discovered and synced as a Third-Party Form

How Fields Map

Calendly sends a single name field by default. Paminga uses First Name and Last Name, so:

• If you've added explicit First Name / Last Name fields to a Calendly Event Type, Paminga maps them directly
• If you've only got name, Paminga splits on the first space — everything before is First Name, everything after is Last Name

Email is mapped automatically. Any additional fields you've added to an Event Type can be mapped however you like — or not at all.

The Action Set Hook

For each Event Type, choose an Action Set to fire when an event is booked.

Concrete playbooks this unlocks:

• "Book a demo" → enroll the contact in a pre-demo nurture, alert the AE, sync to CRM with Demo Booked status
• "Support call" → tag the contact, route the AE notification differently, skip the pre-demo nurture
• "Customer check-in" → CSM-side notification only, no marketing follow-up

Same integration. Different Event Type. Different Action Set. Zero glue code.

What Contact Resolution Looks Like

When an event is booked, Paminga looks up the Contact by email:

• Match found — mapped fields are updated to the values Calendly passed
• No match — a new Contact is created

You don't have to think about it. The Action Set runs either way.

Recent Enhancement

We followed the original integration with a small but mighty add: Calendly event names can now be mapped as a field on Third-Party Forms — so you can branch follow-up logic by which specific Event was booked, even inside a single Action Set.

Get Started

1. Make sure a Calendly admin is the one connecting — otherwise Paminga can't see team-wide Event Types
2. Connect on the Integrations page
3. For each Event Type that matters, pick the Action Set you want fired

Read the Calendly integration docs for the full walkthrough.