Log every alert
When SentryKit raises an alert, add a row with its details to Lark.
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
SentryKit Explore SentryKit →
TriggersFires when a monitor or check in SentryKit raises an alert.
Fires when an incident is opened or updated in SentryKit.
Fires when a monitored site, service or alarm in SentryKit changes state.
Opens a new incident or alert in SentryKit.
Acknowledges an open incident in SentryKit.
Resolves an incident in SentryKit.
Lark Explore Lark →
TriggersFires when a new page or doc is created in Lark.
Fires when a new record is added to a database or table in Lark.
Fires when a doc in Lark is published or shared.
Fires when a status field changes on a record in Lark.
Starts a new page in Lark from a saved template.
Creates or updates a record in Lark.
Adds text to the end of an existing doc in Lark.
Moves a page in Lark into a different space.
More SentryKit + Lark workflows
Start a post-incident review
When an incident is resolved in SentryKit, create a review document in Lark.
See details
Track uptime check results
When a monitor changes state in SentryKit, record the change in Lark for monthly reporting.
See details
See all SentryKit + Lark integrations → · Browse the full workflow library →
Common questions
Can Knit build “Log every alert” between SentryKit and Lark?
Yes — describe it in the box above and Knit's Integrations Agent researches SentryKit and Lark's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Why log incidents to a spreadsheet or document?
A running log in Lark makes it easy to review incident counts, durations and causes over time without exporting data from SentryKit.
Can I build a post-incident review automatically?
Yes. When an incident is resolved in SentryKit, create a document or row in Lark with its timeline as the starting point for the review.