Hello everyone!
I am working with a client who needs to create a ticket through API call once an identity is created. I’ve been working with workflows but it is not allowed because the api call is only reachable though the tenant.
Our first approach is to open the dinamic IPs but it is not a good practice to use workflows. Can anyone help us just to find the best solution for our client?
Kind regards,
Pablo
Hi @pablonovoa
Can you provide more details, when you mention creating a ticket, do you mean a service now ticket? Workflows do allow creation of service now ticket.
Do you mean your application has explicit API which needs to be called to create a ticket?
Regards,
Uday Kilambi
Hi @uday_kilambiCTS thanks for your response,
When i am talking about creating a ticket is doing an API POST call to a custom url which is only reachable inside the intranet and the API call has a bearer token. It is not a servicenow ticket, it is a generic ticket manager for that client.
Regards,
Pablo
Two ideas for you to think about:
If you are creating an account at birthright, can you put the API POST in an after rule? For example, create the AD account and then use an after create rule to send the ticket?
Treat the ticketing system as a target account. Then you could setup a web services connector that uses the VA to interact with the ticketing system.
Alicia
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.