Resources · Make integration

MDSpin Make integrationAutomate MDSpin with Make.

Need clean Markdown out of files your tools already handle? The MDSpin Make integration gives you 7 action modules that convert a file link, one attachment or a batch of them. This guide shows what each one does, how to link your account and how to build a first scenario.

Try the MDSpin integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you automate with the MDSpin Make integration?

The MDSpin Make integration lets a Make scenario (the automation you build, a chain of modules) hand a document to MDSpin and get Markdown back. Each module is one brick of that chain. MDSpin brings only actions, so something else starts the scenario: a module of another app or the Make schedule.

Turn shared links into text you can reuse. A form or a spreadsheet gives you the address of a PDF or a page. Convert file from url to markdown takes that link and returns Markdown that the next module can store, post or pass to an AI step.

Clean up what arrives by email. When a message carries a file, Convert attachment to markdown handles one attachment, and Convert attachment batch to markdown takes several in a single step. A support team can keep the content of every attached brief in plain text.

Reach what the list leaves out. Make an API call reuses your MDSpin connection to call any endpoint of its API. Three modules carry the label [deprecated] in their name: they still appear, but a new build is better off without them.

Be aware that Make itself flags this app as having limited documentation, so the page stays with what the module names say. If you are still weighing platforms, read the n8n vs Make comparison, and the Make pricing page before counting operations. For a guided start, the Make training walks through the editor.

Connect

How do you connect MDSpin to Make?

  1. 01

    Add an MDSpin module

    In your scenario, click the +, search for MDSpin and pick any of its modules. Then click Create a connection. A connection is your MDSpin account linked to Make once and reused by every MDSpin module.

  2. 02

    Name it and authorize

    Give the connection a name you will recognize later, which is optional. Then follow what MDSpin asks: either approve access on its own page, or paste the key it gives you. The Make doc does not say which of the two applies.

  3. 03

    Save and check

    Click Save. Back in the module, the connection now shows in the list, and any other MDSpin module you add later can pick the same one without asking you to log in again.

First scenario

Build your first scenario with MDSpin

GoalWhen another app hands over a file link, Make sends it to MDSpin and gets Markdown back.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. It belongs to the app that holds your file links, such as a form or a sheet.

  2. 02

    Set up the starting module

    Pick the module of that app, create its connection and fill its fields. Make lists what it can read once the account is linked, so you choose from a menu instead of typing names.

  3. 03

    Add the MDSpin conversion

    Click the + on the right, search MDSpin and choose Convert file from url to markdown. Link your MDSpin account, then map the link coming from the first module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. A bundle is one item passing along, here one file and its converted text.

  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 cannot go lower. Set your pace, then turn the scenario on.

Modules

What each MDSpin module does in Make

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

MDSpin1

Convert Google Doc to markdown [deprecated]

ActionIn the docs only

You get a Google Doc turned into Markdown, which older scenarios built around Google documents still rely on. Its name carries the [deprecated] label, which marks it as a module to phase out.

When to use it
only while you maintain an existing scenario that already contains it and still works.
Watch out
for a new scenario, pass the document as a link to Convert file from url to markdown instead.
MDSpin2

Convert Google Slide to markdown [deprecated]

ActionIn the docs only

Slides become readable Markdown text here, handy to reuse the words of a presentation elsewhere. Make lists this module with [deprecated] in its name, so treat it as legacy.

When to use it
when you inherit a scenario that converts decks this way and you are not ready to rebuild it.
Watch out
the doc gives no date for its removal, so plan the switch before it surprises you.
MDSpin3

Convert attachment batch to markdown

ActionIn the docs only

Several attachments come out as Markdown in one step, rather than one module run per file. It suits messages or records that carry more than one document at a time.

When to use it
a client sends a contract, an annex and a quote in the same email and you want all three as text.
Watch out
each module run is an operation, what Make counts on your plan, so check what the batch consumes after your first test.
MDSpin4

Convert attachment to markdown

ActionIn the docs only

A single attached file, received from the previous module, is returned as Markdown you can store or pass along. This is the simplest way to read the content of one document inside a scenario.

When to use it
a form upload or an email with one file, where the next step needs the text rather than the file.
Watch out
if the previous module hands over several files, pick the batch module instead.
MDSpin5

Convert file from url to markdown

ActionIn the docs only

Give it the address of a file and it hands back Markdown, without downloading anything yourself first. It is the module to reach for when your data holds links rather than attachments.

When to use it
a spreadsheet column or a CRM field stores document links that you want to turn into text.
Watch out
the link must be one MDSpin can open; test with Run once on a real record before switching on.
MDSpin6

Make an API call

ActionIn the docs only

With this module, any endpoint of the MDSpin API becomes reachable from your scenario, using the connection you already created. It fills the gap when the six other modules do not cover your case.

When to use it
you know from the MDSpin side that an operation exists and no listed module offers it.
Watch out
Make has limited documentation for this app, so you need the MDSpin API reference at hand.
MDSpin7

Save markdown to Google Drive [deprecated]

ActionIn the docs only

This one takes Markdown and drops it into Google Drive, closing the loop in older conversion scenarios. The [deprecated] tag in its name tells you Make no longer wants new builds on it.

When to use it
keep it only in a running scenario you have not migrated yet.
Watch out
for new work, send the converted text to a storage module of another app after the MDSpin step.
Need help

Need help automating MDSpin with Make?

A person reads every message.

FAQ

MDSpin and Make: common questions

01Is the MDSpin Make integration free?
Yes, MDSpin is a standard app, so its modules work from the Free plan onward. That plan comes with limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to one minute, remove the cap on active scenarios and allow 40 minutes per execution. Usage is counted in operations each month. The price of MDSpin itself is not covered here.
02What do you need to connect MDSpin to Make?
An MDSpin account and a Make account are enough to begin, since the Make doc lists no other prerequisite. You add an MDSpin module, click Create a connection, optionally name it, then either approve access on the MDSpin page or paste the key MDSpin gives you, and click Save. Make says it cannot document this app fully, so if a step differs, the MDSpin side is where to look. The same connection is then reused by all seven modules.
03Does the MDSpin Make integration have a trigger?
No, all seven MDSpin modules are actions, so the scenario needs another starting point. Two options work. Put a module of another app first, for example the form or mailbox that receives your files, and place MDSpin after it. Or start on a schedule: the clock on the first module runs the scenario every 15 minutes by default, and the Free plan cannot go below that interval. Either way, MDSpin does its conversion once the data reaches it.
04What if an MDSpin module is missing or does not fit?
Use Make an API call. It sends a request to any endpoint of the MDSpin API with the connection you already set up, so you can reach an operation that none of the other modules offers. Keep in mind that Make flags this app as having limited documentation, which means the MDSpin API reference is your guide. For the three modules marked deprecated, prefer the url or attachment conversions in a new scenario.
05Should you use Make or n8n for MDSpin?
It depends on where your other automations already run. On the Make side, this page documents seven modules, including a generic API call that reuses your connection. Many apps also have an n8n node, but that has not been checked for MDSpin here, so confirm it before deciding. The practical criteria are which platform your team already knows, which apps sit around MDSpin in your process, and which plan limits you can live with.
Same platform

Other docs you might need on this stack.

Browse all integrations