Skip to content

Calendly (Independent Publisher)#4135

Open
aaronmahbuild wants to merge 6 commits intomicrosoft:devfrom
aaronmahbuild:connector/calendly
Open

Calendly (Independent Publisher)#4135
aaronmahbuild wants to merge 6 commits intomicrosoft:devfrom
aaronmahbuild:connector/calendly

Conversation

@aaronmahbuild
Copy link
Copy Markdown

@aaronmahbuild aaronmahbuild commented Mar 3, 2026

  • I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
  • I attest that the connector works and I verified by deploying and testing all the operations.
  • I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
  • I attest that I have added response schemas to my actions, unless the response schema is dynamic.
  • I attest that I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
  • If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.
  • I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
  • Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
  • Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
  • If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

Calendly — Independent Publisher Connector

Overview

Calendly is a scheduling automation platform that helps individuals, teams, and organizations schedule meetings without back-and-forth emails. This connector enables Power Automate users to list and manage scheduled events, inspect invitees, check availability, generate single-use booking links, and cancel events — complementing the certified Calendly connector's trigger-focused coverage with comprehensive action-based operations.

This connector provides action operations only. Polling triggers for scheduled events are planned for a future version.

Publisher

Aaron Mah

Operations (11 total — all actions)

Operation Type Description
Get Current User Action Returns the authenticated user's profile including URI, organization, and scheduling URL
List Scheduled Events Action Lists scheduled events with optional filtering by status, date range, and invitee email
Get Scheduled Event Action Returns full details of a specific scheduled event by UUID
List Event Invitees Action Lists all invitees for a specific scheduled event
Get Event Invitee Action Returns full details of a specific invitee for a scheduled event
Cancel Scheduled Event Action Cancels a scheduled event with optional cancellation reason
Create Scheduling Link Action Creates a single-use scheduling link for an event type
List Available Times Action Returns available time slots for a specific event type within a date range
List Event Types Action Lists all event types (meeting templates) for the authenticated user
Get User Busy Times Action Returns time ranges where the user is busy within a specified window
List Availability Schedules Action Returns the user's configured availability schedules including working hours

Authentication

API Key — Calendly Personal Access Token with Bearer prefix, applied via setheader policy template.

Test Results

  • Direct API: 7/7 testable operations passed, 4 skipped (no test data or destructive), 0 known issues
  • Import & Connection: Connector imported and connected successfully in PA environment
  • PA Test Tab: 6/6 APIM-testable operations passed with green checkmarks; 4 skipped (no test data), 1 known issue (listAvailableTimes — account config, not spec bug)
  • End-to-End Scenarios: 3/3 scenario flows passed — all Calendly operations validated through APIM gateway
  • paconn validate: Passed at build time (swagger-cli validation)

Test Tab — All Operations

all-operations-passed

Scenario Flows

Scenario 1: Daily Scheduling Digest
Uses Get Current User + List Scheduled Events to build a daily summary, posted to Microsoft Teams.
scenario-1-run-success

Scenario 2: Booking Link Generator
Uses List Event Types + Create Scheduling Link to generate single-use booking URLs, posted to Teams.
scenario-2-run-success

Scenario 3: Availability Check via Teams
Uses Get Current User + List Event Types + Create Scheduling Link to check availability and share a booking link via Teams.
scenario-3-run-success

Updated API key display name and tooltip for clarity. Added additional operation names to the authorization header template.
Updated the Readme.md to fix formatting issues and remove duplicate content.
@aaronmahbuild aaronmahbuild marked this pull request as ready for review March 6, 2026 09:21
@aaronmahbuild aaronmahbuild requested a review from a team as a code owner March 6, 2026 09:21
@vmanoharas
Copy link
Copy Markdown
Contributor

vmanoharas commented Mar 6, 2026

Hi @aaronmahbuild,

Thank you for your interest in submitting the Calendly connector under the Independent Publisher (IP) program.

After review, we’re unable to proceed with this submission because Calendly already exists as an Verified Publisher connector in the Power Platform connector catalog.

As per the Independent Publisher certification policy, new Independent Publisher connectors cannot be created for services that already have an existing Microsoft or certified connector.
This requirement is documented publicly here: https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip#step-1-verify-connector-isnt-already-built

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants