Generate PDFs with Make
Call SheetsToLabels from a Make scenario and pass the PDF to storage, email, Airtable, or printing
Use Make's HTTP module to call SheetsToLabels. A successful response is a PDF file, so it can be connected directly to an upload, email attachment, or printing step.
Import the starter blueprint
- Create a scenario and import the SheetsToLabels Make blueprint.
- Open the HTTP module and replace
custom-REPLACE_MEwith a cloud Template ID. - Replace the API key placeholder using a Make credential, keychain, or team variable appropriate for your plan. Do not leave a real key in an exported blueprint.
- Run the scenario once and confirm the HTTP response status is
200and its content type isapplication/pdf. - Add Google Drive Upload a File, Dropbox, OneDrive, S3, email, Airtable, or another file-aware module after the HTTP step.
The blueprint is intentionally a one-step starting point. Add the source trigger that matches your system rather than importing a large scenario with guessed field names.
Configure the HTTP request manually
Use these settings when building without the blueprint:
| Setting | Value |
|---|---|
| Method | POST |
| URL | https://sheetstolabels.com/api/v1/generate-pdf |
| Authorization | Bearer <stored API key> |
| Content-Type | application/json |
| X-Integration-Source | make, or the source system such as airtable |
| Parse response | No; keep the PDF as a file/binary response |
Map the output data and filename from the HTTP module to the next file module. If the destination asks for a MIME type, use application/pdf.
Idempotency and retries
Build Idempotency-Key from a source ID plus a source version, for example an Airtable record ID and its watched last-modified time. Make must reuse that same value when retrying the same generation. Do not use a random value generated separately for every retry.
- For
409 IDEMPOTENCY_REQUEST_IN_PROGRESS, wait forRetry-Afterand retry. - For
429, use theRetry-Aftervalue. - For
500or503, retry with increasing delays. - For other
4xxresponses, fix the record, template, account, or layout before retrying.
Build a batch
Use an Array Aggregator to produce the records array, then call SheetsToLabels once. A batch uses one template and one print layout. The generated PDF keeps records in array order and can include up to 250 output items and 25 pages.
Start an API trial and test the completed scenario with one record before enabling scheduling.