360 Secure SkillHub
360 安全技能中心

Feishu/Lark Setup and Troubleshooting

该 Skill 指导在 Hermes Agent 上配置和排查飞书或 Lark 消息集成：检查环境变量与域名/连接模式，查看网关状态和日志，测试消息投递，处理未回复、未授权用户、错误区域及模型响应失败等常见问题，并提示访问控制与凭据安全事项。

xuxuclassmate
xuxuclassmate
热度 45.77
最近更新 2026-05-11 17:44:10
分类：协作依赖：代码执行 / 第三方 API应用场景：API 集成 / 工作流

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add feishu-setup-troubleshooting
Metadata
name
feishu-setup-troubleshooting
description
Set up and troubleshoot Feishu or Lark messaging integration with Hermes Agent, including connection checks, access control, and common failure modes.
tags
["feishu","lark","messaging","troubleshooting","setup","integration"]
version
1.2.2
primaryEnv
FEISHU_APP_SECRET
requires
{"bins":["hermes"],"env":["FEISHU_APP_ID","FEISHU_APP_SECRET","FEISHU_DOMAIN","FEISHU_CONNECTION_MODE","FEISHU_GROUP_POLICY","FEISHU_ALLOW_ALL_USERS","GATEWAY_ALLOW_ALL_USERS","FEISHU_ALLOWED_USERS","FEISHU_ENCRYPT_KEY","FEISHU_VERIFICATION_TOKEN"]}

Feishu or Lark Setup and Troubleshooting

When to use

  • A user wants to connect Hermes Agent to Feishu or Lark.
  • The bot is online but does not reply to messages.
  • You need to diagnose permissions, gateway state, or connection issues.

Prerequisites

  • Hermes Agent is installed and the hermes CLI is available.
  • A Feishu or Lark app exists with bot capability enabled.
  • The required App ID and App Secret are available.

Access-control reminder

Feishu access has two separate layers:

  • FEISHU_ALLOW_ALL_USERS
  • GATEWAY_ALLOW_ALL_USERS

If the gateway layer is still closed, Feishu users will be rejected even when the Feishu layer looks open.

Setup and troubleshooting flow

  1. Confirm configuration. Check that the required Feishu or Lark variables are present and that the domain and connection mode match the deployment.
  2. Confirm the gateway is running.
hermes gateway status
  1. Review recent logs.
hermes logs 2>&1 | grep -i feishu | tail -20
  1. Test message delivery. Send a direct message and look for an inbound message log followed by a model response.
  2. Restart after config changes.
hermes gateway restart

Common issues

  • Bot does not reply at all: the gateway is not running.
  • Unauthorized user in logs: the gateway-level allow rule is still blocking access.
  • Wrong region or domain: FEISHU_DOMAIN does not match the deployment.
  • Messages arrive but there is no answer: the model provider or API key behind Hermes is failing.

Security notes

  • Prefer an allowlist for production.
  • Never commit App Secret, encrypt keys, or verification tokens.
  • Keep the gateway running under a limited user account.
  • Review logs for sensitive output before sharing them externally.