# Welcome to docMaker
User guide
## Overview
Learn how you can automate your documents creation with docMaker.
## Get Started
We've put together some helpful guides for you to get setup with our product quickly and easily.
{% content-ref url="/pages/Dnscs8KyKKhTLBDDI4rB" %}
[Bubble.io](/integrations/bubble.io)
{% endcontent-ref %}
{% content-ref url="/pages/s6lbvbIwKgZIHrbQ2MIk" %}
[Easy pdf from docx template](/integrations/bubble.io/easy-pdf-from-docx-template)
{% endcontent-ref %}
{% content-ref url="/pages/XIaxSP2jdwlnng0ElqqH" %}
[Fill-out pdf forms](/integrations/bubble.io/fill-out-pdf-forms)
{% endcontent-ref %}
# Create pdf from docx template
The easiest way to generate beautiful pdfs
Create a docx template in MS Word, Libre Office or Google docs. Then use your favorite app to send data, and connect with docMaker to get fantastic pdf or docx documents!
:arrow\_forward:[ Go to the next chapter](/features/create-pdf-from-docx-template/build-your-docx-template/overview) to learn how to build your docx template.
Or click on the list below to discover our integrations for this feature:
* [Bubble.io plugin](/integrations/bubble.io/easy-pdf-from-docx-template)
* [Typeform integration](/integrations/typeform)
* [Zapier integration](/integrations/zapier)
* [API](https://elian-faggion.gitbook.io/moovsur)
# Build your docx template
In most document automation workflows, you will have to start with the creation of a docx template.
You can also copy one of those offered in your docMaker dashboard ( dashboard).
Read the next chapters to discover the syntax to be used in your docx files to enable docMaker to replace tags with dynamic data!
# Overview
### How does it work?
docMaker finds all tags **`{}`** in your document (docx) and replaces these tags by data. According to the syntax of your tags, you can make a lot of operations including
* Replacing a field
* Formatting data
* Repeating a document portion (a table row or anything else)
* Looping on unlimited nested arrays
* Conditionally displaying a data based on a test expression
The syntax is **easy to learn**. It is like using a JSON Array or Object in Javascript.
Combined with features of LibreOffice™ or MS Office™, you can easily create documents with:
* Graphics
* Headers, footers
* Automatically repeated table header across pages
* Insert computed field
* Page count
* ...
### How to read this documentation
{% hint style="info" %}
If you are using our Zapier or Typeform integrations, **you do not have to care about the JSON data information in the following documentation**. Indeed, it will be handled behind the scenes by Zapier or Typeform.
You just have to create the docx template, and then map the dynamic data with the template, either in Zapier or in docMaker dashboard for Typeform.
{% endhint %}
Each part of this documentation shows exactly what happens if you send **Data** (JSON Object) and a **Template** (handmade docx, odt, ...) to docMaker.
> Please note that you may also start with one of our pre-built templates (see the ["Templates"](https://app.docmaker.co/dashboard?menu=templates) section in your docMaker dahsboard), and adjust it using the below guidelines.
The first thing to do is to open your document editor (Libreoffice, Microsoft Word, Google docs etc.). Once you have done it, you will be able to start building your template.
> Once you have built it, we recommend that you test your template in the [“Template check”](https://app.docmaker.co/dashboard?menu=templatev) section of your docMaker dashboar, to make sure that it is valid. This will also get you all the tags from your template in a JSON format which you may use to easily build your API call.
# Text substitution
This is the most basic example. This is what your JSON data should contain :
**Data**
{% code lineNumbers="true" %}
```json
{
"firstname": "John",
"lastname": "Doe"
}
```
{% endcode %}
Template
Result
Hello {firstname} {lastname} !
➡️
Hello John Doe!
In your template, the tags between curly braces will be replaced by the data you provided
# Images
You can insert .png and .jpeg images into your document, and you can adjust images width :
* either glogally with the `“forceWidth”` parameter in the body of your JSON. Example : `"forceWidth" : 200`, will apply a 200 pixels width to all the images in your document (height will adjust automatically)
* or individually for any individual image, by sending a `“.setImageWidth”` parameter in your data (see example below)
In order to insert an image into your document, you have to send the image URL in your data
You can also set the image width (in pixels) by adding a `.setImageWidth` parameter, as shown below:
**Data**
{% code lineNumbers="true" %}
```json
{
"flower": "https://cdn.pixabay.com/photo/2019/12/15/11/22/flowers-4696878_960_720.jpg",
"flower.setImageWidth": 200
}
```
{% endcode %}
In the template, an image tag is like a substitution tag, but with an additional “%” sign:
Template
Result
{%flower}
➡️
# Conditions
Conditions enable you to control the display of parts of your template based on conditional data:
* either a boolean (true/ false)
* or the presence of the data itself
{% hint style="info" %}
We recommend that when using conditions, you should always use tags starting with if\_, like {#if\_myTag} text to be dislayed if true {/if\_myTag}. This will enable docMaker to know that you are using this tag as a conditional tag.
{% endhint %}
A condition section begins with a pound and ends with a slash. That is {#if\_person} begins a "if\_person" section while {/if\_person} ends it.
> **Example :** if you use in your template : {#if\_myTag} conditional data {/if\_myTag} => if you send {"if\_myTag" = true} the data inside the{#if\_myTag} section will be displayed.
You may also use inverted sections to display data when the condition is false :
> **Example :** in your template : {^if\_myTag} conditional data {/if\_myTag} => if you send {"if\_myTag" = false} the data inside the {^if\_myTag} section will be displayed.
Check out the examples below.
### Example 1: block not displayed
Data
{% code lineNumbers="true" %}
```json
{
"if_display" : false,
"firstname": "John",
"lastname": "Doe"
}
```
{% endcode %}
### Example 3: block not displayed based on data itself
**Data**
{% code lineNumbers="true" %}
```json
{
"firstname": null,
"lastname": "Doe"
}
```
{% endcode %}
Template
Result
{#firstname}
Hello {firstname} !
{/firstname}
Your last name is {lastname} !
➡️
Your last name is Doe!
### Example 4: inverted conditions
An inverted section begins with a caret (hat) and ends with a slash. That is {^person} begins a "person" inverted section while {/person} ends it.
**Data**
{% code lineNumbers="true" %}
```json
{
"if_display" : false,
"firstname": "John",
"lastname": "Doe"
}
```
{% endcode %}
Template
Result
{#if_display}
Hello {firstname} !
{/if_display}
{^if_display}
Inverted hello {firstname} !
{/if_display}
Your last name is {lastname} !
➡️
Inverted hello John!
Your last name is Doe!
# Loops
# Simple list
The loop should have a a JSON array strcuture, i.e. : be embedded in `[ ]` and contain key/ value pairs inside `{ }` , as shown below :
As the loop contains only one element, we can use a dot tag `{.}` to create a list.
| **Template** | | Result |
| ------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | ------------------------------------------------------ |
|
{#cars}
- {.}
{/cars}
|
➡️
|
Renault
Tesla
Toyota
|
If the data loop contained more than 1 item type, then we would have to specify which data we want to display, with this tag :`{brand}` :
| **Template** | | Result |
| ----------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | ------------------------------------------------------ |
|
{#cars}
- {brand}
{/cars}
|
➡️
|
Renault
Tesla
Toyota
|
# List with multiple values
When sending multiple values in your JSON data, you simply have to add as many tags as required in your template :
{% code lineNumbers="true" %}
```json
{
"orderLines": [
{
"item_name": "trousers",
"item_price": 100
},
{
"item_name": "shirt",
"item_price": 50
}
]
}
```
{% endcode %}
Copy
| **Template** | | Result |
| ----------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
|
{#orderLines}
- Ref. : {item\_name}, price : {item\_price}€
{/orderLines}
|
➡️
|
Ref. : trousers, price : 100€
Ref. : shirt, price : 50€
|
# Adding rows into a table
docMaker can add rows to your document's tables. It will add as many rows as you provide data in the JSON.
{% hint style="info" %}
The beauty of it, is that page numbers will increment automatically, and page breaks will be perfectly fitted !
{% endhint %}
Example data :
```plaintext
{"orderLines": [
{
"item_name": "Shirt",
"item_price": 88,
"item_quantity" : 2
},
{
"item_name": "Shoes",
"item_price": 123
"item_quantity" : 1
},
{
"item_name": "Dress",
"item_price": 345,
"item_quantity" : 4
}
]
}
```
Template
Result
➡️
# Loops in columns + lines (grids)
If you have a list of items which you want to display in multiple columns and multiple lines, you may use our columns features.
{% hint style="info" %}
The beauty of it, is that page numbers will increment automatically, and page breaks will be perfectly fitted !
{% endhint %}
Example data :
```plaintext
{"images": [
{
"title": "Shirt",
"image": "https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcTjHWwPvOYKj1hg5y1UdGQw1RbG9HpKwpOZmw&s",
"description" : "red, long sleeves"
},
{
"title": "Dress",
"image": "https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcTjHWwPvOYKj1hg5y1UdGQw1RbG9HpKwpOZmw&s",
"description" : "blue and green"
},
{
"title": "trousers",
"image": "https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcTjHWwPvOYKj1hg5y1UdGQw1RbG9HpKwpOZmw&s",
"description" : "blue jeans"
}
]
}
```
In your template, you have to add Col1, Col2, Col3 to each one of your variables, as shown below:
|
{#images}{%imageCol1}
{titleCol1}
{descriptionCol1}
|
{%imageCol2}
{titleCol2}
{descriptionCol2}
|
{%imageCol3}
{titleCol3}
{descriptionCol3}{/images}
|
| ---------------------------------------------------------------------- | ------------------------------------------------------------- | ---------------------------------------------------------------------- |
\
And in addition to that you have to provide the number of columns in the plugin JSON data, like this: "images.nbColumns" :3,\
Then just create your JSON loop as usual.\
You can see a demo on this page : \
Editor:
Template
Result
➡️
# Nested loops
docMaker lets you create nested loops, without any limit in terms of depth of the loops.
The nested loops feature is very useful when you need to group your output by categories. They can be used inside tables or also for plain text, in order to repeat multiples lines inside main paragraphs.
Below is an example of this feature in a template.
The Bubble demo can be found here : [demo](https://docxtopdfplugintest.bubbleapps.io/version-test/nested_loops?debug_mode=true) | [editor](https://bubble.io/page?type=page\&name=nested_loops\&id=docxtopdfplugintest\&tab=tabs-1)
In order to do that, you will have to create a nested loops JSON and nested loops in your template.
```plaintext
{“orders” : [
{
"name": "Order1",
"orderLines": [
{
"item_name": "trousers",
"item_quantity": 1,
"item_price": 100,
},
{
"item_name": "shirt",
"item_quantity": 50,
"item_price": 50,
},
{
"item_name": "shoes",
"item_quantity": 1,
"item_price": 1,
},
]
},
{
"name": "Order2",
"orderLines": [
{
"item_name": "socks",
"item_quantity": 1,
"item_price": 33,
}
]
}
]
}
```
Copy
Template
Result
➡️
# QR codes
### How to transform any text/ URL into QR code image with docMaker
With docMaker you can convert any text string or webpage URL into a QR code.
In order to do that, you simply need to add “.toQRCode” to your dynamic data, like this:
```plaintext
{ “myURL.toQRCode” : “https://espn.com” }
```
Copy
The trick for the QR codes feature is that in your template you have to use an image tag (starting with %) like this :
| **Template** | | Result |
| --------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
|
{%myURL}
|
➡️
| |
# Rich text & html
### Insert rich text in html format into your template
Ideal for user-generated content: enables you to add style and formatting to create your pdf.
Your docx should contain the text: `{~html}`.
* Any tag starting with `~` is used for inline HTML, such as : `{~html}` or {\~inlineComment} which will use the "inlineComment" data
* Any tag starting with `~~` is used for block HTML, such as : `{~~html}` or {\~\~styledTable} which will use the "styledTable" data
To be clear :
* The `{~inline}` tag is used when you want to replace part of a paragraph. For example you can write :
```txt
My product is {~blueText} and costs ...
```
The tag is inline, there is other text in the paragraph. In this case, you can only use inline HTML elements (`` , `` , ``, ``\\, …)
* The `{~~block}` tag is used when you want to replace a whole paragraph, and you want to insert multiple elements
```txt
{~~block}
```
The tag is block, there is no other text in the paragraph. In this case, you can only use block HTML elements (`
`, `
`, `
`, ``, `
`)
###
List of accepted html tags :
docMaker currently supports:
* ` `
* `
`
* `` tags
* `
`
* ``
* ``
* ``
* `
`, `` and `
` for ordered and unordered lists
* ``
* ``
* ``
* `` and ``
* ``
* ``
* ``
* `
`, by using Courrier font and retaining all spaces
* `style="color: #bbbbbb"` property
* `style="font-size: 30px"` property
* `style="font-family: 'Times New Roman'"` property
* `style="background-color: blue"` property (or with rgb codes)
* `style="text-decoration: underline"` property
* `style="padding-left: 30px"`
* `style="width:33%; height: 50%;"` (on td only)
* `style="text-align:justify"` (or other values)
* `style="vertical-align: bottom"` (on td)
* `style="border: none"` (on table)
* `style="break-after:page"`
* `style="break-before:page"`
* `style="white-space:pre"`
# docx\_fill\_convert API parameters
Use all of our below options to personalize your pdf creation.
**API documentation:**
**Endpoint URL:**
### List of API call parameters:
Parameter
Values enum
Decription
"templateID"
ID of the docx template uploaded in your docmaker.co dashboard.
"templateURL"
As an alternative to the templateID, you may provide the full URL of your docx template file. Has to be a public file.
"name"
Name of the result file, has to include the extension (.pdf or .docx)
"pdfEngine"
"custom", "standard"
"custom" pdf engine is faster but restricted to open source fonts (mostly google fonts) "standard" pdf engine accepts most standard fonts
"outputType"
"pdf", "docx"
Define the format of the result file: docMaker can generate either docx or pdf files
"emptyTags"
"removeTags",
"leaveTags",
"undefined",
"N/A"
"removeTags": if no data is sent to replace a specific substitution tag, then the tag will be removed "leaveTags": if no data, tag will remain in the document. Useful when creating custom templates with your app. "undefined": if no data, tags will be replaced by "undefined" "N/A": if no data, tags will be replaced by "N/A"
"showJSONinLogs"
true,
false
Boolean parameter, if set to "no", then none of your data will be stored in docMaker servers, not event in technical logs
"metadata"
Free text field, where you can store any useful data to identify a specific docMaker API call in the logs
"upload_output_file"
true,false
Boolean parameter, defining whether result files should be uploaded to docMaker S3 buckets (files are deleted after 48 hours). Should be set to "yes" for most API calls. Except for Bubble.io, for which this can be set to "yes" if you chose to upload the result file to Bubble (see Bubble plugins specific parameters).
"privateUpload"
true,false
Boolean parameter, if set to "yes", your result files will be uploaded to a private S3 bucket. You will get a presigend URL valid for 2 hours.
"webhook_url"
URL of the webhook where you want the result file to be sent.
"webhook_token"
You may provide an auth token in order to authenticate the webhook call to your server. docMaker will add it as a Beare token in the "Authorization" header of the webhook API call.
"webhook_object_id"
Free text field, which you can use to help your backend identifiy the object to which the docMaker result_file should be attached.
"webhook_object_type"
Free text field, which you can use to help your backend identifiy the table to which the docMaker result_file should be attached.
"mailTo"
List of email adresses (separated by comma) to receove the email
"senderName"
Sender's name, when using docMaker to send the created file in attachment to an email.
"replyTo"
reply to: email adress to be used when your users will reply to the message set by docMaker
"ccTo"
cc to: List of email adresses (separated by comma) to receive a copy of the email sent by docMaker
"bccTo"
bcc to: List of email adresses (separated by comma) to receive a blind copy of the email sent by docMaker
"mailSubject"
subject of the email
"mailContent"
email contents (html or text)
"attachOutput"
true, false
If true, the generated pdf will be attached ot the email
# Fill-out pdf forms
Automate cumbersome tasks like filling out official and custom pdf forms.
Start with a fillable pdf form, then send data from your favorite software.
Available through API in all of our integrations!
Click the "Next" button below to learn how to build your pdf form.
# Build your pdf form
In order to build your pdf form, or add editable fields into an existing pdf file, you may either:
* use the official Adobe pdf editing software like Acrobat DC ([official website](https://www.adobe.com/acrobat.html))
* use alternative pdf editing solutions like Sejda form builder ([website](https://www.sejda.com/pdf-forms)) or pdf filler ([website](https://www.pdffiller.com/en/functionality/create-fillable-pdf-forms-to-online-fillable-forms-online.htm))
* use free demo websites like [this one](https://developer.mescius.com/document-solutions/javascript-pdf-viewer/demos/sample/edit-pdf/purejs/)
docMaker accepts the following field types:
* simple input text fields
* multiline input text fields
* radio buttons
* checkboxes
* buttons (to be used if you want to insert images or signatures in your document)
* options lists
* dropdown inputs
# pdf\_fill API parameters
Use all of our below options to personalize your pdf creation
**API documentation:**
**Endpoint URL:**
### List of API call parameters:
Parameter
Values enum
Decription
"templateID"
ID of the docx template uploaded in your docmaker.co dashboard.
"templateURL"
As an alternative to the templateID, you may provide the full URL of your docx template file. Has to be a public file.
"name"
Name of the result file, has to include the extension (.pdf)
"fontSize"
Font size to be used to fill your pdf document
"readOnly"
true, false
Define whether the result file should remain editable (set to false) or if you want to create a non-editable file (set to true) .
"minFontSize"
In the case of multiline input, docMaker will automatically adjust the font size in order to make sure that the text data fits the box size. With the minFontSize parameter, you can define what is the minimum font size you want to accept for these fields.
"metadata"
Free text field, where you can store any useful data to identify a specific docMaker API call in the logs
"upload_output_file"
true,false
Boolean parameter, defining whether result files should be uploaded to docMaker S3 buckets (files are deleted after 48 hours). Should be set to true for most API calls. Except for Bubble.io, for which this can be set to false if you chose to upload the result file to Bubble (see Bubble plugins specific parameters).
"privateUpload"
true,false
Boolean parameter, if set to true, your result files will be uploaded to a private S3 bucket. You will get a presigend URL valid for 2 hours.
"webhook_url"
URL of the webhook where you want the result file to be sent.
"webhook_token"
You may provide an auth token in order to authenticate the webhook call to your server. docMaker will add it as a Beare token in the "Authorization" header of the webhook API call.
"webhook_object_id"
Free text field, which you can use to help your backend identifiy the object to which the docMaker result_file should be attached.
"webhook_object_type"
Free text field, which you can use to help your backend identifiy the table to which the docMaker result_file should be attached.
"mailTo"
List of email adresses (separated by comma) to receove the email
"senderName"
Sender's name, when using docMaker to send the created file in attachment to an email.
"replyTo"
reply to: email adress to be used when your users will reply to the message set by docMaker
"ccTo"
cc to: List of email adresses (separated by comma) to receive a copy of the email sent by docMaker
"bccTo"
bcc to: List of email adresses (separated by comma) to receive a blind copy of the email sent by docMaker
"mailSubject"
subject of the email
"mailContent"
email contents (html or text)
"attachOutput"
true, false
If true, the generated pdf will be attached ot the email
"data"
This field will contain all of the dynamic data to fill-out the pdf form.
# Print web page to pdf
# page\_pdf API parameters
Use all of our below options to personalize your pdf creation
**API documentation:**
**Endpoint URL:**
### List of API call parameters:
Parameter
Values enum
Decription
"url"
Required. URL of the webpage which you would like to print to pdf.
"name"
Name of the result file, has to include the extension (.pdf or .docx)
Required. Size of the pdf file which you would like to print. If you chose 'full_length' the whole webpage will be printed into 1 long pdf without page breaks.
"loadTime"
Optional. Minimum loading time which you want to set for your page before triggering the export to pdf. Useful for pages with long loading time.
"pageRanges"
Optional. Page ranges to print to pdf. Examples : 1 or 2-4 or 3-7, 8-9. Leave empty if you want to print the whole document.
"landscape"
true,
false
Required. Define your page orientation: true for landscape, false for portrait.
"metadata"
Free text field, where you can store any useful data to identify a specific docMaker API call in the logs
"upload_output_file"
true,false
Boolean parameter, defining whether result files should be uploaded to docMaker S3 buckets (files are deleted after 48 hours). Should be set to "yes" for most API calls. Except for Bubble.io, for which this can be set to "yes" if you chose to upload the result file to Bubble (see Bubble plugins specific parameters).
"privateUpload"
true,false
Boolean parameter, if set to "yes", your result files will be uploaded to a private S3 bucket. You will get a presigend URL valid for 2 hours.
"getBase64"
Optional. If "true", your output file will be sent in base64 format in the JSON response.
"marginLeft"
Optional. Size of the left margin in pixels or in centimeters.
"marginRight"
Optional. Size of the right margin in pixels or in centimeters.
"marginTop"
Optional. Size of the top margin in pixels or in centimeters.
"marginBottom"
Optional. Size of the bottom margin in pixels or in centimeters.
Optional. Browser language (locale) to be used by docMaker server when accessing your webpage for printing, according to ISO 3166-1 standard. List here: https://lingohub.com/developers/supported-locales/language-designators-with-regions
"vWidth"
Optional. Viewport width: width of the viewport to be used by docMaker when loading your page before exporting to pdf. Unit: pixels.
"vHeight"
Optional. Viewport height: height of the viewport to be used by docMaker when loading your page before exporting to pdf. Unit: pixels. Recommended height for full page printing : 600px
"showFooter"
"noFooter", "pageNumbers",
"customFooter"
Optional. Chose wether you want to displaya footer on each pdf page.
"htmlFooter"
Optional. If you have selected "customFooter" above, provide here Html footer code to be displayed on each page printed to pdf. Must include div position.
"webhook_url"
URL of the webhook where you want the result file to be sent.
"webhook_token"
You may provide an auth token in order to authenticate the webhook call to your server. docMaker will add it as a Bearer token in the "Authorization" header of the webhook API call.
"webhook_object_id"
Free text field, which you can use to help your backend identifiy the object to which the docMaker result_file should be attached.
"webhook_object_type"
Free text field, which you can use to help your backend identifiy the table to which the docMaker result_file should be attached.
# Typeform
# Create pdf or docx for each Typeform response
This article will show you how to create super easily pdf or docx files based on the responses to your Typeform questionnaires with docMaker.
**In this article you’ll learn how to:**
1. Create a new workflow
2. Customise a docx template with the form answers as variables
3. Turn on the workflow
## 1. Create a new workflow and select Typeform source
First, once you've created your account on docMaker, go into the dashboard and go ahead to the workflows section, then add a new workflow with a Typeform source.
This will add a first step to your workflow.
In this step you have to connect your Typeform account: click on the "connect Typeform" button, and provide the required information.
Now you can choose the form that you're going to use for this workflow.
### 2. Customise a docx template with the form answers as variables
When the form is connected to the workflow, go back to your workflow and add a new step, and in this step add a template. The template must be a Docx file:
\- you can either upload your template to your Google Drive and then paste the Google Drive link into docMaker (easier for online edit of the template). Make sure that your file is shared with "anyone with the link", with editor rights
\- or you can directly upload the Docx file to docMaker.
You can noiw enter a template name. docMaker is going to give a template ID to make sure that there are no duplicates in IDs.
Paste your file URL and click on save. You can see that the template has been added and a new step was added in your workflow.
Click on this new step and you can see that on the right hand side you can get all of the questions from your Typeform and the list of variables (or tags) corresponding to each question.
The tags represent the place where the response to this question is going to be used in the in the template.
You can choose in which format to insert each tag into the document.
When clicking on the "copy" button, docMaker adds curly braces, that's how we represent the variables in the document.
It's very important that you choose the format before clicking on copy because the tag will be different, as you can see with the list tag below, which consists of 3 parts :
* the opening tag
* the list itself
* the closing tag
You can use a condition type of tag. And you will see that conditions are also loops. Everything between those two tags will be visible if the client answers yes and not visible if the client answers no.
You can give a name to your output file using the variables on the right hand side.
Of course, only text, numbers and date types of variables can be used for the title
. The result file can be a PDF file or a docx file. (toggle button)
#### 3. Turn on the workflow
Eventually, you have to publish your changes, by pressing the "Publish" buttton in the top right corner.
Every time you change things in your workflow, you have to publish the changes to make sure that docMaker is up to date with all the latest settings that you have created.
Now you are all set! :tada:
Every time this form will be submitted, a pdf will automatically be generated.
Move to the result section and hit "Refresh" to see the results of your workflow.
If you click on any line, you will see the details of the request which was received by docMkaker from Typeform.
So this way you can see exactly what your users have answered in the form.
You can also open each result file individually, or zip and download all of them by clicking the download button.
Next, in your workflow you can use the result files in additional steps:
1. to send it to a Webhook URL
2. to send it as attachment in an email
We hope you will enjoy using docMaker together with Typeform!
We are always available to help you: .
# Bubble.io
Thanks to our Bubble expertise, we have created the perfect experience for Bubble developers
We offer 3 plugins to help you get the most of your docMaker subscription:
Easy pdf from docx templatesFill-out pdf formsWebpage to pdf
# Easy pdf from docx template
The easiest solution to create pdfs in Bubble.io
{% hint style="info" %}
**Useful links :**
* [Bubble plugin page](https://bubble.io/plugin/docmaker---easy-pdf-creator-1678738839292x889230646623338500)
* [Bubble forum page](https://forum.bubble.io/t/new-plugin-easy-pdf-creator/264447)
* [Demo app (run mode)](https://docmaker-plugins.bubbleapps.io/version-test/demo_docx_simple?debug_mode=true\&tab=Create%20pdf%20from%20docx%20template\&sub=Simple%20demo)
* [Demo app (editor)](https://bubble.io/page?type=page\&name=demo_docx_simple\&id=docmaker-plugins\&tab=tabs-1)
{% endhint %}
## Tutorials
Have a look at our tutorial videos to learn how to use all of docMaker's great features.
Add hyperlinks and html formated text to your documents
Coming soon
# Fill-out pdf forms
As a Guest UserAs an EditorAs an Admin
# Webpage to pdf
# Make.com
Create pdf documents in your Make scenarios
Click on the following link to access our Make modules:
{% embed url="" %}
Modules currently available:
* Create pdf from docx template with immediate response
* Create pdf from webpage URL with immediate response (i.e. polling logic included)
* Create pdf from webpage URL with webhook
# Coda
Create pdf documents in Coda
Chek-out our Coda pack and set-up your pdf documents printing within minutes
{% embed url="" %}
This pack includes 2 actions:
{% tabs %}
{% tab title="Create pdf from docx template " %}
With this action you can use the data from your Coda databases to generate docx or pdf documents automatically.
Instructions:
* how to create your docx template: [Build your docx template](/features/create-pdf-from-docx-template/build-your-docx-template)
* parameters for documents creation: [docx\_fill\_convert API parameters](/features/create-pdf-from-docx-template/docx_fill_convert-api-parameters)
* The pack also includes a formula which lets you create JSON-formatted line items, to be used when data loops are used (to add rows to a table or add pages to your document)
Full tutorial coming soon!
{% endtab %}
{% tab title="Fill out pdf form" %}
With this action you can use the data from your Coda databases to fill-out pdf forms automatically.
Insctructions:
* how to create your pdf form: [Build your pdf form](/features/fill-out-pdf-forms/build-your-pdf-form)
* parameters: [pdf\_fill API parameters](/features/fill-out-pdf-forms/pdf_fill-api-parameters)
Full tutorial coming soon!
{% endtab %}
{% endtabs %}
# Xano
Create pdf documents in Xano
Copy our snippet to easily add pdf creation features to your Xano apps:
{% embed url="" %}
docMaker official Xano snippet
{% endembed %}
The snippet contains the following API templates:
* Create pdf from docx template with immediate response (i.e. polling logic included)
* Create pdf from docx template with webhook (webhook example provided)
* Create pdf from webpage URL with immediate response (i.e. polling logic included)
* Create pdf from webpage URL with webhook (webhook example provided)
* Fill-out pdf form with immediate response (i.e. polling logic included)
* Fill-out pdf form with webhook (webhook example provided)
* Webhook example
# Zapier
# API
## Create a new user
`POST` `/users`
\
**Headers**
| Name | Value |
| ------------- | ------------------ |
| Content-Type | `application/json` |
| Authorization | `Bearer ` |
**Body**
| Name | Type | Description |
| ------ | ------ | ---------------- |
| `name` | string | Name of the user |
| `age` | number | Age of the user |
**Response**
{% tabs %}
{% tab title="200" %}
```json
{
"id": 1,
"name": "John",
"age": 30
}
```
{% endtab %}
{% tab title="400" %}
```json
{
"error": "Invalid request"
}
```
{% endtab %}
{% endtabs %}
# Bubble.io questions
Bubble FAQ
How do I properly handle docMaker errors in Bubble?
In order to handle errors in your workflows:
\- if you are using a button to trigger docMaker actions, you will have to set-up a specific workflow to catch errors on this button's workflow, using the custom event : "An element has an error running a workflow" for this button. Then display to your user the Currrent workflow error's message, and also add it to your logs table (if you have one in your app) for future reference.
\- in addition to that, if you use a webhook : when initializing the webhook you will see that there are a status code and a message in the JSON received from docMaker. Example of successful message to webhook :
```
{
"success": true,
"statusCode": 200,
"message": "file created successfully",
"result_file": "//3611f468aafc8649dcc4ec273e00346a.cdn.bubble.io/f1693992574960x341126990077366140/result4.pdf",
"filename": "result4.pdf",
"object_id": "abc",
"object_type": "type_abc"
}
```
With this you can implement an error management, by testing if "success" = false, then there is an error. In this case you can display the statusCode and message to your user, and also add them to your logs for future reference.Example of error response sent to webhook:
```
{
"success": false,
"status_code": 403,
"message": "Client error message: missing template, please provide template URL or ID",
"result_file": "error",
"filename": "error",
"object_id": "abc",
"object_type": "type_abc"
}
```
How to handle multiline inputs in Bubble?
When passing data in a JSON format with the docMaker Bubble plugin, if the data comes from a multiline input, you will have to use some formulas in order to format data properly:
1. First you have to use the "format as JSON-safe formula to your multiline input's value
2. Then you have to use a trick, which consist in replacing \n by \n, as shown in the screenshot below. It may seem odd, but it is the only solution currently for Bubble to accept line breaks inside a JSON value.
View in editor [here](https://bubble.io/page?type=page\&name=demo_docx_loops\&id=docmaker-plugins\&tab=tabs-2)
# Questions on docx templates
How to add page breaks where needed in the template ?
In order to force page breaks, use this tag : {@pagebreak}
Place it anywhere in your templtae, including in loops, and it will force the creation of a page break.
No need to change anything in the data you are sending to docMaker. Breaks are handled idrectly from the template.
How to avoid image cropping in tables
When generating a pdf based on a docx template, it may happen that images in tables could be cropped.\
Solution : you have to double the line spacing in the cell where your image tag (should look like {%image}) is located.
# Questions on pdf templates
## Coming soon