Triggers and actions in the new Flow

The actions that you can use in a workflow are determined by the trigger you use to start the workflows. Actions can be set to take place when the trigger event occurs, or checked against a condition.

Triggers and actions reference

Draft order created

The draft order created trigger starts when a user in your organization or a third-party app creates a draft order.

Considerations

This trigger only applies to newly created draft orders. Draft orders that were created before the workflow using the draft order created trigger and draft orders that do not contain any line items won't cause a workflow using this trigger to start.

Workflows that use a draft order trigger don't affect orders. To affect orders, use the Order created trigger instead.

Actions

Using the draft order created trigger allows actions to be taken with the Order Graphql API object. The following actions can be used in workflows that start with the draft order created trigger.

  • Add customer tags
  • Add draft order tags
    After a draft order is converted to an order, these tags become order tags.
  • Add order line item
  • Create draft order metafield
  • Create redirect URL
  • Create shop metafield
  • Delete redirect URL
  • Remove customer tags
  • Remove draft order tags
  • Send email
  • Send HTTP request
  • Update customer note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter: {{customer.note}} The content that you want to add to the note.
  • Update draft order note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter: {{order.note}} The content that you want to add to the note.

Example

Example of a workflow that adds tags to a customer when a draft order is created

In this example workflow, a tag is added to a customer account when a draft order they're attached to is created.

Draft order deleted

The draft order deleted trigger starts when a user in your organization or a third-party app deletes a draft order.

Considerations

Workflows that use a draft order trigger don't affect orders. To affect orders, use the Order deleted trigger instead.

Actions

Using the draft order deleted trigger allows actions to be taken with the Order Graphql API object. The following actions can be used in workflows that start with the draft order deleted trigger.

  • Send email
  • Send HTTP request
  • Create redirect URL
  • Delete redirect URL

Example

Example of a workflow that sends an email when a draft order is deleted

In this example workflow, an email is sent when a draft order is deleted.

Product deleted

The product deleted trigger starts when a user in your organization or a third-party app deletes a product from the Shopify admin.

Considerations

Deleted products can't be restored, so you can't create a workflow that undoes a deletion.

Actions

Using the product deleted trigger allows actions to be taken with the Product Graphql API object. The following actions can be used in workflows that start with the product deleted trigger.

  • Send email
  • Send HTTP request
  • Create redirect URL
  • Delete redirect URL

Example

Example of a workflow that sends an email when a product is deleted

In this example workflow, an email is sent when a product is deleted.

Customer profile created

The customer profile created trigger starts when a new customer places an order in your store, or when a customer profile is manually created by a user.

Considerations

This trigger only applies to newly created customer profiles. Editing an existing customer profile won't start the customer profile created trigger.

Actions

Using the customer profile created trigger allows actions to be taken with the Customer Graphql API object. The following actions can be used in workflows that start with the customer profile created trigger.

  • Add customer metafield
  • Add customer tags
  • Add shop metafield
  • Create redirect URL
  • Delete redirect URL
  • Remove customer metafield
  • Remove customer tags
  • Remove shop metafield
  • Send email
  • Send HTTP request
  • Update customer note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter: {{customer.note}} The content that you want to add to the note.

Example

Example of a workflow that adds a customer tag when a customer profile is created

In this example workflow, a tag is added to the customer account when a customer profile is created.

Customer deleted

The customer deleted trigger starts when a user in your organization or a third-party app deletes a customer profile from the Shopify admin.

Considerations

Customer profiles with an order history can't be deleted, but they can be disabled. To create workflows that run when a customer account is disabled, refer to the customer account disabled trigger trigger.

Actions

Using the customer deleted trigger allows actions to be taken with the Customer Graphql API object. The following actions can be used in workflows that start with the customer deleted trigger.

  • Create redirect URL
  • Delete redirect URL
  • Send email
  • Send HTTP request

Examples

Example of a workflow that sends an email when a customer is deleted

In this example workflow, an email is sent when a customer is deleted.

Customer account enabled

The customer account enabled trigger starts when a customer profile becomes a customer account. This change in status occurs when a customer accepts an email invitation to create an account, or when they submit information during checkout from your online store.

Actions

Using the customer account enabled trigger allows actions to be taken with the Customer Graphql API object. The following actions can be used in workflows that start with the customer account enabled trigger.

  • Add customer metafield
  • Add customer tags
  • Add shop metafield
  • Create redirect URL
  • Delete redirect URLs
  • Remove customer metafield
  • Remove customer tags
  • Remove shop metafield
  • Send email
  • Send HTTP request
  • Update customer note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter: {{customer.note}} The content that you want to add to the note.

Example

Example of a workflow that adds a customer tag when a customer account is enabled

In this example workflow, a customer tag is added when a customer account is enabled.

Customer account disabled

The customer account disabled trigger starts when a user in your organization or a third-party app disables a customer account in the Shopify admin.

Actions

Using the customer account disabled trigger allows actions to be taken with the Customer Graphql API object. The following actions can be used in workflows that start with the customer account disabled trigger.

  • Add customer metafield
  • Add customer tags
  • Add shop metafield
  • Create redirect URL
  • Delete redirect URLs
  • Remove customer metafield
  • Remove customer tags
  • Remove shop metafield
  • Send email
  • Send HTTP request
  • Update customer note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter: {{customer.note}} The content that you want to add to the note.

Example

Example of a workflow that adds a customer tag when a customer account is disabled

In this example workflow, a customer tag is added when a customer account is disabled.

Inventory quantity changed

The inventory quantity changed trigger starts when an order is placed that deducts available inventory from a specific product.

Considerations

Products must have Track quantity checked in order to start a workflow with the inventory quantity changed trigger. Draft orders do not affect available inventory until they are converted to orders. This trigger allows the use of conditions and actions that affect products. For workflows that affect inventory items, refer to the inventory item created trigger.

Actions

Using the inventory quantity changed trigger allows actions to be taken with the Product Graphql API object. The following actions can be used in workflows that start with the inventory quantity changed trigger.

  • Add product tags
  • Add product to collection
  • Add shop metafield
  • Create product metafield
  • Create product variant metafield
  • Create redirect URL
  • Delete redirect URL
  • Hide product
  • Publish product
  • Remove product from collection
  • Remove product metafield
  • Remove product tags
  • Remove product variant metafield
  • Remove shop metafield
  • Send email
  • Send HTTP request

Examples

Example of a workflow that publishes a product when the inventory changes from under zero to above zero

In this example workflow, a product is published when the inventory quantity for a product changes from below zero to more than zero.

Product added to store

The product added to store trigger starts when a user in your organization or a third-party app adds a new product in the Shopify admin.

Considerations

This trigger only applies to new products. It does not start when a new variant is added to an existing product. For workflows that start when a new variant is added, refer to the product variant added trigger. The product added to store trigger starts when any new product is added to the Shopify admin, regardless of whether it is added to the Online Store sales channel.

Actions

Using the product added to store trigger allows actions to be taken with the Product Graphql API object. The following actions can be used in workflows that start with the inventory quantity changed trigger.

  • Add product tags
  • Add product to collection
  • Add shop metafield
  • Create product metafield
  • Create redirect URL
  • Delete redirect URLs
  • Hide product
  • Publish product
  • Remove product from collection
  • Remove product metafield
  • Remove product tags
  • Remove shop metafield
  • Send email
  • Send HTTP request

Example

Example of a workflow that adds a product to a collection when it is added to the store

In this example workflow, a product is added to a collection when it is added to the store.

Order cancelled

The order cancelled trigger starts when a user in your organization or a third-party app cancels an unfulfilled order.

Considerations

Cancelling an order stops an order in progress. It is not the same as deleting an order. For workflows that start when an order is deleted, refer to the order deleted trigger. Depending on your settings for refunds and restocking, cancelling an order might create conditions that start workflows using the refund created or inventory item created triggers. Avoid creating workflows that start several triggers simultaneously, which can cause unexpected results.

Actions

Using the order cancelled trigger allows actions to be taken with the Order Graphql API object. The following actions can be used in workflows that start with the order cancelled trigger.

  • Add customer tags
  • Add order line item
  • Add order tags
  • Add order metafield
  • Add shop metafield
  • Archive order
  • Cancel order
  • Capture payment
  • Create redirect URL
  • Delete redirect URL
  • Mark order as paid
  • Remove customer tags
  • Remove order tags
  • Remove order metafield
  • Remove shop metafield
  • Request fulfillment
  • Send email
  • Send HTTP request
  • Unarchive order
  • Update customer note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter: {{customer.note}} The content that you want to add to the note.
  • Update order note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter:{{order.note}} The content that you want to add to the note.

Example

Example of a workflow that archives an order when the order is cancelled

In this example workflow, an order is archived when when the order is cancelled.

Order created

The order created trigger starts when an order is placed by a customer, or when a draft order is marked as paid and converted to an order.

Actions

Using the order created trigger allows actions to be taken with the Order Graphql API object. The following actions can be used in workflows that start with the order created trigger.

  • Add customer tags
  • Add order line item
  • Add order tags
  • Add order metafield
  • Add shop metafield
  • Archive order
  • Cancel order
  • Capture payment
  • Create redirect URL
  • Delete redirect URL
  • Mark order as paid
  • Remove customer tags
  • Remove order tags
  • Remove order metafield
  • Remove shop metafield
  • Request fulfillment
  • Send email
  • Send HTTP request
  • Unarchive order
  • Update customer note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter: {{customer.note}} The content that you want to add to the note.
  • Update order note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter:{{order.note}} The content that you want to add to the note.

Example

Example of a workflow that updates a customer note when an order is created

In this example workflow, a customer note is updated when that customer creates a new order.

Order deleted

The order deleted trigger starts when a user in your organization or a third-party app deletes an order.

Considerations

Deleting an order removes the order from the Shopify admin. It is not the same as cancelling an order. For workflows that start when an order is cancelled, refer to the order deleted trigger.

Actions

Using the order deleted trigger allows actions to be taken with the Order Graphql API object. The following actions can be used in workflows that start with the order deleted trigger.

  • Create redirect URL
  • Delete redirect URL
  • Send email
  • Send HTTP request

Example

Example of a workflow that sends an email when an order is deleted

In this example workflow, an email is sent when an order is deleted.

Order fulfilled

The order fulfilled trigger starts when all the line items in an order are fulfilled.

Considerations

This trigger applies to both automatically fulfilled and manually fulfilled orders. Partially fulfilled orders won't start a workflow with the order fulfilled trigger.

Actions

Using the order fulfilled trigger allows actions to be taken with the Order Graphql API object. The following actions can be used in workflows that start with the order fulfilled trigger.

  • Add customer tags
  • Add order line item
  • Add order tags
  • Add order metafield
  • Add shop metafield
  • Archive order
  • Cancel order
  • Capture payment
  • Create redirect URL
  • Delete redirect URL
  • Mark order as paid
  • Remove customer tags
  • Remove order tags
  • Remove order metafield
  • Remove shop metafield
  • Request fulfillment
  • Send email
  • Send HTTP request
  • Unarchive order
  • Update customer note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter: {{customer.note}} The content that you want to add to the note.
  • Update order note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter:{{order.note}} The content that you want to add to the note.

Example

Example of a workflow that archives an order when it is fulfilled

In this example workflow, order is archived when that order is fulfilled.

Order paid

The order paid trigger starts when an order's payment status changes to paid.

An order is in paid status after a credit card payment has been captured, or when an order using a manual payment method is marked as paid.

Considerations

Partially paid or authorizing funds won't start a workflow with the order paid trigger.

Actions

Using the order paid trigger allows actions to be taken with the Order Graphql API object. The following actions can be used in workflows that start with the order paid trigger.

  • Add customer tags
  • Add order line item
  • Add order tags
  • Add order metafield
  • Add shop metafield
  • Archive order
  • Cancel order
  • Capture payment
  • Create redirect URL
  • Delete redirect URL
  • Mark order as paid
  • Remove customer tags
  • Remove order tags
  • Remove order metafield
  • Remove shop metafield
  • Request fulfillment
  • Send email
  • Send HTTP request
  • Unarchive order
  • Update customer note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter: {{customer.note}} The content that you want to add to the note.
  • Update order note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter:{{order.note}} The content that you want to add to the note.

Example

Example of a workflow that adds a tag to an order when it is paid

In this example workflow, a tag is added to an order when it is paid.

Order risk analyzed

The order risk analyzed trigger starts when an order's fraud analysis is complete.

Considerations

Fraud analysis takes some time to process, so workflows that start with the order risk analyzed will not run immediately after an order is created.

Actions

Using the order risk analyzed trigger allows actions to be taken with the Order Graphql API object. The following actions can be used in workflows that start with the order risk analyzed trigger.

  • Add customer tags
  • Add order line item
  • Add order tags
  • Add order metafield
  • Add shop metafield
  • Archive order
  • Cancel order
  • Capture payment
  • Create redirect URL
  • Delete redirect URL
  • Mark order as paid
  • Remove customer tags
  • Remove order tags
  • Remove order metafield
  • Remove shop metafield
  • Request fulfillment
  • Send email
  • Send HTTP request
  • Unarchive order
  • Update customer note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter: {{customer.note}} The content that you want to add to the note.
  • Update order note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter:{{order.note}} The content that you want to add to the note.

Example

Example of a workflow that cancels an order if the risk level is high

In this example workflow, an order is canceled if its risk level is high.

Order transaction created

The order transaction created trigger starts when a transaction on an order is created.

Actions

Using the order transaction created trigger allows actions to be taken with the Order Graphql API object. The following actions can be used in workflows that start with the order paid trigger.

  • Add customer tags
  • Add order line item
  • Add order tags
  • Add order metafield
  • Add shop metafield
  • Archive order
  • Cancel order
  • Capture payment
  • Create redirect URL
  • Delete redirect URL
  • Mark order as paid
  • Remove customer tags
  • Remove order tags
  • Remove order metafield
  • Remove shop metafield
  • Send email
  • Send HTTP request
  • Unarchive order
  • Update customer note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter: {{customer.note}} The content that you want to add to the note.
  • Update order note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter:{{order.note}} The content that you want to add to the note.

Example

Example of a workflow that sends an email when an order transaction is created

In this example workflow, an email is sent when an order transaction is created.

Refund created

The refund created trigger starts when a user in your organization or a third-party app partially or completely refunds an order.

Considerations

Returns can't be created after an order is refunded, so any actions attempting to create a return will fail. Don't use an action that creates a return in a workflow that starts with the refund created trigger.

Depending on your settings for refunds and restocking, refunding an order might create conditions that start workflows with the order cancelled or inventory item created triggers. Avoid creating workflows that start several triggers simultaneously, which can cause unexpected results.

Actions

Using the refund created trigger allows actions to be taken with the Order Graphql API object. The following actions can be used in workflows that start with the refund created trigger.

  • Add customer tags
  • Remove customer tags
  • Update customer note
  • Add order line item
  • Add order tags
  • Remove order tags
  • Update order note
  • Archive order
  • Cancel order
  • Capture payment
  • Send fulfillment request
  • Unarchive order
  • Send email
  • Create redirect URL
  • Delete redirect URL
  • Send email
  • Send HTTP request
  • Mark order as paid
  • Add order metafield
  • Add shop metafield

Example

Example of a workflow that sends an email when a refund is created

In this example workflow, an email is sent when a refund is created.

Collection deleted

The collection deleted trigger starts when a user in your organization or a third-party app deletes a collection from the Shopify admin.

Considerations

Deleted collections can't be restored, so you can't create a workflow that undoes a deletion.

Workflows that start with the collection deleted trigger apply to both manual and automatic collections.

Actions

Using the collection deleted trigger allows actions to be taken with the Collection Graphql API object. The following actions can be used in workflows that start with the collection deleted trigger.

  • Create redirect URL
  • Delete redirect URL
  • Send email
  • Send HTTP request

Example

Example of a workflow that sends an email when a collection is deleted

In this example workflow, an email is sent when a collection is deleted.

Collection created

The collection created trigger starts when a user in your organization or a third-party app creates a collection in the Shopify admin.

Considerations

Workflows that start with the collection created trigger apply to both manual and automatic collections.

Actions

Using the collection created trigger allows actions to be taken with the Collection Graphql API object. The following actions can be used in workflows that start with the collection deleted trigger.

  • Add shop metafield
  • Create collection metafield
  • Create redirect URL
  • Delete redirect URL
  • Remove collection metafield
  • Remove shop metafield
  • Send email
  • Send HTTP request

Example

Example of a workflow that sends an email when a collection is created

In this example workflow, an email is sent when a collection is created.

Product variant added

The product variant added trigger starts when a user in your organization or a third-party app adds a variant to an existing product.

Considerations

Workflows using the product variant added trigger start when a new product is added to the Shopify admin, because adding a new product creates a single default variant. This trigger affects variants created by any method, such as adding a new product, creating variants in existing products, duplicating variants, or bulk actions.

Actions

Using the product variant added trigger allows actions to be taken with the ProductVariant Graphql API object. The following actions can be used in workflows that start with the product variant added trigger.

  • Create redirect URL
  • Delete redirect URL
  • Send email
  • Send HTTP request

Example

Example of a workflow that sends an email when a product variant is added

In this example workflow, an email is sent when a product variant is added.

Product variant deleted

The product variant deleted trigger starts when a user in your organization or a third-party app deletes a variant from a product.

Considerations

Creating variants for an existing product deletes the product's single default variant, so workflows using the product variant deleted trigger will start when variants are added to a product already in the Shopify admin. This trigger affects variants deleted by any method, such as deleting a product, deleting a product's variants, or bulk actions.

Actions

Using the product variant deleted trigger allows actions to be taken with the ProductVariant Graphql API object. The following actions can be used in workflows that start with the product variant deleted trigger.

  • Create redirect URL
  • Delete redirect URL
  • Send email
  • Send HTTP request

Example

Example of a workflow that sends an email when a product variant is deleted

In this example workflow, an email is sent when a product variant is deleted.

Fulfillment created

The fulfillment created trigger starts when a new fulfillment is created.

Actions

Using the fulfillment created trigger allows actions to be taken with the Fulfillment Graphql API object. The following actions can be used in workflows that start with the fulfillment created trigger.

  • Add customer tags
  • Add order line item
  • Add order tags
  • Add order metafield
  • Add shop metafield
  • Archive order
  • Cancel order
  • Capture payment
  • Create redirect URL
  • Delete redirect URL
  • Mark order as paid
  • Remove customer tags
  • Remove order tags
  • Remove order metafield
  • Remove shop metafield
  • Request fulfillment
  • Send email
  • Send HTTP request
  • Unarchive order
  • Update customer note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter: {{customer.note}} The content that you want to add to the note.
  • Update order note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter:{{order.note}} The content that you want to add to the note.

Example

Example of a workflow that adds an order tag when a fulfillment is created

In this example workflow, an order tag is added when a fulfillment is created.

Fulfillment event created

The fulfillment event created trigger starts when changes occur in an existing order's fulfillment status.

Considerations

The fulfillment event created trigger applies to updates from third-party fulfillment services, such as picked up, in transit, or delivered. Manual fulfillment events do not start workflows with the fulfillment event created. For manual fulfillment workflows, refer to refer to the order fulfilled trigger.

Actions

Using the fulfillment event created trigger allows actions to be taken with the FulfillmentEvent Graphql API object. The following actions can be used in workflows that start with the fulfillment event created trigger.

  • Add order metafield
  • Add order line item
  • Add order tags
  • Add shop metafield
  • Archive order
  • Cancel order
  • Capture payment
  • Create redirect URL
  • Delete redirect URL
  • Mark order as paid
  • Remove order metafield
  • Remove order tags
  • Remove shop metafield
  • Request fulfillment
  • Send email
  • Send HTTP request
  • Unarchive order
  • Update draft order note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter: {{order.note}} The content that you want to add to the note.
  • Update order note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter:{{order.note}} The content that you want to add to the note.

Example

Example of a workflow that sends an email when the fulfillment status is ready for pickup

In this example workflow, an email is sent when a fulfillment is ready for pickup.

Inventory item created

The inventory item created trigger starts when an inventory item attached to a product variant is created.

Considerations

The inventory item created trigger starts whether or not inventory tracking is enabled for a specific product variant, so workflows using this trigger start whenever inventory is added, including the creation of a new variant. For workflows that affect products, refer to the inventory quantity changed trigger.

Actions

Using the inventory item created trigger allows actions to be taken with the InventoryItem Graphql API object. The following actions can be used in workflows that start with the inventory item created trigger.

  • Create redirect URL
  • Delete redirect URL
  • Send email
  • Send HTTP request

Example

Example of a workflow that sends an email when an untracked inventory item is created

In this example workflow, an email is sent when an untracked inventory item is created.

Inventory item deleted

The inventory item created trigger starts when an inventory item attached to a product variant is deleted.

Considerations

The inventory item created trigger starts whether or not inventory tracking is enabled for a specific product variant.

Actions

Using the inventory item deleted trigger allows actions to be taken with the InventoryItem Graphql API object. The following actions can be used in workflows that start with the inventory item deleted trigger.

  • Create redirect URL
  • Delete redirect URL
  • Send email
  • Send HTTP request

Example

Example of a workflow that sends an email when an inventory item is deleted

In this example workflow, an email is sent when an inventory item is deleted.

Tender transaction created

The tender transaction created trigger starts when a monetary action takes place, such as a payment or a refund.

Actions

Using the tender transaction created trigger allows actions to be taken with the TenderTransaction Graphql API object. The following actions can be used in workflows that start with the tender transaction created trigger.

  • Add order metafield
  • Add order line item
  • Add order tags
  • Add shop metafield
  • Archive order
  • Cancel order
  • Capture payment
  • Create redirect URL
  • Delete redirect URL
  • Mark order as paid
  • Remove order metafield
  • Remove order tags
  • Remove shop metafield
  • Request fulfillment
  • Send email
  • Send HTTP request
  • Unarchive order
  • Update order note
    By default, this action replaces the contents of the note. If you want to add content to the existing note, then in the Note field, enter:{{order.note}} The content that you want to add to the note.

Example

Example of a workflow that sends an email when a tender transaction of 10,000 or more is created

In this example workflow, an email is sent when a tender transaction of 10,000 or more is created.

Ordering conditions

You can create workflows that have multiple conditions, each of which can result in different actions. The order of the conditions matters. Conditions are checked from the top down and the checking stops after a condition is met.

Combining conditions and actions

You can combine conditions together to make one large condition. When conditions are combined, all conditions must be met for the whole condition to be true. If any condition is not met, then the whole condition is false. In the following example, the customer must accept marketing materials and the total price of the order must meet a certain threshold.

Example of a workflow that checks a customer's total spend amount and adds tags

Similarly, you can combine actions together so that multiple actions can run. This example uses multiple conditions to check if a customer is eligible for a loyalty program based on the total amount that they have spent in the store. In the image above, the following conditions are checked in the order in which they appear.

  1. If the total price is greater than $1000 and the customer agreed to accept marketing materials, then tag them with the Gold loyalty tag.
  2. If the total price is less than $1000 but more than $500 and the customer agreed to accept marketing materials, then tag them with the Silver loyalty tag.
  3. If the customer has spent more than $200 and the customer agreed to accept marketing materials, then tag them with the Bronze loyalty tag.

Actions that send messages

You can add an action to any workflow to send a message to yourself or to your staff.

Ready to start selling with Shopify?

Try it free