Resources · Make integration

Markdown Make integrationAutomate Markdown with Make.

Need clean HTML from Markdown text, or Markdown from an HTML page? The Markdown Make integration gives you 2 converter modules, one for each direction. This guide shows where each one fits and walks you through a first scenario, from the empty editor to switching it on.

Try the Markdown integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Markdown Make integration do?

The Markdown Make integration is a built-in converter inside Make. You place one of its modules in a scenario, the automation you build in Make, and it rewrites the text it receives: Markdown becomes HTML, or HTML becomes Markdown. Each module is one brick of that scenario, and here both bricks are transformers, so they change data rather than read or write an account.

Publish notes as a web page. Writers often draft in Markdown because it stays readable. Put Markdown to HTML after the module that fetches the draft, and the next module receives HTML that a website or an email tool can display.

Archive web content as plain text. Going the other way, HTML to Markdown takes a page or an email body and gives back lighter Markdown, easier to store in a notes app or a text file and easier to read by eye.

Clean up what a scraper returns. When another app hands you raw HTML, for example the AI Scraper by Parsera Make integration, converting it to Markdown before the next step keeps the headings and links while dropping the markup.

What the app does not do: it has no trigger, so it never starts a scenario on its own, and it has no Make an API Call module. It only converts. If you also use n8n, there is a Markdown n8n integration page too, and the n8n vs Make comparison helps you place both tools.

Connect

How do you add Markdown to a scenario?

  1. 01

    Search for the app

    In the editor, click the + where you want the conversion, type Markdown in the search box and open the app. Make shows its two modules, HTML to Markdown and Markdown to HTML.

  2. 02

    Pick the direction

    Choose the module that matches the text you already have. The Markdown documentation lists no prerequisite, so there is no account of your own to prepare before this step.

  3. 03

    Save any connection Make requests

    If a Create a connection button appears, follow Make's usual path: click it, give the connection a name if you like, then click Save. A connection is an account linked to Make once and reused by every module of that app.

First scenario

Your first scenario with Markdown

GoalWhen another app delivers a Markdown text, Make turns it into HTML that the next step can publish or send.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Markdown cannot start a flow, this first brick comes from the app that holds your text.

  2. 02

    Add the source module

    Search for that app, pick the module that returns your draft and click Create a connection if Make asks for one. Fill its fields; Make lists what it can read once the account is linked.

  3. 03

    Add Markdown to HTML

    Click the + on the right of the source module, search Markdown and pick Markdown to HTML. Map the text coming from the previous module into it, so every bundle (one item passing between modules) gets converted.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Open the output of Markdown to HTML and check that the headings and links came through as HTML tags.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, and the Free plan allows 15 minutes at the shortest. Pick your schedule, save, then switch the scenario on.

Modules

What the Markdown modules do

Markdown gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Markdown1

HTML to Markdown

Transformer

In Make“Transforms HTML into Markdown.”

Hand this module a piece of HTML and it returns the same content written as Markdown, so a web page or an email body becomes light text you can read without a browser.

When to use it
right after a module that brings back HTML, when the next step is storage, a note or a text file rather than a screen.
Watch out
it is a transformer, so it converts the text you map into it and nothing else; it does not fetch the page for you.
Markdown2

Markdown to HTML

Transformer

In Make“Transforms Markdown into HTML (SVG, MathML).”

You get HTML ready for display: the module reads Markdown text and outputs the matching tags, and the documentation mentions SVG and MathML among what it can produce.

When to use it
when drafts are written in Markdown but the destination, a newsletter tool or a website, expects HTML.
Watch out
each conversion is one operation, one run of one module on one bundle, and Make counts operations on your plan.
Need help

Need help automating Markdown with Make?

A person reads every message.

FAQ

Markdown and Make: common questions

01Is the Markdown Make integration free?
Yes. Markdown is a standard app, available from the Free plan onward. The Free plan gives you 2 active scenarios, 15 minutes at least between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and lift the cap on active scenarios. Keep in mind that every conversion counts as an operation, which is how Make measures usage on each plan.
02What does the Markdown Make integration need before the first run?
Very little. The Markdown documentation lists no prerequisite and no connection steps of its own. You add a module from the app to a scenario and map text into it. If Make still shows a Create a connection button, the generic path applies: click it, name the connection if you want, then save. The more important requirement is upstream: a module from another app that delivers the Markdown or HTML you want to convert.
03Can the Markdown Make integration start a scenario in real time?
No. Markdown has no trigger at all, neither scheduled nor instant, so it never launches a scenario by itself. The scenario starts with the first module of another app. If that module is an instant trigger, meaning the app calls Make through a webhook as soon as something happens, the conversion follows right away. If it is scheduled, Make checks on the scenario's schedule, every 15 minutes by default for a new scenario.
04What if the Markdown Make integration lacks a needed conversion?
It depends on the gap. The app has exactly 2 modules, HTML to Markdown and Markdown to HTML, and no Make an API Call module to reach anything beyond them. For another format, look for a different app in Make that handles it, or place the converted text into the next module of the app that owns the data. When the flow gets tangled, a Make agency can review the scenario with you.
05Is Make or n8n better suited to Markdown conversion?
Both can work. The same app often has an n8n node, and Markdown does, with its own page on this site. The practical criterion is where the rest of your workflow already runs: converting inside the tool that already holds the source and destination modules avoids moving text between two platforms. This page makes no claim about which tool is faster or cheaper; the n8n vs Make comparison covers the broader differences.
Same platform

Other docs you might need on this stack.

Browse all integrations