DonationAlerts Settings

Comes with strAImer: this module is installed together with the app, so there is nothing to download. It is listed under Module Catalog → Built-in.

What this page is

Connections → Monetization → DonationAlerts is where the app is given access to your DonationAlerts account. The page does one thing — sign you in through the browser — and reports whether that access is still alive.

How to set it up

1. Open Connections → Monetization and find the DonationAlerts card. Connect DonationAlerts opens this page. On a card that is already connected the same page opens with Configure, and with Reconnect when the card is asking you to sign in again.
2. The page is headed DonationAlerts Settings, with the line "Configure DonationAlerts integration to receive donation notifications." under it. The arrow in the top left, Back, returns to the list.
3. The first row is Connection Status, and beside it a badge with one of six wordings: Connected as {username}, Connecting…, Connected, but no events are arriving, Sign-in required, Connection error or Disconnected. The badge re-reads itself every four seconds while the page is open — there is no need to reopen it to see a change. One of the six needs a word of explanation: Connected, but no events are arriving means donations are reaching the app late instead of live. Why that happens, and what to do about it, is in "Connected, but nothing arrives".
4. The hint under the status says why the sign-in is needed: "Requires authorization to receive real-time donation alerts."
5. Press Authorize via Browser. The app opens the DonationAlerts sign-in page in your ordinary browser — nothing is typed inside the app.
6. Finish the sign-in in that browser window. It shows Finishing sign-in… with "One moment, saving the connection.", then Authorization successful! with "Account {username} has been successfully connected." and "You can close this window. It will close automatically in a few seconds."
7. Come back to the app. The settings page shows DonationAlerts configuration successfully saved! and closes itself a moment later, back to the list of services.
8. Open it again to check the result: Account Name (login) now holds the login of the connected account, and the badge reads Connected as {username}. If the badge says Sign-in required, press Authorize via Browser once more — that is the whole repair.

A refusal is not taken as final at once. If DonationAlerts has accepted this sign-in before, a refusal is answered with a pause and another try: 5 seconds, then 10, 20 and so on, up to five minutes. The badge shows Connection error from the third refusal in a row, and Sign-in required only after refusals have gone on for ten minutes without a single accepted answer (two minutes right after a start or a save). Even then the sign-in is tried again every five minutes, and the badge turns back by itself once DonationAlerts accepts it. A sign-in that DonationAlerts has never accepted asks for a replacement at once.

What it cannot do

• There is no field for a token. Neither an access token nor a refresh token, nor an application Client ID or Client Secret, is asked for anywhere on this page — the button does all of it. Advice that tells you to paste a token does not match this page.
• Nothing here is typed or saved by hand. The page has no save button, and Account Name (login) is display-only — it is filled by the sign-in.
• The badge cannot be dismissed, reset or acknowledged. It reports what the module found, and it changes only when what the module finds changes.
• The connected account cannot be swapped by editing that field. Signing in again is the only way to change it.
• Disconnecting is not on this page: Disconnect and the bin icon, Remove connection, live on the DonationAlerts card under Connections → Monetization.
• No donations, amounts, history or currency are shown here — this page is only about access.