Skip to content

feat(notifications): require provider integration id; add trigger attention and language check - #27

Merged
Domantas merged 3 commits into
mainfrom
feat/notifications-alignment
Oct 4, 2026
Merged

Domantas merged 3 commits into
mainfrom
feat/notifications-alignment

Conversation

@Domantas

@Domantas Domantas commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

The gateway now requires the provider integration id on Email, Push and SMS campaign create and on every Email/Push/SMS trigger action, and adds two endpoints (gateway refactoringV2 0fcf8f1d2). This PR adds hub.triggers.get_triggers_needing_attention and hub.account.check_project_languages (sync and async, hand-written — the generator script is not in the repo; marked HAND-WRITTEN), updates docs and examples, refreshes the Hub DTO reference, and adds 21 tests.

Tests: uv run pytest — 827 passed; mypy and ruff clean.

Breaking: the server now requires the provider integration id — pass integrationId (from get_*_integrations) when you create a campaign (SMS: top level; Email/Push: on campaign) or save an Email/Push/SMS trigger action. Released as a minor (major frozen until launch).

🤖 Generated with Claude Code

Domantas and others added 3 commits October 4, 2026 14:21
Taken from Hub /types/python of a local gateway that has the notifications
alignment change (provider integrationId on campaigns and trigger actions,
GetTriggersNeedingAttention, CheckProjectLanguages). Reference only; nothing
imports it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ject_languages

- hub.triggers.get_triggers_needing_attention: GET /{version}/triggers/attention
  (triggerType query value; response items[]). New small module, registered
  on the sync and async hub namespaces.
- hub.account.check_project_languages: POST
  /{version}/account/projects/{projectId}/settings/languages/check
  (defaultLanguage?, languages?; response templates[]), account scope.

Both are hand-written (the generator script is not in the repo) and marked
HAND-WRITTEN so a regeneration keeps them. Sync and async variants, tests
for verb, path, query/body and scope.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… campaigns and triggers

The gateway now requires the provider integrationId when an Email, Push or
SMS campaign is created (Email/Push: campaign.integrationId; SMS: a new
top-level integrationId, distinct from databaseIntegrationId) and on every
trigger action, which also takes the optional language and initiatorId.
The SDK methods pass the request through, so no signature changes; the
README and the SMS / Push pages now show the id, and tests pin that it
reaches the wire for each case.

Breaking: the server now requires the provider integration id. Calls that
create a campaign or save a trigger without integrationId are refused;
pass the id from get_email_integrations / get_push_integrations /
get_sms_integrations.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Domantas
Domantas merged commit 6be72e5 into main Oct 4, 2026
9 checks passed
@Domantas
Domantas deleted the feat/notifications-alignment branch October 4, 2026 11:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant