How to send Wachete alerts to Slack

To send Wachete alerts to Slack, get a Slack webhook URL and add it to the Wachete monitor under Advanced settings → Notification → Webhook. Set the monitor’s notification condition, then save. Wachete documents this as a per-monitor configuration, so add the webhook to each monitor that should send alerts.

What you need

A Wachete account and the monitor you want to configure.
A Slack workspace where you can add the Wachete application and create its webhook.
The change condition that should trigger a message, such as a page change, text appearing or disappearing, or a numeric threshold.

A webhook URL is a secret endpoint for the configured destination. Keep it out of public documents, screenshots, source code repositories, and shared logs. The example below is only a placeholder; use the URL issued for your workspace and channel.

Configure Wachete alerts in Slack

Create the Slack webhook. In Slack, add the Wachete application to your workspace and obtain the webhook URL it provides. Wachete’s example URL has the form https://hooks.slack.com/services/EXAMPLE; do not use that example as a live endpoint.
Open the Wachete monitor. Create a monitor or open the existing one that should send Slack messages. Wachete supports monitoring a full page or part of a page, as well as password-protected pages and media files.
Choose what to monitor. Set the page URL and select the monitoring frequency and notification type appropriate to the page.
Set the Slack destination. Edit the monitor, open Advanced, select the Notification tab, and paste the Slack webhook URL into the Webhook field.
Choose the alert condition. Select the relevant condition: a page change, text appearing or disappearing, or a numeric value reaching a threshold or starting to grow.
Save and verify. Save the monitor. Check the selected Slack channel after the next matching alert, or use a safe test monitor or change if available. Do not assume delivery succeeded until you see the message in the intended channel.

Choose an alert condition that is useful

The destination controls where a notification goes; the monitor condition controls when it is sent. Pick the narrowest condition that captures the change the team needs. A whole-page change can be noisy when unrelated page content changes. If the important signal is a particular text value or number, use Wachete’s text or numeric condition when suitable.

Also choose a monitoring frequency that fits the urgency of the change. The research available for this guide does not establish delivery-time guarantees or a particular frequency for every plan, so check the options shown in your Wachete account.

Per-monitor setup and alternatives

Wachete’s documented Slack instructions put the webhook in an individual monitor’s advanced notification settings. Configure each relevant monitor; do not assume connecting one monitor automatically applies to existing or future monitors.

Wachete also lists Microsoft Teams, Discord, and Telegram as chat destinations. For custom workflows, it documents a REST API and generic webhooks; the API can configure notification endpoints on monitor tasks and requires credentials from the Wachete account profile. Zapier is another route when an alert should trigger a downstream action. For a straightforward Slack channel notification, the direct per-monitor webhook is the documented path with the fewest moving parts.

Security, reliability, and cost considerations

Protect the endpoint. Treat the webhook URL as a credential. If it is exposed, replace or revoke it using the controls available in the relevant service, then update the Wachete monitor.
Verify the full path. A saved monitor configuration does not prove a message reached the channel. Confirm a matching alert arrives in the intended Slack channel.
Reduce noisy alerts. Prefer a targeted text or numeric condition when the whole page changes frequently for irrelevant reasons.
Account for monitoring frequency. Faster checks may be useful for urgent changes, but available frequencies and any plan limits should be confirmed in Wachete.
Check current plan terms. The cited setup guidance does not specify Wachete pricing, webhook delivery guarantees, or rate limits. Consult the account’s current plan and product documentation for those details.

Troubleshooting

Symptom	Likely cause	What to check
No Slack message arrives	The URL is missing, malformed, expired, or belongs to a different destination.	Copy the current webhook URL for the intended workspace and channel, paste it into the monitor’s Webhook field, save, and verify with a matching alert.
Only some monitors post to Slack	The webhook was configured on only some monitors.	Open each monitor that should notify Slack and check its Advanced → Notification settings.
No alert is triggered	The page has not met the configured condition, or the monitor is watching the wrong content.	Review the monitored URL or page part, condition, text or threshold, and monitoring frequency. Use a safe test change if available.
Too many alerts	A broad page-change condition is matching incidental changes.	Use a more specific text or numeric condition if it fits the signal, and review the monitored page area.
Alerts go to the wrong Slack channel	The webhook was created for another channel or workspace.	Use the webhook associated with the intended destination and update the monitor.
A webhook URL was exposed	The endpoint was included in a public or widely shared place.	Rotate or revoke it using the service’s available controls, then replace it in Wachete. Avoid sharing the replacement URL.

Or skip the browser setup

If your goal is to capture a website when an alert fires, ScreenshotNeo is a website screenshot API and MCP server. A single GET request returns a PNG, JPEG, WebP, or PDF. For a Slack workflow, your own automation can call the API after receiving an alert; the Wachete webhook setup above remains the way to deliver Wachete notifications to Slack.

cURL:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python:

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

Node.js:

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer())));

See the ScreenshotNeo API documentation for request options. Cookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots.

FAQ

Can Wachete send website change alerts to a Slack channel?

Yes. Wachete documents Slack as a chat destination and uses a webhook URL configured on the monitor.

Where do I paste the Slack webhook in Wachete?

Open the monitor’s Advanced settings, select Notification, and paste the URL in the Webhook field.

Does one Slack setup cover every Wachete monitor?

The documented workflow configures the webhook on an individual monitor. Set it on each monitor that should send Slack alerts.

Do I need Wachete’s API to send alerts to Slack?

No. The direct webhook field is sufficient for the documented basic setup. The API or Zapier may suit workflows that need custom routing or downstream actions.