Feishu Contacts Sync

Problem

Feishu (Lark) DM messages only include the sender's open_id — no name. Group messages include Sender metadata with the name, but DMs don't. Without a lookup table, the agent will either:

• - Assume all DMs are from the person in USER.md (wrong)
• Fail to identify the sender entirely

Solution

Embed the full contacts table directly in USER.md. Since workspace files are injected into the system prompt at gateway startup, the agent can match open_id from inbound metadata against the table — zero tool calls needed.

Important: open_id is per-app

Feishu open_id is scoped to each app. The same person has different open_ids across different Feishu apps. Each OpenClaw instance using a different Feishu app must pull contacts with its own app credentials.

Setup

1. Ensure Feishu app has contacts permission

The app needs contact:user.employee_id:readonly or contact:user.base:readonly scope to list users via the contacts API.

2. Run the sync script

CODEBLOCK0

Example:
CODEBLOCK1

Arguments:

• - openclaw_config_path: Path to your openclaw.json (contains Feishu app credentials)
• INLINECODE7: The account name under channels.feishu.accounts in your config
• INLINECODE9: Path to your USER.md file

3. USER.md format

The script expects USER.md to contain a contacts section with this format:

CODEBLOCK2

On first run, if no contacts section exists, add the section header and description line manually, then run the script to populate the table.

4. Add sender identification to AGENTS.md

Add this to your startup sequence:

CODEBLOCK3

5. Set up periodic sync (optional)

Add a system crontab to keep contacts fresh (e.g., weekly Monday 7am):

CODEBLOCK4

Note: After sync updates USER.md, restart the gateway for changes to take effect (workspace files are cached at gateway startup).

Multi-user principle

USER.md should clearly state:

• - Who the "primary human" (主人) is
• That the agent serves multiple users and must not assume DM sender identity
• A communication preference to address people by their actual name

Privacy

• - The contacts table contains only names and openids (no emails, phone numbers, or other PII)
• openid is an opaque identifier meaningful only within your Feishu app
• The sync script reads app credentials from openclaw.json but never outputs them