appflowy-integration

Name: appflowy-integration
Availability: InStock
Author: HelloWorldSungin

Convert Markdown to AppFlowy Delta blocks via a configuration-driven Git PushSync workflow.

2|1|Updated Nov 21, 2025

Search Tags:#automation #documentation #markdown #integration #mapping #delta-blocks #AppFlowy

Ready to run

npx skills add https://github.com/HelloWorldSungin/AI_agents --skill appflowy-integration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: appflowy-integration
Source: https://github.com/HelloWorldSungin/AI_agents/tree/main/skills/custom/appflowy-integration
Command: npx skills add https://github.com/HelloWorldSungin/AI_agents --skill appflowy-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, pyyaml, python-dotenv, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates AppFlowy integration to streamline task and documentation syncing, reducing manual overhead and ensuring consistent alignment between repository changes and AppFlowy workspaces.

Core Features & Use Cases

Git PushSync workflow: Push to GitHub and automatically sync tasks and documentation to AppFlowy in one command.
Documentation automation: Delta-based content blocks (Markdown to AppFlowy) with optional database-backed storage and mapping to prevent duplicates.
Workspace and project management: Automates setup of workspaces, folders, and documentation hierarchy across AI agents projects.
Configurable, generic syncing: Works with any project via YAML/JSON configuration and auto-discovery modes.
Incremental updates: Watches for changes and only pushes updated content, with support for dry-run and force-resync.
Rich tooling integration: Supports mappings, environment-configured credentials, and Docker/hosted deployment workflows.

Quick Start

Set up AppFlowy credentials and workspace IDs in your environment or .env file.
Use the git pushsync workflow to push changes and automatically sync to AppFlowy.
If starting fresh, run a dry-run to preview what would be synced, then perform a real sync.
For documentation, consider a database-based approach and a mapping file to prevent duplicates.

Frequently Asked Questions about appflowy-integration

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

FAQPage Schema

How do I sync Markdown documentation to AppFlowy automatically?▼

To sync Markdown documentation to AppFlowy, this Skill converts Markdown files into AppFlowy Delta blocks and pushes them via the AppFlowy REST API. It uses a mapping file to prevent duplicates and supports incremental updates for consistent documentation automation.

Can I automate AppFlowy task tracking through a GitHub push?▼

Yes, you can automate AppFlowy task tracking through a GitHub push using the git PushSync workflow. This pattern triggers the syncing of repository changes to AppFlowy workspaces in a single command, reducing manual overhead and keeping tasks aligned.

How do I prevent duplicate content blocks when syncing to AppFlowy?▼

To prevent duplicate content blocks when syncing to AppFlowy, the workflow enforces a mapping file to track previously synced items. This database-backed approach ensures incremental updates only push new or modified documentation.

Do I need YAML configuration to sync project tasks to AppFlowy?▼

Yes, you need YAML or JSON configuration to establish a generic syncing workflow for AppFlowy. Configuring workspace IDs and AppFlowy credentials in your environment enables the system to auto-discover and map project tasks correctly.

What are the limitations of using the AppFlowy REST API for documentation syncing?▼

A key limitation of using the AppFlowy REST API for documentation syncing is the strict reliance on a mapping file to prevent duplicates. If the mapping is lost or corrupted, you must use the force-resync capability to rebuild your workspace hierarchy.