> ## Documentation Index > Fetch the complete documentation index at: https://docs.conduit.ai/llms.txt > Use this file to discover all available pages before exploring further. # Run Agent > Manually dispatches a V2 agent as if one of its triggers fired. Cron triggers run immediately; webhook and workflow triggers use the supplied `payload`. Channel/message triggers are not supported. Requires a token with write access. ## OpenAPI ````yaml POST /v1/agents/{id}/run openapi: 3.0.0 info: title: Conduit API version: 1.0.0 description: Public API for Conduit. servers: - url: https://api.conduit.ai description: Production security: [] tags: - name: meta description: Discovery and API metadata endpoints. - name: agents description: >- V2 chat agent configuration, including instructions, skills, triggers, and automation behavior. - name: contacts description: >- Contact profile and contact-scoped related resources such as tickets and calls. - name: workspaces description: Workspaces accessible to the current API token. - name: escalations description: >- Chat escalations that require operator review, including message, proposed response, and disposition context when available. - name: conversations description: >- Canonical message threads. Use these endpoints to list threads, inspect conversation state, read transcripts, and send replies. - name: conversation-tags description: >- Conversation labels, root topics, and subtopics used for classification and topic analytics. - name: tickets description: >- Operational queue items tied to conversations, including ticket-scoped transcripts and replies. - name: calls description: Phone call records, transcripts, summaries, and recordings when available. - name: reservations description: >- PMS reservations synced from the workspace's integrations (Hostaway, Guesty, Airbnb, etc.), including guest identity, payment status, and stay dates. - name: appointments description: >- Scheduled appointments (bookings) backed by the Conduit booking service. Exposes allocation context and the upstream booking-service `external_id`. - name: helpdesk_tickets description: >- Helpdesk tickets mirrored from external helpdesk integrations (Zendesk, Pylon, Plain), including requester identity and upstream metadata. - name: kb description: >- Knowledge base search and node management. Nodes represent knowledge base entries (files or directories), chunks are the indexed retrieval units used by search. - name: skills description: >- Workspace agent skills that can be attached to V2 chat agents. Sidebar/global-assistant skills are intentionally excluded. - name: custom_tools description: >- Custom code tools: user-authored Python/JavaScript functions executed in a sandbox when an agent calls them. Includes a runtimes endpoint describing the entrypoint signature, return shape, and available dependencies per language. - name: inbox_types description: >- Workspace inbox types. Each id is stable and usable as a message trigger's `inboxTypeId` and as the `inbox_type_id` filter on list conversations. paths: /v1/agents/{id}/run: post: tags: - agents summary: Run V2 chat agent description: >- Manually dispatches a V2 agent as if one of its triggers fired. Cron triggers run immediately; webhook and workflow triggers use the supplied `payload`. Channel/message triggers are not supported. Requires a token with write access. operationId: runAgent parameters: - schema: type: string description: Agent id. example: ag77c0dy0mgdpzmqz6tesry8w184002s required: true name: id in: path - schema: type: string description: >- Optional workspace override. If omitted, Conduit resolves the agent's workspace automatically. example: j57demo8f8x7c9v0n2q4r6t8y1u3i5o required: false name: workspace_id in: query requestBody: required: false content: application/json: schema: type: object properties: trigger_id: type: string description: >- Which trigger to run. Required only when the agent has more than one trigger. Cron runs immediately; webhook and workflow runs use `payload`. example: tr77c0dy0mgdpzmqz6tesry8w184002s payload: nullable: true description: >- Event payload for webhook / workflow triggers — the same JSON shape that trigger would receive when it fires for real. Ignored for cron triggers. Defaults to an empty object. description: Request body for manually dispatching a V2 chat agent. example: trigger_id: tr77c0dy0mgdpzmqz6tesry8w184002s payload: reservation_id: res_123 status: confirmed responses: '200': description: Agent dispatched content: application/json: schema: type: object properties: data: type: object properties: dispatched: type: boolean trigger_id: type: string trigger_type: type: string enum: - cron - webhook - event required: - dispatched - trigger_id - trigger_type required: - data description: Result of a manual agent dispatch. example: data: dispatched: true trigger_id: tr77c0dy0mgdpzmqz6tesry8w184002s trigger_type: event '400': description: Invalid request content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '401': description: Unauthorized content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '403': description: Forbidden content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '404': description: Not found content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '422': description: Trigger cannot be dispatched content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '429': description: Rate limit exceeded content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id security: - bearerAuth: [] components: securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: API Token description: >- Conduit API token. Use `Authorization: Bearer `. Read/write endpoints require a token with write access. ````