> 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/mesa.md).

# Automations (MESA)

Let the Yedric assistant run MESA workflows, fill in MESA forms with shoppers, and start workflows from chat events like a request for your team.

[MESA](https://apps.shopify.com/mesa) is ShopPad's workflow automation app. Connected to Yedric, your assistant can run workflows you build in MESA, such as checking a loyalty balance or creating a ticket, fill in MESA forms with shoppers in chat, and start MESA workflows when things happen in chat, like a shopper asking for your team.

Automations work on every plan and are off until you connect MESA.

***

## Connecting MESA

1. Open **Capabilities > Automations (MESA)**, or click **Connect** on the MESA card under **Better with friends**.
2. Click **Connect MESA**. MESA opens, and installs itself first if your store does not have it yet.
3. Back in Yedric, a page titled **MESA wants to connect to {your store}** lists what MESA will be able to do. Click **Allow**.

There is nothing to copy or paste. Only the store owner or an admin can connect MESA, and you can disconnect it at any time from the same page.

[image:Screenshot of the Yedric approval page in the Shopify admin titled "Connect MESA", with the line "MESA wants to connect to {store}", the list under "If you allow it, MESA can:", the note "You can disconnect it at any time from Capabilities." and the Allow and Deny buttons. Spotlight the Allow button.]

***

## Workflows your assistant can run

In MESA, create a workflow that starts with **AI: Skill triggered**, set the fields the assistant should fill to **Let AI choose**, and turn it on. It appears in Yedric under **Workflows your assistant can run**, off until you switch it on.

Switched on, the assistant runs a workflow when a shopper's request matches the workflow's description in MESA. Each workflow shows what it asks the shopper for. You can switch on up to 50.

[image:Screenshot of the "Workflows your assistant can run" section of the Yedric Automations (MESA) page (Apps > Yedric > Capabilities > Automations (MESA)), listing two MESA workflows, each with its name, description, an "Asks the shopper for:" line and a switch, one switched on. Spotlight the switch that is on.]

When a shopper is logged in, their customer id is passed to the workflow from their login, never from what they typed in the chat. See [how skill workflows work](https://docs.getmesa.com/tools/ai) in the MESA docs.

***

## Forms your assistant can fill in

In MESA, create a workflow that starts with **Form**, build it in the Form Builder, and turn it on. It appears under **Forms your assistant can fill in**.

Switched on, the assistant collects the form's fields in chat, reads them back, and sends them to MESA once the shopper agrees. The shopper gets a short reference number. Fields filled in for you, such as the customer, come from the signed-in customer, never from the chat. Each form can be sent once per conversation, in the chat on your storefront.

For each form you can set:

* **Offer this form when**: What the assistant reads to decide when this form fits. Leave it blank to use the workflow's description in MESA.
* **After sending, say**: What the assistant tells the shopper once the form is sent.

A form with a field that cannot be asked in chat, such as a file upload, is marked as not usable from chat.

***

## Chat events in MESA

To start a MESA workflow when something happens in chat, add a Yedric trigger to any workflow in MESA:

* Conversation created
* Conversation escalated to your team
* Conversation summarized
* Live chat started, assigned, transferred or ended
* Live chat rated
* Return requested

MESA gets who, when and what happened, never what was said in the chat.

***

## If something goes wrong

* **MESA no longer accepts this connection**: Click **Reconnect**.
* **MESA is not responding**: Your workflows are paused until MESA answers again. Nothing needs to change in Yedric.