FlowPost Tutorial
Last updated: September 11, 2026
Send transactional email from Shopify Flow through your own provider and domain — using FlowPost’s Send transactional email action.
Setup in 5 steps
- Install Shopify Flow + FlowPost
FlowPost only sends when a Flow workflow runs. Install Flow, then open FlowPost from Apps. - Connect your email provider
Settings → pick SMTP or an API provider → Save → Send test email. Don’t skip the test. - Copy a template
Templates → pick one → Send test (optional) → Copy all. Keep the {{ Liquid }} tags. - Build the Flow
Admin → Flow → new workflow → add action “Send transactional email” → paste To, Subject, HTML → turn on. - Confirm in Logs
Place a test order (or run the workflow). Check FlowPost → Logs. Failed sends can be retried.
Ready-made Flow recipes
In Shopify Flow, create a workflow with the trigger below, add Send transactional email, then paste the matching FlowPost template.
Order confirmation (customer)
Thank the buyer with items, totals, and shipping address.
- Trigger: Order created
- To:
{{ order.email }} - Template: Order confirmation — customer
- Subject:
Thanks for your order {{ order.name }}
- Paste the template HTML into the Flow action body field (keep Liquid as-is).
- Works best after your From domain has SPF/DKIM set at your provider.
New order alert (staff)
Notify your team the moment an order lands.
- Trigger: Order created
- To:
ops@yourstore.com - Template: New order — staff alert
- Subject:
New order {{ order.name }} received
- Use a fixed staff inbox in To, or a comma-separated list if your provider allows it.
- Add a condition (e.g. total > 200) if you only want high-value alerts.
Shipped / tracking (customer)
Send tracking when fulfillment is created.
- Trigger: Fulfillment created
- To:
{{ order.email }} - Template: Order shipped
- Subject:
Your order {{ order.name }} is on the way
- The shipped template includes tracking Liquid when fulfillments have tracking info.
- If your trigger exposes fulfillment variables, keep those Liquid tags from the template.
COD / payment pending
Remind customers or staff about cash-on-delivery orders.
- Trigger: Order created
- Condition: Payment gateway / tags include COD (or unpaid)
- To:
{{ order.email }} - Template: COD alert
- Subject:
Cash on delivery for {{ order.name }}
- Add a Flow condition so this only runs for COD checkouts.
- Staff copy: change To to your warehouse email and use the same template.
Refund notice (customer)
Confirm a refund after you issue it in Shopify.
- Trigger: Refund created
- To:
{{ order.email }} - Template: Refund issued
- Subject:
Refund for {{ order.name }}
- Transactional refunds are clearer when they come from your store domain (not a shared ESP).
Flow action fields
- To— Customer: {{ order.email }}. Staff: a fixed address like ops@yourdomain.com.
- Subject— Supports Liquid from the workflow (order.name, shop.name, etc.).
- HTML body— Paste from Templates → Copy. Do not strip {{ … }} tags — Flow fills them at send time.
- Preview text (optional)— Inbox snippet after the subject. Optional but improves open rates.
- From name / From email / Reply-to (optional)— Override Settings for this send. From email must be allowed by your provider.
- Attachment URLs (optional)— One HTTPS URL per line (max 5, 5MB each). Trial and paid plans.
Useful Liquid
- Customer email:
{{ order.email }} - Order number:
{{ order.name }} - First name:
{{ order.customer.firstName }} - Shop name:
{{ shop.name }} - Order total:
{{ order.totalPriceSet.shopMoney.amount }}
Troubleshooting
In Flow, search actions for “Send transactional email” or “FlowPost”. Reinstall FlowPost if the action is missing after install.
You pasted into a field that doesn’t run Liquid, or used the wrong trigger variables. Build the workflow from an order/fulfillment trigger and paste into FlowPost’s action fields.
Check Spam/Promotions. Confirm From matches your provider domain. For Gmail/Microsoft 365 use an App Password. Authenticate SPF/DKIM at your provider.
Open the error on the log row, fix provider credentials or From address, then use Retry when the body was saved — or fix the Flow and trigger again.
More help
- Documentation
- FAQ
- Support: info@avoits.com
FlowPost by AVOITS. Support: info@avoits.com.