> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/experience-editor/tutorials/intermediate-undersea-educational-content/add-triggers.md).

# Add triggers

We’ll add buttons so that a user can choose which sea creature to learn about.

1. Move the play head to approximately 0:03. This will give users a small amount of time to acclimatize.
2. On the left-hand side of the timeline, select **Trigger**.
3. From the library of triggers, select **3D Button**.
4. Place the button in front of the **Transport all Players to Location** IFX, on the opposite side to the cliff wall.
5. On the timeline, select the cog on the 3D Button's container.
6. In the **End Time** field, type `00:00:30`.
7. In the **Custom Name** field, type `Clown button`.
8. In the **UI Text** field, type `Clown Fish`, and then select **Save Effect**.
9. Repeat from step 2 to create a button for the Orca Whale.

<figure><img src="https://3460182399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwVx6bvwqEE7tD0TYOcfj%2Fuploads%2Fgit-blob-465b726e1778051b5d33ab124eb6b9ad66e3e750%2Ftut_button_placement.jpg?alt=media" alt=""><figcaption><p>Placement of the trigger buttons</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://docs.engagevr.io/engage/experience-editor/tutorials/intermediate-undersea-educational-content/add-triggers.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.