Slack and ClickUp
Your team can get alerts where it already works. Both take a few minutes and no code.
Where to set it up
In your account, open Alerts and find Sent to. Choose Slack, ClickUp or a webhook, paste the address, and save. Every alert of yours is then sent there as well as to the Alerts page. One connection per account.
Use Send a test to check it at once. You can pause or remove the connection on the same page; your alerts stay either way.
Slack
- At api.slack.com/apps, create an app for your workspace.
- Turn on Incoming Webhooks, then choose Add New Webhook to Workspace and pick the channel.
- Copy the address. It starts with
https://hooks.slack.com/. - Paste it under Sent to, save, and send a test.
Each send is a message in that channel: the alert's name, then its changes under a heading for each kind, every product linked to its page at the store with its colour and size, the price before and now, and a View button. Up to 20 changes a message. Names from the stores are escaped, so none can mention or notify your channel.
Treat the address like a password: anyone who has it can post to the channel. Once saved, the site does not show it again.
ClickUp
- In the ClickUp list where the tasks should go, open Automations.
- Choose the trigger When a webhook is received and the action Create a task.
- Set the task's name from
titleand its description fromtext. - Copy the webhook address ClickUp gives, paste it under Sent to, and save.
Each send becomes one task: its name says how many changes it holds, and its description lists them, one per line.
One alert to its own channel
The connection above takes all your alerts. To send one alert to a different Slack channel, give
that alert its own webhook address (a Slack incoming-webhook address works) in its form, or by API
with "channel": "webhook" on POST /api/v1/alerts.
When it stops
If Slack or ClickUp refuses six tries in a row (over about 8.5 hours), the connection is paused and your alerts keep collecting on the Alerts page. Fix the address, then resume it: sending starts again from that moment, and what happened meanwhile stays on the page. See Webhooks for the full retry rules.