Contact person: Custom Cal.com Fork Zapier public app build

Phone:Show

Email:Show

Location: Lone tree, United States

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I maintain a fork of the [login to view URL] open-source scheduling platform and now need a public Zapier app that mirrors the behavior of the official [login to view URL] integration (see [login to view URL]). The flow, field mapping, and user experience inside Zapier should feel identical—only the branding and endpoints will point to my fork.

Core scope
The app must expose these triggers:
• New event created
• Event updated
• Event cancelled
• Rescheduled
• Meeting ended
• Out-of-office created

All should return the same payload shape [login to view URL] supplies so existing Zap templates work out of the box.

Technical notes
• You can work in Zapier Platform CLI or the online builder as long as the final package can be submitted as a public Zapier app.
• Authentication stays OAuth2, matching [login to view URL]’s flow, but directed at my fork’s endpoints.
• Please include automated tests, sample Zaps, and brief developer docs so I can maintain future versions myself.

Acceptance criteria
1. Triggers fire reliably from my staging and production instances.
2. Field names, optional/required flags, and help text match [login to view URL]’s listing.
3. App passes Zapier’s public-app review without changes.

If you have shipped Zapier integrations before—especially calendar-related—let’s chat." (client-provided description)