Raw Message Contents Reference for Shopify Connector

In general, Raw Message Content settings are used by workflow triggers to define how to process data fetched from a system. This converts data from one format (such as csv or json) into Saltbox Message format (XML) so it can be processed by the workflow.

Refer to the instructions below for examples with walkthroughs.

Shopify Connector triggers utilize the following message formats:

Message Format Description Version
Shopify Converter - Convert & Split Handle Shopify’s message format (convert JSON to XML). Split this message as defined by advanced settings. 1.7+
Shopify Converter - Convert Only Handle Shopify’s message format (convert JSON to XML). 2.0+
Shopify Converter Handle Shopify’s message format (convert JSON to XML). Note that this message format is only supported in versions 1.0 through 1.7. 1.0 to 1.7

Message Formats

Shopify Converter - Convert & Split

Message Format Description Version
Shopify Converter - Convert & Split Handle Shopify’s message format (convert JSON to XML). Split this message as defined by advanced settings. 1.7+

Shopify Converter - Convert Only

Message Format Description Version
Shopify Converter - Convert Only Handle Shopify’s message format (convert JSON to XML). 2.0+

Shopify Converter

Message Format Description Version
Shopify Converter Handle Shopify’s message format (convert JSON to XML). Note that this message format is only supported in versions 1.0 through 1.7. 1.0 to 1.7

How to find an XPath in Trigger source data

When a single source message contains multiple data points that need to be processed (for example, an order may be split into multiple lines, or a customer may be split into multiple contacts), they may be split using advanced Raw Message Contents settings. To find the desired “XPath to contained messages”, use the process outlined below to generate the trigger data source and inspect it.

  1. Open a workflow whose trigger is already configured. To set up a new workflow trigger, watch our 2-minute video tutorial: Workflow Trigger Setup.

  2. Open Workflow Designer.

  3. Add the “Assert” workflow action from the Core Connector. Place this as the first action in the workflow.

  4. Configure the Assert action to fail. The goal is to force the workflow to fail so that we generate the data but don’t process it yet. This can be re-processed at a later time on the Messages page using the “retry” option.

    To configure the Assert action to fail:

    • Edit the action.

    • Assign the following values. This will force the workflow to fail at the beginning, which will allow a user to save/inspect the data generated by the trigger.

    • Click away from the settings.

    • Press the Save button.

    • Run the workflow to generate a message. This will fail (on purpose).

    • After running the workflow:

      • Drill into the failed message trace.

      • Expand the status bar at the top.

      • Click on the link to open the Trigger Message XML. From here, you may press the Save button to save a copy to the samples folder for future reference.

      • Search the XML for the desired data. Build the path to this data by inspecting each parent node containing the data. For example: /BOM/BO/Document_Lines/row/ points to the SAP Business One document’s lines array.

        This XPath can be used to split messages by pasting it into the XPath to contained messages field.