Zendesk to Airtable, a clean Markdown knowledge base
Your Zendesk Help Center looks “organized” until you need the same article somewhere else. Then it’s copy, paste, fix formatting, hunt for the latest version, repeat.
This Zendesk Airtable sync hits support leads first, but knowledge managers and ops folks feel it too. You end up maintaining the same content in two places, and it quietly steals hours every month.
This workflow pulls your Zendesk articles, converts them into clean Markdown, and upserts them into Airtable so you always have a searchable, reusable archive. Below, you’ll see exactly how it works, what you need, and what kind of time you get back.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Zendesk to Airtable, a clean Markdown knowledge base
flowchart LR
subgraph sg0["When clicking ‘Execute workflow’ Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "When clicking ‘Execute workf..", pos: "b", h: 48 }
n1@{ icon: "mdi:swap-vertical", form: "rounded", label: "Split Out", pos: "b", h: 48 }
n2@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
n3@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set fields to store", pos: "b", h: 48 }
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/airtable.svg' width='40' height='40' /></div><br/>Store Zendesk articles to Ai.."]
n5@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set base_url", pos: "b", h: 48 }
n6@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set base url", pos: "b", h: 48 }
n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Get articles since last run"]
n8["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Get all articles"]
n9["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/markdown.dark.svg' width='40' height='40' /></div><br/>Body to Markdown"]
n1 --> n3
n6 --> n7
n5 --> n8
n9 --> n4
n8 --> n1
n2 --> n6
n3 --> n9
n7 --> n1
n0 --> n5
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0,n2 trigger
class n4 database
class n7,n8 api
classDef customIcon fill:none,stroke:none
class n4,n7,n8,n9 customIcon
The Problem: Zendesk articles are hard to reuse elsewhere
Zendesk is great for serving help content to customers. It’s not great when you need to reuse that same content in other systems. The second you try to migrate, audit, or repurpose articles, you run into messy HTML, inconsistent formatting, and a lack of a clean “source of truth” outside Zendesk. Teams end up exporting ad hoc, saving random files to Drive, or rebuilding articles from scratch in another tool. It’s exhausting. And honestly, it’s a little risky because you never fully trust what’s “current.”
The friction compounds fast. Here’s where it breaks down in real life.
- Copying article content out of Zendesk usually brings along extra HTML clutter, so every reuse turns into a mini cleanup project.
- When someone updates an article, there’s no reliable archive in a second system unless a person remembers to export it again.
- Migration projects stall because nobody wants to manually pull 50 to 500 articles, one page at a time.
- Audits and compliance checks become painful because you can’t quickly search, filter, and review all article content in one table.
The Solution: Sync Zendesk articles into Airtable as Markdown
This n8n workflow creates a clean pipeline from your Zendesk Help Center into Airtable. On the first run, you trigger it manually and it retrieves all existing articles through the Zendesk Help Center API, handling pagination so you’re not limited by volume. Each article gets split into individual records, the important fields are mapped (Article ID, Title, URL, and body), and the body is converted from HTML into Markdown for portability. Finally, the workflow upserts each item into Airtable using Article ID as the unique key, so reruns update existing rows instead of creating duplicates. Once the baseline is in place, the scheduled trigger runs every 30 days by default and pulls only new or recently updated articles since the last run.
It starts with either a one-time manual import or a recurring schedule. Then it fetches articles from Zendesk, transforms the content into Markdown, and writes the results into Airtable. From there, your team can search, filter, audit, and reuse content without touching Zendesk exports again.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you have 120 Zendesk articles and you’re prepping for a knowledge base migration. Manually copying, cleaning, and pasting each one can easily take about 10 minutes per article, so you’re looking at roughly 20 hours of tedious work. With this workflow, the “before” becomes: start the manual run, wait for the API fetch and conversion to finish, and review the Airtable rows, which is usually closer to 30 minutes of active time. After that, the monthly sync keeps the archive fresh without anyone remembering to do it.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Zendesk for Help Center articles and API access.
- Airtable to store a searchable Markdown archive.
- Zendesk API token (Admin Center > Apps and Integrations > Zendesk API).
Skill level: Beginner. You’ll connect credentials, paste a base URL, and choose an Airtable base/table.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A manual run or a monthly schedule kicks things off. Use the manual trigger once to import everything already in Zendesk. After that, a schedule trigger (every 30 days by default) can keep syncing new or updated articles.
Zendesk is queried through the Help Center API. The workflow builds the base endpoint first, then uses HTTP requests to retrieve articles. Pagination is handled so you can pull a large knowledge base without babysitting it.
Each article is normalized and cleaned. The workflow splits the API response into individual items, maps the fields you care about (Article ID, title, URL, and body), then converts the body from HTML into Markdown so it’s portable and easier to edit.
Airtable is updated without duplicates. Records are upserted based on Article ID, which means reruns update the same row instead of creating a second version. This is what makes the scheduled sync usable long-term.
You can easily modify the schedule frequency to run weekly instead of monthly based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
This workflow supports a manual run path for full syncs. Configure the manual trigger to kick off the initial base URL setup.
- Add a Manual Run Trigger node as the starting trigger for the full sync path.
- Connect Manual Run Trigger to Define Base Endpoint.
Step 2: Configure the Monthly Schedule Trigger
The scheduled path fetches only recent articles on a 30-day interval. This runs alongside the manual path but is configured independently.
- Add a Monthly Schedule Trigger node.
- Set Interval to
30days in the rule configuration. - Connect Monthly Schedule Trigger to Define Base Endpoint 2.
Step 3: Connect Zendesk and Fetch Articles
Both the manual and scheduled paths set the Zendesk base URL and then request articles via HTTP calls.
- In Define Base Endpoint, set base_url to
https://[YOUR_ID].zendesk.com. - In Retrieve All Articles, set URL to
={{$json.base_url}}/api/v2/help_center/articlesand enable pagination with Next URL={{ $response.body.next_page }}and Complete When={{ $response.body.next_page.isEmpty() }}. - Set query parameters in Retrieve All Articles: sort_by to
created_atand sort_order todesc. - In Define Base Endpoint 2, set base_url to
https://[YOUR_ID].zendesk.com. - In Fetch Recent Articles, set URL to
={{ $json.base_url }}/api/v2/help_center/incremental/articles.json?start_time={{ $now.minus($('Monthly Schedule Trigger').params.rule.interval.first().daysInterval, 'days').toSeconds().round() }}and configure pagination using={{ $response.body.next_page }}and={{ $response.body.next_page.isEmpty() }}. - Credential Required: Connect your zendeskApi credentials in both Retrieve All Articles and Fetch Recent Articles.
https://[YOUR_ID].zendesk.com value in both Define Base Endpoint and Define Base Endpoint 2.Step 4: Split, Map, and Convert Article Content
Both article-fetching paths merge into a shared processing pipeline that splits, maps, and converts the article body to Markdown.
- In Split Records, set Field to Split Out to
articles. - In Map Article Fields, map fields using these expressions: id
={{ $json.id }}, url={{ $json.url }}, title={{ $json.title }}, and body={{ $json.body }}. - In Convert Body to Markdown, set HTML to
={{ $json.body }}and Destination Key tomarkdown.
Step 5: Configure Airtable Upsert
Mapped Markdown content is upserted into Airtable, matching on article ID to prevent duplicates.
- In Upsert Articles to Airtable, select your Base and Table (e.g.,
Zendesk KB→Articles). - Set Operation to
upsertand Matching Columns toArticle ID. - Map fields: URL
={{ $json.url }}, Title={{ $json.title }}, Content={{ $json.markdown }}, and Article ID={{ $json.id }}. - Credential Required: Connect your airtableTokenApi credentials in Upsert Articles to Airtable.
Step 6: Test and Activate Your Workflow
Validate both the manual and scheduled paths before activating the workflow.
- Click Execute Workflow from Manual Run Trigger and confirm records flow through Retrieve All Articles → Split Records → Map Article Fields → Convert Body to Markdown → Upsert Articles to Airtable.
- Check Airtable for new or updated rows with populated Title, Content, URL, and Article ID.
- Optionally run a test from Monthly Schedule Trigger to verify recent article syncs.
- Once verified, toggle the workflow to Active for production use.
Common Gotchas
- Zendesk credentials can expire or need specific permissions. If things break, check Admin Center > Apps and Integrations > Zendesk API first, then confirm the token is still valid.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- HTML-to-Markdown conversion isn’t magic. If your Zendesk articles contain heavy tables or embedded widgets, expect to tweak the conversion settings or do a quick cleanup pass in Airtable.
Frequently Asked Questions
About 30 minutes if your Zendesk and Airtable credentials are ready.
No. You’ll mostly paste credentials, confirm the Zendesk base URL, and pick the Airtable base and table.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Airtable and Zendesk plan limits based on your usage.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, but it’s a simple change. Update the Monthly Schedule Trigger to run weekly (or daily), and adjust the “Fetch Recent Articles” request so it pulls updated articles since your preferred cutoff. Some teams also add extra Airtable fields like category, section, or locale by expanding the “Map Article Fields” step.
Most of the time it’s an API token issue. Confirm “Token Access” is enabled in Zendesk, then regenerate the token and update the credentials in n8n. Also double-check the Zendesk subdomain in your base URL, because a tiny typo will cause authentication to fail. If you’re syncing a lot at once, rate limiting can show up as intermittent HTTP errors, so spacing runs out can help.
A lot. The workflow paginates Zendesk results, so pulling hundreds (even thousands) of articles is normal; the real limits are your n8n execution capacity and Airtable’s API rate limits. On n8n Cloud Starter, many teams run this comfortably as a monthly job. If you self-host, you’re mainly constrained by your server and how aggressively you schedule it.
Often, yes. Zapier and Make can work for simple “new record” triggers, but syncing a full knowledge base usually needs pagination, upserts by a unique key, and content transformation (HTML to Markdown) in one flow. n8n is better suited for that kind of logic, and self-hosting is a big cost lever if you run lots of automations. If you just want a tiny two-step sync, the other tools might feel faster at first. Talk to an automation expert if you want a quick recommendation based on volume.
Once your Zendesk articles live in Airtable as clean Markdown, everything gets easier: audits, rewrites, migrations, even quick reuse for customer emails. Set it up once, then let it run.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
