Overflow Tap 1.0.0: switch Overflow Tap destinations from keywords in ProPresenter slide notes

Conversation 0 Commits 2 Files Changed 10

+1808 -2

2 Commits

Author	SHA1	Message	Date
Waters ChurchandClaude Fable 5.1	459d8b9c38	Overflow Tap: speak Overflow's Dashboard API, as its own helper app does The first cut guessed a write route on Overflow's public API, which documents only reads for Tap. With the helper app's bundle in hand (Overflow ProPresenter Integration 1.2.3, read 2026-10-11) the module now makes exactly the calls the helper makes, against the Dashboard's own backend: POST /nonprofit-dashboard/authentication/login/jwt a Dashboard sign-in → JWT GET /nonprofit-dashboard/propresenter/nonprofits/{id}/keywords the Keyword Mappings POST …/nonprofits/{id}/keywords?syncNonprofit=true { keywords } = the switch So the keyword → destination → Tap groups mapping stays where Overflow keeps it (Dashboard › Integrations › ProPresenter › Keyword Mappings) and is read from there: on start, every five minutes, on the tile's refresh button, and from every trigger's answer. Admin config shrinks to the ProPresenter endpoint, the Overflow Dashboard login (plus a Nonprofit ID only for an @overflow.co staff login) and the alert switch; the API-key, Tap-groups, keyword-text and match-mode fields are gone. Behaviour follows the helper: both the presentation layer (/v1/status/slide) and the announcement layer (/v1/announcement/slide_index + /active) are watched; when a layer's set of matched keywords changes to a non-empty set it is sent; matching is per word, case-insensitive, punctuation around the word ignored. The session token is cached across re-inits for the same login so an admin saving config repeatedly cannot trip Overflow's "too many attempts"; a 401 signs in again once; a refused sign-in is not retried within 20 s. tools/overflow-tap-mock.js now plays the Dashboard API (any email/password signs in; --fail-switch, --expire=<s>, --login=<email>:<password>) and gives the mock ProPresenter an announcement layer (--no-announcements for an older one). Verified against it: sign-in, keyword load, triggers on both layers, token expiry → re-login, 500 → NOT SWITCHED + alert + retries, wrong login → the reason on the tile and in the health line, and recovery. keywords.selftest.js pins the matching rule (8 cases). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-11 10:25:02 -04:00
Waters ChurchandClaude Fable 5.1	6b51044be6	Overflow Tap 1.0.0: switch Overflow Tap destinations from keywords in ProPresenter slide notes A new module that does what Overflow's "ProPresenter Integration" helper app does, inside ProdDash: the live slide's notes are read from ProPresenter (GET /v1/status/slide, twice a second) and when they carry one of the admin page's keywords, the chosen Overflow Tap groups are pointed at that keyword's destination. One tile: the keyword Tap is on (and since when), its destination and the groups moved, a chip saying whether the slide on screen carries a keyword, and the last four switches. A failed switch turns the tile red with the reason, retries three times, and can flash an alert channel. Admin config: ProPresenter endpoint + password; Overflow client ID + API key (x-client-id / x-api-key, the public API's two headers); Tap groups to switch (multiselect read from the account over /groups); keywords as text, one per line (`give = Give Online`, optionally `@ Lobby, Kids Wing`); match mode (whole word / anywhere / own line); alerts switch + channel. The one unverified piece: Overflow's public API documents only reads for Tap (OpenAPI checked 2026-10-07), while Overflow's helper uses the Dashboard's private API. The switch is sent as PATCH /api/v3/tap/groups/{id} with the new destinationId — the natural shape for this API — and every switch is confirmed by reading the group back, so a refusal shows on the tile instead of passing silently. overflow.js is the one place to change if Overflow names a different route. Also: tools/overflow-tap-mock.js (a ProPresenter whose slide notes carry keywords on :1602 plus the Overflow Tap API on :24720, --read-only to fail every switch), keywords.selftest.js (14 cases), README + CLAUDE.md entries. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-10-07 14:00:37 -04:00

Author

SHA1

Message

Date

Waters ChurchandClaude Fable 5.1

459d8b9c38

Overflow Tap: speak Overflow's Dashboard API, as its own helper app does

The first cut guessed a write route on Overflow's public API, which documents
only reads for Tap. With the helper app's bundle in hand (Overflow ProPresenter
Integration 1.2.3, read 2026-10-11) the module now makes exactly the calls the
helper makes, against the Dashboard's own backend:

  POST /nonprofit-dashboard/authentication/login/jwt      a Dashboard sign-in → JWT
  GET  /nonprofit-dashboard/propresenter/nonprofits/{id}/keywords
                                                          the Keyword Mappings
  POST …/nonprofits/{id}/keywords?syncNonprofit=true      { keywords } = the switch

So the keyword → destination → Tap groups mapping stays where Overflow keeps
it (Dashboard › Integrations › ProPresenter › Keyword Mappings) and is read
from there: on start, every five minutes, on the tile's refresh button, and
from every trigger's answer. Admin config shrinks to the ProPresenter endpoint,
the Overflow Dashboard login (plus a Nonprofit ID only for an @overflow.co
staff login) and the alert switch; the API-key, Tap-groups, keyword-text and
match-mode fields are gone.

Behaviour follows the helper: both the presentation layer (/v1/status/slide)
and the announcement layer (/v1/announcement/slide_index + /active) are
watched; when a layer's set of matched keywords changes to a non-empty set it
is sent; matching is per word, case-insensitive, punctuation around the word
ignored. The session token is cached across re-inits for the same login so an
admin saving config repeatedly cannot trip Overflow's "too many attempts";
a 401 signs in again once; a refused sign-in is not retried within 20 s.

tools/overflow-tap-mock.js now plays the Dashboard API (any email/password
signs in; --fail-switch, --expire=<s>, --login=<email>:<password>) and gives
the mock ProPresenter an announcement layer (--no-announcements for an older
one). Verified against it: sign-in, keyword load, triggers on both layers,
token expiry → re-login, 500 → NOT SWITCHED + alert + retries, wrong login →
the reason on the tile and in the health line, and recovery. keywords.selftest.js
pins the matching rule (8 cases).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

2026-10-11 10:25:02 -04:00

Waters ChurchandClaude Fable 5.1

6b51044be6

Overflow Tap 1.0.0: switch Overflow Tap destinations from keywords in ProPresenter slide notes

A new module that does what Overflow's "ProPresenter Integration" helper app
does, inside ProdDash: the live slide's notes are read from ProPresenter
(GET /v1/status/slide, twice a second) and when they carry one of the admin
page's keywords, the chosen Overflow Tap groups are pointed at that keyword's
destination. One tile: the keyword Tap is on (and since when), its
destination and the groups moved, a chip saying whether the slide on screen
carries a keyword, and the last four switches. A failed switch turns the tile
red with the reason, retries three times, and can flash an alert channel.

Admin config: ProPresenter endpoint + password; Overflow client ID + API key
(x-client-id / x-api-key, the public API's two headers); Tap groups to switch
(multiselect read from the account over /groups); keywords as text, one per
line (`give = Give Online`, optionally `@ Lobby, Kids Wing`); match mode
(whole word / anywhere / own line); alerts switch + channel.

The one unverified piece: Overflow's public API documents only reads for Tap
(OpenAPI checked 2026-10-07), while Overflow's helper uses the Dashboard's
private API. The switch is sent as PATCH /api/v3/tap/groups/{id} with the new
destinationId — the natural shape for this API — and every switch is confirmed
by reading the group back, so a refusal shows on the tile instead of passing
silently. overflow.js is the one place to change if Overflow names a
different route.

Also: tools/overflow-tap-mock.js (a ProPresenter whose slide notes carry
keywords on :1602 plus the Overflow Tap API on :24720, --read-only to fail
every switch), keywords.selftest.js (14 cases), README + CLAUDE.md entries.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

2026-10-07 14:00:37 -04:00

Overflow Tap 1.0.0: switch Overflow Tap destinations from keywords in ProPresenter slide notes #47