Best Ways to Extract Data from G-code or 3MF Files for Manufacturing Workflows? Body:

Platform discussions
, , ,
1

Hi all,
I’m looking for effective methods (integrations, apps, scripts, or workflows) to automatically extract key information from G-code and 3MF files—things like print settings, part name, estimated print time, or other slicer metadata. Ideally, I’d like to capture this info and make it accessible in Monday.com for better tracking and process management.

If you have any tools, automation tips, or experience linking these file types with Monday boards, I’d really appreciate your insights!

Thanks in advance,
Brandonopening new topics, first please search to check if someone else has already asked the question! Make sure to use at least 2 tags that describe your topic so that others can easily find your topic and join the conversation.

2

monday.com doesn’t natively read/parse G-code or 3MF files, so the “magic” has to happen before the data hits your board (via an external script, app, or automation tool). The good news: it’s totally doable with some preparation and setup:

1. Where the parsing happens

You basically have two realistic options:

  1. External script / small service

    • Write a small script (Node/Python) that:

      • Reads the uploaded G-code / 3MF file,

      • Extracts the fields you care about (part name, estimated print time, material, etc.),

      • Sends the result into monday via the API (create_item or change_multiple_column_values).

    • Typical pattern:

      • G-code: most slicers put metadata in comments / headers at the top of the file.

      • 3MF: you extract and read the relevant XML nodes.

  2. Integration platform (Make, Zapier, etc.)

    • Use a scenario/flow like:

      • Trigger when a new file is uploaded to a folder (e.g. cloud storage / drive),

      • Pass it through a custom code step that parses the file,

      • Push parsed values into your monday board columns.

This keeps monday as the system of record, while parsing happens elsewhere.

As there are different slicers available with different output formats and where the data is stored is unknown, I can’t provide more information :slight_smile: