> For the complete documentation index, see [llms.txt](https://docs-conversational-ai.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-conversational-ai.syntphony.com/ai-agents/actions/how-to....md).

# How to...

This section presents common use cases that show **how to configure** Actions and Skills to meet practical needs.\
\
Each example covers typical scenarios when designing AI Agents. It explains how to structure data collection, manage execution flow, and adapt behavior to different contexts using the platform’s documented capabilities.

### Case 1: Confirm data to call a service&#x20;

There is a transactional API that requires specific user data to be confirmed before it runs. Once confirmed, an OTP code is generated and the API is invoked.

<figure><img src="/files/Rjlj5kUAaDWQM0tkLRjP" alt=""><figcaption></figcaption></figure>

\
\
To meet this requirement, create an Action to collect the required data and trigger the OTP code generation service. Then, create a second Action to perform the transactional query.

<figure><img src="/files/NgcgunMXWCGgPKvY6lmH" alt=""><figcaption></figcaption></figure>

### Case 2 - Formatting responses for each channel

To meet this requirement, create an Action with a simple prompt to format responses.

<figure><img src="/files/1GBHSPBQoiJWxov8Hx5L" alt=""><figcaption></figcaption></figure>

Next, each property was defined with a channel-specific formatting prompt (for example, web chat, WhatsApp, or voice). This allows the AI Agent to generate the appropriate output for each target channel.

<figure><img src="/files/z08Nhe63GYkA62biAKGT" alt=""><figcaption></figcaption></figure>

Finally, a response was created in which the corresponding variable was used for each channel.\
This ensures that the format and content are correctly adapted to each channel type.

<figure><img src="/files/71qXHZl2HlvAmiqlRJgU" alt="" width="375"><figcaption></figcaption></figure>

### Case 3 - Triggering an Action after a skill

Sometimes an Action needs information that it doesn't have yet. In these situations, you can instruct an Action to work with other Actions or skills before completing its task.

In the example below, the `create_ticket` Action first uses another capability to validate and gather the required information. Once everything is confirmed, it proceeds with ticket creation.

This approach helps ensure that Actions always have the context they need before executing a task.

<figure><img src="/files/9QnBl2ve0WpAyoqlcaAE" alt=""><figcaption></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://docs-conversational-ai.syntphony.com/ai-agents/actions/how-to....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.
