Back to the changelog

• Feature

  Inbound webhooks

  Every Custom or External event can have one or more webhooks, one per external system: calling the address with the secret triggers the event, which does what it always does (subscribers, starting cases). Calls are signed by default and each receipt stays in the history, without its content. Create them from the event definition, on the Events page: the address and secret are shown only once, with a ready-to-copy example. Admins find them all in Settings → Webhooks, with their latest receipts. The history clears itself after 10 days (the period can be changed per organization) and a burst of calls beyond the limit leaves one row per minute per webhook, not a thousand.

• Feature

  Outbound webhooks

  The opposite of an inbound webhook: when an event happens, FlowSharp notifies the external systems you connected. Webhook and n8n subscribers are now set up with a guided form (address, method, headers) instead of JSON, sign their calls by default and have "Send a test" with the outcome right away. Every delivery stays in the history, and in Settings → Webhooks the "Outbound" tab lists them all. In "Latest events" you see how many deliveries succeeded and which failed.

• Improvement

  Event tasks on Core events flagged

  An Event task that publishes a Core event would fail every time it runs: the designer now flags it on save and publish, and Settings → Diagnostics lists every task to fix. Publishing is not blocked.