> For the complete documentation index, see [llms.txt](https://help.clickatell.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clickatell.com/chat-flow/user-facing-nodes/display-nodes/rich-link.md).

# Rich Link

This node behaves slightly differently on WhatsApp and Apple Messages for Business (AMB).

**WhatsApp** 

On WhatsApp, the Rich Link node is used to send Call-to-action URL button messages, allowing you to map any URL to a button in a free-form WhatsApp message. 

More information about setting this up is available [here](/chat-flow/channel-capabilities/use-whatsapp-with-chat-flow/map-url-to-button-in-free-form-message.md).

**Apple Messages for Business (AMB)** 

On Apple Messages for Business, the Rich Link node is used to send a web link that a customer can use to visit a specific site. You can add an image or video in Chat Flow to display together with the web link.  

This is especially useful if you want to use a different preview than the one that automatically pulls through based on the URL you've added. 

<figure><img src="https://3262477137-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjoAgInTNsBfDdfx1I23z%2Fuploads%2F7mnMN0kuz8xyD1U2hcrh%2Fimage.png?alt=media&amp;token=c8578dc8-a4f6-43fe-8103-f9b337518540" alt=""><figcaption><p>Setting up the Rich Link node (for Apple Messages for Business) in Chat Flow.</p></figcaption></figure>

{% hint style="info" %}
When adding a video:

* You cannot make use of embedded links (e.g. YouTube), it has to be a direct URL to a video.
* The supported media types are **video/mp4** and **video/mpeg**.
* The thumbnail of the video will be used as a preview in-channel. You can override this thumbnail by adding an image to the node.
  {% endhint %}

<figure><img src="https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/cIc2Iz7SxnX61PuP7vd2/image.png" alt="" width="563"><figcaption><p>A rich link message, displaying an image (left) and video (right) to the customer on their Apple device.</p></figcaption></figure>

### Image size

Optimizing your image for 240 x 240 pixels results in the best experience for your customers. The image binary size must be 200KB or smaller. How the image displays to your customers depends on the size of the image you add, as shown below.

<figure><img src="https://content.gitbook.com/content/joAgInTNsBfDdfx1I23z/blobs/Hre1PI6i0FAvkMCJedkn/image.png" alt="" width="563"><figcaption><p>Image size and related experience on device.</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.clickatell.com/chat-flow/user-facing-nodes/display-nodes/rich-link.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.