> For the complete documentation index, see [llms.txt](https://changelog.shopwaive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://changelog.shopwaive.com/posts/quickstart-7.md).

# Flow action for native Shopify store credit

April 2, 2025

The Shopwaive Development team is excited to announce release of the native Shopify store credit action for Shopify Flow.  This new action is available from the Shopify Flow app and can be paired with the <mark style="color:blue;">**Send email**</mark> Flow action to send an email with the native Store credit amount credited to the customer. The Shopwaive Development team previously released native Shopify store credit features for customer service teams to issue within the Shopwaive Admin app. Now, we've extended this capability to automations in Shopify Flow to unlock powerful work flows that issue credit when new products are purchased and much more. [Learn more](https://help.shopify.com/en/manual/customers/store-credit)

{% hint style="info" %}
Need support for Shopify Plus integration? Reach out to our team at <support@shopwaive.com> and we'll be glad to support or consider new feature or available options with this release upon request.
{% endhint %}

{% embed url="<https://storage.googleapis.com/steel-spark-359918.appspot.com/NativeStoreCredit.mp4>" %}
New! Issue and email native Shopify store credit now with automations in Shopify Flow
{% endembed %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://changelog.shopwaive.com/posts/quickstart-7.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.