> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qa.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Trigger automation

> Fire an automation on demand, regardless of its configured trigger. Use this
from CI, deploy hooks, or monitoring to start the automation's chat-based
workflow with your own context. Returns 202 immediately.



## OpenAPI

````yaml /api-reference/api.json post /v1/automations/{automationId}/trigger
openapi: 3.0.0
info:
  title: QA.tech API
  version: 1.0.0
  contact:
    name: QA.tech
    url: https://qa.tech
    email: support@qa.tech
  description: API for triggering and managing AI-powered test runs
servers:
  - url: https://api.qa.tech
    description: Production
    variables: {}
security:
  - BearerAuth: []
tags:
  - name: Runs
  - name: Infrastructure
  - name: Test Cases
  - name: Application Builds
  - name: Status badge
  - name: Remote Tunnels
  - name: Chat
  - name: Applications
  - name: Features
  - name: Metrics
  - name: Release Checks
  - name: Projects
  - name: Knowledge
  - name: Rules
  - name: Issues
  - name: Automations
paths:
  /v1/automations/{automationId}/trigger:
    post:
      tags:
        - Automations
      summary: Trigger automation
      description: >-
        Fire an automation on demand, regardless of its configured trigger. Use
        this

        from CI, deploy hooks, or monitoring to start the automation's
        chat-based

        workflow with your own context. Returns 202 immediately.
      operationId: TriggerAutomation
      parameters:
        - name: automationId
          in: path
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/TriggerAutomationRequest'
      responses:
        '202':
          description: >-
            The request has been accepted for processing, but processing has not
            yet completed.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TriggerAutomationResponse'
components:
  schemas:
    TriggerAutomationRequest:
      type: object
      properties:
        context:
          type: object
          additionalProperties: {}
          description: >-
            Free-form context for this trigger, such as the deployment version
            or environment name.
      description: >-
        Optional payload forwarded to the automation as trigger context. Any
        JSON object; it is surfaced verbatim to the agent that runs the
        automation.
    TriggerAutomationResponse:
      type: object
      required:
        - automationId
        - triggered
      properties:
        automationId:
          type: string
          description: The automation that was queued.
        triggered:
          type: boolean
          description: >-
            Always true; the automation runs asynchronously and its work appears
            as a chat conversation in the project.
  securitySchemes:
    BearerAuth:
      type: http
      scheme: Bearer

````