Add Autype to Make.com
Click here to add the Autype app to your Make.com account
Variable syntax: Make.com uses
{{...}} for its own template variables, which conflicts with Autype’s default variable syntax. When building Make.com scenarios, use the alternative ${varName} syntax for Autype variable placeholders instead. The API automatically converts ${...} to {{...}} internally. This applies to all API input — document JSON, Markdown content, and bulk render items.Overview
The Autype Make.com integration lets you generate documents, render PDFs, and manage content directly from Make.com scenarios — no code required. Connect Autype to thousands of apps and automate your document workflows.Prerequisites
- An Autype account with an API key (Dashboard → Settings → API Keys)
- A Make.com account
What you can do
With the Autype integration for Make.com, you can:- Render documents from JSON or Extended Markdown to PDF, DOCX, or ODT
- Bulk render documents with variable data from spreadsheets, CRMs, or databases
- Manage projects and documents — create, list, and retrieve documents
- Upload images for use in documents
- PDF tools — merge, split, rotate, watermark, compress, and more
Using variables in Make.com
Since Make.com reserves the{{...}} syntax for its own data mapping, Autype accepts ${...} as an alternative on all API inputs.
Example: Document JSON in Make.com
Instead of:${...} to {{...}} before processing.
Example: Markdown content in Make.com
Mixing Make.com variables and Autype variables
You can freely combine Make.com’s data mapping with Autype’s${...} variable placeholders:
{{1.companyName}}is a Make.com expression that maps data from a previous module${companyName}is an Autype variable placeholder that gets substituted during rendering
The
${...} syntax is only for input. If you retrieve document content from the API (e.g., via the Get Document module), variable placeholders will always be returned as {{...}}.Built-in variables
The following Autype variables are always available and work with both syntaxes:Getting started
1
Create an API key
Go to the Autype Dashboard and navigate to Settings → API Keys. Create a new key — it will start with
ak_....2
Add the Autype app in Make.com
Open the Autype app invitation link to add Autype to your Make.com account. Then, in your scenario, click + to add a module and search for Autype.
3
Connect your account
When prompted, paste your API key. The connection is verified automatically.
4
Build your scenario
Choose a module (e.g. Render Document from JSON) and configure it. Run the scenario to generate your first document.
Available modules
The Autype integration provides 41 modules across 9 groups. Each module is an action that you can add to your Make.com scenario.Rendering
Bulk Rendering
Documents
Projects
Images
PDF Tools — Files
PDF Tools
Document Tools
Tool Jobs
How tool modules work
Most PDF and document tool modules follow the same pattern:- Submit — The module sends a request to the API and receives a job ID
- Poll — The module automatically polls for job completion (every 2 seconds, up to 5 minutes)
- Return — Once completed, the module returns the job ID, status, output file ID, and metadata
Common workflow patterns
Generate a PDF from dynamic data
- Use a trigger module (e.g. Google Sheets, Airtable, or a webhook) to get your data
- Add Render Document from JSON and build your document JSON with Make.com data mapping
- Use HTTP — Get a file to download the rendered PDF from the returned
downloadUrl
Bulk generate personalized documents
- Add Bulk Render from JSON with a document ID and an array of variable sets
- The module waits for all documents to be generated
- Use Download Bulk Render Output to get a ZIP file with all documents
Process an existing PDF
- Use HTTP — Get a file to download a PDF from any source
- Add Upload a Document to upload it as a tool file
- Apply any tool action (e.g. Add PDF Watermark, Compress PDF, Merge PDFs)
- Use Download a File with the
outputFileIdto get the processed result
