createFlowmark

Node.jsCopy Anchor Link

import { createFlowmark } from "@flowmarkdev/node"
import type { FlowmarkClient, FlowmarkConfig } from "@flowmarkdev/node"

// Signature: createFlowmark(config?: FlowmarkConfig): FlowmarkClient
const flowmark = createFlowmark({
  environment: "production",
  release: "2026.10.2",
})

The client returns workflow(), flush() and shutdown(). Reuse it across work; close it at the process boundary. Creating it validates server settings and can throw FlowmarkConfigError. Starting a workflow can also throw for invalid run context or a closed client.

See configuration for URL rules and precedence.

Next.jsCopy Anchor Link

import { createFlowmark } from "@flowmarkdev/node/next"

const flowmark = createFlowmark()
// Exposes workflow() only; no flush() or shutdown().

Accepts the same server options but creates a request-scoped delivery client when workflow() is called. Call it only in supported Route Handler or Server Action contexts; after() drains after the response. Invalid configuration/context can throw when starting the run. See Next.js integration.

BrowserCopy Anchor Link

import { createFlowmark } from "@flowmarkdev/node/browser"
import type { BrowserFlowmarkConfig } from "@flowmarkdev/node/browser"

const flowmark = createFlowmark({
  publicKey: "fm_browser_...",
  apiUrl: "https://your-flowmark-api.example",
})

Direct settings and proxyPath are mutually exclusive. Creation is SSR-safe; the first workflow() validates browser context/settings and must run in an event handler or effect. No React provider or environment-file loader is needed. See browser integration.