Connecting an Artux digital employee to Feishu or Lark takes five steps: create a custom app in the developer console, grant the required permissions, copy five values into the Artux console, wait for the employee instance to pull the configuration, and add the bot to a group chat. You do not need to host a public callback endpoint or write application code. The variable part is your company’s approval process for app permissions.
What you need before starting
You need administrator access to the Feishu or Lark developer console, access to the Artux workspace that owns the digital employee, and permission to create or approve a custom app. Decide which groups and users the bot should serve before requesting broad permissions.
The app belongs to your company. Its identity and credentials are not shared with another Artux tenant.
Step 1: create a custom app
Open the Feishu/Lark developer console and create an internal custom app. Give it a recognizable name and icon so employees can distinguish it from consumer bots. Enable the bot capability and record the App ID and App Secret.
Do not publish credentials in a document or group chat. Copy them directly into the protected configuration form in Artux.
Step 2: grant the required permissions
The stable integration covers messages, Bitable, documents and knowledge bases, tasks, and calendars. Grant only the scopes needed for the jobs you intend to delegate. A bot that only answers in a group does not need the same scope as one that maintains a Bitable workflow and calendar.
If your organization requires approval, submit the permission request and wait until the app version is approved. “Permission added in the console” and “permission active for the tenant” are separate states.
Step 3: enter the five configuration values
In the Artux console, open the digital employee’s configuration and provide:
- Feishu/Lark App ID.
- App Secret.
- Verification token or the corresponding application verification value.
- Encryption key when your app configuration uses encrypted events.
- Tenant/app region and time-zone configuration required by the workspace.
The console validates format, stores secrets on the control plane, and delivers the effective configuration to the correct employee. The exact labels in Feishu can vary slightly by console version, but they are all found in the app’s credentials and event settings.
Where are secrets stored?
Artux keeps credentials scoped to the tenant and uses the platform’s credential-delivery path. They are not shown again as plain text in the normal interface. Access to configuration changes is restricted and audited.
When troubleshooting, rotate a secret rather than pasting it into logs or support messages. After rotation, update Artux and restart or redeliver configuration so the running employee receives the new value.
Step 4: no public callback URL is required
The stable Feishu/Lark connection uses a long-lived connection initiated by the employee. This avoids exposing a customer-managed public callback endpoint and is especially useful for dedicated instances and privately managed machines.
If the app console asks you to choose an event-delivery method, select the long-connection option supported by the current Feishu/Lark app configuration.
Step 5: add the bot and assign work
Publish the app version, make it available to the intended users, and add the bot to a group. Mention it with a small, verifiable task first—for example, summarize a document into a Bitable record or produce a daily category brief.
Confirm that the result appears in the expected company system and that the employee reports missing authority instead of silently failing.
Four common issues
- The bot does not receive messages: the app version may not be published, the event scope may be missing, or the bot is not in the group.
- It can read but cannot write: the write scope or document-level permission is missing.
- Credentials look correct but authentication fails: a secret may have been rotated without configuration redelivery.
- Times are wrong: set the employee time zone explicitly; do not assume the server region matches the operating team.
How long does setup take?
The technical steps usually take minutes. Internal approval can range from a few minutes to half a day. Once credentials are accepted and the instance is online, configuration delivery should be observable in the console rather than guessed from the bot’s silence.
FAQ
Do we need our own server or public domain?
No. Artux hosts the dedicated employee instance, and the Feishu/Lark integration uses a long-lived outbound connection.
Is this a shared marketplace bot?
No. You create an internal app owned by your organization and control its permissions.
Can we start with one group?
Yes. Starting with one group and one bounded task is the safest way to validate permissions and operating rules.
What if we use DingTalk or WeCom?
Feishu/Lark is the stable integration today. DingTalk, WeCom, and WhatsApp remain roadmap items; check the current capability matrix.