docs(next): document workflow discovery and server actions

[EfeDurmaz16]

Summary

• document how the Next.js integration discovers workflows from start() calls in app/pages entries
• clarify that Server Actions can call start(), while workflow-imported modules should not carry top-level "use server"
• add a small split-wrapper example for Server Actions and workflow logic

Closes#817.

Verification

• pnpm install
• pnpm --filter docs lint:links
• pnpm --filter docs build(blocked by existing prerender failure on /en/v5/docs/api-reference/workflow-api/get-hook-by-token: generateDefinition.code resolved as any; build reached this unrelated docs page after compiling successfully)

Notes

The local environment warns that Node v26.0.0 is outside the repo supported engine range (^18 || ^20 || ^22 || ^24).

[changeset-bot]

⚠️ No Changeset found

Latest commit: 26684ea

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@EfeDurmaz16 is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[VaguelySerious]

(AI) Approving. Verified the documented behavior against the implementation:

• Entry scanning of App Router route/page/layout and pages/src/pages matches packages/next builder config (dirs: ['pages','app','src/pages','src/app']) and the eager builder's entry filter.
• start is exported from workflow/api, and discovery is transitive through the import graph — workflow/step files don't need to live under app/pages.
• The "use server" incompatibility (synchronous module-init wrapper → Server Actions must be async functions) is accurate.

The two markdown rendering bugs (stray code fence; missing blank line before the Monorepos heading) were already fixed by the code-review commits. I pushed a follow-up that clarifies the transitive-discovery behavior and tightens the prose in both new sections. docs lint:links passes.

[EfeDurmaz16]

Summary

• document how the Next.js integration discovers workflows from start() calls in app/pages entries
• clarify that Server Actions can call start(), while workflow-imported modules should not carry top-level "use server"
• add a small split-wrapper example for Server Actions and workflow logic

Closes#817.

Verification

• pnpm install
• pnpm --filter docs lint:links
• pnpm --filter docs build(blocked by existing prerender failure on /en/v5/docs/api-reference/workflow-api/get-hook-by-token: generateDefinition.code resolved as any; build reached this unrelated docs page after compiling successfully)

Notes

The local environment warns that Node v26.0.0 is outside the repo supported engine range (^18 || ^20 || ^22 || ^24).

[changeset-bot]

⚠️ No Changeset found

Latest commit: 26684ea

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@EfeDurmaz16 is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[VaguelySerious]

(AI) Approving. Verified the documented behavior against the implementation:

• Entry scanning of App Router route/page/layout and pages/src/pages matches packages/next builder config (dirs: ['pages','app','src/pages','src/app']) and the eager builder's entry filter.
• start is exported from workflow/api, and discovery is transitive through the import graph — workflow/step files don't need to live under app/pages.
• The "use server" incompatibility (synchronous module-init wrapper → Server Actions must be async functions) is accurate.

The two markdown rendering bugs (stray code fence; missing blank line before the Monorepos heading) were already fixed by the code-review commits. I pushed a follow-up that clarifies the transitive-discovery behavior and tightens the prose in both new sections. docs lint:links passes.

[EfeDurmaz16]

Summary

• document how the Next.js integration discovers workflows from start() calls in app/pages entries
• clarify that Server Actions can call start(), while workflow-imported modules should not carry top-level "use server"
• add a small split-wrapper example for Server Actions and workflow logic

Closes#817.

Verification

• pnpm install
• pnpm --filter docs lint:links
• pnpm --filter docs build(blocked by existing prerender failure on /en/v5/docs/api-reference/workflow-api/get-hook-by-token: generateDefinition.code resolved as any; build reached this unrelated docs page after compiling successfully)

Notes

The local environment warns that Node v26.0.0 is outside the repo supported engine range (^18 || ^20 || ^22 || ^24).

[changeset-bot]

⚠️ No Changeset found

Latest commit: 26684ea

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@EfeDurmaz16 is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[VaguelySerious]

(AI) Approving. Verified the documented behavior against the implementation:

• Entry scanning of App Router route/page/layout and pages/src/pages matches packages/next builder config (dirs: ['pages','app','src/pages','src/app']) and the eager builder's entry filter.
• start is exported from workflow/api, and discovery is transitive through the import graph — workflow/step files don't need to live under app/pages.
• The "use server" incompatibility (synchronous module-init wrapper → Server Actions must be async functions) is accurate.

The two markdown rendering bugs (stray code fence; missing blank line before the Monorepos heading) were already fixed by the code-review commits. I pushed a follow-up that clarifies the transitive-discovery behavior and tightens the prose in both new sections. docs lint:links passes.

[EfeDurmaz16]

Summary

• document how the Next.js integration discovers workflows from start() calls in app/pages entries
• clarify that Server Actions can call start(), while workflow-imported modules should not carry top-level "use server"
• add a small split-wrapper example for Server Actions and workflow logic

Closes#817.

Verification

• pnpm install
• pnpm --filter docs lint:links
• pnpm --filter docs build(blocked by existing prerender failure on /en/v5/docs/api-reference/workflow-api/get-hook-by-token: generateDefinition.code resolved as any; build reached this unrelated docs page after compiling successfully)

Notes

The local environment warns that Node v26.0.0 is outside the repo supported engine range (^18 || ^20 || ^22 || ^24).

[changeset-bot]

⚠️ No Changeset found

Latest commit: 26684ea

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@EfeDurmaz16 is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[VaguelySerious]

(AI) Approving. Verified the documented behavior against the implementation:

• Entry scanning of App Router route/page/layout and pages/src/pages matches packages/next builder config (dirs: ['pages','app','src/pages','src/app']) and the eager builder's entry filter.
• start is exported from workflow/api, and discovery is transitive through the import graph — workflow/step files don't need to live under app/pages.
• The "use server" incompatibility (synchronous module-init wrapper → Server Actions must be async functions) is accurate.

The two markdown rendering bugs (stray code fence; missing blank line before the Monorepos heading) were already fixed by the code-review commits. I pushed a follow-up that clarifies the transitive-discovery behavior and tightens the prose in both new sections. docs lint:links passes.

[EfeDurmaz16]

Summary

• document how the Next.js integration discovers workflows from start() calls in app/pages entries
• clarify that Server Actions can call start(), while workflow-imported modules should not carry top-level "use server"
• add a small split-wrapper example for Server Actions and workflow logic

Closes#817.

Verification

• pnpm install
• pnpm --filter docs lint:links
• pnpm --filter docs build(blocked by existing prerender failure on /en/v5/docs/api-reference/workflow-api/get-hook-by-token: generateDefinition.code resolved as any; build reached this unrelated docs page after compiling successfully)

Notes

The local environment warns that Node v26.0.0 is outside the repo supported engine range (^18 || ^20 || ^22 || ^24).

[changeset-bot]

⚠️ No Changeset found

Latest commit: 26684ea

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@EfeDurmaz16 is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[VaguelySerious]

(AI) Approving. Verified the documented behavior against the implementation:

• Entry scanning of App Router route/page/layout and pages/src/pages matches packages/next builder config (dirs: ['pages','app','src/pages','src/app']) and the eager builder's entry filter.
• start is exported from workflow/api, and discovery is transitive through the import graph — workflow/step files don't need to live under app/pages.
• The "use server" incompatibility (synchronous module-init wrapper → Server Actions must be async functions) is accurate.

The two markdown rendering bugs (stray code fence; missing blank line before the Monorepos heading) were already fixed by the code-review commits. I pushed a follow-up that clarifies the transitive-discovery behavior and tightens the prose in both new sections. docs lint:links passes.

[EfeDurmaz16]

Summary

• document how the Next.js integration discovers workflows from start() calls in app/pages entries
• clarify that Server Actions can call start(), while workflow-imported modules should not carry top-level "use server"
• add a small split-wrapper example for Server Actions and workflow logic

Closes#817.

Verification

• pnpm install
• pnpm --filter docs lint:links
• pnpm --filter docs build(blocked by existing prerender failure on /en/v5/docs/api-reference/workflow-api/get-hook-by-token: generateDefinition.code resolved as any; build reached this unrelated docs page after compiling successfully)

Notes

The local environment warns that Node v26.0.0 is outside the repo supported engine range (^18 || ^20 || ^22 || ^24).

[changeset-bot]

⚠️ No Changeset found

Latest commit: 26684ea

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@EfeDurmaz16 is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[VaguelySerious]

(AI) Approving. Verified the documented behavior against the implementation:

• Entry scanning of App Router route/page/layout and pages/src/pages matches packages/next builder config (dirs: ['pages','app','src/pages','src/app']) and the eager builder's entry filter.
• start is exported from workflow/api, and discovery is transitive through the import graph — workflow/step files don't need to live under app/pages.
• The "use server" incompatibility (synchronous module-init wrapper → Server Actions must be async functions) is accurate.

The two markdown rendering bugs (stray code fence; missing blank line before the Monorepos heading) were already fixed by the code-review commits. I pushed a follow-up that clarifies the transitive-discovery behavior and tightens the prose in both new sections. docs lint:links passes.

[EfeDurmaz16]

Summary

• document how the Next.js integration discovers workflows from start() calls in app/pages entries
• clarify that Server Actions can call start(), while workflow-imported modules should not carry top-level "use server"
• add a small split-wrapper example for Server Actions and workflow logic

Closes#817.

Verification

• pnpm install
• pnpm --filter docs lint:links
• pnpm --filter docs build(blocked by existing prerender failure on /en/v5/docs/api-reference/workflow-api/get-hook-by-token: generateDefinition.code resolved as any; build reached this unrelated docs page after compiling successfully)

Notes

The local environment warns that Node v26.0.0 is outside the repo supported engine range (^18 || ^20 || ^22 || ^24).

[changeset-bot]

⚠️ No Changeset found

Latest commit: 26684ea

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@EfeDurmaz16 is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[VaguelySerious]

(AI) Approving. Verified the documented behavior against the implementation:

• Entry scanning of App Router route/page/layout and pages/src/pages matches packages/next builder config (dirs: ['pages','app','src/pages','src/app']) and the eager builder's entry filter.
• start is exported from workflow/api, and discovery is transitive through the import graph — workflow/step files don't need to live under app/pages.
• The "use server" incompatibility (synchronous module-init wrapper → Server Actions must be async functions) is accurate.

The two markdown rendering bugs (stray code fence; missing blank line before the Monorepos heading) were already fixed by the code-review commits. I pushed a follow-up that clarifies the transitive-discovery behavior and tightens the prose in both new sections. docs lint:links passes.

[EfeDurmaz16]

Summary

• document how the Next.js integration discovers workflows from start() calls in app/pages entries
• clarify that Server Actions can call start(), while workflow-imported modules should not carry top-level "use server"
• add a small split-wrapper example for Server Actions and workflow logic

Closes#817.

Verification

• pnpm install
• pnpm --filter docs lint:links
• pnpm --filter docs build(blocked by existing prerender failure on /en/v5/docs/api-reference/workflow-api/get-hook-by-token: generateDefinition.code resolved as any; build reached this unrelated docs page after compiling successfully)

Notes

The local environment warns that Node v26.0.0 is outside the repo supported engine range (^18 || ^20 || ^22 || ^24).

[changeset-bot]

⚠️ No Changeset found

Latest commit: 26684ea

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@EfeDurmaz16 is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[VaguelySerious]

(AI) Approving. Verified the documented behavior against the implementation:

• Entry scanning of App Router route/page/layout and pages/src/pages matches packages/next builder config (dirs: ['pages','app','src/pages','src/app']) and the eager builder's entry filter.
• start is exported from workflow/api, and discovery is transitive through the import graph — workflow/step files don't need to live under app/pages.
• The "use server" incompatibility (synchronous module-init wrapper → Server Actions must be async functions) is accurate.

The two markdown rendering bugs (stray code fence; missing blank line before the Monorepos heading) were already fixed by the code-review commits. I pushed a follow-up that clarifies the transitive-discovery behavior and tightens the prose in both new sections. docs lint:links passes.