Use this checklist before turning a workflow, template, connector, webhook, or API integration into a production dependency.

Launch readiness coverage

Operational areas to clear before publishing a workflow or integration.

Required coverage
CheckRequirement
Definition validatesThe workflow passes validation and every node payload matches its action or trigger schema.
Connectors are scopedEach connector belongs to the correct organization, has the minimum required provider access, and has a clear owner.
Wallet actions are boundedAny action that can move funds has chain, recipient, token, amount, and approval behavior reviewed with simulation or test funds.
Failure paths are observableFailed runs, failed nodes, webhook delivery errors, and retry exhaustion are visible through the app, API, or execution webhooks.
Docs are updatedAny new action, trigger, endpoint, or workflow pattern has matching public docs and reference output.
Production launch loop
readyleast privilegetest pathslaunch Validate definition Schemas, triggers, payloads Scope access API keys, connectors, service accounts Bound side effects Wallets, webhooks, provider writes Observe failures Runs, executions, streams, hooks Publish and document Live version, public reference, runbook

Operational Policy

AreaRequirement
API keysUse service-specific keys with the narrowest available scope. Rotate after incidents and team changes.
ConnectorsStore credentials in connectors, not workflow payloads or documentation.
WalletsUse dedicated organization wallets for automated workflows. Avoid mixing operational wallets and human wallets.
WebhooksVerify signatures, handle retries idempotently, and monitor replay volume.
TemplatesTreat public templates as product surfaces. Remove organization-specific secrets, IDs, and assumptions.

Public Contract Review

Before launch, confirm the public docs, API reference, action reference, trigger reference, and runbook match the workflow behavior users will rely on.

Action and trigger schemas are user-facing contracts. Keep public references aligned with the product behavior developers will build against.

Ask a question... ⌘I