> 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/convai-unity-sdk/features/character-actions.md). # Character actions Find the Actions Editor, executor reference, dispatcher configuration, scripting API, and usage guides for Convai character actions in Unity. Character actions let a Convai character respond to what a player says with an in-scene behavior — walking to a target, making eye contact, playing a gesture, or running your own gameplay code. Convai identifies which action to run and what to target; the Actions Editor is where you add and configure the 21 built-in executors that carry it out, or wire in your own. This section covers everything from your first action to the full scripting API. Several built-in executors run through the Gaze and Body Animation embodiment modules, so a character needs the matching module installed before those actions work — see [Embodiment](/api-docs/plugins-and-integrations/convai-unity-sdk/embodiment.md).


How character actions work Understand the pipeline, key concepts, required components, and built-in executors.	How character actions work
Character actions quick start Add a ready-made action to your NPC from the Actions Editor's starter catalog — no scripting required.	Character actions quick start
Actions Editor Reference for the Actions Editor window: the Add Action catalog, and one-click executor provisioning.	Actions Editor
Configure character actions Full reference for `ConvaiActionConfigSource` — action definitions, targets, and connect-time overrides.	Configure character actions
Update character actions at runtime Apply `ConvaiActionConfigPatch` updates to actions, objects, characters, and attention while a session is active, confirmed by Convai's acknowledgment.	Update character actions at runtime
Action executors Reference for all 21 executor components with Inspector field tables.	Action executors
Dispatcher and batch policies Configure how `ConvaiActionDispatcher` handles concurrent batches and step failures.	Dispatcher and batch policies
Write a custom action executor Implement `IConvaiActionExecutor` to create project-specific behaviors for any action.	Write a custom action executor
How action target resolution works How a command's target words are matched to real objects in your scene, and how attention narrows the match.	How action target resolution works
Character actions scripting reference Complete public API for all action system types, events, enums, and components.	Character actions scripting reference
Character actions examples Six progressive scenarios from no-code Inspector setup to scripted batch injection, speech-synced timing, and observation actions.	Character actions examples
Troubleshoot character actions Diagnose action pipeline issues with the Action Troubleshooter and a symptom/cause/fix reference.	Troubleshoot character actions

--- # 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.convai.com/api-docs/plugins-and-integrations/convai-unity-sdk/features/character-actions.md?ask=&goal= ``` `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.