Webhook trigger
The webhook trigger is the inbound side. It gives external systems a dedicated endpoint, receives the event and turns it into a Lark message or the next action according to your configuration.
What it solves
- An external system emits events but has no ready-made Lark connector.
- Event formats vary and need a translation layer.
- Without retries, messages are easy to lose.
Core capabilities
Dedicated webhook URL
Each trigger has its own endpoint for easier source management and debugging.
Signature checks
Verify request signatures and reject forged events.
Event mapping
Map external event fields into Lark messages or HTTP request parameters.
Retries
Retry according to policy when a downstream service is temporarily unavailable, with logs for debugging.
How to connect
- Add the bot to the Lark group and get its webhook URL.
- Configure the event source, target group and notification rules.
- Send a test event and confirm the message and @mention.
This page does not show the internal console. Configuration details and permissions are provided during onboarding, or contact sales to learn more.
Who it is for
- Engineering teams
- Platform engineering
- Teams integrating internal systems
FAQ
How is this different from the message push assistant?
The push assistant focuses on sending messages. The webhook trigger focuses on receiving external events and starting the next step.
Can one trigger serve multiple sources?
Use separate triggers per source so signatures and mappings stay independent.
Related capabilities and solutions
Bring this capability into your Lark groups
Tell us about your team and use case. We will recommend SaaS or self-hosted deployment.