Hi @Carl Christensen 

Good question.

Add this JSON to the Body section.

{
  "body": {
    "contentType": "html",
    "content": "Hello World"
  }
}

I added the JSON to the body message, and I got the same error.

Here is the MS Graph Request with the confirmation code that it worked.  I triple checked the URL and the body code.  

What am I missing?

Hi @Carl Christensen! 

I’ve seen cases before where a @ symbol caused a similar invalid URL error when using an API Request (Beta) action.

Can you try swapping out the @ symbol in the URL field for it’s URL encoded equivalent: %40

Keen to ensure you’re all set here so please do keep us in the loop on how that goes! 

I changed the “@” sign to the HTML equivalent %40

Oooh, that is a lot closer.  Now it says “Raw request failed”

Same inputs as above.

Thanks for giving that a try, @Carl Christensen. Let’s see what we can do about this new error! 

Hmm, perhaps you don’t need to reference the body since you’re putting that into the Body field? I’m wondering if having the following code in the Body field would work:

{
	"contentType": "html",
	"content": "Hello World"
}

I’m assuming you’ll still need the { } curly brackets there, I’ve not tested this so can’t confirm for certain whether that’s definitely the case or not.
 
Could you give that a try and let us know if that sorts it?

I tried changing the body field to 

{
	"contentType": "html",
	"content": "Hello World"
}

And

"contentType": "html",
"content": "Hello World"

Same error--”Raw request failed”

@SamB 

There may be a bug with this Zap action behind the scenes with how data is being sent as part of the API request.

Yes, quite possibly @Troy Tessalone! That API Request action is still in beta so it’s expected that there may be a few glitches and bugs that could pop up still.

@Carl Christensen - it may well be worth reaching out to our Support Team to investigate further in case this is indeed a bug. Before doing so I just wanted to double-check that the API Request action is connected to a work, rather than personal, Microsoft account? If it is, I wonder if it might be missing certain permission scopes that are required: 


I know it doesn’t reference the permissions in the error specifically, but thought it best to double-check on that just in case. 

Please do keep us updated on how you get on!

The permissions you reference are the Microsoft Graph permissions to call the MS Teams Reply to message API. Microsoft Graph is working fine.  I am able to reply to messages in the Graph explorer no problem. 

I will reach out to Support.  To be clear, I am trying to reply to a Teams channel message.  MAKE has a prebaked task that can do this.