Skip to main content
Solved

Add additional Fact Sheet data to a webhook callback?

  • August 29, 2025
  • 2 replies
  • 132 views

Hello,

I am working to automatically sync LeanIX data over to Jira. Because we are only interested in a small set of data to get sent to Jira, we are looking at using Automations that are watching for certain fields to change (such as Description, Alias, Subscriptions) that would then trigger a webhook.

From what I can tell though, the data that is available to the webhook through the automation trigger is pretty limited (factSheet id, type, and name, automation id and source url, automation tag, userId and workspaceId).

Right now the plan is to use the factSheet id and tag to call graphQL to get the relevant data to update on the Jira side, but it would be simplify things greatly if I could somehow just include the fact sheet field data directly in the webhook data.

Is there a way to include additional fact sheet data in the Callback section of the webhook?

 

(BTW, we did look at using the FACT_SHEET_UPDATE webhook trigger, as that passes a lot more data. But it also triggers a quite a lot and often for data that we don’t need to sync, like completion percentages. It also, as far as I can tell, doesn’t include information on what was changed, so we’d have to compare every time on the Jira side)

 

Best answer by Thomas Schreiner

Hi ​@DavidFoote , did you try looking at the FACT_SHEET_FIELD_UPDATED event payload? If you use this event, you automatically get the relevant values, and you can add a callback filter to only react on changes of those fields that you want to monitor.

2 replies

Thomas Schreiner
Forum|alt.badge.img+3

Hi ​@DavidFoote , did you try looking at the FACT_SHEET_FIELD_UPDATED event payload? If you use this event, you automatically get the relevant values, and you can add a callback filter to only react on changes of those fields that you want to monitor.


  • Author
  • Rookie
  • August 29, 2025

@Thomas Schreiner  I don’t know how I missed the FACT_SHEET_FIELD_UPDATED event type! That does, indeed, have all the data I need.

Thank you!