Documentation
Slack, Teams & webhooks
Send scheduled Search Console reports and alerts to Slack, Microsoft Teams or any HTTPS endpoint, all managed from one page with a delivery log.
AutoPSEO can carry its numbers out of the app in two ways: scheduled reports with a property's headline Search Console figures, and alerts that fire when a detector sees clicks, CTR, positions, indexing, tracked rankings or audits move. Both go to a channel you add once: a Slack incoming webhook, a Microsoft Teams Workflows URL, or any public HTTPS endpoint that accepts signed JSON. You manage all of it on one page.
Where to find it
Open Slack, Teams & Webhooks in the left sidebar, or go to Account and choose Manage on the Slack, Teams & webhooks card (open it in the app). The page has a section per destination (Slack - Connected workspaces, Microsoft Teams, Outbound webhooks), followed by Scheduled reports, Alerts and Delivery history.
Channels, rules and deliveries
Three things make up the feature.
- Channel: one destination URL, labelled Slack, Microsoft Teams or Webhook. AutoPSEO stores the URL encrypted and afterwards shows only its host and last few characters. An account can hold 25 channels.
- Rule: a scheduled report or an alert, pointed at exactly one channel. A channel can feed any number of rules, up to 50 rules per account. To get the same alert in Slack and in Teams, create two rules.
- Delivery: one attempt to post a message. Delivery history keeps the last 50 attempts across every channel, tests and one-off summaries included, with the status (sent, failed or skipped), the HTTP status, how long the destination took to answer and the reason any failure gave.
Channels and rules belong to your own login. A teammate who wants alerts in their own channel sets up their own.
From zero to the first message
- Connect the Search Console properties you want to report on (Connecting Search Console). The demo property appears in every picker, so you can try a rule before your own data is in.
- Add a channel with Add to Slack, New Teams channel or New webhook: give it a name and paste the URL. Where each URL comes from: Slack, Microsoft Teams, webhooks.
- Click Send test on the channel's row and check that the message arrived.
- Create a rule with New scheduled report or New alert. Both buttons stay greyed out until at least one channel exists.
When messages are sent
A job runs at the start of every hour (UTC) and works out what is due.
| Message | When it goes out |
|---|---|
| Scheduled report | At the hour you choose, daily, weekly or monthly, at most once per period |
| Alert on clicks, CTR, position, lost queries, rank tracking or audits | Checked once a day, in the 06:00 UTC run |
| Alert on index flips | Checked every hour |
| Send test, Send now, Test rule | Immediately |
| Send to Slack from a report page | Immediately (Using AutoPSEO in Slack) |
Report and alert windows end on the day before the run, because Search Console publishes its data with a delay. Every message states the dates it used, so nobody has to guess.
What you need
- An active plan or a running trial. When a trial ends without a plan, scheduled reports and alerts stop, and new channels, rule changes, tests and sends are refused until you pick one (plans and billing).
- A destination you control: permission to create an incoming webhook in Slack, a Workflows webhook in a Teams channel, or an HTTPS endpoint of your own.
Mind who can read the channel
Every message carries search performance data: clicks, impressions, queries and page addresses. Anyone who can read the Slack or Teams channel, or the system behind a webhook, sees it, so post client properties to private channels. The destination URL is a secret too: whoever holds it can post into your channel, as Slack points out for its webhooks. That is why AutoPSEO never displays it again after you save it.
Read next
- Connecting Slack with an incoming webhook: creating the URL in Slack, adding it, and the errors Slack can return.
- Scheduled reports: report types, periods, cadence and the once-per-period rule.
- Alerts: the nine detectors, thresholds, severity and muting.
- Using AutoPSEO in Slack: what a message contains and how Send to Slack works.
- Microsoft Teams: Workflows URLs and Adaptive Cards.
- Outbound webhooks: the JSON body, the event types and the signature check.
Product overviews: AutoPSEO for Slack and AutoPSEO for Microsoft Teams.
In this section
Connecting Slack with an incoming webhook
Create a Slack incoming webhook for a channel, add it to AutoPSEO, send a test message, and fix the errors Slack returns when a post fails.
Scheduled reports in Slack, Teams or a webhook
Post a property's clicks, impressions, CTR and position, with its top queries, pages or ranking movers, to a channel daily, weekly or monthly.
Alerts: detectors, thresholds and severity
Nine detectors watch clicks, CTR, position, lost queries, index flips, rankings and audits, and post to a channel only when a threshold is crossed.
Using AutoPSEO in Slack
What AutoPSEO's Slack messages contain, how Send to Slack posts any report table to a channel, and what you can and cannot do from Slack itself.
Microsoft Teams alerts and reports
Create a Workflows webhook in a Teams channel, add it to AutoPSEO, and receive alerts and scheduled reports as Adaptive Cards coloured by severity.
Outbound webhooks: payload and signature
Receive AutoPSEO alerts and reports as signed JSON at any HTTPS endpoint: the request headers, body fields, event types and how to check the signature.