# Build and edit custom workflows

> Use Console for organization-owned workflows when a published Workflow Starter does not cover the required sequence.

Canonical: https://entirefeed.com/docs/workflows/build-and-edit

Custom workflows are a signed-in Console surface. They are separate from the public Workflow Starter API: creating or editing a custom workflow does not publish a new starter or create a public starter contract.

## Choose the right path

Use a Workflow Starter when its published input and output schemas match the result you need. The starter API is the shortest self-serve path because discovery, pricing, execution, and lifecycle handling use stable public resources.

Use a custom workflow when an operator needs to arrange a different sequence, configure steps, or reuse organization-specific setup.

## Build and edit in Console

Create or open a workflow in Console, make the required changes, and save deliberately. Editing alone does not run paid work. Estimate the current saved workflow before deciding whether to run it, and estimate again after execution-affecting changes.

Custom workflows stay scoped to the signed-in organization. Their editing surface and permissions are governed by the current user's Console access.

## Connect an agent

A trusted agent can discover and operate supported custom workflow actions through a delegated MCP credential. The credential uses the owner's current authority and can be revoked independently.

Start with [Connect Console MCP](/docs/agents/connect), then read [Tasks and workflows](/docs/agents/tasks-and-workflows). Discovery and read actions can be used without starting a paid run.