Ability to import custom fields (via API, etc.) and use them in event workflow notifications

[barjoy01]

Is your proposal related to a problem?

Yes, lack of options

Provide a clear and concise description of what the problem is.
For example, "I'm always frustrated when..."

There is currently no mechanism to import any information to cal.com from other apps.

Describe the solution you'd like

I’d like to import a field from another app (via Zapier, for example) and include it alongside the meeting details in Cal.com’s event workflow notification—so I can send a single, consolidated email or SMS instead of multiple notifications from separate apps.

Describe alternatives you've considered

Initially, I planned to send a single email from another app while pulling booking data from Cal.com. I invested significant time into implementing this approach, but during testing, I realized there’s no way to disable Cal.com’s own emails—whether they come from a custom workflow or the default notification. As a result, the booker would always receive at least two emails: one from Cal.com and another from the external app.

Additionally, I found that it’s not possible to retrieve Cal.com’s “Add to Calendar” links in other apps in a way that would automatically remove or update the original calendar event if the booking is canceled or rescheduled.

(Write your answer here.)

Additional context

It would be really helpful if we could include additional information from other apps and send just one consolidated email through Cal.com, rather than multiple emails to the booker.
Thanks so much in advance for looking into this.

Requirement/Document

(Share it here.)

---

House rules

• If this issue has a 🚨 needs approval label, don't start coding yet. Wait until a core member approves feature request by removing this label, then you can start coding.
  • For clarity: Non-core member issues automatically get the 🚨 needs approval label.
  • Your feature ideas are invaluable to us! However, they undergo review to ensure alignment with the product's direction.
  • Follow Best Practices lined out in our Contributor Docs

[linear]

CAL-6863