Twill Brain

#371 Facade support Customer notifications from BD

1 min read

#371 — Facade support Customer notifications from BD

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

Created: 2025-06-18 · Updated: 2025-09-15

Description

Request

Caused by https://github.com/Twill-AI/business-data/issues/138 and https://twill-network.slack.com/archives/C07TPN6FCBX/p1750255525815679

In order to show notifications caused by BD background updates like

Customer ‘Fritsch Ortiz and O’Har Card 4’ got linkage updated to token {gid=card_sandbox_0pxn1hbsw8zHzA50YG04M3bK, token_type=card, type=same_phone, fields=[address ‘6755b619-25dc-4482-93f1-75bb792625eb’, payment method ‘1a9df5c2-74f7-423f-8a13-35109192511e’]}

need to support new “customer_updated” notification type. Now it causes errors in logs like:

2025-06-18 13:34:11.175|ERROR|ALKSNDRTST|ws_connection_manager:399|924070bd-9065-40dc-a4f3-45e91b93810b: Unsupported click_dest_type for notification Notification(id=266, user_id=785b418a-77e8-4896-966c-cb6f19a5b49a, integration=None, llmchat_item=None, customer_id=None, severity=info, sent_at=None, created_at=2025-06-18 13:06:18.373345+00:00)

Acceptance criteria

  • Facade supports “customer_updated” notification type and sends it to UI.
  • There is a task in UI to receive these notifications.
  • Logic above is covered with unit tests.

Implementation details

Actually support of “customer_updated” notification types was added month ago in https://github.com/Twill-AI/facade/pull/348. But it looks like due to some issues in https://github.com/Twill-AI/business-data/issues/138 implementation notifications are sent by BD without “customer_id” specified. So issue is on BD side.

Implemented verif

Notes

Add implementation notes, blockers, and context here

Add wikilinks to related people, meetings, or other tickets

Graph View