Jira Spoke, bi-directional integration of on-premise Jira to ServiceNow only working one direction

kfitch
Tera Contributor

8 hours ago

We have a on-prem Jira instance and have connected it to ServiceNow.

We are using IPA Key for Credentials.

Using our Mid Server for connection.

For Connection & Credentials Alias - using Jira Spoke with HTTP connection, Basic Auth with API Key, Connection attribute= server_type and API version.

Webhook, Jira webhook token.

Flow for outbound - working fine.

Inbound SubFlow created.

 

We can create Jira records as needed but can't get it to work the opposite way.

 

This is where it gets confusing. Do I need a second webhook Routing Policy? I've read different things but can't seem to figure out what is needed for the on-premise case.

 

Anyone with the same setup have it working? 

0 Helpfuls
  • 103 Views
1 REPLY 1

pavani_paluri
Tera Guru
Tera Guru

6 hours ago

Hi @kfitch ,

 

Inbound (Jira → ServiceNow):
Jira needs to send updates back into ServiceNow. For that to work, ServiceNow has to be “listening” for Jira’s webhook messages.

You need a webhook routing policy so the MID Server knows how to accept Jira’s inbound messages and pass them into ServiceNow.

1. In ServiceNow, set up a Webhook Listener Routing Policy tied to your MID Server.
2. In Jira, point your webhook URL to that listener.
3. Map the webhook to your inbound subflow in ServiceNow.
4. Now when Jira sends an event (like issue updated), ServiceNow will catch it and run your subflow.

 

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for
Kind Regards,
Pavani P
0 Helpfuls