Integrations:
Alerts, Exports & API
LemReveal fits into your existing workflow. Send registry change alerts to email, Slack, Teams or any webhook endpoint, export records and change history as CSV or Google Sheets, and fetch any mirrored record as JSON.
Available Integrations
Email alerts
The default delivery for registry change monitoring. When a watched company's legal name, status, legal form, registered address or officers change on its official register, you get an email with the before and after values.
Webhooks
Send a structured JSON payload to any endpoint when a watched registry record changes. The payload names the register, the field that changed, the previous value, the new value and the retrieval timestamp.
Setup Guide →
Settings → Webhooks → Add endpoint. Send a test payload before going live; failed deliveries are retried with backoff and logged.
CSV export
Export your delivered records and the full dated change history of every company you watch. Download on demand from any list view.
Google Sheets
Push delivered records and detected registry changes straight into a Google Sheet, so the rest of your team can work from the same list without an account.
Zapier / Make / n8n
Connect registry change events to thousands of apps using the webhook trigger. Route a status change into your CRM, a Slack channel, or a compliance ticket queue.
Setup Guide →
Create a Zap → 'Webhooks by Zapier' → 'Catch Hook' → copy the URL → paste it into your LemReveal webhook endpoint → map the change fields to your destination app.
Slack / Microsoft Teams
Post registry change alerts into a channel using an incoming webhook, so procurement, finance or compliance see a supplier's status change the day it happens.
Setup Guide →
In Slack or Teams: create an incoming webhook for the channel and copy the URL. In LemReveal: add it as a webhook endpoint.
Public JSON lookup
Every mirrored record has a stable JSON representation you can fetch and cite. Public lookups are documented at /openapi.json.
Embeddable search
Drop the company lookup box onto your own site or intranet with a single script tag. Results carry the source register and retrieval date.
What a change event looks like
Every alert is tied to one company on one official register, with the field that changed and the date we retrieved it.
- Legal status changes from active to in liquidation → email and webhook fire the same day we see it
- A director is added or removed on the register → the payload lists both the old and new officer set
- The registered address changes → before and after values, with the source register named
- The legal name or legal form changes → the record and its change history update together
Monitoring is a one-off $19 per company, including 12 months of re-checks. Email alerts, webhooks and exports are included.
Frequently Asked Questions
How do I get notified when a company's registry record changes?
Email is the default. You can also add a webhook endpoint and receive a JSON payload naming the register, the changed field, and the before and after values.
Can I push registry changes into my CRM?
Yes — point a webhook at Zapier, Make or n8n and map the change fields to any destination, or export records and change history as CSV.
Is there an API?
Yes. Public lookups are documented at /openapi.json, and every mirrored record has a stable JSON representation you can fetch and cite.
Can I put company search on my own site?
Yes — the embeddable lookup is a single script tag and cites the source register on every result.
Do webhooks retry on failure?
Yes. Failed deliveries are retried with exponential backoff and logged so you can see what happened.
Put registry changes where your team already works
Watch a company once and every change on its official register lands in your inbox, your channel or your own systems.
Search a company