> For the complete documentation index, see [llms.txt](https://docs.yedric.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yedric.ai/shopify/capabilities/shopify-flow.md).

# Shopify Flow

Use the Yedric triggers and actions in Shopify Flow to start workflows from conversations, send replies, tag chats and flag unanswerable questions.

Yedric adds triggers and actions to [Shopify Flow](https://apps.shopify.com/flow), so you can start a workflow when a conversation ends, a shopper needs a person, a shopper asks about a return, or Yedric finds a question your store cannot answer. Flow can also send a reply or tag a conversation. They work on every plan.

No message text ever reaches Flow: triggers carry Yedric's summary, sentiment, tags and links, never what the shopper wrote.

***

## Getting started

1. Install Shopify Flow if you have not already. The **Shopify Flow** card under **Capabilities > Better with friends** has **Open Flow**, and shows how many of your workflows use Yedric.
2. In Flow, create a workflow and choose one of the Yedric triggers below.
3. Add conditions and actions, then turn the workflow on.

[image:Screenshot of the Shopify Flow editor with a new workflow whose trigger is "Yedric hand-off requested", followed by a "Send internal email" action addressed to the support team, and the trigger's fields (Conversation id, Conversation url, Reason, Channel) listed in the side panel. Spotlight the Yedric trigger.]

For example: email your support team a link whenever a shopper needs a person, or tag a signed-in customer `yedric-unhappy` when their conversation ends on a negative note.

***

## Triggers

* **Yedric conversation ended**: A conversation ended and was summarized. Fires for every conversation, signed in or not. Gives you the **Conversation id**, a **Conversation url** that opens it in Yedric, the **Summary**, the **Sentiment** (positive, neutral or negative), the **Outcome** (answered, handed_off or unanswered), the **Tags**, and the **Channel** (web, email or whatsapp).
* **Yedric customer conversation ended**: The same, only for signed-in customers, with the **Customer** so you can act on them.
* **Yedric hand-off requested**: A conversation needs a person from your team. Fires once per conversation, with the **Reason**: the assistant passed it to your team, the shopper started a live chat, or an email needs a person.
* **Yedric customer hand-off requested**: The same, only for signed-in customers, with the **Customer**.
* **Shopper asked about a return in Yedric**: The assistant looked up an order because a shopper asked about returning it, with the **Order**. Needs [Returns](https://docs.yedric.ai/shopify/capabilities/returns/) on.
* **Customer asked about a return in Yedric**: The same, only for signed-in customers, with the **Customer** and the **Order**.
* **Yedric found a knowledge gap**: Shoppers keep asking something your store's content does not answer, with the **Question** and how many conversations asked it (**Count**). Checked weekly. A good moment to write a [custom reply](https://docs.yedric.ai/shopify/capabilities/custom-replies/).

Your own test chats never fire a trigger.

***

## Actions

* **Send a reply on a Yedric conversation**: Sends your **Message** to the shopper, as written: by email for an email conversation, or into the live chat if one is open. Its **delivered** result tells you whether it reached them.
* **Tag a Yedric conversation**: Adds a **Tag** (up to 40 characters) to a conversation, so you can filter for it in [Conversations](https://docs.yedric.ai/shopify/going-deeper/conversations/).

Both take the **Conversation id** from a Yedric trigger.