Answered

Unable to create custom connector from working Postman collection

(0) Share

Report

Posted on by F_Quint

257

I'm trying to create a custom connector to access an API, however I cannot get it to work. I'm using Client credentials as the grant type.

In Postman I'm able to get the access token and make POST calls to this API but this does not work when trying to build the connector.

There's an option to import a Postman collection when creating a custom connector but Power Apps/Automate requires this to be in v1 format, however, that's no longer supported by Postman (available formats are v2 or v2.1)

Any suggestions on how to get this to work?

Categories:

Connector development

I have the same question (0)

All responses (3)

Answers (1)

Sort by

JohnMitchell 6 on at

Like (0)

Report
Copy link

Link copied!

I have exactly the same problem. The ability to import a Postman collection effective no longer exists since you can't export the collection in V1 format in Postman. C'mon Microsoft! Anyone have any ideas?

Was this reply helpful? Yes No
Verified answer

kierian Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!
Workarounds

Option 1: Install an older version of Postman

Uninstall current Postman version (8.0 or higher).

Download and install version 7.0 or lower from here: https://learning.postman.com/docs/administration/upgrading-to-v8/#downloading-postman-v7

Option to export to Collection v1 now exists.

Option 2: Convert from v2 to v1 with the Postman Collection Transformer

If not already installed, install NodeJS (Node.js) or npm (npm | get npm (npmjs.com))

Note: you can check installation by opening Command Prompt as Administrator on your computer and using the commands node -v and npm -v

Open Command Prompt as Administrator on your computer

Run the command to install the transformer: npm install -g postman-collection-transformer

Convert the entire collection with the following command:

postman-collection-transformer convert \

    --input ./v2-collection.json \

    --input-version 2.0.0 \

    --output ./v1-collection.json \

    --output-version 1.0.0 \

    --pretty \

    --overwrite

Note:

“v2-collection.json” is the exported file in v2, replace with the name of your file, and provide the full file path;

“v1-collection.json” is the resulting file after the command, name it as you prefer; it will be created in the current folder you are in within CMD, if you want it in a separate location either navigate to that location or specify the full path;

Resource and further info on the postman collection transformer here: GitHub - postmanlabs/postman-collection-transformer: Perform rapid conversion and validation of JSON structure between Postman Collection Format v1 and v2.

Was this reply helpful? Yes No
joelzehring 208 on at

Like (0)

Report
Copy link

Link copied!
I was able to convert a Postman collection to v1, but after importing the collection to a new custom connector, I'm still running into a similar issue: I'm not able to specify clientCredentials as the value for the securityDefinitions.oauth2_auth.flow. I get an error
Structural error at securityDefinitions.oauth2_auth.flow should be equal to one of the allowed values allowedValues: implicit, password, application, accessCode

Was this reply helpful? Yes No