> For the complete documentation index, see [llms.txt](https://guides.clickatell.com/release-notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.clickatell.com/release-notes/release-notes-archive/2023-release-notes/q4-2023/automated-messaging/business-triggered-messages.md).

# Business-Triggered Messages

Previously, the only way a workflow could be triggered in Chat Flow was when an end-user sent a keyword to the business WhatsApp number. If a business wanted to initiate a conversation with its end-users, it had to integrate with One API to trigger a WhatsApp template message, which is quite a technical and roundabout way to start a conversation.

With this release, we've introduced the concept of a “**dynamic API flow**” in Chat Flow. This workflow gets triggered by an **incoming payload** and lets a business initiate a conversation with their customers by sending a pre-approved WhatsApp template (using the [*Send Template*](broken://pages/JSxIfU0Dy35C0FNJl7ZB) node), prompting them to take action and trigger a standard workflow. This opens up many opportunities for new use cases, e.g., sending reminders, shipping updates, marketing messages, and promotions via WhatsApp message templates without having to wait for customers to contact the business first.

Clickatell creates these dynamic API flows on your behalf during onboarding. In the flow list on the left of the canvas, a new yellow icon is used to differentiate the dynamic API workflows from the standard ones. Dynamic API flows are read-only and not visible to end-users.  

In combination with the new [*Send Template*](broken://pages/JSxIfU0Dy35C0FNJl7ZB) node, it is now easier than ever for businesses to send WhatsApp message templates to their customers!

<figure><img src="/files/luJru4UTU9MEo44M0chW" alt=""><figcaption><p>A yellow icon differentiates it from a standard flow.</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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guides.clickatell.com/release-notes/release-notes-archive/2023-release-notes/q4-2023/automated-messaging/business-triggered-messages.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.