Collect your content
Start with a Google Doc, form response, database record, or AI-generated text in your workflow.
Google Docs · Forms · AI · CRMAPI online · DOCX and WordPress · built for n8n
Turn workflow content into documents and posts.
Send Markdown, HTML or structured JSON. Get back a ready-to-use Word file or native WordPress blocks—without building a document engine inside your automation.
- No credit card
- 20 operations included
- One key for every API
Live request
POST /v1/generate
{
"input_type": "markdown",
"content": "# Monthly report\n...",
"response_format": "file",
"filename": "report-august"
} 200 OKreport-august.docx
2APIs, one key
3input formats
1request, one result
24htemporary URL validity
01
A simple document pipeline
From content to DOCX in three steps.
DocxAPI handles conversion. Your workflow stays in control of where content comes from and where the document goes.
Call DocxAPI
Use the n8n HTTP Request node. Choose the input type and how you want the result returned.
One authenticated POST requestRoute the document
Upload it to Drive, attach it to an email, or pass it to the next step in your automation.
File · Base64 · Temporary URL02
Choose the right input
Three formats. Two destinations.
Use the simplest input for the document you need. The same endpoint handles all three.
Best for
AI content, reports and documentation
Headings, lists, tables, links and emphasis translate naturally into an editable Word file.
- Fastest format to generate
- Ideal for LLM output
- Easy to inspect and debug
# Performance report
## Executive summary
Organic traffic grew **24%**.
| Channel | Leads |
|---------|------:|
| Search | 1,240 |Best for
Content already rendered as HTML
Send semantic HTML from your app or automation and convert common document structures to DOCX.
- Headings and paragraphs
- Tables, lists and links
- Remote resources stay blocked
<h1>Client proposal</h1>
<p>Prepared for Acme Inc.</p>
<table>
...
</table>Best for
Documents assembled block by block
Build an explicit document structure when your workflow works with records instead of long-form text.
- Headings and paragraphs
- Lists, tables and quotes
- Explicit page breaks
{ "blocks": [
{ "type": "heading",
"text": "Invoice" },
{ "type": "table",
"rows": [...] },
{ "type": "page_break" }
]}03
One key, one balance
Two APIs for the same content.
The same Markdown, HTML or JSON reaches two destinations. Every operation draws from the same monthly allowance, whichever API you call.
Word documents
A real .docx file, returned as binary, base64 or a temporary link. Ready to upload to Drive, attach to an email or hand to a client.
Markdown → API → .docx
Gutenberg blocks
Native block markup that opens clean in the WordPress editor—each heading, list and table individually editable, instead of one frozen Classic block.
Markdown → API → blocks
04
Built for repeatable work
Documents your automations can deliver.
Use the content and tools you already have. Add DOCX as a reliable final output.
Recurring reports
Turn analytics, CRM, finance, or operational data into client-ready monthly reports.
Data → n8n → DOCX
Proposals and agreements
Combine form and CRM fields with prepared content to produce editable commercial documents.
CRM → n8n → DOCX
Human-reviewed AI output
Give generated research, briefs, and drafts a familiar format for review and collaboration.
LLM → n8n → DOCX
Internal documentation
Create meeting notes, SOPs, summaries, and handoffs from structured workflow data.
Apps → n8n → DOCX
Designed for production workflows
Small API surface.
Serious safeguards.
The conversion layer stays focused, observable, and easier to operate.
View live API health →Transactional usage
Credits are reserved and finalized atomically, including concurrent requests.
Sandboxed conversion
Pandoc runs with resource limits and without access to remote content.
Flexible delivery
Receive the binary file, Base64 data, or a signed temporary URL.
Traceable requests
Request IDs help connect an automation run to an API response.
04
Start small, scale when needed
Clear plans for every workflow stage.
Every plan uses the same generation endpoint. Upgrade for more volume and API keys.
Free
$0/ month
Explore the API and build your first workflow.
- 20 operations / month
- Both APIs included
- 1 API key
Starter
$9/ month
For lightweight, recurring automations.
- 200 operations / month
- 1 API key
- $0.05 per extra document
Most popular
Pro
$29/ month
For active teams and production workflows.
- 1,000 operations / month
- 3 API keys
- $0.03 per extra document
Agency
$59/ month
For high-volume client operations.
- 3,000 operations / month
- Unlimited API keys
- $0.02 per extra document
Questions, answered
Before your first request.
Need something else? The dashboard includes complete API documentation and examples.
What counts as one document?+
Each successful generation counts as one document, independent of input format or response type.
Can it read Google Docs directly?+
No. Use n8n's Google Docs or Drive node to read or export the content, then send it to DocxAPI through an HTTP Request node.
Does DocxAPI store my document?+
Binary and Base64 responses are returned directly. Temporary URL responses are stored only for their limited validity period.
Can I use custom fonts or templates?+
Not yet. Generated files currently use the standard document reference. Custom reference templates are planned, not part of the current API.
Your workflow already has the content.
Give it a document people can use.
Create your free API key →
20 operations included. No credit card required.