HTTP request action
Many workflows end outside Lark, in your business system. The HTTP request capability lets the bot call an external API after a message or event, turning a notification into an action.
What it solves
- After confirming in the group, someone still has to update the business system.
- Approvals, ticket creation or status changes cannot be triggered automatically.
- Custom scripts are scattered and lack a unified log.
Core capabilities
Standard HTTP methods
Use common methods and JSON bodies to fit most internal APIs.
Authentication
Configure headers or tokens per endpoint instead of scattering credentials across scripts.
Retries
Retry on downstream failures and keep request results for debugging.
Composable triggers
Trigger from a webhook or group message to complete the automation flow.
How to connect
- Choose webhook or custom-app onboarding for this capability.
- Configure the event source, target group and notification rules.
- Send a test event and confirm the result in the group.
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
- Business system owners
- Teams building internal automation
FAQ
Can it call internal APIs?
With self-hosting, the bot runs inside your network and can call internal APIs according to your network policy.
Are custom headers supported?
Yes. Headers and authentication are configured per endpoint.
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.