Airtable to Contentful: clean HTML from Markdown
Your copy looks fine in Airtable… until it lands somewhere that expects HTML. Suddenly you’re fixing broken line breaks, missing links, and weird formatting that keeps drifting from record to record.
This Airtable Contentful integration hits content managers first, honestly. But marketing ops teams and agency folks managing client content feel it too. The outcome is simple: consistent HTML output you can reuse in Contentful without reformatting every time.
You’ll learn how this workflow converts Airtable Markdown into clean HTML, then writes it back to Airtable (either one record or every record in a batch).
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: Airtable to Contentful: clean HTML from Markdown
flowchart LR
subgraph sg0["Flow 1"]
direction LR
n0["<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/webhook.dark.svg' width='40' height='40' /></div><br/>Incoming Airtable Sync Hook"]
n1@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Determine Record Scope", pos: "b", h: 48 }
n2["<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/>Fetch Single Airtable Row"]
n3["<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/>Markdown to HTML Transform A"]
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/>Modify Single Airtable Row"]
n5["<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/>Retrieve Airtable Records"]
n6["<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/>Markdown to HTML Transform B"]
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/airtable.svg' width='40' height='40' /></div><br/>Modify All Airtable Rows"]
n3 --> n4
n6 --> n7
n5 --> n6
n0 --> n1
n2 --> n3
n1 --> n2
n1 --> 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 n1 decision
class n2,n4,n5,n7 database
class n0 api
classDef customIcon fill:none,stroke:none
class n0,n2,n3,n4,n5,n6,n7 customIcon
Why This Matters: Markdown That Doesn’t Travel Well
Markdown is great for quick drafting, but it breaks down the moment you need the same content in a system that expects HTML (like many CMS rich text fields). What starts as “just copy and paste it” turns into a recurring cleanup job: headings render differently, lists lose indentation, links look inconsistent, and someone always forgets to convert a record before publishing. The worst part is the mental load. You’re never fully sure the formatting is correct until you preview it in the destination tool, so you keep context-switching to double-check.
The friction compounds. Here’s where it usually goes wrong.
- Copying Markdown into a rich text editor often creates inconsistent spacing and list formatting across posts.
- Teams end up doing “one-off fixes” that never get written back to Airtable, so the next reuse is broken again.
- When multiple people touch the same fields, formatting rules drift and your content stops looking like one brand.
- Bulk updates become scary, because no one wants to manually reformat 50 records the day before a launch.
What You’ll Build: Airtable Markdown → HTML Sync (Single or Bulk)
This workflow gives you a repeatable way to turn Markdown in Airtable into clean HTML, then store that HTML back in Airtable so it becomes the “ready-to-publish” version everywhere else. It starts when Airtable triggers a webhook (you can run it on demand or whenever a record changes). Next, the workflow decides if it should process one record or sweep through all records in your table. For a single record, it fetches the row, converts the Markdown field into HTML, then updates the same record with the HTML output. For a bulk run, it retrieves multiple records, converts each one, and writes HTML back in batch. Same transformation, two modes, so you’re not stuck running everything manually.
The workflow starts with an Airtable sync hook, then branches based on scope (single vs. all). Markdown gets transformed into HTML, and Airtable is updated so the HTML field becomes your reusable source for Contentful and other tools.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you publish 20 Airtable records a week into a CMS that expects HTML. If formatting cleanup takes about 10 minutes per record, that’s roughly 3 hours of repetitive editing every week. With this workflow, you trigger a single-record sync when a draft is ready (or run a bulk sync before a launch), then let the Markdown-to-HTML conversion and Airtable update happen automatically. The waiting time is just processing time, not your time, so you get those hours back for actual editing and QA.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Airtable for the source Markdown and HTML fields.
- Contentful to reuse the HTML in rich text.
- Airtable API token (create it in Airtable Developer Hub)
Skill level: Beginner. You’ll connect Airtable, map a couple of fields, and test with one record before running bulk.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
An Airtable webhook triggers the run. The workflow begins when your Airtable automation (or manual test call) hits the “Incoming Airtable Sync Hook” webhook in n8n.
The workflow decides how much to process. An “If” condition checks the payload to determine record scope, so you can sync a single record for day-to-day publishing or run through the whole table when you’re cleaning up older content.
Markdown becomes clean HTML. For single record runs, n8n fetches the row from Airtable, then passes the Markdown field through the Markdown transform node. For bulk runs, it retrieves Airtable records first, then transforms each one using a second Markdown transform branch.
The HTML gets written back to Airtable. The final Airtable update nodes store the HTML output in a dedicated field, which means Contentful (or any other system) can pull the “ready” version without extra formatting steps.
You can easily modify which table, view, or field gets processed based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Webhook Trigger
This workflow starts when Airtable sends a webhook request to n8n.
- Add the Incoming Airtable Sync Hook node as your trigger.
- Set the Path to
848644e5-6b1d-42b3-9259-5828c29780a8. - Copy the generated webhook URL and configure your Airtable automation to call it when records are updated.
recordId query parameter, the workflow can’t target a single row and will run the bulk update path instead.Step 2: Connect Airtable
All Airtable nodes use the same token-based credentials and target the same base and table.
- Open Fetch Single Airtable Row and select Credential Required: Connect your airtableTokenApi credentials.
- Repeat the credential connection for Modify Single Airtable Row, Retrieve Airtable Records, and Modify All Airtable Rows using the same airtableTokenApi credentials.
- In each Airtable node, confirm the Base is set to
[YOUR_ID](cached name:360Creators) and the Table is set to[YOUR_ID](cached name:📺 Videos).
Step 3: Set Up the Record Scope Logic
The workflow decides whether to process a single record or multiple records based on the incoming webhook query.
- Add the Determine Record Scope node after Incoming Airtable Sync Hook.
- Configure the condition to check if
{{ $json.query.recordId }}exists. - Ensure the flow branches as follows: Determine Record Scope outputs to both Fetch Single Airtable Row and Retrieve Airtable Records in parallel.
Step 4: Set Up Markdown to HTML Processing
Both branches transform the Airtable markdown field into HTML before updating records.
- In Fetch Single Airtable Row, set the Operation to
getand the Record ID to{{ $json.query.recordId }}. - Configure Markdown to HTML Transform A with Mode set to
markdownToHtmland Markdown set to{{ $json['📥 Video Description'] }}. - In Retrieve Airtable Records, set Operation to
search, Return All tofalse, and Limit to3. - Configure Markdown to HTML Transform B with Mode set to
markdownToHtmland Markdown set to{{ $json["📥 Video Description"] }}.
Step 5: Configure the Airtable Updates
The workflow writes HTML back to Airtable, either for a single row or multiple rows.
- In Modify Single Airtable Row, set Operation to
updateand map fields: id to{{ $json.id }}and Video description HTML to{{ $json.data }}. - In Modify All Airtable Rows, set Operation to
updateand map fields: id to{{ $json.id }}, Unpublished tofalse, and Video description HTML to{{ $json.data }}.
Step 6: Test and Activate Your Workflow
Validate both single-record and bulk-update paths, then enable the workflow for production.
- Click Execute Workflow and call the webhook URL with
?recordId=YOUR_RECORD_IDto test the single-record path. - Remove the
recordIdparameter to verify the bulk path through Retrieve Airtable Records and Modify All Airtable Rows. - Confirm Airtable rows have the Video description HTML field updated with converted HTML.
- Toggle the workflow to Active once tests succeed.
Troubleshooting Tips
- Airtable credentials can expire or need specific permissions. If things break, check your Airtable token scopes in the Developer Hub and confirm the base is included.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Quick Answers
About 30 minutes if your Airtable base is ready.
No. You’ll mainly connect Airtable credentials and map the Markdown field to your HTML field.
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 plan limits and API rate limits, which can matter if you batch-update a lot of records.
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, pretty easily. Most people swap the input and output field mappings in the “Modify Single Airtable Row” and “Modify All Airtable Rows” nodes, then adjust the record selection in “Retrieve Airtable Records” (for example, only process a specific view). You can also change the webhook payload to force single-record syncs from an Airtable button field, which keeps bulk runs as a separate “maintenance” action.
Usually it’s an expired token or the token doesn’t have access to the base you’re querying. Regenerate your Airtable personal access token, confirm it includes the right scopes, and update it in n8n. Also check that the table name (or table ID) matches exactly, because a renamed table can make a previously working node fail. If you’re doing bulk runs, you can also hit Airtable rate limits, so slow it down or narrow the view.
On n8n Cloud Starter, assume “a few thousand” executions per month depending on plan limits. If you self-host, there’s no execution cap from n8n, but Airtable API limits still apply, so bulk runs are best done in smaller batches or against a filtered view.
Often, yes, because you get more control over branching (single record vs. bulk) and you’re not forced into per-task pricing when you process lots of rows. The Markdown transform step is also straightforward in n8n, while other tools sometimes push you into awkward formatter workarounds. That said, if your process is literally “when record updates, update another field,” Zapier or Make can be quicker to click together. The moment you need bulk runs, views, or careful record selection, n8n tends to feel less limiting. Talk to an automation expert if you want help choosing.
Once your HTML lives back in Airtable, publishing stops being a formatting project. You’ll feel the difference the next time you need to reuse the same copy in Contentful on a deadline.
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.
