Product and API guide

Make and Zapier integrations

Before you connect

You need a PDFgine customer account, a template in that workspace, available page quota and a Make or Zapier account. Create your template first and note its Template Code.

The Make app is under catalog review. The Zapier integration is private. Contact PDFgine for access; neither integration is publicly listed yet.

Request integration access

Connect your workspace

Create a dedicated API key in your PDFgine account with usage:read and documents:render. Use the hosted API URL below. Add templates:read only if you use the optional Brand Kit selector for previews.

https://api.pdfgine.com · usage:read · documents:render

The connector's Locale selector currently offers English and Turkish. The website language does not change document data or the connector's available fields.

Set up a Make scenario

  1. Accept the private app access provided by PDFgine. Add a PDFgine module to your scenario and create a connection with your API URL and dedicated API key.
  2. Choose Create a Document, set Template Code and Format, then map the previous module's values into the Template Data JSON object. Use Queue a Document for asynchronous work or Create a Public Preview for a recipient-facing link.
  3. Run once with sample data and inspect the module result and generated document. Enable scheduling only after the mapping is correct. Make an API call supports authorized relative API paths; the connection's scopes still apply.

Set up a Zap

  1. Accept PDFgine's private integration invitation in your Zapier account. Choose your trigger, add a PDFgine action and connect using your API URL and dedicated API key.
  2. For Create Document, set Template Code and Format, then map trigger data into Template Data as valid JSON. Queue Document and Create Public Preview are separate actions. Brand Kits is an optional dropdown source, not a trigger.
  3. Test the action, publish the Zap and send a new trigger event. Confirm a successful run in Zap History and inspect that event's document; an editor Test Step alone does not prove the live workflow ran.

Map real values, keep JSON valid

Template Data must be a JSON object matching your template's fields, not a file path or an empty placeholder. The example below is for a quote template. Map names and amounts from your trigger, keep numeric values as numbers and verify any calculated totals before sending.

JSON 
{
  "document": { "title": "DEMO ONLY" },
  "referenceNo": "DEMO-001",
  "issueDate": "2026-10-27",
  "currency": "USD",
  "customer": "Demo Customer",
  "quoteItems": [
    { "name": "Demo service", "quantity": 2, "unitPrice": 50, "total": 100 }
  ],
  "subtotal": 100,
  "vatAmount": 20,
  "grandTotal": 120
}

Choose the right output

Create Document returns a protected downloadUrl that requires API authentication. For a customer-facing browser link, use Create Public Preview and choose an allowed access duration. Queue Document returns a job statusUrl; a queued response is not a completed document.

Queued rendering · Preview links

Test before switching on

Use synthetic customer data first. Check the recipient, reference, line items, totals and output format. After enabling the workflow, send one new event and verify the platform's execution history. Avoid repeated production runs: generated pages consume your PDFgine quota.

Limits and troubleshooting

For 401 or 403, check the connection and API scopes. For 402, check available quota. For 429, respect Retry-After and reduce request frequency. Fix invalid JSON or template data before retrying. Preview duration and generation limits depend on your plan.

Errors · Read your quota

Keep connection keys private

Enter your API key only in the platform's connection settings. Do not put it in Template Data, screenshots or shared execution logs. Use a separate key for each connection and revoke it in PDFgine if access is no longer needed.

Need document events? See the API webhook guide. Webhooks