> For the complete documentation index, see [llms.txt](https://docs.documint.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.documint.me/introduction/use-case-library/purchase-orders.md).
# Purchase Orders
Learn how to automate purchase order generation with Documint using Airtable, HubSpot, Make, or Zapier. Connect your data and generate professional purchase order PDFs automatically.
## Connect to your datasource:
## Generating Purchase Orders with Airtable
{% stepper %}
{% step %}
### Connect your Airtable Account to Documint
To connect your Airtable account with Documint, go to **Settings > Integrations**. You'll pick the Airtable option. In OAuth accounts, you'll click `Add Account`.
A page will show up for you to grant access to your bases. Feel free to add all current and future bases, or select the ones you want to work with.
And you're all connected! Now, let's work on a Purchase Order Template :tada:
{% endstep %}
{% step %}
### Connect a Purchase Order Template to your Base
Open the template gallery and select the Purchase Order Blueprint you want to work with.
Under **Sources**, you'll see that there's a **Custom Data Source**. It's holding the fields that are currently in the template. To connect to Airtable, just click `Connect` in the Airtable option below it.
{% endstep %}
{% step %}
### Map the Fields
After connecting to Airtable, select the base and table you want to connect with Documint.
In the field selector, pick the fields that will be used in the template.
To use fields coming from a Linked Record, you can click the + to expand it and select the fields coming from it.
Click Finish setup, and the Fields mapped will show up in the Fields panel!
{% endstep %}
{% step %}
### Place the Fields in the Template
Now, with the fields mapped, you can just drag them from the Fields panel and drop them into the canvas.
{% endstep %}
{% step %}
### Format the Fields
With the fields placed, you might need to adjust the formatting of some content. It's pretty simple. Just double-click the token and the formatting options will show up.
* **Number**
For numerical fields, you can display them as currency or percentage. Feel free to specify your country's currency and the required decimal places.
* **Date**
It's possible to format the date just as you need. There are the standard formats, but you can also change it to the one you need.
* **Rich Text**
If you have rich text content, you can make it display just as it is in your database. For that, you just need to set `Markdown` as the text type in the token settings.
{% endstep %}
{% step %}
### Displaying a List of Items
If you're working with Line Items, Documint can display them dynamically. For that, you'll need to set up a loop. Just select the element you want to be repeated for each item (in this case, it will be the row). Click Edit Logic in its properties panel.
In the popup, go to the Repeat/Loop tab and select the list field. Don't forget to save.
And that's it! Now a row will be repeated for each item in that list, and the template will display the table dynamically :tada:
{% endstep %}
{% step %}
### Preview the Template with Real Data
Go to the Preview tab and select a record to preview the final document with data from your base
{% endstep %}
{% step %}
### Generate the Final Document
Now, back to the table connected with Documint, you will need to create an attachment field. This field will store the PDF generated from each record.
Now, under Sources, click `Add Formula` in the Airtable connection. Then select the `Generation Link` option.
Select the Attachment field that will store the generated PDF.
{% hint style="info" %}
**Override past attachments** will ensure the attachment field only stores the most recently generated document for that record.
{% endhint %}
Then click Generate Link and a URL will be available for you to copy. Copy it and switch back to Airtable.
In the table we have the attachment field, create a **Button** field. This button will store the URL to generate the PDF from each record in that table.
Click the button to test it out!
{% endstep %}
{% step %}
### Activate the Template
Once everything is displaying properly and all the adjustments were made, it's time to activate the template to generate unbranded documents.
And that's it! Get ready to save countless hours spent manually editing documents with variable information :tada:
{% endstep %}
{% endstepper %}
## Generating Purchase Orders with HubSpot
{% stepper %}
{% step %}
### Connect your Documint account with HubSpot
Go to **HubSpot's marketplace** and look for **Documint**. Install it, grant the required permissions, and **connect app**.
Now, you'll need to create an API key. Log in to Documint and go to **Settings > API keys**. Click `New API Key` to create a new one and name it **HubSpot**. The key will show up, and you can copy it.
Back to HubSpot, you will access the **Connected Apps**. Access Documint and go to **Settings**. In the **Authentication** section, click `Add/Edit API Key`. Paste the API key you just copied and save it.
{% endstep %}
{% step %}
### Purchase Order Template
Open the template gallery and select the Purchase Order Blueprint you want to work with.
Under **Sources**, you'll see that there's a **Custom Data Source**. It's holding the fields that are currently in the template. Delete it so you can add the HubSpot fields in the next step.
{% endstep %}
{% step %}
### Map HubSpot Fields
Once the template has been added to your gallery and the **Field schema** is cleared, launch Documint from a record in one of your standard objects. In this example, we'll use a **Deal** object.
After selecting a record, you'll see the **Documint** banner in the right-hand panel.
Launch Documint from the selected record, then select the template you want to use and open its **Properties**.
In the Properties panel, you'll see the object's **primary fields** as well as any **lists associated with the object**.
To make the setup easier, download the complete **Field schema**. This downloads a JSON file containing the fields available for the object, including fields from associated lists.
Return to your Documint template and set up the **Custom Data Source**. Upload the JSON file you downloaded in the previous step.
Once the file is uploaded, Documint will automatically map the fields defined in the schema, including fields from associated lists.
Save your changes. The fields from the schema will now appear in the **Fields** panel, ready to be added to your template.
{% endstep %}
{% step %}
### Place the Fields in the Template
Once your fields are mapped, you can start adding them to your template.
From the **Fields** panel, select the field you want to use and **drag and drop it onto the canvas**. The field will be added to your template and populated with data when the document is generated.
{% endstep %}
{% step %}
### Format the Fields
Once your fields have been added to the canvas, you may need to adjust how some values are displayed. You can easily customize a field's formatting directly from its token settings. Double-click the token on the canvas to open its formatting options.
* **Number**
For numerical fields, you can display them as currency or percentage. Feel free to specify your country's currency and the required decimal places.
* **Date**
You can customize how date values are displayed in your document. Choose from the available standard date formats, or enter a custom format to match your requirements.
* **Rich Text**
If your data source contains rich text, you can preserve its formatting when displaying it in your document. To do this, open the token settings and set the **Text Type** to `Markdown`. This allows the rich text content to be rendered with its original formatting.
{% endstep %}
{% step %}
### Preview the Template with Real Data
Once your template is ready, return to **HubSpot** and launch **Documint** from a record.
Select the **Purchase Order** template you've been working on. The **Preview** tab will open and display the template using real data from the selected record.
Review the preview carefully to make sure all fields and dynamic content are displaying as expected. If anything needs adjustment, return to the template editor, make the necessary changes, and preview the document again.
{% endstep %}
{% step %}
### Activate the Template
Once everything looks good in the preview, it's time to **activate your template**.
Activating the template removes the Documint branding from generated documents, allowing you to generate **unbranded documents** for your customers or internal use.
{% hint style="info" %}
Keep in mind that once the template is active, every document generated with it will **count toward your document quota**.
{% endhint %}
{% endstep %}
{% step %}
### Generate the Final Document
Once your template is active, return to **HubSpot** and click `Generate`.
Documint will generate the final PDF using the data from the selected record. The generated document will be added to the record's **Notes** and will also be available in its **Attachments**.
And that's it! Get ready to save countless hours spent manually editing documents with variable information :tada:
{% endstep %}
{% endstepper %}
## Generating Purchase Orders with Make.com
{% stepper %}
{% step %}
### Create a Trigger
You can create a trigger that fits your workflow and use **Documint** as an action later in your scenario.
Whether you want to generate a document when a record is created, updated, or when another event occurs, you can build the automation around your specific needs.
{% endstep %}
{% step %}
### Get a Purchase Order Template
Select one of the **Purchase Order templates** from our gallery and check whether the available fields meet your needs.
If you need to add additional fields, access the schema by clicking `Manage fields` in the Fields panel. In the **Field Editor**, click `Add field` and enter a name for each field. Then, select the appropriate **field type**.
Once you've added all the fields you need, **save the schema** and place the new fields on your template.
When everything is set up, return to **Make.com** to continue configuring your scenario.
{% endstep %}
{% step %}
### Add Documint's Module (action)
Add a new module to your scenario, search for **Documint**, and select the **Create a document** action.
You'll first need to connect your Documint account to Make.com. In the **Connection** section, click `Add`.
To create the connection:
1. In Documint, go to **Settings > API Keys**.
2. Click `New API key` and give it a name, such as **Make.com**.
3. Copy the generated API key.
4. Return to Make.com and paste the API key into the connection settings.
5. Save the connection.
Once the connection is saved, your Documint account will be synced with Make.com. The **Purchase Order** template you prepared will then be available to select from the template dropdown.
{% endstep %}
{% step %}
### Map Source Fields to Template Fields
Once you select your template, its fields will appear, ready to be mapped to your source data.
For each template field, select the corresponding source field by clicking the name that matches the field. Repeat this process for each field until all the template fields are mapped to the appropriate data.
Don't forget to save once all the fields are mapped.
{% endstep %}
{% step %}
### Add HTTP Module
After configuring the Documint module, add an **HTTP** module and select **Download a file**.
In the **URL** field, map Documint’s **File URL**. This retrieves the generated PDF and makes it available for the next steps in your scenario.
{% endstep %}
{% step %}
### Store the Documents in the Cloud
The URL provided by Documint is only available for a few hours. We recommend adding a cloud storage module to upload and store the generated PDF.
{% endstep %}
{% step %}
### Test the Scenario
Once everything is set up, save the scenario and run it once to test the workflow. Check the generated PDF to make sure the correct data is displayed, and make any necessary adjustments.
{% endstep %}
{% step %}
### Activate the Template
Is everything working properly? Time to **activate the template**!
Activating the template removes the Documint branding from generated documents, allowing you to generate **unbranded documents** for your customers or internal use.
{% endstep %}
{% endstepper %}
## Generating Purchase Orders with Zapier
{% stepper %}
{% step %}
### Create a Trigger
You can create a trigger that fits your workflow and use **Documint** as an action later in your scenario.
Whether you want to generate a document when a record is created, updated, or when another event occurs, you can build the automation around your specific needs.
{% endstep %}
{% step %}
### Get a Purchase Order Template
Select one of the **Purchase Order templates** from our gallery and check whether the available fields meet your needs.
If you need to add additional fields, access the schema by clicking `Manage fields` in the Fields panel. In the **Field Editor**, click `Add field` and enter a name for each field. Then, select the appropriate **field type**.
Once you've added all the fields you need, **save the schema** and place the new fields on your template.
When everything is set up, return to **Zapier** to continue configuring your Zap.
{% endstep %}
{% step %}
### Add Documint's Step
Add a step and look for Documint. In the Setup, select Create Document as the Action event. And then, connect your account. For that, you'll need an API key. To get an API key, let's go back to Documint.
To create the connection:
1. In Documint, go to **Settings > API Keys**.
2. Click `New API key` and give it a name, such as **Zapier**.
3. Copy the generated API key.
4. Return to Zapier and paste the API key into the connection settings.
5. Save the connection.
Once the connection is saved, your Documint account will be synced with Zapier. Click Continue to the Configure step. The **Purchase Order** template you prepared will then be available to select from the template dropdown.
{% endstep %}
{% step %}
### Map Source Fields to Template Fields
Once you select your template, click the `Template Fields` dropdown and the fields will appear, ready to be mapped to your source data.
For each template field, select the corresponding source field by clicking the name that matches the field. Repeat this process for each field until all the template fields are mapped to the appropriate data.
Continue once all the fields are mapped and test the Documint step.
{% endstep %}
{% step %}
### Store the Documents in the Cloud
The URL provided by Documint is only available for a few hours. We recommend adding a cloud storage step to upload and store the generated PDF.
{% endstep %}
{% step %}
### Test the Zap
Once everything is set up, publish the Zap and Test run to test the workflow. Check the generated PDF to make sure the correct data is displayed, and make any necessary adjustments.
{% endstep %}
{% step %}
### Activate the template
Is everything working properly? Time to **activate the template**!
Activating the template removes the Documint branding from generated documents, allowing you to generate **unbranded documents** for your customers or internal use.
{% endstep %}
{% endstepper %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.documint.me/introduction/use-case-library/purchase-orders.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media&token=c20ebe7d-4789-42f3-863a-33a5f008ad16)
.png?alt=media&token=954ca19f-067e-4469-bc87-174c1e9d9974)
