React Flow Triggers & Actions

In this article:
React Flow triggers
React Flow actions

Depending on the selected trigger the conditions and actions are different. There are different groups of all the components that are related to different elements of your store.

Such elements are:
Collection
Customer
Fulfillment
Order
Product
Transaction
React Flow triggers
Collection triggers
· Collection created
· Collection deleted
Customer triggers
· Customer created
· Customer deleted
· Customer account enabled
This trigger starts a workflow after the customer has configured and activated his account, which means enabled it.
· Customer account disabled
This trigger starts the workflow when customer’s account was deactivated by the store admin.
Fulfillment triggers
· Fulfillment created
This trigger starts a workflow when the fulfillment has been created, i.e., all the items in the order have been sent to the customer.
· Fulfillment event created
This trigger starts a workflow when one of the fulfillment events has been created, as in one order there can be more than one fulfillment.
Order triggers
· Order cancelled
This trigger starts a workflow when an order is canceled and cannot be completed.
· Order created
· Order deleted
· Order fulfilled
This trigger starts a workflow when the order has been completely finished, i.e., the order products have been delivered to customer.
· Order paid
This trigger will launch a workflow when an order is paid by customer.
· Draft order created
This trigger starts a workflow when a draft order, i.e., an order manually created by a store owner for the customer, was created.
· Draft order deleted
· Order transaction created
This trigger starts a workflow when the transaction operation has been created, i.e., money for the order have been transferred by the customer to the merchant.
Product triggers
· Product added to store
· Product deleted
· Inventory item created
This trigger starts a workflow when a new item was created in your store. The inventory item contains the information about the product’s availability in the stock (if it can shipped), and about its tracking.
· Inventory item deleted
· Inventory quantity changed
This workflow starts if the inventory quantity changes when there is an order created or canceled in your store
Transaction triggers
· Refund created
This trigger starts the workflow when the refund of items or transactions in an order was created, i.e. the merchant has requested the refund of customer’s money from the payment app.

React Flow actions
Shopify actions
Collection actions
· Add collection metafield
This action tags the collection that triggered the workflow with new metadata such as the key and value, chosen by you, and by this it marks this collection.
· Remove collection metafield
· Add shop metafield
This action tags the particular shop that triggered the workflow with new metadata (the key and value) chosen by you.
· Remove shop metafield
· Create redirect URL
This action creates a URL address that will send (redirect) visitors of your store to another store page with a similar product, in case if the product he is looking for is out of stock.
· Delete redirect URLs
Customer actions
· Add customer metafield
This actions tags the new metadata to customer (the key and value chosen by you).
· Remove customer metafield
· Add customer tags
This action helps you quickly find customers in your store by marking them with special tags (e.g., if you need to find the the customers who triggered this workflow you’ll click on the tag and they will be sorted).
· Remove customer tags
· Update customer note
Use this action when you need to replace a particular note made for a particular customer (for example, you need to track some customer information and you make a note for this).
Order actions
· Add order metafield
This action tags the order that triggered a particular workflow with the new custom metadata (these are key and value) chosen by you.
· Remove order metafield
· Add order tags
This action adds your own tags to the order that triggered the workflow (e.g., you want to mark particular order to quickly find it among all).
· Remove order tags
· Archive order
This action allows you to hide the fulfilled order from the list of activated ones by moving it to the archive. It will keep all your completed orders in one place.
· Unarchive order
This action lets you return an archived order back to the list of open.
· Cancel order
This action cancels the created order. In the field on the right, you can set the necessary reason for the cancellation (e.g., if the order is fraudulent, order items are unavailable, payment has been declined, the customer has changed or canceled the order), and there are four actions to tick:

refund items- this action creates a refund that covers all the product and duty charges the customer had spent on the order and return money back to the customer.
refund shipping - this action creates a refund of the shipping charges the customer had paid.
restock items - the ordered quantity of items will be returned to your store after the cancellation of the order.
send a notification to the customer - this action notifies customer of the cancellation of the order.

· Capture payment
This action does the payment operation, i.e., capture it from the payment app. The payment process is composed of two parts - the process of an authorized payment and a capture itself. When making a payment customer needs to authorize it first, and, after the authorization is complete, a merchant can send a capture request to receive it from the app.
· Mark order as paid
This action marks an order when it meets the workflow criteria as paid.
· Update order note
Using this action you can change the note for the order that has triggered the workflow.
Product actions
· Add product metafield
This action adds a new metadata to a product that has triggered the workflow (that matches the key and value set by you).
· Remove product metafield
· Add product tags
This action allows you to add particular tags to the product that triggered the workflow to help you quickly find such product among all.
· Remove product tags
· Add product to collection
This action adds the product that triggered the workflow to the selected collection.
· Remove product from collection
This action removes a particular product from collection.
· Add shop metafield
· Remove shop metafield
· Create redirect URL
· Delete redirect URLs
· Hide product
Use this action if you want to make a particular product unavailable in your store.
· Publish product
This action allows you to make a particular product available in your store.
Fulfillment actions
· Add customer tags
· Add order metafield
· Add order tags
· Add shop metafield
· Archive order
· Unarchive order
· Cancel order
· Capture payment
· Create redirect URL
· Delete redirect URLs
· Mark order as paid
· Remove customer tags
· Send fulfillment request
This action sends a request for the fulfillment of any items that support the fulfillment requests. Such requests are sent to the selected services. This action excludes the Fulfillment by Amazon.
· Update customer note
· Update order note
External actions
External actions are aimed at interacting with customers outside of your store and connecting other apps to request some additional data. For example, notify customers about the new products or some store updates via email, or connect to the third-party apps to send messages.

You can send these messages to customers or your staff (or yourself). For this, use the following actions:

· Send email - the action that sends an email to a defined email address. You can write it right there in the email field - add an email address, its subject, and compose the message.

· Send HTTP request - this action requests a connection to other external apps, devices, data, etc. To create an HTTP request you need to select an appropriate HTTP method, add a URL, set headers, and write the request message in the “body” field.

An HTTP method determines the desired action to perform in the resource. There are seven possible methods that have different aims :
Post - a method that creates resources, or replaces them with the new ones on the server.
Get - is used to retrieve the necessary data from a server via special request.
Put - an HTTP method that updates a resource on the server.
Head - requests the response from the server without its body (response headers).
Delete - this method removes the specified resource from the server.
Patch - a method used to partially update a resource on the server.
Options - the last method that is used to describe the parameters of the connection to the target resource.

Suggestion articles

Components of the workflow
Most popular flows
Was this article helpful?
Cancel
Thank you!