Resources · Make integration

Autype Make integrationAutomate Autype with Make.

Documents that fill themselves in, and PDFs that get merged, stamped or locked without anyone opening them? The Autype Make integration offers 42 modules, 36 actions and 6 searches, for teams that produce documents from data. This guide connects your API key and walks you through a first scenario.

Try the Autype integration on MakeSee the 42 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Autype Make integration automate?

The Autype Make integration links your Autype account to Make so a scenario (the automation you build in Make, a chain of modules) can produce and rework documents for you. Each module is one brick of that chain. Autype brings 42 of them: rendering documents from data, converting Word and ODT files, and editing PDFs.

Quotes that write themselves. When a deal is marked as won in another app, Render a document from JSON turns its details into a document, and Download render output hands the finished file to the next module, ready to be emailed or stored.

One clean file per client folder. An accountant who receives scattered PDFs can chain Merge PDFs, Compress a PDF and Protect a PDF, so the client gets one light file with a password instead of five attachments.

Certificates for a whole class. A training company with a list of attendees sends it to Bulk render from JSON, follows the batch with Get bulk render status and collects everything with Download bulk render output.

Autype has no trigger module in Make: a scenario starts from another app or from a schedule, never from an event inside Autype. For anything the listed modules skip, Make an API call reaches the rest of the Autype API. Hesitating between tools? Read our n8n vs Make comparison, and if a scenario fails, Make troubleshooting lists the usual fixes. The Make training goes further on the editor itself.

Connect

How do you connect Autype to Make?

  1. 01

    Copy your API key in Autype

    You need an active Autype account. Open your workspace settings in Autype and copy the API key shown on the screen. Keep it at hand: Make asks for it in the next step, and it is the only credential this connection uses.

  2. 02

    Add an Autype module to a scenario

    In Make, open a scenario, click the +, search for Autype and pick any module. Click Create a connection. The connection is your Autype account linked to Make once, then reused by every Autype module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when several workspaces are linked. Paste the API key you copied, save, and Make can now read your Autype documents and projects in the module fields.

First scenario

Your first scenario with Autype

GoalWhen a new order lands in your sales app, Make renders its document in Autype and passes the finished file along.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Autype has no trigger, so pick the trigger of the app that holds your orders as the first module.

  2. 02

    Add Render a document from JSON

    Click the + on the right of that first module, search for Autype and choose Render a document from JSON. Create the connection with your API key if it is not done yet.

  3. 03

    Map the order data

    Fill the module fields and map the order values coming from the first module. Once connected, Make lists what it can read from your Autype account, so there is no path to type by heart.

  4. 04

    Fetch the finished file

    Add Download render output after the render module. It gives the next module a file it can attach to an email or drop into storage.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time. Open each module's bubble to read the bundles it received (a bundle is one item passed along, here one order and one file).

  6. 06

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) and turn the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Modules

What can Autype do in Make?

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

Autype1

Add a PDF watermark

ActionIn the docs only

You get a PDF stamped with a visible mark, so a draft or a confidential copy cannot be mistaken for the final version once it leaves your team.

When to use it
a contract goes out for legal review and the copy sent should clearly read as a draft.
Watch out
the watermark options appear in the module once the connection exists; read them there rather than assuming a layout.
Autype2

Bulk render from JSON

ActionIn the docs only

A whole batch of documents comes out of one request, built from JSON data you assemble in Make, instead of one render per record.

When to use it
a list of attendees or customers arrives from a spreadsheet module and each person needs a personal certificate or letter.
Watch out
Autype offers separate modules to check a batch and fetch its output, so plan Get bulk render status and Download bulk render output after this one.
Autype3

Bulk render from file

ActionIn the docs only

This one starts the same kind of batch, but the records come from a file rather than JSON you build step by step in the scenario.

When to use it
choose it over Bulk render from JSON when an earlier module already hands you a data file, which saves rebuilding every record.
Watch out
this page does not list the accepted file types; open the module in Make and read the field help before mapping.
Autype4

Compress a PDF

ActionIn the docs only

A lighter PDF is the result, easier to attach to an email or push to a portal that is picky about file size.

When to use it
right after Merge PDFs has produced a heavy bundle of scans, before the file goes to a client.
Watch out
the Make Free plan handles files up to 5 MB, so keep file size in mind whenever documents move from one module to the next.
Autype5

Convert PDF to image

ActionIn the docs only

PDF pages come back as images, useful when the next tool displays pictures but cannot show a PDF.

When to use it
a product sheet or a report needs a preview picture for a web page or a chat message.
Watch out
run the scenario with Run once on a document with several pages and look at the bundles to see exactly what the module returns before mapping it further.
Autype6

Convert a DOCX file

ActionIn the docs only

A Word file (DOCX) is converted into another format offered by Autype, so the same content reaches the recipient in the form they expect.

When to use it
a colleague drafts in Word and the version sent outside must not be edited by accident.
Watch out
the output formats are listed in the module itself; if the source comes from LibreOffice, Convert an ODT file is the right sibling.
Autype7

Convert an ODT file

ActionIn the docs only

Files written in LibreOffice or OpenOffice (ODT) get converted into another format without anyone opening an office suite.

When to use it
a public body or a school sends you ODT files and the rest of your process only handles other formats.
Watch out
for Word files use Convert a DOCX file instead; keep each source in its own scenario to stay clear.
Autype8

Create a document

ActionIn the docs only

A new document appears in your Autype workspace, which later render modules can reuse without anyone creating it by hand.

When to use it
a new client or a new offer line deserves its own document in Autype as soon as it is recorded elsewhere.
Watch out
if your workspace is organised by project, run List projects first so the new document ends up in the right place.
Autype9

Create a project

ActionIn the docs only

This action opens a new project in Autype, a clean container for the documents that belong together.

When to use it
a new client signs, and you want their quotes, contracts and reports grouped from day one without a manual setup.
Watch out
nothing stops a scenario from creating the same project twice; check with List projects before creating when the scenario may run again on the same client.
Autype10

Delete a file

ActionIn the docs only

A file stored on the Autype side is removed, which keeps your workspace from filling with outputs nobody will read again.

When to use it
at the end of a scenario, once the finished document has been sent or archived in your own storage.
Watch out
treat a deletion as final; place this module last and test it with Run once on a file you can lose.
Autype11

Delete a temporary image

ActionIn the docs only

An image you uploaded for a single render disappears from Autype once it has served its purpose.

When to use it
a logo or a signature was sent as a temporary image for one document and should not stay stored afterwards.
Watch out
map the image identifier from the upload module of the same run, not a fixed value, or the scenario deletes the wrong picture.
Autype12

Download a file

ActionIn the docs only

You retrieve a file held by Autype so the following module can attach it, store it or send it on.

When to use it
a document produced by a PDF tool module has to travel to your drive or into an email.
Watch out
for the result of a render, Download render output is the module built for that job; keep this one for other files in your account.
Autype13

Download bulk render output

ActionIn the docs only

Everything a batch render produced comes back in one step, ready for the storage or email module that follows.

When to use it
after Bulk render from JSON or Bulk render from file, once the batch is reported as finished.
Watch out
check the batch with Get bulk render status before this module, otherwise the scenario may ask for files that do not exist yet.
Autype14

Download render output

ActionIn the docs only

The finished file of a single render lands in your scenario, where you can attach it to a message or save it wherever you keep documents.

When to use it
just after Render a document from JSON or from Markdown, in the simplest document flow.
Watch out
if the render is not ready yet, add Get render job status in between and read its answer in the bundles after Run once.
Autype15

Fill a PDF form

ActionIn the docs only

An existing PDF form gets completed with your data, which spares someone from typing the same values into every copy.

When to use it
a registration or a supplier form must be filled for each new contact coming from your CRM.
Watch out
field names differ from one form to another; run Get PDF form fields first to learn which ones this PDF expects.
Autype16

Get PDF form fields

ActionIn the docs only

This module reveals the fields a PDF form contains, so you know what to fill before touching the document.

When to use it
you prepare Fill a PDF form on a form received from a partner and do not know its field names.
Watch out
it only reads; run it with Run once while building, then decide whether it needs to stay in the finished scenario.
Autype17

Get PDF metadata

ActionIn the docs only

You read the information stored inside a PDF file itself, the kind of detail that helps sort or check documents without opening them.

When to use it
before archiving incoming PDFs, the next modules can use what this one returns to decide where each file goes.
Watch out
this page does not list the returned properties; look at the bundle after Run once before mapping it further.
Autype18

Get a document

ActionIn the docs only

One Autype document is fetched with its details, so later modules can use them without a manual lookup.

When to use it
you know which document a client file refers to and want its details before rendering or updating anything.
Watch out
it needs the right document identifier; if you only know a name, List documents finds candidates first.
Autype19

Get bulk render status

ActionIn the docs only

You learn where a batch render stands, which tells the scenario whether it can collect the documents yet.

When to use it
between Bulk render from JSON and Download bulk render output, whenever the batch is large enough to take a while.
Watch out
map the batch identifier from the module that launched it; a hard-coded value will always report the same old batch.
Autype20

Get document variables

ActionIn the docs only

The variables a document expects are listed for you, the placeholders you must feed for a clean render.

When to use it
you are building the JSON for Render a persistent document and want to be sure no variable is left out.
Watch out
run it again whenever someone edits the document in Autype, because a renamed variable breaks mappings made earlier.
Autype21

Get file details

ActionIn the docs only

Here you read the details Autype keeps about one file, a quick way to check a result before handing it to another app.

When to use it
before emailing an output, you want to confirm the file matches what the recipient expects.
Watch out
the returned details are not listed on this page; read the bundle after Run once and map only what you actually see.
Autype22

Get render job status

ActionIn the docs only

For a single render, this answers the question the scenario needs before downloading: is the document ready?

When to use it
between a render module and Download render output, when the file is not always available on the first try.
Watch out
each call is one more operation on your plan; place it once, where it is really needed, rather than in several spots.
Autype23

Get tool job status

ActionIn the docs only

PDF tool jobs (merge, split, compress and the like) report their progress through this module, so you know when the result can be picked up.

When to use it
after a PDF tool module, before Download a file, if the output is not ready at once.
Watch out
it covers tool jobs, not renders; for a document render the matching module is Get render job status.
Autype24

Keep or remove PDF pages

ActionIn the docs only

A PDF comes out trimmed to the pages that matter, with the cover, the blank pages or the appendix gone.

When to use it
an insurer or a supplier sends long PDFs and your team only files the signature pages.
Watch out
check the result on a real file with Run once, since removing the wrong pages is easy when documents do not share the same layout.
Autype25

List documents

SearchIn the docs only

Your Autype documents come back as a list, each one as its own bundle for the modules that follow.

When to use it
you need to find the right template by name before a render, or build an inventory of what the workspace holds.
Watch out
a search can return zero, one or many bundles, and every later module runs once per bundle, which multiplies operations.
Autype26

List projects

SearchIn the docs only

With this search, the projects of your workspace arrive one bundle each, handy for picking the right container before creating anything.

When to use it
before Create a project, to check the client does not already have one, or before Create a document.
Watch out
an empty result is a normal answer, not an error; plan what the next module should do when nothing comes back.
Autype27

List render jobs

SearchIn the docs only

Past and current render jobs show up as a list, a way to see what Autype has been asked to produce.

When to use it
a teammate asks whether yesterday's contracts were rendered, and you want an answer from data rather than from memory.
Watch out
the list can be long; keep it for checks and reporting, not as a step in every run of a busy scenario.
Autype28

List temporary images

SearchIn the docs only

This returns the temporary images currently stored in Autype, so you can see what is left behind after your renders.

When to use it
as a cleanup scenario, followed by Delete a temporary image on the ones no document needs anymore.
Watch out
pairing this search with a delete removes every image it returns; test on a copy of the workspace first.
Autype29

List tool files

SearchIn the docs only

The files produced by the PDF tools are listed, one bundle each, so you can collect or clean them in a single pass.

When to use it
you want to archive every compressed or merged PDF in your own storage before deleting them from Autype.
Watch out
each file becomes a separate bundle; the download and delete modules after it run once per file and count as operations.
Autype30

List tool jobs

SearchIn the docs only

You see the PDF tool jobs Autype has run, useful to follow what your scenarios asked for and what came back.

When to use it
a client says a merged file never arrived, and you check whether the merge job ever happened.
Watch out
it lists jobs, not files; to reach the files themselves use List tool files or Download a file.
Autype31

Make an API call

ActionIn the docs only

Any endpoint of the Autype API becomes reachable from your scenario, with the connection you already set up, even when no ready-made module covers it.

When to use it
the ready-made modules stop just short of what you need and Autype's API documentation shows the missing request.
Watch out
you write the request yourself, so read Autype's API reference first; the rest of this page does not describe it.
Autype32

Merge PDFs

ActionIn the docs only

Several PDFs become one file, in the order you give, so the recipient opens a single document instead of a pile of attachments.

When to use it
a quote, the general terms and a product sheet must go out together as one PDF.
Watch out
when the PDFs come from several bundles, an aggregator (the Make module that groups several bundles into one) must gather them first, or the merge runs once per file.
Autype33

Protect a PDF

ActionIn the docs only

A password now guards the PDF, so only people who receive that password can open the document.

When to use it
payslips, medical records or signed contracts travel by email and must stay private.
Watch out
never send the password in the same email as the file; route it through another channel in a separate module.
Autype34

Render a document from JSON

ActionIn the docs only

Structured data turns into a finished document, the core move for quotes, invoices or certificates built from records in other apps.

When to use it
an order or a deal arrives from your sales app with every value already split into fields.
Watch out
a missing value shows up in the document; check the variables with Get document variables and test with Run once on a real record.
Autype35

Render a document from Markdown

ActionIn the docs only

Text written in Markdown (plain text with simple marks for titles and bold) becomes a formatted document without a template.

When to use it
an AI module or a notes app produces a report in Markdown and it must be sent as a proper file.
Watch out
prefer Render a document from JSON when the content is structured data rather than prose.
Autype36

Render a persistent document

ActionIn the docs only

This module renders a document already saved in your Autype workspace, filled with the data you pass it.

When to use it
your team designed a contract template once in Autype and every new client should get a copy with their own details.
Watch out
the document must exist first; Get document variables tells you which values to map before the first run.
Autype37

Replace placeholders in DOCX/ODT

ActionIn the docs only

Word or ODT files keep their layout while the placeholders inside them receive real values from your scenario.

When to use it
legal already maintains its letters in Word and does not want to rebuild them as Autype documents.
Watch out
the placeholders must be written exactly as the module expects; test on one file with Run once before running a whole list.
Autype38

Rotate PDF pages

ActionIn the docs only

Sideways or upside-down pages get turned the right way, which spares the reader from tilting their head.

When to use it
a scanner or a phone app delivers delivery notes with landscape pages in the wrong direction.
Watch out
the rotation settings are in the module; test on a sample with Run once, because a wrong setting turns the good pages too.
Autype39

Split a PDF

ActionIn the docs only

One large PDF is cut into several smaller files, each easier to file, send or process on its own.

When to use it
a batch of invoices was scanned as one PDF and each invoice has to reach its own folder.
Watch out
the output may hold several files; add an iterator (the Make module that splits a list into separate bundles) if every piece has to be handled separately.
Autype40

Unlock a PDF

ActionIn the docs only

The password protection is removed from a PDF you are allowed to open, so the next modules can read or edit it.

When to use it
a bank or a supplier sends protected statements and your scenario needs to merge or archive them.
Watch out
you still need the password; store it in the module field, not in a shared note, and unlock only files you have the right to open.
Autype41

Upload a document

ActionIn the docs only

The file an earlier module fetched from another app lands in your Autype account, ready for the Autype steps that follow.

When to use it
an attachment or an export from another app has to pass through Autype, for example before a merge or a conversion.
Watch out
on the Make Free plan, files are capped at 5 MB, so a heavy scan can stop the run; click Run once with a real file first.
Autype42

Upload a temporary image

ActionIn the docs only

An image goes into Autype as a temporary file rather than a lasting document, so a logo or a signature used for one render does not clutter your account.

When to use it
pick it over Upload a document when the image has no reason to stay once the scenario is done.
Watch out
the Autype docs give no lifetime for these images; pair it with List temporary images and Delete a temporary image to clean up yourself.
Need help

Need help automating Autype with Make?

A person reads every message.

FAQ

Autype and Make: frequent questions

01Is the Autype Make integration free?
Yes on the Make side: Autype is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and count usage in credits. Autype itself needs an active account and an API key; its subscription is described on the Autype pricing page.
02What do you need to connect Autype to Make?
Two things: an active Autype account and its API key. To get the key, open the workspace settings of your Autype account and copy the key shown on the screen. Then, in Make, add any Autype module to a scenario and click Create a connection. Naming the connection is optional, but a clear name helps if you link several workspaces. Paste the key and save. That single connection serves all 42 Autype modules, so you only do it once per workspace, and every module you add later picks it up from a list.
03Does the Autype integration react in real time?
No, because Autype has no trigger module in Make, so nothing inside Autype can start a scenario on its own. The scenario starts from something else. Either the trigger of another app, such as a new order in your shop or a new row in a spreadsheet, or a schedule set on the first module, which runs every 15 minutes by default (1 minute at the shortest on a paid plan). Autype then comes in as an action or a search further down the chain, and does its work on each bundle the first module sends.
04What if an Autype module you need is missing?
Use Make an API call. It reaches any endpoint of the Autype API with the connection you already created, so a request that no ready-made module covers stays possible, without a second login. The catch: you write that request yourself, from the Autype API documentation, and you read the answer in the bundle after Run once. Start with the 42 listed modules and only fall back on this one when they stop short. Note that the Autype docs used by Make are flagged as AI-generated and may contain mistakes, so confirm important details with Autype.
05Should you use Make or n8n for Autype?
It depends mostly on the tool your team already runs. On Make, Autype comes with 42 ready-made modules, a visual editor and a first scenario you can build from this page, plus Make an API call for the rest of the API. Apps like Autype often have an n8n node too, so check the n8n side before assuming it is missing. Then compare, on your own case, how each tool fits the apps around your documents and who will maintain the scenarios, rather than picking by reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations