#560 — Define support of webhooks for Partner Portal

Repo: Twill-AI/facade State: open | Status: open Assignee: Unassigned

Created: 2025-09-05 · Updated: 2025-09-15

Description

Caused by necessity to show real-time updates to sales reps and https://github.com/Twill-AI/facade/issues/516.

In order to provide TwillAI Partner Portal users with real-time notifications we need to get relevant events via:

On internal discussion with Sparsh, Martin, Aleksandr (see https://twill-network.slack.com/archives/C078KS0R05B/p1756914148549709) we chosen “Webhook on Facade - via reverse-proxy” approach. It includes:

Confirming list of uses for webhooks with Michael and Nader, decision about persistence requirements.
Facade’s new API-s to listen webhooks from reverse-proxy securely (due to Azure CApps doesn’t allow to listen on different ports from one pod the only solution is to make reverse-proxy call “master credentials” with credentials which it shouldn’t expose).
Reverse-proxy corrections (disable BD and enable Facade) and ticket to restore it.
Facade’s API handler which applies PE webhooks by creating relevant activities. A lot of unit tests here..

Add implementation notes, blockers, and context here

Add wikilinks to related people, meetings, or other tickets