agency-feishu-integration-developer

Implement Feishu integrations for bots, approvals, Bitable, SSO, and event-driven automation.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/omeraltn/ice_cream_website_testing --skill agency-feishu-integration-developer-omeraltn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-feishu-integration-developer
Source: https://github.com/omeraltn/ice_cream_website_testing/tree/main/.antigravity/agency-feishu-integration-developer
Command: npx skills add https://github.com/omeraltn/ice_cream_website_testing --skill agency-feishu-integration-developer-omeraltn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the complexity of building and operating production-grade integrations on the Feishu (Lark) Open Platform by providing best practices, architectural patterns, and concrete implementation guidance for bots, approvals, Bitable synchronization, SSO, and event-driven automation.

Core Features & Use Cases

  • Bot & Messaging: Build webhook and app bots that send interactive message cards, handle callbacks, and gracefully handle API failures.
  • Approval Workflows & Automation: Define, submit, and react to approval instances programmatically and trigger downstream business logic on approval events.
  • Bitable & Data Sync: Perform batched table operations and bidirectional synchronization between Feishu Bitable and external systems with rate-limit-aware batching.
  • SSO & Event Reliability: Implement OAuth/OIDC flows, QR code login, tenant vs user token handling, event subscription verification/decryption, idempotent handlers, and retry strategies.
  • Use Case: Automatically notify approvers with a validated interactive card, process their card actions via a verified webhook, and persist outcomes into a Bitable table while respecting token caching and rate limits.

Quick Start

Create a Feishu bot that sends an interactive approval card, verifies incoming events, caches tenant_access_token, and updates a Bitable record when an approval is granted.

Frequently Asked Questions about agency-feishu-integration-developer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a Feishu bot that sends interactive message cards and handles callbacks?

To build a Feishu bot for interactive message cards, implement webhook or app bots that send cards and process card action callbacks via verified webhooks, while gracefully handling potential API failures.

What is the correct way to handle Feishu event subscription verification and decryption?

Feishu event subscription verification and decryption requires implementing specific event handlers that decrypt incoming payloads, verify the event source, and ensure idempotent callback processing to prevent duplicate actions.

How do I synchronize data between an external system and Feishu Bitable?

Synchronizing data with Feishu Bitable involves performing batched table operations for bidirectional synchronization, utilizing rate-limit-aware batching strategies to ensure data consistency between Feishu and external systems.

How do I manage tenant_access_token and user token separation for Feishu integrations?

Managing Feishu token separation requires caching tenant_access_token and user tokens independently, ensuring correct token usage for OAuth/OIDC flows, QR code login, and multi-tenant API authentication.

Can I trigger downstream automation when a Feishu approval instance is submitted or approved?

Yes, you can define, submit, and react to approval instances programmatically, triggering downstream business logic automatically based on specific approval events and persisting outcomes to Bitable.

How do I handle API rate limits and retries when developing enterprise Feishu integrations?

Handling Feishu API rate limits and retries requires implementing specific retry strategies and rate-limit-aware batching in your code to ensure reliable execution of enterprise-grade integrations without exceeding API quotas.