Skip to main content

Monitor and fix Pro

Webhooks for Slack, Teams and your own tools

Send new-error alerts, fix-task changes, reports, dismissals and settings changes to up to ten endpoints, as signed JSON or formatted for Slack or Teams.

Get Pro from $149/year Start with the free plugin Read the docs

Overview

Webhooks are set up under Accessibility → Settings → Integrations. Add a webhook asks for an Address (https), which must start with https:// and point to a public server, and a Format: JSON (signed, for your own code or Zapier/Make), Slack incoming webhook, or Microsoft Teams (Workflows webhook). Under Send these events you tick the groups this address should receive; all are ticked to start with. You can add up to ten.

There are six groups. Fix tracking covers tasks created, assigned, moved to another status, given a note, verified or reopened by a re-scan, closed by a dismissal, and sent to an issue tracker. Alerts covers new errors on published content and on scheduled page checks. Reports covers client reports created and deleted. License and Settings cover changes to each, and Dismissed and ignored issues covers per-post dismissals and restores and site-wide ignore rules.

A JSON delivery carries the whole event: its name, the time in UTC, the site, who caused it, the object it is about and event-specific data. Its X-Lumtera-Signature header is "sha256=" followed by an HMAC-SHA256 of the raw body, made with the webhook's signing secret, so your receiver can check the request came from your site. Slack gets a short message and Teams an Adaptive Card, each with the same sentence the activity log shows and an Open in Lumtera link.

Why it matters

Accessibility work touches content, development and client teams, each in a different tool. Copying updates between them by hand means someone always hears last.

What you get

  • Up to ten HTTPS endpoints, each subscribed to the event groups it needs.
  • Signed JSON (HMAC-SHA256) for your own tools, or ready-made messages for Slack and Microsoft Teams.
  • Sent in the background, and retried three times when an endpoint is down.
  • Payloads never contain license keys, passwords, secrets or setting values.

How it works

  1. Add an endpoint

    Under Accessibility → Settings → Integrations, paste the URL and choose JSON, Slack or Teams.

  2. Choose events

    Fix tracking, alerts, reports, license, settings, and dismissed or ignored issues.

  3. Verify the signature

    Your receiver checks the X-Lumtera-Signature header against the endpoint's secret.

Who it helps

  • Teams that live in Slack or Teams

    Post new-error alerts and fix assignments to the channel where the team already talks, so nobody has to open WordPress to hear about them.

  • Developers with their own systems

    Verify the signature and feed events into a dashboard, a ticketing system or a reporting database.

  • No-code automation

    The JSON format works with Zapier, Make and similar services that accept a webhook, so a Lumtera event can start another workflow without custom code.

Good to know

How it behaves, what it needs, and where its limits are.

Plans and access
Included in every Pro plan. Setting up webhooks needs an administrator, and nothing is sent without an active license.
Delivery
Deliveries run in the background, so saving a post never waits for them. A network error, a server error or a "too many requests" answer is retried after 1, 5 and 30 minutes. Requests time out after 10 seconds, and redirects are not followed.
Testing and status
Send test sends a webhook.test event straight away and reports the HTTP status. Each webhook shows its last delivery, such as "delivered (HTTP 200)". Turn off Enabled to pause one without losing its settings, or tick Remove on save to delete it.
Secrets and privacy
The signing secret is shown only once, when you save. Regenerate secret makes a new one, and the old one stops working straight away. Payloads never contain license keys, webhook addresses, secrets, tracker tokens or setting values.
Microsoft Teams
Create the address in Teams with the Workflows template "Post to a channel when a webhook request is received", then paste it in. Older Office 365 connector webhooks, which Microsoft is retiring, accept the same card.

Questions

Something else on your mind? Contact support

Is there a Zapier app?

No, but any tool that accepts a webhook can receive Lumtera events.

How is this different from the Slack field under Alerts?

The Alerts screen has one Slack address for new-error alerts. Webhooks can send every group of events, to up to ten addresses, as JSON, Slack or Teams messages.

Can a developer change what is sent?

Yes. In PHP, the lumtera_pro_event action fires for every event, and the lumtera_pro_event_payload filter can change the payload before it is logged and sent.

More in “Monitor and fix”

  • Pro

    Email and Slack alerts

    Hear about it when a publish introduces new errors — never twice for the same one — plus a Monday summary and a score history.

  • Pro

    Fix tracking

    Turn issues into tasks, assign them, and let Lumtera close each task when a re-scan confirms the fix.

  • Pro

    Ignore everywhere

    Ignore a finding across the whole site in one step — such as markup your theme repeats on every page — with a reason, an optional expiry and a log.

Start with the free plugin today

All 64 checks, the editor sidebar, Elementor panel and site report — free, with no account and no page limits.

Download freeSee Pro plans