> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/plugins-and-integrations/web-plugins/narrative-design-guide/narrative-design-triggers.md).
# Narrative Design Triggers
## Use of Invoke Narrative Design Trigger in Web.
These triggers would be used to navigate through the story graph and activate specific narrative design sections.
In the example bellow calling the trigger (start tour) would activate "Greet User" section.
Narrative Design Trigger
Once the logic is decided we can move to our Javascript code. Where we have initialised convaiClient.\
We can call `convaiClient.invokeTrigger()` whenver we require it in our use case.\
Additional information for context can also be passed as the second argument : message.
```javascript
convaiClient = new ConvaiClient({
apiKey: "", // Replace with your API key
characterId: "", // Replace with your character ID
enableAudio: true,
faceModal: 3,
enableFacialData: true,
});
// in the above scenario triggerName = "Start tour."
convaiClient.invokeTrigger("triggerName", "message");
```
---
# 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.convai.com/api-docs/plugins-and-integrations/web-plugins/narrative-design-guide/narrative-design-triggers.md?ask=&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.
