Skip to content

Guru (Independent Publisher)#4152

Open
aaronmah wants to merge 3 commits intomicrosoft:devfrom
aaronmah:connector/guru
Open

Guru (Independent Publisher)#4152
aaronmah wants to merge 3 commits intomicrosoft:devfrom
aaronmah:connector/guru

Conversation

@aaronmah
Copy link
Copy Markdown

@aaronmah aaronmah commented Mar 10, 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 the swagger file, apiDefinition.swagger.json, has been validated by running paconn validate command.
  • I attest that apiProperties.json has a valid brand color (#da3b01) and I am not submitting a connector icon (independent publisher connector).
  • 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. (This connector uses Basic Auth ΓÇö no OAuth.)

Guru ΓÇö Independent Publisher Connector

Overview

Guru is a knowledge management platform that helps teams capture, organize, and share verified information. This connector enables Power Automate users to search, create, update, and verify knowledge cards, browse collections and folders, and manage tag categories ΓÇö bringing team knowledge into automated workflows.

Publisher

Aaron Mah

Authentication

Basic Auth (email + API token). Users generate an API token from Guru → Manage → Apps & Integrations → API Access. Full setup instructions are in the Readme.

Operations (13 total)

Operation Type Description
Search Cards Action Search for cards using free-text terms and Guru Query Language filters
Get Card Action Retrieve a single card by ID with full content and verification state
Create Card Action Create a new knowledge card in a collection
Update Card Action Update an existing card's title, content, or sharing status
Verify Card Action Mark a card as verified (trusted)
Unverify Card Action Remove verification from a card
Archive Card Action Archive (soft-delete) a card
List Collections Action Get all accessible knowledge collections
Get Collection Action Get details of a specific collection
Get Folder Action Retrieve details of a specific folder
Get Folder Items Action List all cards and subfolders within a folder
List Tag Categories Action Get all tag categories and their tags for the team
List Card Versions Action Get all historical versions of a card

Test Results

  • 12/14 operations tested successfully via direct API (Tier 1)
  • 11/11 operations passed via APIM gateway in PA environment
  • 10/11 operations show green checkmarks in PA test tab (1 red ΓÇö PA platform limitation, see below)
  • 2 operations skipped (folder ops ΓÇö no folders in trial account)
  • 3/3 end-to-end scenario flows validated with real Teams integration
  • Swagger validation passed (0 errors, 0 warnings)

Known Issue: archiveCard ΓÇö PA Test Tab 415

The archiveCard operation shows red in the PA test tab only. This is a PA platform limitation: the test tab sends a Content-Type: application/json header on DELETE requests, and Guru's API rejects this with HTTP 415. The operation works correctly via direct API (204), APIM gateway (204), and in actual flows. This does not affect end users.

Test Tab ΓÇö All Operations

Screenshot: PA custom connector test tab showing 10 green checkmarks across all testable operations

All operations passed ΓÇö 10 green checkmarks in PA test tab

Scenario Flows

Scenario 1: New Card Published → Teams Notification
Trigger → Search Cards → Get Card → Post to Teams. All 4 steps green.

Scenario 1 flow run success ΓÇö all steps green

Scenario 2: Create Card from Knowledge Suggestion
Trigger → List Collections → Create Card → Post to Teams. All 4 steps green.

Scenario 2 flow run success ΓÇö all steps green

Scenario 3: Weekly Verification Digest → Teams
Trigger → Search Unverified Cards → Post to Teams. All 3 steps green.

Scenario 3 flow run success ΓÇö all steps green

aaronmahbuild and others added 3 commits March 8, 2026 04:08
…nsumes

- Move top-level consumes to per-operation (updateCard, createCard, archiveCard)
- Set top-level consumes:[] to prevent PA test tab text/plain rejection
- Add setheader policyTemplate to override Content-Type for archiveCard DELETE
- All 13 operations tested and passing in PA environment
@aaronmah aaronmah marked this pull request as ready for review March 12, 2026 22:37
@aaronmah aaronmah requested a review from a team as a code owner March 12, 2026 22:37
@aaronmah aaronmah mentioned this pull request Mar 12, 2026
10 tasks
@vmanoharas
Copy link
Copy Markdown
Contributor

vmanoharas commented Mar 17, 2026

Hi @aaronmah,

Thank you for submitting the connector. However, our Independent publisher connector certification process has been changed. Please follow the instructions from the below links and submit connector package.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip

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.

3 participants