Connect Lark to VNe

1Choose how to connect Lark

The right way depends on which Lark organization you belong to.

1. “Your company uses Lark for its staff” — an admin connects the company's Lark app (sections 2–4). Employees open VNe from Lark in one click, and the bot notifies each person about mail, messages and tasks.
2. “You're in a different Lark organization, or only need it for yourself” — use a personal webhook (section 5). Works with any Lark organization, no admin approval needed.
3. People in another Lark organization still sign in to VNe with Google or an emailed code as usual — only notifications go through the webhook.

If you turn on both, notifications arrive in both places. Pick one to keep it tidy.

2Admins: the company Lark app

Done once, about 10 minutes, with your company's Lark admin account. The app lives inside your company's Lark organization, so only your employees can open it.

1. In VNe, open “Manage” → “Lark” and pick “Lark” or “Feishu” to match your company.
2. Click “Open Lark Developer” → “Create Custom App”, name it “VNe” and create it.
3. Under “Add Features”, add the “Bot” feature.
4. Go to “Permissions & Scopes” → “Batch import/export scopes”, paste the JSON that VNe shows and continue to add the scopes. It includes “Tenant token” scopes (bot sends messages, looks people up by email) and “User token” scopes (read the signed-in person's email).
5. Go to “Security Settings” → “Redirect URLs” and add the “Redirect URL” that VNe shows.
6. Go to “Version Management & Release” → “Create Version”, add a note and submit it for approval. Once a Lark admin approves, the app is ready.
7. Under “Credentials & Basic Info”, copy the “App ID” and “App Secret”, paste them in step 5 on VNe's Lark page and click “Connect Lark”.

The App Secret is write-only — encrypted when saved and never shown again. If VNe says “Lark didn't accept this App ID / App Secret”, check the pair and make sure the app version has been approved.

3Put VNe in your employees' Lark

Once connected, VNe gives you an “Address that opens VNe”. Put it where employees click every day.

1. On VNe's Lark page, copy the “Address that opens VNe”.
2. In Lark Admin, add that address as a link in “Workplace” so employees see VNe right inside Lark.
3. Employees click once: Lark confirms who they are and VNe opens their mailbox directly — no password or Google account needed.

VNe matches people by their Lark email against a mailbox address, or against an email that has been granted a mailbox. Anyone who doesn't match is told VNe couldn't link them and can sign in the usual way.

4Sync Lark people

The bot only knows employees who have signed in from Lark. Sync links the whole company in advance, so employees get notifications without signing in first.

1. Open VNe's Lark page, section “Sync Lark people”.
2. Click “Sync now”. VNe looks up in Lark the emails of every mailbox and of the people granted a mailbox.
3. Read the result: “Looked up … emails · … people matched a mailbox · … Lark people matched none”.

New people? Click again any time (a minute apart). VNe only links people whose email has been granted a mailbox — on purpose, so notifications never reach the wrong person.

5Members: personal webhook

No app, no admin, about 2 minutes. Works in any Lark organization.

1. In Lark, create a new group with only you in it, for example “VNe notifications”.
2. Open the group → “⋯” → “Settings” → “Group bots” → “Add bot” → “Custom bot”. Name the bot and click “Add”.
3. Copy the “Webhook URL” — it looks like https://open.larksuite.com/open-apis/bot/v2/hook/…
4. In VNe: “Settings” → “Notifications” → the “Lark” card → “Connect Lark”, paste the URL and click “Connect and send test card”.
5. A test card arriving in your Lark group means you're done. Choose what to receive: new mail, messages and @mentions, tasks / calendar / other events.

Keep the webhook URL private — anyone with it can post into your group. If the bot has “Custom keywords” or “IP allowlist” on, Lark blocks VNe's cards: turn both off. If the bot has “Signature verification” on, paste the signing key under “Advanced”.

6Something went wrong?

Common errors and how to fix them.

1. “Lark didn't accept this App ID / App Secret” — recheck the pair, and make sure the app version has been approved by a Lark admin.
2. “Lark rejected the signature” — the bot has “Signature verification” on: paste the right signing key under “Advanced”.
3. “The bot has Custom keywords on” — turn off the bot's “Custom keywords” and try again.
4. “The bot has an IP allowlist” — turn off the bot's “IP allowlist” and try again.
5. “Sending to Lark is paused” — Lark rejected the webhook several times in a row, usually because the bot was removed from the group. Click “Reconnect” and paste the new URL.
6. “The app doesn't have Bot enabled” — sign-in still works but notifications don't: add the Bot feature in Lark Developer and publish again.
7. An employee can't get into their mailbox from Lark — their Lark email must match a mailbox address or an email granted a mailbox. Check under “People”, or ask them to sign in the usual way.

7Privacy and security

Notifications pass through Lark's servers, so VNe lets you control what's in the card.

1. Turn off “Show content in the card”: the card shows only a generic title (for example “You were assigned a task”) — no names, mail subjects or content.
2. The App Secret and webhook URL are encrypted when saved and never shown again on screen.
3. The company's Lark app only signs in people from that Lark organization, and only opens mailboxes of the VNe organization it is connected to.
4. Disconnect any time — mailboxes and data are not affected.

A personal webhook can only post into the group you created. VNe cannot read messages in your Lark group.