Catch regressions and fix at scale Pro
Webhooks for Slack, Teams and your own tools
Send alerts, fix tasks, reports, feedback, scans, manual tests and other evidence events to up to ten endpoints, as signed JSON or for Slack or Teams.
Updated for Lumtera 1.2.2 and Lumtera Pro 1.1.1.
Overview
Webhooks are set up under Lumtera → 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 14 groups: Fix tracking, Alerts, Reports (created, deleted, and share-link views), License, Settings, Dismissed and ignored issues, Accessibility feedback, and the evidence groups Scans, Manual tests, Accessibility statement, Applied fixes, Disproportionate burden, Exception tags and Evidence ledger. Feedback and evidence events never carry a visitor's name, email or message, notes or screenshots.
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 a link back to WordPress.
Why does it matter?
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 do 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 does it work?
-
Add an endpoint
Under Lumtera → Settings → Integrations, paste the URL and choose JSON, Slack or Teams.
-
Choose events
Pick from 14 groups, from fix tracking and alerts to scans, manual tests and the evidence ledger.
-
Verify the signature
Your receiver checks the X-Lumtera-Signature header against the endpoint's secret.
Who is it for?
-
Teams that live in Slack or Teams
Post new-error alerts, overdue feedback and fix assignments to the channel where the team already talks.
-
Developers with their own systems
Verify the signature and feed scans, fixes and manual test results into a dashboard 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 asks you to confirm, then makes a new one, and the old one stops working straight away. Only JSON webhooks are signed, so Slack and Teams webhooks have no secret to regenerate. 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 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 “Catch regressions and fix at scale”
-
Pro
Email and Slack alerts
Hear about it when a publish adds new errors or feedback goes past its target, never twice for the same one, plus a Monday summary and a score history.
-
Pro
Compare scans
See what is new, what was fixed and what is still there between two scans, by check and by site part, with the likely cause marked.
-
Pro
Fixes queue: bulk fixes you review and approve
Propose the same fix on many pages at once — built-in fixes or text you write (and AI drafts, only if you connect an AI provider) — review every change, then apply and undo them in the background.
Webhooks for Slack, Teams and your own tools
Get it with Lumtera Pro
In every Pro plan. Personal is $75 a year. Pro installs alongside the free plugin, and your settings and results stay.
14-day refund (opens in a new tab)Keeps working if you don't renew