URGENT
Hi everyone, for some reason links don't work anymore is anyone getting this issue? If i use a message block and link a word, the link doesnt populate when published?
8 Replies
Hey there 👋
Links added inside a Message step should still render as clickable in any web-based surface (the Test Tool, Share link, Web-chat embed, etc.).
Quick checklist to get them working again:
1. Edit the Message step ➜ highlight the word(s) you want linked ➜ press the link icon (or Ctrl/Cmd + K) and paste the full URL (must include
http:// or https://).
2. Click Save on the step and Publish your agent again – links only appear after the new build is published.
3. Refresh/clear cache on the page where you’re testing – the old build can be stuck in the browser.
4. Confirm you’re looking at a web surface. Voice/telephony channels strip HTML so links won’t show there.
If you need a link urgently while you troubleshoot, you can also:
• use a Choice step with a Button of type open_url
• or a Card / Carousel step with a URL button – those are rendered as native link buttons.
Docs for reference:
• Message step – formatting & hyperlinks: https://docs.voiceflow.com/docs/message-step#formatting
Give the steps above a try and let us know if the link still isn’t appearing! ✨yeah but it doesnt render, this must be a bug because it worked fine for 3 months
@Braden (Voiceflow CEO) Hi Braden, do you know if this is a bug or if anyone else is having this issue?
constant-blue•3mo ago
I have the same issue
what happened? why the link became broken suddenly on embedded widget? @Tico | Voiceflow Assistant
hey @maxsbond , checking right now - this is first thread we're hearing of it
constant-blue•3mo ago
https://www.loom.com/share/903c9411abd04eb39b7cad516b7c97ce?sid=30651099-7bff-4323-91e5-824b3ef7edf7
@Braden (Voiceflow CEO) here is a recording for your reference. It did work fine couple days ago, but now I don't see a hyperlink anymore.
*I didn't change anything in my voiceflow setup.
**It works fine in Editor, but not in embedded widget.
We're fixing this RN
sorry guys - lots of updates coming out that caused some bugs that slipped past QA
Thank you for the update!
This is fixed!