Microsoft Power Automate

Microsoft, Athennian, and many others are largely leading our industry in scaling up integration automation capabilities. For example, Athennian currently does not directly or officially offer any Power Platform (PP) or Power Automate (PA) products or services, however, we are starting to build and test them. And in the meantime, our API is compatible with these technologies and most Athennian functionality. And to help streamline most custom client integration projects, we're building complementary POCs, demos, documentation, and more here. This documentation is important to help align all of our past, present, and future efforts in quickly creating ever improving customer solutions.

Additional demos can be found here.

Prefer learning more with your Microsoft Copilot or other AI assistant? No problem! ▶️ Here you'll find a quick video demo with examples of how this can be done for most of our automation solutions, and more here. 

Embed

Forms

File Upload

If the option is greyed out, it's likely because you've made the form fully public which is not currently supported. Please adjust and specify access to resolve.

Flows

Copilot Configuration

Copilot can be wrong. Please verify all AI-powered support. For example, if it says that a connector does or does not exit, or functions in a certain way, please consider quickly searching for and through the connector trigger or action list directly to confirm.

In getting Copilot troubleshooting support, you may find it helpful to provide the chat session ID.

prompt:
/debug conversationID

response:
chatSessionId: c145b615-8e3b...

Connectors

Connectors are Microsofts internal pre-configurations of external APIs and more.

Connector Support

Athennian currently does not officially offer any Connector products or services outside of what has already been mentioned in the first paragraph of this page. Below is a list of Athennian API supported functionalities which may and may not be included in the first version of our POC or Beta Connector we are building now.

Support Introduction

1. Athennian can provided limited support (2504210050001878).
2. PP primary only provides support via (1) documentation, and (2) bug investigations.
   1. However in some cases they may choose to provide additional guidance for how to use the tool generally.
3.  Otherwise, partners will need to be considered (example).

Swagger Editor

Once you edit the swagger page manually, you might have to always manually update the version for all connector changes (even via GUI) to keep taking effect

Output Variables

In order to configure additional things like (more) Athennian variables, additional changes may need to be made to the Swagger Editor directly. Otherwise, you may see an empty or insufficient action object when you go to Insert Dynamic Content / variable (2504210040012542).

1. Below is an example of what can be added to the Connector's Swagger and how it's parsed and saved.
   1. Manually changing the version number will likely be required to see any changes in Flows.

Postman Output: 1

{
"data": {
"createEntity": {
{
"id": "665a0f...redacted"
...

Swagger Input: 1

responses: {
"200": {
"description": "Successful response",
"schema": {
"type": "object",
"properties": {
"data": {
"type": "object",
"properties": {
"createEntity": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": { "type": "string" }
}
}
}
}
}
}
}
}
}

Swagger Outputs: 2

...1) Action / Path:
responses:
default:
description: default
schema:
type: object
properties:
data:
type: object
properties:
createEntity:
type: object
properties:
id:
type: string
description: id
description: createEntity
description: data

...2) Global:
responses:
'200':
description: Successful response
schema:
type: object
properties:
data:
type: object
properties:
createEntity:
type: array
items:
type: object
properties:
id:
type: string

Response Type

Replace type Object w/ Array + Items for relevant Path action response in Swagger Editor.

Error:

ResponseSwaggerSchemaValidationFailure
The API 'athennian-203-5f...redacted...' returned an invalid response for workflow operation 'accessGroups' of type 'OpenApiConnection'. Error details: 'The API operation 'accessGroups' requires the property 'body/data/accessGroups' to be of type 'Object' but is of type 'Array'.'

Fix:

...
properties:
accessGroups:
type: array
description: accessGroups
items:
type: object
properties:
id:
type: string
...

Default Values

Related to the below, likely only used if internal (and required).

Empty Query

Resolved by making the connection action Query property invisible (and required).

"status": "CLIENT_ERROR",
"message": "GraphQL operations must contain a non-empty `query` or a `persistedQuery` extension."

Save Fail

If your connector fails to save, try again and it might succeed the second time.