> For the complete documentation index, see [llms.txt](https://studio.docs.ai.vonage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studio.docs.ai.vonage.com/http/events.md).

# Events

**Events** are all conversation and workflows executed through the agent.

These can be individual sessions between either agent and user or actions performed by the agent (like sending a text message or email, or API request). Events can be triggered fully separate from one another.

For HTTP agents, we currently offer only one event type:

### API Event

The **API event** flow will be triggered by an incoming API call. This HTTP-event-based flow can be initialized at any time completely separate from the main flow from an API call platform such as Postman.

**Use Case Example:** A customer inquires about a certain product. The customer's database receives that information and uses this event to trigger an email with discount opportunities to the customer.

To initiate this event, click on the node, copy the endpoint and all other request parameters to your API platform of choice.&#x20;

![](https://3877181490-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-L_81A0PNZfdawu_TPAO%2Fuploads%2F5Om8Gx8P04V271SB5ngf%2FScreen%20Shot%202022-05-16%20at%2017.21.37.png?alt=media\&token=aaac6846-f5c2-4e93-b11c-824a12e5a580)

{% hint style="info" %}
*You can only use action-based nodes for this event, e.g. webhooks, custom code, etc.*

*You can create multiple API events per agent.*&#x20;
{% endhint %}


---

# 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://studio.docs.ai.vonage.com/http/events.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.
