# rpk ai trigger

> For the complete documentation index, see [llms.txt](https://docs.redpanda.com/llms.txt). Component-specific: [agentic-data-plane-full.txt](https://docs.redpanda.com/agentic-data-plane-full.txt)

---
title: rpk ai trigger
latest-operator-version: v26.2.4
latest-console-tag: v3.12.0
latest-connect-version: 4.113.1
latest-redpanda-tag: v26.2.4
docname: rpk/rpk-ai/rpk-ai-trigger
page-component-name: agentic-data-plane
page-version: master
page-component-version: master
page-component-title: Agentic Data Plane
page-relative-src-path: rpk/rpk-ai/rpk-ai-trigger.adoc
page-edit-url: https://github.com/redpanda-data/adp-docs/edit/main/modules/reference/pages/rpk/rpk-ai/rpk-ai-trigger.adoc
description: "Manage the triggers on an agent: the configured ways an agent is invoked from the outside (Microsoft Teams, or a cron schedule). A trigger belongs to exactly one agent, and its resource name carries that parent: <code>agents/\\{agent}/triggers/\\{trigger}</code>."
page-git-created-date: "2026-09-18"
page-git-modified-date: "2026-09-22"
---

<!-- Source: https://docs.redpanda.com/agentic-data-plane/reference/rpk/rpk-ai/rpk-ai-trigger.md -->

Manage the triggers on an agent: the configured ways an agent is invoked from the outside (Microsoft Teams, or a cron schedule).

A trigger belongs to exactly one agent, and its resource name carries that parent: `agents/{agent}/triggers/{trigger}`. So `create` and `list` take the parent agent, while `get`, `update`, `delete` and `runs` take the full two-segment name they print.

The trigger id is server-assigned unless you pass `--id`. The kind (`--teams-`\* or `--cron-`\*) is fixed at creation; to change it, delete and recreate.

adp-api is a registry: it stores the trigger config but never validates the credentials or resolves the secret refs. A trigger that is accepted here can still be reported unhealthy by the component that operates it.

## [](#usage)Usage

```bash
rpk ai trigger [flags]
```

## [](#subcommands)Subcommands

| Command | Description |
| --- | --- |
| rpk ai trigger apply | Reconcile triggers from one or more YAML manifests. For each manifest: create the resource if absent, otherwise update every field that differs from the live resource. |
| rpk ai trigger create | Create a trigger on <agent>, given as the agent id (my-agent) or its resource name (agents/my-agent). Exactly one kind: the --teams-* flags register a Microsoft Teams entry point, the --cron-* flags a schedule. |
| rpk ai trigger delete | Delete one trigger. <name> is the full resource name, for example, agents/my-agent/triggers/t1a2b3c4. |
| rpk ai trigger diff | Dry-run of apply for triggers. Prints, per manifest, whether apply would create, update (and which fields), or leave the resource unchanged. |
| rpk ai trigger get | Get one trigger. <name> is the full resource name, for example, agents/my-agent/triggers/t1a2b3c4. |
| rpk ai trigger list | List every trigger on <agent>, given as the agent id (my-agent) or its resource name (agents/my-agent). |
| rpk ai trigger runs | List the recorded fires of a cron trigger, newest first. <name> is the full trigger resource name, for example, agents/my-agent/triggers/t1a2b3c4. |
| rpk ai trigger update | Update one trigger. <name> is the full resource name, for example, agents/my-agent/triggers/t1a2b3c4. |

## [](#global-flags)Global flags

| Value | Type | Description |
| --- | --- | --- |
| --config | string | Redpanda or rpk config file; default search paths are ~/.config/rpk/rpk.yaml, $PWD/redpanda.yaml, and /etc/redpanda/redpanda.yaml. |
| -X, --config-opt | stringArray | Override rpk configuration settings; -X help for detail or -X list for terser detail. |
| --ignore-profile | bool | Ignore rpk.yaml and redpanda.yaml; use default settings. |
| --profile | string | rpk profile to use. |
| -v, --verbose | bool | Enable verbose logging. |