Global Action: Send to Zapier

The Send to Zapier Action in Arigato allows merchants to send data to a Zapier Zap.

Configuring the Action

This Action requires the integration be set up and configured first. See the Related Article at the bottom of the page for instructions on configuring the integration and general

Formatting the Body Payload 

Formatting the Body field in the Send to Zapier Action in Arigato can be tricky at first. The data sent to the Zap must be properly formatted JSON for Zapier to process it correctly. In Arigato, coding uses Twig code, which is similar to Shopify's Liquid code format. This can create confusing syntax as they both use curly braces. 

The following example highlights how Twig and JSON are mixed. 

{% set my_variable = "my value from the variable" %}   { "my_key": "{{ my_variable }}" }

When the above is rendered, it would evaluate to valid JSON and look like this:

{ "my_key": "my value from the variable" }

Taking this a bit further, the next example uses a variable that all stores have in all situations; the store's name.

{ "store_name": {{shop.name}} }

Taking this further still, the next example uses a special filter to prepare Twig variables as valid JSON using the  to_json filter. In this example, a JSON payload would be rendered with the customer key containing all the customer data and the last_order key containing all data for last order.

{ "customer": {{ customer | to_json }},  "last_order": {{ customer.last_order | to_json }} }

For additional Twig coding examples, refer to the Code Reference, or reach out to our Support team for more help.

Custom Actions

Using this Action in a Custom Action is supported. See documentation.