Power Automate Custom Connector not displaying nested array properties

Hi everyone,

I’m building a custom connector in Power Automate and encountering an issue where a property from my Swagger/OpenAPI definition isn’t showing up when I test the connector. Specifically, I’m trying to send an array of objects as part of the request body, but the property (products) doesn’t appear in the UI.

Here’s the relevant part of my Swagger definition:

parameters:
  - name: promotionId
    in: path
    required: true
    type: string
    description: Identifiant unique promotion
  - name: body
    in: body
    required: false
    schema:
      type: object
      properties:
        triggers:
          type: array
          items:
            type: object
            properties:
              shop:
                type: object
                properties:
                  id:
                    type: string
              products:
                type: array
                items:
                  type: object
                  properties:
                    ean:
                      type: string
                    quantity:
                      type: integer
              logical_operator:
                type: object
                properties:
                  value:
                    type: string
              trigger_type:
                type: object
                properties:
                  value:
                    type: string

The Problem:

When I test the connector in Power Automate, I can see fields like shop.id, logical_operator.value, and trigger_type.value, but the products property doesn’t show up at all.

What I’ve Tried:

Using Example Payloads: I added examples to my Swagger file to make the structure explicit.
Raw Body Input: I toggled the raw body mode in Power Automate, which works, but it’s not ideal since I need the fields to appear in the UI.

Questions:

Has anyone successfully used arrays of objects in Power Automate custom connectors?
Is there a workaround to make the products property appear in the UI while keeping it as an array?
Do I need to restructure the schema, or is this a known Power Automate limitation?

Any help or insights would be greatly appreciated!

Thanks in advance!

Categories:

Licensing

Quick Links