# Update a trigger

**PATCH** `/projects/{project_id}/branches/{branch_id}/triggers/{trigger_id}`

Applies a partial update. The required `type` discriminator must identify
the existing trigger kind. The supported types are `schedule` and
`storage_object_created`. Editing an inherited trigger creates a
child-local shadow with the same `trigger_id`; it remains disabled unless
this request explicitly enables it. For a schedule trigger, updating the
schedule or enabled state increments `version` and recomputes
`next_run_at`.

Disabling stops future scheduling but does not cancel occurrences already
committed for delivery. For `storage_object_created`, the configuration
selects one exact bucket. An omitted object-key prefix matches every key
in that bucket; a present prefix is matched byte-for-byte and
case-sensitively against the full key, without path normalization or a
path-segment boundary.

**Note**: This endpoint is currently in Beta.

Base URL: `https://console.neon.tech/api/v2`

Tags: `Functions`

## Authorization

Any ONE of the following options authorizes this operation; every scheme listed within an option is required together.

| Option | Scheme | Type | Sent as | Scopes |
| --- | --- | --- | --- | --- |
| Option 1 | `BearerAuth` | `http` | `Authorization: Bearer <token>` | — |
| Option 2 | `CookieAuth` | `apiKey` | cookie `zenith` | — |
| Option 3 | `TokenCookieAuth` | `apiKey` | cookie `keycloak_token` | — |

## Path parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `project_id` | `string` | Yes | The Neon project ID |
| `branch_id` | `string` | Yes | The Neon branch ID |
| `trigger_id` | `string` | Yes | The opaque, project-wide trigger ID |

## Request body

Required. Media type: `application/json`

### Example request body

```json
{
  "enabled": true,
  "function_path": "string",
  "function_slug": "string",
  "name": "string",
  "schedule": {
    "cron": "0 9 * * 1-5"
  },
  "type": "schedule"
}
```

## Responses

| Status | Description | Media type |
| --- | --- | --- |
| `200` | The updated trigger | `application/json` |
| `default` | General Error. The request may or may not be safe to retry, depending on the HTTP method, response status code, and whether a response was received. - If no response is returned from the API, a network error or timeout likely occurred. - In some cases, the request may have reached the server and been successfully processed, but the response failed to reach the client. As a result, retrying non-idempotent requests can lead to unintended results. The following HTTP methods are considered non-idempotent: `POST`, `PATCH`, `DELETE`, and `PUT`. Retrying these methods is generally **not safe**. The following methods are considered idempotent: `GET`, `HEAD`, and `OPTIONS`. Retrying these methods is **safe** in the event of a network error or timeout. Any request that returns a `503 Service Unavailable` response is always safe to retry. Any request that returns a `423 Locked` response is safe to retry. `423 Locked` indicates that the resource is temporarily locked, for example, due to another operation in progress. | `application/json` |

### Example response: 200 — The updated trigger

```json
{
  "trigger": {
    "enabled": true,
    "function_path": "string",
    "function_slug": "string",
    "inherited": true,
    "name": "string",
    "next_run_at": "string",
    "schedule": {
      "cron": "0 9 * * 1-5"
    },
    "trigger_id": "string",
    "type": "schedule",
    "version": 0
  }
}
```

### Example response: default — General Error.

The request may or may not be safe to retry, depending on the HTTP method, response status code,
and whether a response was received.

- If no response is returned from the API, a network error or timeout likely occurred.
- In some cases, the request may have reached the server and been successfully processed, but the response failed to reach the client. As a result, retrying non-idempotent requests can lead to unintended results.

The following HTTP methods are considered non-idempotent: `POST`, `PATCH`, `DELETE`, and `PUT`. Retrying these methods is generally **not safe**.
The following methods are considered idempotent: `GET`, `HEAD`, and `OPTIONS`. Retrying these methods is **safe** in the event of a network error or timeout.

Any request that returns a `503 Service Unavailable` response is always safe to retry.

Any request that returns a `423 Locked` response is safe to retry. `423 Locked` indicates that the resource is temporarily locked, for example, due to another operation in progress.

```json
{
  "code": "",
  "message": "string",
  "request_id": "string"
}
```

## Related pages

- [Accept a project transfer request](./acceptprojecttransferrequest.md)
- [Add an OAuth provider](./addneonauthoauthprovider.md)
- [Add an OAuth provider](./addbranchneonauthoauthprovider.md)
- [Add domain to redirect_uri whitelist](./addbranchneonauthtrusteddomain.md)
- [Add JWKS URL](./addprojectjwks.md)
- [Add trusted redirect URI domain](./addneonauthdomaintoredirecturiwhitelist.md)
- [AI Gateway](./tags/ai-gateway.md)
- [API Key](./tags/api-key.md)
- [Assign or update VPC endpoint](./assignorganizationvpcendpoint.md)
- [Auth](./tags/auth.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.