Skip to main content
Question

Using Send Email action - {"code":"access.is.denied","details":null,"message":"Access is denied"}

  • February 24, 2025
  • 4 replies
  • 123 views
M
Forum|alt.badge.img+1

Hello, i have a task where i need to send an email with processed data, but when i use a “send email” action i get the following error message:

 

{"code":"access.is.denied","details":null,"message":"Access is denied"}

 

For context i am using EWS Server, Exchange Server 2010,  OAuth2 - ROPC.

 

What could be the problem for me getting an access denied?

Marc Mueller
Dineshkumar Muthu

4 replies

Dineshkumar Muthu
Flight Specialist | Tier 4
Forum|alt.badge.img+9
  • Dineshkumar Muthu
  • Flight Specialist | Tier 4
  • February 25, 2025

Hi ​@mti.molina , check these two.

  • Check Username and password are valid.
  • Check email EWS host URL is accessible in the bot running device.

check this too 

 

"Everything fails all the time, so plan for failure and nothing fails" - Werner Vogels ========== Linkedin Profile : https://www.linkedin.com/in/dineshkumar-muthu/
M
M
Forum|alt.badge.img+1
  • mti.molina
  • Author
  • Cadet | Tier 2
  • February 25, 2025

I’ve checked both options and they weren’t the mistake.

 

I have other bots working on the same virtual machine, and they don’t have any issues with the send email action. I am using the same locker with the same credential and configuration for the action.

 

How can i check a deeper configuration or message?

Dineshkumar Muthu
Dineshkumar Muthu
Flight Specialist | Tier 4
Forum|alt.badge.img+9
  • Dineshkumar Muthu
  • Flight Specialist | Tier 4
  • February 25, 2025

​@mti.molina,  have you checked the bot runner user have access to the credentials.

"Everything fails all the time, so plan for failure and nothing fails" - Werner Vogels ========== Linkedin Profile : https://www.linkedin.com/in/dineshkumar-muthu/
M
Forum|alt.badge.img+1
  • mti.molina
  • Author
  • Cadet | Tier 2
  • February 26, 2025

It has consumer permissions for the credentials.

Terms & ConditionsCookie settingsAccessibility statement