Email re-engagement campaigns underperform in Japan compared to other markets. Japanese shoppers use LINE as their primary digital communication channel. Brands that rely solely on email to follow up on wishlist activity are missing the channel where their customers actually respond.

This playbook connects Wishlist Plus intent signals to LINE via Shopify Flow's HTTP Request action. When a shopper saves a product to their wishlist, Shopify Flow sends an automated message through your LINE Official Account. The shopper receives a personalised product reminder in LINE.

Who This Playbook Is For

Shopify merchants with a Japanese customer base using LINE Official Account for customer communication. Also relevant for agencies managing Shopify stores for Japanese clients. This workflow requires Shopify Grow, Advanced, or Plus plan for the HTTP Request action.

What You Will Build

When a shopper adds a product to their wishlist, Shopify Flow sends an HTTP request to the LINE Messaging API. The shopper's connected LINE account receives a personalised message with the product name, image, and a link to return and purchase. The workflow runs automatically without manual sends.

Click Select Trigger. Select the Swym trigger: Added to Wishlist. Metadata passed includes: shopper email, product ID, product title, variant details, and product URL.

Before firing a LINE message, confirm the shopper has a LINE User ID stored in their customer metafields or a connected field. Common conditions:

• Customer has a LINE User ID stored (metafield is not empty)
• Product price above a set threshold (e.g. above 3,000 yen)
• Customer is tagged as line-connected or has completed LINE registration

Click Select Action. Choose Send HTTP Request (requires Grow, Advanced, or Plus plan).

HTTP Request configuration:

Method: POST
URL: https://api.line.me/v2/bot/message/push
Headers: Authorization: Bearer {YOUR_CHANNEL_ACCESS_TOKEN}
         Content-Type: application/json
Body: {
  "to": "{{customer.metafields.custom.line_user_id}}",
  "messages": [{
    "type": "template",
    "altText": "A product you saved is waiting for you.",
    "template": {
      "type": "buttons",
      "thumbnailImageUrl": "{{product.featuredImage.url}}",
      "title": "{{product.title}}",
      "text": "You saved this. It is still available.",
      "actions": [{"type": "uri", "label": "View product", "uri": "{{product.url}}"}]
    }
  }]
}

Replace YOUR_CHANNEL_ACCESS_TOKEN with your LINE channel token. Replace the metafield path with the field where you store the shopper's LINE User ID in your store.

Publish the workflow. Test with a LINE-connected test account by adding a product to the wishlist. Verify the message arrives in LINE with the correct product details.

Message Design for LINE

LINE Buttons Template supports an image, a title, a text field, and up to four action buttons. Recommended configuration:

• Image: product featured image
• Title: product name (max 40 characters)
• Text: a short prompt. 'You saved this item. It is still available.' (max 160 characters)
• Action button 1: View product (links to product page with UTM tag)
• Action button 2 (optional): Add to wishlist / Share (links to wishlist page)

Adding a Price Drop Variant

Stack a second workflow with the same trigger but add a condition: product price has decreased since the wishlist add (requires tracking the saved price via metafield or a third-party price tracking tool). When the price drops, send a second LINE message with the new price.

This is a more advanced build. Start with the basic reminder workflow first and add price drop messaging once the base workflow is live and performing.

What Success Looks Like

• LINE messages sent per week from wishlist triggers
• Message open rate (LINE Messaging API provides delivery and open data in the LINE Official Account Manager)
• Click-through rate on the product link
• Revenue attributed to LINE-triggered purchases within 7 days

Agency Note

If you are building this workflow for a client, confirm the following before starting: LINE Official Account is active, LINE Messaging API access is approved, Channel Access Token is issued, and the Shopify store has a mechanism for collecting and storing LINE User IDs. Build time is typically 2 to 4 hours once prerequisites are confirmed.