Create custom environment - Automate.ax

vercel.createCustomEnvironment creates a custom deployment environment for one project.

automations/create-custom-environment.automation.ts

import { automation } from "automate.ax"
import { vercel } from "automate.ax/vercel"

export default automation("Create custom environment", () => {
  vercel.createCustomEnvironment({
    project: "prj_1",
    slug: "staging",
    teamId: "team_1",
  })
})

Input

project: included in the runnable example and checked by the callable’s TypeScript contract.
slug: included in the runnable example and checked by the callable’s TypeScript contract.
teamId: included in the runnable example and checked by the callable’s TypeScript contract.

Optional filters, pagination controls, request bodies, and provider enums remain visible in editor autocomplete. Unknown keys are rejected by TypeScript instead of being silently discarded.

Output

Returns the typed Vercel resource created by the operation, including its provider ID when Vercel supplies one. Public request and response fields use camelCase.

Provider behavior

OAuth installations default teamId to the installed team; access-token connections must identify the intended scope when Vercel requires it. Automate.ax does not treat this write as replay-safe. Vercel validates identifiers, permissions, and state transitions and returns its provider error when the request is not allowed.