Hello, I am integrating a dynatrace workflow to generate incidents in servicenow, my problem is that I generate the basic authentication credentials in servicenow, create the connection in dyntrace. But when calling the connection in the integration block to create incidents it returns an “unauthorized” error, maybe you can help me understand if this error is from dynatrace because the basic authentication credentials in servicenow are created as indicated.
If you want to create an incident in ServiceNow, you will probably want a Problem in Dynatrace. Then the integration is direct. What is the use-case here?
I have already made the use case in the flow that I detail, in summary with the trigger the problem is analyzed and the attention of the case is categorized and prioritized or not, once with this the creation of the tk is raised in servicenow so I am not doing a direct integration.
Regarding the initial query, do you have any information as to why it is not connecting correctly?
may be you need to add the servicenow url under Limit outbound connections if triggering through workflow
Settings >>Preferences>>Limit outbound connections
or it could be with the user permission of the user that is being used for authentication
We are also interested to hear about a solution to this issue as one of our customers is facing the same issue. Currently under investigation.
So is there a solution to this? Is this related to the need for Edge Connect to enable Workflow integration with ServiceNow???
Hey there,
I recently implemented Dynatrace integration with ServiceNow using Workflow and I had to use the EdgeConnect to route the traffic internally. Our serviceNow instance blocks traffic from outside and as integration through workflow doesn’t have a fixed range ips EdgeConnect is the solution for this scenario.
I hope that clarifies your scenario.
Thanks… So EdgeConnect basically uses the same whit3listed IPs for your tenant to send Problem Notification to ServiceNow to work with Workflows - right?
Did you deploy it on docker or on AWS ECS?




