Trotec Ruby®

We'd love to know what you think of Ruby®


Share your ideas about Ruby® and what features you would like to see in the future directly with the Product Team.


To report bugs please contact your local Trotec service team https://www.troteclaser.com/en/contact/technical-support

Add option to export projects via API / 2.12./ 3.0

Description:
Currently, the API allows interaction with projects but does not provide a direct way to export a project to a file (e.g., PDF, PNG, SVG). Having an export endpoint in the API would enable automated workflows without requiring manual intervention from the UI.

Use Case:
Our company specializes in personalized products (such as gifts with custom text). To streamline production, we use automation tools to prepare designs dynamically. In order to complete the process, we need the ability to export the finalized project directly from the API. This would:

  • Save time by removing manual steps.

  • Enable full end-to-end automation.

  • Reduce the risk of human error in production.

  • Guest
  • Sep 26 2025
  • In development
Ruby Version 2.11
  • Attach files
  • Guest commented
    October 07, 2025 10:49

    Yes, saving the executed job data together would be very helpful. This
    would allow me to monitor the folder and capture the data as soon as the
    job is completed ' and then easily pass it to our production system.

    Regarding the export functionality ' I noticed that there is now an option
    to export SVG files directly from the project view, but it still requires
    manual clicking and saving to the correct folder.

    Currently, our workflow is based on product templates stored on a network
    drive in TLD format. When we receive an order for a specific product, the
    person responsible for generating the design uploads the corresponding TLD
    file to Ruby via API, fills in the customer data, and manually exports the
    SVG file ' naming it with the order number.

    When the production of that order starts on laser workstation X, we load
    the ready design with the matching order number from the project database
    into Ruby. This process works reasonably well for now, although there are a
    few areas that could be improved.

    At this stage, the most important feature for us would be the ability
    to *download
    the generated project (after customer data is filled in) via API*.
    That would reduce our design generation time by up to 20%.

    Best regards,
    *Grzegorz ��migielski*
    ----------------------------------------------------------------
    *FIRMA HANDLOWA GRZEGORZ ��MIGIELSKI*
    NIP: 7842521884 , REGON: 385959508
    tel. +48 575 702 607
    e mail. kontakt.fhsmigielski@gmail.com

    pt., 26 wrz 2025 o 11:10 Trotec Laser <
    b61ef44732263c186b5eefb0-troteclaser@iad-prod1.mailer.aha.io> napisa��(a):

    >

    Attachments Open full size
  • Admin
    Product Management commented
    October 01, 2025 08:38

    Good Morning!


    Thanks a lot for your valuable inputs and feedback.

    With Ruby 2.11 we implemented the export option as you've seen.

    I am sure we will come up with more functionality around that in the future.


    Just one question as a potential future idea for implementation:

    Would it be already helpful in fist step, if after the job got executed, the job data PLUS the exported job file as PDF or SVG would be saved together?

    This might be more realistic to be implemented within comparatively short time maybe.


    BR

    Harald







    Attachments Open full size

Related ideas