Zendesk Knowledge Base Sync to Airtable with Markdown Conversion - n8n Workflow

• Customer service or support teams needing off-platform access to Zendesk articles.
• Content Managers consolidating or migrating knowledge bases.
• Automation specialists looking for reusable n8n templates for API data synchronization.
• Users who require Markdown versions of their help center content for use in tools like Notion or custom documentation systems.

This comprehensive n8n workflow addresses the critical need for knowledge base content portability and backup. Zendesk articles, often locked within the platform, can be challenging to reuse or store in a structured database like Airtable. This n8n workflow solves this by providing a reliable synchronization pipeline. It features a dual-path n8n trigger system, allowing for both immediate, full data dumps and scheduled, incremental updates to ensure your Airtable base remains current without excessive API calls. Crucially, the automation includes a specific conversion step, transforming the raw HTML body content into clean Markdown, making the resulting data highly portable and ready for repurposing. Utilizing specialized n8n node configurations for both Airtable and HTTP requests, this solution provides a robust foundation for managing mission-critical content.

This n8n workflow utilizes two distinct entry points, each initiated by a different n8n trigger:

1. Initial/Manual Sync: The process starts with the Manual Trigger. It sets the base URL for the Zendesk domain and then uses an HTTP Request n8n node (Get all articles) to pull the entire existing Knowledge Base, handling pagination automatically.


2. Incremental/Scheduled Sync: The Schedule Trigger runs automatically (e.g., every 30 days). This path also sets the base URL, but the subsequent HTTP Request n8n node (Get articles since last run) uses dynamic expressions to calculate the start_time based on the schedule interval. This ensures that only articles created or updated since the last run are fetched.

Regardless of the starting n8n trigger, the data converges. A Split Out n8n node processes the fetched article array into individual items. A Set n8n node extracts key fields (id, url, title, body). Next, a Markdown n8n node converts the HTML body into a new markdown field. Finally, the Airtable n8n node performs an Upsert operation, using the Article ID as the unique identifier to insert new records or update existing ones, ensuring no duplicates and maintaining data integrity in the target Airtable base. This entire sequence is an example of an efficient, data-transforming n8n workflow.

1. Import the n8n template: Copy the provided JSON and paste it directly into your n8n instance using the 'New' > 'Import from JSON' function.


2. Configure Credentials:

1. Customize the Workflow:

1. Execute: Run the Manual Trigger first for a complete sync. Activate the Schedule Trigger to maintain synchronization automatically.

Manual Trigger / Schedule Trigger: These are the primary n8n trigger components. The Manual Trigger is for ad-hoc full syncs, while the Schedule Trigger runs every 30 days for incremental updates, making this a highly adaptive n8n workflow.
Set (Set baseurl / Set base url): Standard n8n node used to dynamically inject the Zendesk domain URL into the workflow items, simplifying the configuration of subsequent HTTP Request n8n nodes.
HTTP Request (Get all articles / Get articles since last run): These powerful n8n node implementations fetch the data from the Zendesk Help Center API. They are configured with Zendesk API credentials and handle pagination automatically. The 'since last run' node uses complex expression logic to calculate the necessary starttime parameter for incremental fetching.
Split Out: A core logic n8n node that separates the batch of articles received from the HTTP request into individual items, allowing subsequent nodes to process each article independently.
Set (Set fields to store): This n8n node standardizes the data by selecting and renaming the crucial fields (id, url, title, body) before transformation.
Markdown (Body to Markdown): A dedicated n8n node responsible for the data transformation step, converting the raw HTML content of the article body into clean, portable Markdown format.

• Airtable (Store Zendesk articles to Airtable): The final action n8n node. It is configured for the upsert operation, meaning it matches existing records by Article ID. It maps the newly generated markdown content into the Airtable's Content field, completing the data synchronization aspect of this n8n workflow.