cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Ancy
Kudo Kingpin
Kudo Kingpin

How to call a custom connector from powerapp passing raw body as input

Hello everyone,

I have a postman collection having Body in the form of "raw"

I have created a custom connector with above postman collection. Now I want to call this connector.

How could I pass the raw data to the body parameter of the connector?

Please help.

8 REPLIES 8
v-xida-msft
Community Support
Community Support

Hi @Ancy,

It is not necessary to pass a Raw data  as a Body Parameter value into your custom connector. You could consider edit the Body Parameter part, then edit the parameters that you defined within your API.

Please check and see if the following article would help in your scenario:

https://docs.microsoft.com/en-us/connectors/custom-connectors/define-postman-collection#update-gener...

 

https://docs.microsoft.com/en-us/connectors/custom-connectors/create-postman-collection

 

Best regards,

Kris

Best regards,

Kris

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

@v-xida-msft  Nice non-answer to the question! You've simply not understood what is being asked, and if your solution were useful, @Ancy's  question wouldn't even need to be asked in the first place.

I have the same problem. I have a custom connector that works within itself using the "Test Operation" button, but when I call it from a Power App, the request body is null. Technically the API call should work fine if the body is passed in as "body": {} but Power Apps Monitor shows that it's sending "body": "". To clarify, within the custom connector, if we run the Test with no input to the body, the request body gets passed in as {} and the response is successful. However if we call up this connector from within a Power App, the body is passed in as "" and the response looks like this:

 

 

{
  "duration": 450.39,
  "size": 137,
  "status": 400,
  "headers": {
    "Content-Length": 137,
    "Content-Type": "application/json; charset=utf-8",
    "Date": "Wed, 22 Sep 2021 15:48:09 GMT",
    "x-correlation-id": "...",
    "x-ms-apihub-cached-response": false,
    "x-powered-by": "ARR/3.0,ASP.NET",
    "x-ms-client-request-id": "..."
  },
  "body": [
    {
      "success": false,
      "data": null,
      "statusSet": [
        {
          "code": 6,
          "descriptor": "UnableToParse",
          "message": "The input field is required.",
          "field": ""
        }
      ]
    }
  ]
}

 

 


Based on testing this API in Postman with an empty body, that response means that my request has failed because there has to be a body, even if the body is literally just an empty pair of curly brackets: {}.

Whereas I can get the Power App to suggest the header arguments (assuming I set their visibility to "important" rather than "none") and I am able to pass in the headers just fine, but I am unable to get the body parameters to populate the formula suggestions. I have tried this by using {} for the body field in "Import from Sample" in the custom connector definition, and I have obviously also tried this using an actual sample of the body. Either way, neither the body nor its parameters are suggested as arguments in the Power App function editor.

To simplify the troubleshooting process, I have hard-coded the headers into the custom connector for now and made their visibility "none". This way I should be able to call up the custom connector with no input arguments. This works when I click "Test Operation" within the custom connector. And in fact, since we are getting an API response totally unrelated to a failed authorization, I can tell that my hard-coded headers are working fine when calling the custom connector from Power Apps. The error is 100% related to the missing body. I should be able to pass in the raw body as an argument within Power Apps, or I would think so anyway, but I can't figure out how. Or I should be able to set visibility on body parameters to "Important" and then they should show up as suggested arguments in the function editor. But I am not able to make this work.

It's unclear to me what syntax would be necessary here, or how to get those body parameters to fully populate as suggested arguments in the Power Apps function editor.

Would greatly appreciate if any API wizards have some insight!

Thanks

HEATFreight
Kudo Kingpin
Kudo Kingpin

Here's an example of a valid body:

 

{
  "pagination": {
    "pageNumber": 1,
    "pageSize": 999
  }
}

 


Another valid body example:

 

{}

 


I have the default values for pageNumber and pageSize hardcoded in the custom connector. That works when testing within custom connector itself.

I can remove the hardcoded values entirely, and THAT WORKS! But only when testing within custom connector itself.

I am unable to get any kind of body to be passed in with the API call when I run the custom connector within the Power App. I am removing the data connection for the custom connector from the Power App and then adding it back again every single time I make a change to the custom connector. If I don't do this, it's not clear to me that the changes to the custom connector are recognized in the Power App...

Literally all I need to do is pass in a body —any body at all, I don't care what it is as long as it's not a null string! If I could get it to pass a body to the API call, I could get it to work.

I have implemented a trick to dynamically pass in the Access-Token argument from Power App using a policy in the custom connector to set Authorization header to @headers('Access-Token'). The header "Access-Token" is either hardcoded or set to visibility: "important" and passed in as argument in Power App. Either way works.

This is important because I am unable to use the API Key method of setting up this connector. Well I could, and that would work, but it wouldn't be able to be set dynamically. The Access-Token expires every 20 minutes and I am unable to generate new access tokens using the custom connector because custom connectors do not allow an authorization header like:

 

Authorization Basic <base 64 encoded string>

 


The custom connector will always change the authorization header to:

 

Authorization Bearer <some random string of whose origin I have no idea>

 


Anyway, so that's sort of irrelevant to the null body problem, but it makes me wonder if there's a way to set a policy in the custom connector to specify a proper request body. I think I'll try to use a "Set Property" policy to set the body properties, thus the body should never be null...hopefully.

I had wanted to add a policy to set the body itself, but that does not seem possible. But it is possible set properties of the body. If this policy overrides the null body that Power Apps seems to be sending, then that might be the solution. However, I have other API calls to make which need dynamic body properties. I think I may have to add these as headers, as I did with the Access-Token, such that I can get the Power App function editor to recognize them as proper arguments.

I suppose the fundamental problem here is that Power Apps is not able to recognize the body properties and take them as arguments. Or if it can, it's not clear what I'm missing.

HEATFreight
Kudo Kingpin
Kudo Kingpin

fwiw, I am building custom connectors from scratch because I have had zero success importing from Postman collections (V1, V2, V2.1 all tried with no success). So I have to immediately disregard any suggestions of importing Postman collections as it seems totally broken as far as I can tell. Importing Postman collections does not create a working custom connector in my use case, and I have tried all three Postman versions.

JezLomax
Frequent Visitor

Guys, I managed to fix my issue relating to this subject.

 

Basically, the Postman import didnt work correctly. It was specifying the attribute as a string, when in fact it needed to be an object. I edited this in the swagger editor in the customer connector:

JezLomax_0-1683700948465.png

 

JezLomax_1-1683700984692.png

I then built up the Object thus in my flow and sent it into the custom connector.

JezLomax_3-1683701238103.png

 

 

JezLomax
Frequent Visitor

Oh and one further note, It also got some of the data types wrong on the response as well! I edited these in the swagger editor as well and all was good.

petecarl
Frequent Visitor

I hope this helps anyone trying to do this specifically in PowerApps.

 

1. In the custom connector under the action, set the Body of the request to {} using the "Import from sample" function

 

petecarl_0-1704702383548.png

2. Once added to PA it was expecting an UnTypedObject so when calling the custom connector in PowerApps this is the syntax I used

Set(varBody,ParseJSON("MyJsonString"))

Set(varResponse,CustomConnectorName.Action({body:varBody}));

 

or if you have constructed a record or collection in PowerApps already that you need to convert to an UnTypedObject, Use the JSON() function nested inside the ParseJSON() function, like so:

 

Set(varBody,ParseJSON(JSON(varMyRecordOrCollection)))

Set(varResponse,CustomConnectorName.Action({body:varBody}));

Rookie1
Frequent Visitor

Thank you this worked for me.

Helpful resources

Announcements

Copilot Cookbook Challenge | Week 2 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery: https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the challenge.   Week 1 Results:  Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   Week 2 Results:  Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a

Win free tickets to the Power Platform Conference | Summer of Solutions

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏   Markus Franz | LinkedIn  Power Apps: mmbr1606  

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Reminder: To register for the Community Ambassador Call on June 13th

Calling all Super Users & User Group Leaders     Reminder: To register for the Community Ambassador Call on June 13th—for an exclusive event for User Group Leaders and Super Users! This month is packed with exciting updates and activities within our community.   What's Happening: Community Updates: We'll share the latest developments and what's new in our vibrant community.Special Guest Speaker: Get ready for an insightful talk and live demo of Microsoft Copilot Studio templates by our special guest.Regular Updates: Stay informed with our routine updates for User Groups and Super Users.Community Insights: We'll provide general information about ongoing and upcoming community initiatives. Don't Miss Out: Register Now: Choose the session that fits your schedule best.Check your private messages or Super User Forum for registration links. We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Top Solution Authors
Top Kudoed Authors
Users online (5,180)