Quickstart: Generating your first document
Create a reusable HTML template, fill in two values, and generate a PDF saved in Inkit. This walkthrough uses Studio, a Fillable Form workflow, and Files.
Before you start
You need access to create templates and workflows and to launch workflows. Workflow creation requires an Enterprise plan. If New → Workflow is unavailable, ask your organization administrator for access, or use the API generation guide with an authorized API key.
The screenshots show the current application running locally with fictional example data.
Creating a simple HTML template
- Save the following HTML as project-summary.html. The two values inside double braces are merge fields:
project_nameandcustomer_name.
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Project summary</title>
<style>
body { font-family: Arial, sans-serif; padding: 48px; color: #14233a; }
h1 { font-size: 28px; }
p { font-size: 16px; line-height: 1.6; }
.note { margin-top: 48px; color: #526173; }
</style>
</head>
<body>
<h1>Project summary</h1>
<p>Project: {{project_name}}</p>
<p>Prepared for: {{customer_name}}</p>
<p>This sample demonstrates merging project information into a reusable document template.</p>
<p class="note">Fictional example for Inkit documentation.</p>
</body>
</html>- Open Studio. Open the menu beside New and choose Template.
- In Create New Template, choose your HTML file, set Title to Project summary, and click Continue.

- In the HTML editor, click Save to save the template.
- Click Preview. Enter
Documentation refreshforproject_nameandAcme Exampleforcustomer_name, then click Preview in the side panel. - Check that the rendered document contains those values. Close the preview and return to Studio.

Preview checks the template's output. Use the workflow below to generate a document saved in Files.
Generating a document using the Inkit web app
Create the workflow
- In Studio, open the menu beside New and choose Workflow.
- Choose Fillable Form, then click Select.
- In Workflow Details, enter Project summary workflow, leave Active enabled, and click Next.
- In Packet Builder, select Project summary, click Add to Workflow, and confirm it appears in Selected Documents. Click Next.

- In Destinations, keep the automatically included Inkit Storage destination. This example does not need an additional destination. Click Next.
- In Mapping, set File Name to Project summary and choose Personal under Location. Leave expiration disabled for this example, then click Next.
- In Forms, review the
customer_nameandproject_namefields. Leave them editable so you can enter values each time you run the workflow. Click Finish to create the workflow.

Fill out the form
- Find Project summary workflow in Studio and click Fill Out in its row.
- Enter these values:
| Field | Value |
|---|---|
customer_name | Acme Example |
project_name | Documentation refresh |
- Click Submit Form and wait for the submission to finish.

Open your generated PDF
- Open Files and select Personal, matching the location configured in the workflow.
- Find Project summary.pdf. Processing can take a moment; refresh the list if the new file is not visible yet.
- Click the file's name to open it. Check that it contains Project: Documentation refresh and Prepared for: Acme Example.
- Use the download button at the top of the viewer to download the PDF.

You now have a saved template, a reusable workflow, and a generated PDF. Use Fill Out again with different values to create another document. Each submission can create another output, so check the first result before resubmitting.
Generating a document using the Inkit API
To generate directly from the same saved template, follow Generate and download a document. Use your template ID and these merge parameters:
{
"project_name": "Documentation refresh",
"customer_name": "Acme Example"
}The current generation endpoint is POST /api/v1/generate on your Inkit deployment. The API guide covers authentication, the complete request, processing status, and downloading the result. Direct template generation does not require the Fillable Form workflow created above.
Updated 10 days ago