---
sidebar_position: 8
title: Lark Integration
---

# Lark Integration

Connect a Lark (Feishu) self-built app so your agents can send messages, reply, list chats, and read chat history. Lark uses an **App ID + App Secret**.

## How It Works

You create a self-built app in the Lark Developer Console and paste its App ID and App Secret into Zibby. Optionally add a Verification Token and Encrypt Key if you want inbound Lark events to trigger Zibby agents. The `lark` skill then exposes Lark's API to any node that declares it.

## Connect Lark

1. In the Lark Developer Console, open your self-built app and go to **Credentials & Basic Info**
2. Copy the **App ID** (`cli_...`) and **App Secret**
3. In the Zibby dashboard, go to **Settings → Integrations** and click **Connect Lark**
4. Paste the App ID and App Secret
5. (Optional) Add the **Verification Token** and **Encrypt Key** from **Event Subscriptions** if you want inbound events

| Field | Required | Notes |
|---|---|---|
| App ID | Yes | `cli_...` from Credentials & Basic Info |
| App Secret | Yes | From Credentials & Basic Info |
| Verification Token | No | Required only for inbound events (Event Subscriptions) |
| Encrypt Key | No | Only if Lark-side event encryption is enabled |

## What Agents Can Do

Nodes that attach the [`lark` skill](../skills/lark.md) get `lark_send_message`, `lark_reply`, `lark_list_chats`, and `lark_get_chat_history` — used by routing recipes like [Sentry triage](../recipes/sentry-triage.md) as a Slack alternative.

## Inbound events

Adding the Verification Token (and Encrypt Key, if enabled) lets Lark events fire your Zibby agents. Leave them blank for outbound-only (notifications).

## Troubleshooting

**"Invalid App Secret"** — regenerate the secret in the Developer Console and reconnect.

**Bot can't post to a chat** — the app must be added to the target chat/group and have the messaging permission scopes granted in the console.
