Can I create multiple Jira Webhook routing policy and registry

[Rachael12]

I have created 4 different Jira webhooks on four different tables, should I create 4 different policies and registries or can it be handled within a single registry and policy.

Also, the webhooks are similar just create on four different tables, can it be done in single flow.

[Abbas_5]

Hello @Rachael12,

Yes, it's possible to manage multiple similar webhooks for different tables within a single ServiceNow flow. While you can't directly trigger a flow on multiple tables simultaneously with a single webhook, you can achieve the same functionality using a combination of flows and subflows, or by using a scriptable flow to handle the logic.

Here's how you can approach this:

1. Centralized Flow with Subflows or Scriptable Flow:

• Central Flow:

  Create a main flow that receives the webhook event. 
• Table Identification:

  Use the table_name or other fields in the webhook data to determine which table the event relates to. 
• Conditional Logic:

  Use conditional statements (e.g., if, switch) to determine which subflow or scriptable flow to execute based on the table. 
• Subflows or Scriptable Flow:

  For each table, create either a separate subflow or a scriptable flow that performs the specific actions required for that table. 
• Pass Data:

  Pass the webhook data and relevant table information to the chosen subflow or scriptable flow. 

2. Using the "Look Up Record" Action:

• Multiple Lookups:

  Within your main flow, use the "Look Up Record" action to search for the record in each of the relevant tables.
• Conditional Logic:

  Use conditional statements to check the results of each lookup and perform actions based on whether records were found.
• Data Processing:

  If records are found, you can further process the data and trigger additional actions within the flow. 

3. Example Scenario:

Imagine you have four webhooks related to different Jira issues, and you want to update related ServiceNow records based on the Jira event. 

• Main Flow:

  Receives the webhook data from Jira.
• Table Identification:

  Uses the table_name field in the webhook data to determine the relevant ServiceNow table.
• Conditional Logic:

  • If the table_name is "Incident," execute a subflow to update the related Incident record.
  • If the table_name is "Problem," execute a subflow to update the related Problem record.
  • And so on for the other tables.
• Subflows:

  Each subflow would contain the specific actions needed to update the corresponding ServiceNow record based on the Jira event.

Benefits of this approach:

• Centralized Management:

  You only need to manage one main flow, making it easier to maintain and update.
• Reusable Logic:

  Subflows or scriptable flows can be reused for similar webhook processing tasks across different tables.
• Scalability:

  Adding new tables and webhooks becomes easier as you can simply add new conditional branches and subflows. 

By using these techniques, you can efficiently manage multiple webhooks for different tables within a single ServiceNow flow, simplifying your workflow and making it easier to manage and maintain. 

OR please refer to the link below:
https://www.servicenow.com/docs/bundle/yokohama-environmental-social-governance/page/product/esg-man...

If it is helpful, please hit the thumbs up icon and accept the correct solution by referring to this solution in future it will be helpful to them.

Thanks & Regards,

Abbas Shaik