Integrations

Users may notice that after a schema update or data model change, outbound integrations such as Webhooks or Integration Hub event flows stop delivering updates or begin omitting certain fields. This typically happens because outbound events depend on predefined schema definitions that do not automatically refresh when the underlying entity model is updated. As a result, once the schema changes, the configured webhook or integration may reference outdated field mappings or drop unmapped attributes until the schema is manually refreshed and re-published.

Users often expect that once an external system sends updated entity data to Fenergo, those changes should appear instantly in the UI or Journey context. However, Event Ingress and other integration workflows in Fenergo are asynchronous by design. When an event is received, the API returns a 202 Accepted response to confirm successful receipt — but the actual update occurs later, after the event has completed internal processing and passed validation. As a result, updates only become visible once the workflow finishes and a success notification is generated.