Shopify Export to Structured Excel File

I am currently trying to build a scenario that starts with a Shopify export and ends with a printed, organized Excel sheet.

I’m relatively at the beginning, but I need help with the attachment.

I will explain the scenario I have in mind, what I’ve tried so far, and where I’m stuck. Hopefully, someone has some great tips!

The scenario so far:

  • The Shopify export is triggered, and I receive an email in Outlook with a CSV file.
  • I set up a rule to automatically forward this email to my Mailhook, which starts the scenario.
  • The Mailhook receives an email with an attachment, and the data arrives in binary format.

I tried using the ParseCSV module with a toString function, but my results look like this:

At this point, I don’t know what to do next.

What should my next steps be? I would highly appreciate any help!

Thanks,
Carlo

Each row is already in a separate bundle. What do you do when you need to combine all the bundles?

Combining Bundles Using Aggregators

Every result (item/record) from trigger/iterator/list/search/match modules will output a bundle. This can result in multiple bundles, which then trigger multiple operations in future modules (one operation per bundle). To “combine” multiple bundles into a single variable, you’ll need to use an aggregator of some sort.

Aggregators are modules that accumulate multiple bundles into one single bundle. An example of a commonly-used aggregator module is the Array aggregator module. The next popular aggregator is the Text Aggregator which is very flexible and can apply to many use-cases like building of JSON, CSV, HTML.

You can find out more about the other types of aggregator modules here:

Mapping a Specific Structure Into a Complex Field

The Array Aggregator module is very powerful because it allows you to build a complex array of collections for a later module’s field to map multiple items (collections) to it.

This is done using the “Target structure type” field in an Array Aggregator module.

Here is an example:

As you can see, the “Map” toggle on complex fields are used when you have an array. You can easily build an array variable to map to a future module’s field, by using an Array Aggregator module and select the “Target Structure Type” as the future module’s field you have mapped the array into.

Example

Here is an example of how your scenario could look:

This is just an example. Your final solution may or may not look like this depending on your requirements.

Hope this helps! Let me know if there are any further questions or issues.

@samliew

P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.

Another Example

An alternative is you could just upload directly to Google Drive, and have it convert it to a spreadsheet for you.

You’ll need a minimum of two modules:

The trick is to do this:

This is just an example. Your final solution may or may not look like this depending on your requirements.

Hope this helps! Let me know if there are any further questions or issues.

@samliew

P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.

Hey Samliew, thanks for the answer.

My results look promising, but I had to use some regex, so I created three match pattern modules.

However, I can’t save two of those three in my array aggregator. Is this a bug, or am I doing something wrong?

You need to use capturing groups, because the default output of the Text Parser has all the same variable name “value”.