---
title: "Create an object store trigger"
method: POST
path: "/trigger/obj"
tags: ["Object Store Triggers"]
---

# Create an object store trigger

`POST /trigger/obj`

## Request

- Base URL: `https://api.quiva.ai`
- URL: `https://api.quiva.ai/trigger/obj`
- Auth: one of:
  - HTTP bearer
  - API key in header `x-api-key`
- TypeScript: <https://skmtc.dev/quivaworks/apis/quiva-ai-gateway-6/docs/trigger/obj/post.ts> (a function with typed inputs; its response is checked against the schema)

Creates a trigger that starts a flow when an object store bucket changes.

## Request body

- ObjectStoreTriggerRequest
  - `name` string, required: Unique trigger name
  - `collection` string
  - `description` string
  - `flow_subject` string: Subject of the flow the trigger starts

## Response `200`

Trigger created

- ObjectStoreTriggerResponse
  - `body` object
    - `body` object
      - `name` string
      - `collection` string
      - `description` string
      - `subject` string
      - `trigger_type` 'obj'
      - `type` string
      - `flow_subject` string
  - `status_code` integer

## Other responses

- `400`: Invalid request. Occurs when required parameters are missing, validation fails, or the request format is incorrect.
- `401`: Unauthorized access. Occurs when authentication is missing or invalid, or when the authenticated user lacks permission.
- `500`: Internal server error. Occurs when an unexpected condition prevents the server from fulfilling the request.

## Changes

- **2026-11-12** `a9f443efdc5d`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/quivaworks/apis/quiva-ai-gateway-6/changes/trigger/obj/post.md)

---

[API](https://skmtc.dev/quivaworks/apis/quiva-ai-gateway-6.md) - [All operations](https://skmtc.dev/quivaworks/apis/quiva-ai-gateway-6/llms.txt) - [OpenAPI document](https://skmtc.dev/quivaworks/apis/quiva-ai-gateway-6/revisions/a9f443efdc5d?raw)