Skip to main content

I’m working on integrating our app with Calendly and want to enable the “Add Integration” experience like Slack or Zoom.

Our goal:

  1. Users click “Connect” on our app from the Calendly Integrations page.

  2. They are redirected to our OAuth sign-in page.

  3. After successful login, they are redirected back to Calendly to complete the connection.

What we’ve done so far:

  • Created an app in the Calendly Developer Portal (sandbox).

  • Configured Redirect URL / Callback URL.

  • Using Client ID, Client Secret, and Webhook Secret for OAuth and webhook handling.

  • Current flow allows our app to connect to Calendly, and users are redirected to the Calendly dashboard/login page.

Questions:

  1. How should this flow be implemented — on the server side or client side of our app?

  2. Is our current OAuth setup sufficient before submitting to the Partner Marketplace?

  3. Are there any additional technical or validation requirements for Marketplace submission?

I’ve also attached a short video showing our current OAuth flow for reference.

Documentation based : 
Calendly developer account  → Click my apps → Create new app → App name → sandbox → redirec url is calendly callback url will be placed. → Then get the client id , secret id and webhook secret id. configured in the server side. 

When user click the connect there calendly connect api trigger is redirect to the connect calendly displayed → after click connect there will be redirect to the calendly sign in page then after the login there page will be redirect to the dashboard. 

below attached the gif is flow of the current implementation.

but i want the publish my app in to the calendly partner market place . 
user will be integrete my app from the calendly 
flow : calendly → my app sign or oath → calendly dashboard. 

anyone can you please help me to correctly implement on th my app development part and how to publish my app in to the market place.

 

Need Help? Visit 'Get Help. Give Help.'
Terms & ConditionsCookie SettingsAccessibility statement