Skip to main content

Extract Worksheets from Excel in Make

Extract Worksheets from Excel is a Make module that converts entire Excel worksheets to structured JSON within your scenarios, automatically using the first row as column headers. Use it when you need to export multi-sheet workbook data to APIs, databases, or cloud storage without manual copying. The module accepts an Excel file and optional worksheet selectors, and returns a JSON dictionary keyed by worksheet name for immediate downstream routing.

What this module does
PDF4me Extract Worksheets from Excel reads an Excel workbook inside your Make scenario and returns every requested worksheet as structured JSON, with the first row automatically promoted to column headers. Select worksheets by name, by 1-based index, or leave both fields blank to extract the entire workbook. The output is a dictionary keyed by worksheet name, making it straightforward to route each sheet to a separate API endpoint, database table, or storage location.
First row becomes column headers automatically

The module treats the first row of every selected worksheet as column header names in the JSON output. If your worksheet does not have a dedicated header row, the first data row will be used as keys. Restructure the source file before mapping if this would cause issues downstream.

Worksheet Names matching is case-sensitive

When specifying worksheets by name, the match is exact and case-sensitive. Summary and summary are treated as different sheets. If no match is found for a given name, that sheet is silently skipped. Always verify tab names match exactly by opening the workbook first.

Output document is Base64-encoded JSON: decode before routing

The document output field contains the worksheet dictionary serialized as JSON and then Base64-encoded. Add a Make Tools → Base64 Decode module after this one, then a JSON → Parse JSON module to access individual worksheet arrays by their key names before routing to APIs or databases.

Related Blog Posts
No blog post yet for this feature — coming soon.
In the meantime, browse the PDF4me blog for tutorials and workflows across every platform.
Visit the blog

Authenticating Your API Request

To access the PDF4me Web API through Make, every request must include proper authentication credentials. Authentication ensures secure communication and validates your identity as an authorized user, enabling seamless integration between your Make scenarios and PDF4me's powerful Excel worksheet extraction services.

Make PDF4me Extract Worksheets from Excel module showing Connection, File Name, Document binary mapped from prior step, Worksheet Names field set to Summary,Sales, and Worksheet Indexes field left empty to select by name

Map File Name and Document from the prior download step. Enter worksheet names or indexes to select specific sheets, or leave both blank to extract the entire workbook.

What is Extract Worksheets from Excel in Make?

Extract Worksheets from Excel is PDF4me's Make module for converting Excel workbook data to structured JSON without writing any code. It accepts an Excel binary, optional worksheet selectors, and returns a dictionary where each key is a worksheet name and each value is an array of row objects. Unlike a plain CSV export, this module handles multi-sheet workbooks in a single operation, preserving sheet names as routing keys for downstream API or database distribution.

How do I configure Extract Worksheets from Excel in Make?

ParameterRequiredWhat it doesExample
ConnectionRequiredPDF4me API connection. Click Add and paste your API key the first time.My PDF4me connection
File NameRequiredFilename of the Excel workbook including the .xlsx or .xls extension. Used for processing and output identification.report.xlsx
DocumentRequiredBinary content of the Excel workbook. Map from a prior Google Drive download, Dropbox get file, or HTTP response module.1. Data
Worksheet NamesConditionalComma-separated list of worksheet names to extract. Exact case-sensitive matching is required. Leave empty with Worksheet Indexes also empty to extract all worksheets. Example: 'Summary,Sales,Expenses' extracts three sheets.Summary,Sales
Worksheet IndexesConditionalComma-separated list of 1-based worksheet indexes to extract. Index 1 = first worksheet. Combined with Worksheet Names via union when both are provided. Leave empty to use names only or extract all.1,3

Output

The module returns the full worksheet dictionary encoded as JSON.

FieldTypeWhat it contains
documentBase64JSON byte array of the full worksheet dictionary, serialized and Base64-encoded. Decode with Tools → Base64 Decode, then parse with JSON → Parse JSON to access each worksheet array by name.
FileNameStringOutput filename for the JSON result, typically report.txt. Use as the filename when saving to cloud storage.
SuccessBooleanTrue if extraction completed without errors. Check this field in a Make filter before routing output to avoid processing failed responses.

When should I use Extract Worksheets from Excel in Make?

The PDF4me Extract Worksheets from Excel module in Make is ideal for multi-sheet data integration scenarios where each worksheet feeds a different system:

Automated Multi-Worksheet API Distribution Workflow

Distribute different worksheets to different API endpoints automatically:

Complete Scenario Steps:

  1. Trigger: Daily data export scheduled at midnight
  2. Get Multi-Sheet Report: Retrieve consolidated report from Google Drive
  3. Extract All Worksheets: Leave worksheet selectors empty to extract all
  4. Base64 Decode: Decode the document output to get raw JSON
  5. Parse JSON: Parse the JSON dictionary to access worksheet keys
  6. Process Summary Sheet: Extract "Summary" key data and POST to dashboard API
  7. Process Sales Sheet: Extract "Sales" key data and POST to sales analytics API
  8. Process Expenses Sheet: Extract "Expenses" key data and POST to finance API
  9. Email Summary: Send distribution summary to integration team
  10. Archive Source: Store processed Excel in archive for audit trail

Business Benefits:

  • Distributes 3+ worksheets to separate APIs daily
  • Automatic routing eliminates manual worksheet copying
  • Each system receives only relevant worksheet data
  • Reduces data distribution time from 2 hours to 5 minutes

Common Questions

What file types does Extract Worksheets support?

The module supports .xlsx and .xls Excel files. The workbook must contain at least one worksheet with data. Non-Excel formats such as CSV or ODS are not supported. Convert them to Excel before using this module. For the Make binary data handling reference, see the Make documentation on data structures.

Why are some worksheets missing from the output?

Worksheet name matching is exact and case-sensitive. If a name in Worksheet Names does not exactly match a tab name in the workbook, that sheet is silently skipped. Verify tab names by opening the source file. Alternatively, leave both Worksheet Names and Worksheet Indexes empty to extract all worksheets and check which keys appear in the output dictionary.

How much does Extract Worksheets cost in credits?

Extract Worksheets uses PDF4me credits per document processed. Free-tier accounts include a daily credit allowance; paid plans increase the limit. Check the current credit allocations for all plans on the PDF4me pricing page.

Can I extract worksheets from multiple Excel files in one scenario?

Yes. Use a Make Iterator to loop through a list of Excel files and call the Extract Worksheets module once per file. Each iteration returns an independent JSON dictionary for that workbook. This is the recommended approach for batch workbook processing in a single scenario run.

Industry Use Cases & Applications

  • Multi-API Feeds: Extract different worksheets to different system APIs automatically
  • Data Warehouse Loading: Load multi-sheet financial workbooks to data warehouse tables
  • System Migration: Extract complete Excel workbooks to JSON for migration to cloud systems
  • Data Backup: Archive multi-sheet operational workbooks as JSON for disaster recovery
  • ETL Pipeline: Extract worksheets as intermediate format in multi-step transformation pipelines

Get Help