Skip to main content
Question

Agent Studio – Non-HTTPS Protocol URLs Break in Notify Messages

  • July 8, 2026
  • 5 replies
  • 69 views

Hi Team,

When the payload contains a URL that uses a protocol other than HTTPS or HTTP in the Notify, the URL is broken in the frontend user message. For example, when we send a URL with a different protocol (such as mailto:, msteams:, or a custom protocol), the link breaks and is not rendered correctly.

 

Sample payload with a non-HTTPS protocol:

Bot response:

 

HTTPS protocol with the same structure:

 

Bot response:

 

Please help us find a solution for this issue, as it is currently impacting multiple live use cases.

@abhiagarwl  - FYA

5 replies

Kevin Mok
Forum|alt.badge.img+2
  • Community Manager
  • July 8, 2026

Hey ​@Saranya Moorthy - Please try using html instead - for some reason markdown does not bode well with mailto

<a href="mailto:someone@example.com">here</a>


Hi Kevin,

Thanks for your response. We also tried using the HTML format, but we're seeing the same formatting issue.

Payload:

 

Response:

 


Kevin Mok
Forum|alt.badge.img+2
  • Community Manager
  • July 9, 2026

I am a bit confused, you mentioned you are using notify but this doesn’t look like notify’s UI


We are using the Notify with Message

steps:

  - action:

      action_name: mw.get_user_by_email

      output_key: target_user

      input_args:

        user_email: data.email

  - notify:

      output_key: notify

      recipient_id: data.target_user.user.record_id

      message:

        RENDER():

          template: |

            Please use this email for support: {{link}}

          args:

            link : data.message


Kevin Mok
Forum|alt.badge.img+2
  • Community Manager
  • July 13, 2026

Oh I see now, I think you should send the link as a regular string “https://example.com” and then handle the formatting in the notify render message ​@Saranya Moorthy