Choose an action from the user outcome and backend data requirement, not from the artwork label alone.
Action decision map
Camera, camera roll, and location actions are limited to quick replies and should not be placed in Rich Menu JSON.
| Desired outcome | Action | Backend required? |
|---|---|---|
| Open a site, LIFF app, or phone link | URI | Not always |
| Send user text into chat | Message | For automated replies |
| Send hidden workflow data | Postback | Webhook required |
| Pick a date or time | Datetime picker | Webhook required |
| Change menu page | Rich menu switch | Alias required |
| Copy a coupon or reference | Clipboard | No |
Message versus postback
Message behaves like user-entered text and creates a message event, which works well with existing keyword flows. Postback sends data in a postback event and can show separate displayText, making it better for IDs or commands users should not edit.
Do not place secrets in postback data. Even when hidden from chat, it still travels through the client and webhook. Use opaque IDs and authorize on the server.
Details that improve UX
The artwork and action need the same promise. A button labeled “Call us” that opens a form breaks trust and can reduce engagement.
- Use outcome-based labels for accessibility
- Send URI actions to fast mobile pages
- Set datetime min and max to prevent invalid dates
- Keep alias names stable and update the menu ID behind them
- Explain what clipboard copies and require LINE 14.0.0+ on mobile
Official references
Confirm the latest official specification before using a workflow in a critical system.
Ready to map it on a canvas?
Drag, move, and resize action areas, then validate the JSON before publishing.
Open Studio →