Send WeatherX alerts to Discord

This one is a single click. The button in your email sends you to Discord's own screen; you choose the server and the channel; Discord makes a webhook in that channel and hands us its address. We see nothing else about your server.

What you will see on Discord's screen

Discord asks for the server first, then the channel inside it. You need the “Manage Webhooks” right on that server; if you do not have it, Discord will not offer the server in the list, and the person who runs the server has to press the button instead.

The steps

1. Press Connect Discord in the WeatherX email.

2. Sign in if Discord asks.

3. Pick the server, then the channel inside it.

4. Press Authorize.

5. Discord sends you back to a WeatherX page that says the place is connected.

If you closed the window

Nothing was connected, and nothing was spent. The link works once and lasts seven days, so if the connection never finished at Discord's end, press the button in your email again.

If the link is older than seven days, or you already used it, it will say the link is not found. Write to support@weatherx.earth and ask for a new link — we send one in a minute.

What arrives, and when

We look at your place every ten minutes. You get one message when weather is coming or has started, and one when it has passed. A quiet week is a quiet channel — nothing arrives to say that nothing is happening.

The first line is the decision: STOP means it is at the place now or within twenty minutes, PREPARE means it is coming, ALL CLEAR means it has passed.

The last line of every message points back at this page. It is a link to a manual and not a switch: opening it changes nothing, so an alert that is forwarded, quoted or read by a spam filter carries nothing anybody can act on.

What changes on our side

• The place named in your email gets one destination: the Discord channel you picked.
• Alerts for that place go there from the next ten-minute cycle. Nothing else about your account moves.
• Your API key is not touched. It never travels in any of these links.
• You can have more than one destination on a place. Add another and both receive every alert.

How to stop it

Open the channel settings in Discord, find the WeatherX webhook and delete it — that stops the messages at once. Then take the destination off our side too. The Stop link in the next section does that and everything else for the place; to take off only this one and leave the rest running, ask us.

How to stop everything, without asking anybody

Your WeatherX email carries a Stop link at the bottom. Open it, and press the button on the page it shows. It stops every alert for that place and turns off every destination on it, at any hour. It needs no key and no reply.

Write to support@weatherx.earth, and ask us to take one destination off and leave the rest running.

Everything here needs your API key

Send it as an X-API-Key header. It is the key from your welcome message, and it never travels in a connect link — the two are separate on purpose.

Send yourself a real alert, now

You do not have to wait for weather. One call sends a real alert through the real senders:

POST /portal/sites/<place id>/test
X-API-Key: wx_live_…

It arrives as light rain half an hour away, and it says on its face that it is a test — in the first line of the message — so nobody can mistake it for weather. One a minute, twenty a day.

Take one destination off, and leave the rest

The Stop link above turns off everything at once. This takes off one and leaves the place watched. Ask for the list, then delete the one you mean:

GET /portal/sites/<place id>/channels
DELETE /portal/channels/<id>
X-API-Key: wx_live_…

Everything else on that place carries on receiving.

Ask for a fresh connect link

If the Discord link has been used, or is older than seven days, or the message it came in was deleted, mint another:

POST /portal/sites/<place id>/connect/discord
X-API-Key: wx_live_…

{"kind": "discord", "url": "https://…", "expires_at": "…"}

Open the url in a browser and it behaves exactly like the button in your message — the key stays in the header and never travels in the link. Asking again for the same place and the same destination replaces the live link rather than adding a second one, so the newest one you were given is the one that works.

The message as fields, not sentences

This destination receives the alert written out as sentences, because a person reads it. A program usually wants the numbers instead — how far away, which direction, how far ahead the forecast was. That is a second destination kind, and it has its own page: alerts to your own server. A place can carry both at once.