Flingoos Connector (Independent Publisher) #4089
Conversation
|
@microsoft-github-policy-service agree company="Diligent4" |
Hybrid connector for accessing procedural knowledge and workflows.
REST API endpoints for Power Automate:
- GET /api/workflows - List workflows
- GET /api/workflows/{id} - Get workflow details
- GET /api/workflows/search - Semantic search
- GET /api/projects - List projects
- GET /api/projects/{id} - Get project details
MCP endpoint for Copilot Studio:
- POST /mcp - Model Context Protocol (Streamable HTTP)
Authentication: Azure AD OAuth (BYOA model - users create their own app registration)
Publisher: Diligent4
Tslilon
force-pushed
the
flingoos-initial-submit
branch
from
f66a75a to
e1d3f91
Compare
|
Hi @Tslilon, Thank you for submitting connector. Our IP connector certification process has been changed. Please refer the below link and upload the connector package. Additionally, we have contacted through email to the id provided in the swagger file for Onevet verification. Please fill the necessary details. |
- Replace separate /api/workflows and /api/projects with unified /api/contexts
- Add new ModifyContext operation (PATCH /api/contexts/{id})
- Update response schemas for context-first design
- Update documentation for new operations
|
Hi @vmanoharas , Thanks a lot! I have located the verification email in my Google Workspace Admin logs, but it was bounced/rejected by the server due to a DMARC authentication failure on your sender's side ([email protected]). The specific error is: "550-5.7.26 Unauthenticated email from microsoft.com is not accepted due to domain's DMARC policy." Because of this error, the email never reached my inbox. Could you please check the sender configuration or resend the verification link from a standard address that passes DMARC checks? Alternatively, I can also receive emails to [email protected] or [email protected] |
2 participants
Hybrid connector for accessing procedural knowledge and workflows.
Publisher: Diligent4
apiDefinition.swagger.json, by runningpaconn validatecommand.Independent Publisher Attestations:
Proof of Functionality
1. Flow with 3 Unique Operations:
2. Successful Flow Run:
3. Test Operation (Custom Connector UI):
