Check Resource Dependencies
What will a workflow change affect? Read its dependency map, which lists attached agents, calling workflows, connections, and triggers. Check draft and Live separately. Removing a draft tool leaves its published attachment in place until the agent is published again.
This example continues Support helper and its Support desk tool. Otherwise, substitute an existing owned agent and workflow. Every workflow-scoped tool call supplies "workflowId": "<workflowId>".
Find callers and bound accounts
Section titled “Find callers and bound accounts”In the app: open Agents → Support helper → Edit → Tools and inspect the workflow tool. Deletion dialogs list draft attachments, but they omit attachments found only in Live. Those Live-only attachments still block deletion. There is no main-menu Dependencies screen.
With an assistant: start by finding the agent with agent_list and the workflow with workflow_list.
{ "search": "Support helper", "ownership": "mine" }{ "limit": 100 }Search matches substrings, so select one exact displayed-name match. If several match, have the owner choose the ID. Note the selected data.agents[].id as <agentId> and data.items[].id as <workflowId>.
Now read the agent’s tools with agent_tool_list, then the two dependency maps with dependency_map: once with workflowId for the workflow map, and once with no arguments for the account map.
{ "agentId": "<agentId>" }{ "workflowId": "<workflowId>" }The account map covers your owned resources, not every organization resource. Read both sides of each relationship:
| Relationship | Draft field | Live field |
|---|---|---|
| Agent attachments | draftAttachment |
liveAttachment |
| Calling workflows | draftReference |
liveReference |
| Connections | draftUsage |
liveUsage |
| Triggers | draftEnabled |
liveEnabled |
In the account map, draft and live contain agent directActionConnectionIds and workflow connectionIds. These describe saved configuration, not provider health. Chat in Slack connections are absent from the map. Inspect Slack settings separately before deleting a connection.
Change contracts without deleting the flow
Section titled “Change contracts without deleting the flow”Edit existing inputs and outputs and update the callers. Reread renamed input bindings and output keys. Deleting a flow removes its development contract, nodes, and targeted trigger canvases, and clears local subflow references. Agent usage is a warning, not a block. You can test changes immediately, and Live changes when you publish the workflow.
For intentional removal, use Workflows → Support desk → Dev → the flow’s menu → Delete, then confirm Delete. With an assistant, discover the flow with flow_list and { "workflowId": "<workflowId>" }, and save a checkpoint first with workflow_state_save:
{ "workflowId": "<workflowId>", "name": "Before removing escalation flow" }Note the intended data.flows[].id as <flowId>. Keep data.headStateId for definition recovery, subject to restore access. The deletion below, with flow_delete, changes development immediately and takes no confirmation parameter. Call flow_list again afterwards.
{ "workflowId": "<workflowId>", "flowId": "<flowId>" }Confirm the flow is absent, and reread dependencies before publishing. To repoint an agent tool, remove the stale tool as below, then attach its replacement with agent_tool_workflow_add. agent_tool_update cannot change a tool’s workflow or flow.
Detach agents before deleting the workflow
Section titled “Detach agents before deleting the workflow”Deletion is refused while any agent draft or current published version includes the workflow. Other calling workflows do not block deletion. A refusal lists the detach and publish steps for each agent. Do not use deletion as a dependency probe, because it proceeds as soon as nothing blocks it.
In the app: open Agents → Support helper → Edit → Tools, hover the intended workflow tool, choose its trash icon (Remove), then Save changes. For a Live attachment, leave Edit and switch to Test. Review the whole draft, then choose Publish → Publish agent.
With an assistant: note the workflow tool’s data.tools[].id from the earlier list as <toolId>. Remove it with agent_tool_remove, read the tools back with agent_tool_list, and run preflight with agent_publish_preflight.
{ "agentId": "<agentId>", "toolId": "<toolId>" }The read-back and preflight each take { "agentId": "<agentId>" }.
Confirm the tool is absent and resolve preflight blockers. For a Live attachment, review all draft changes and pending Live approvals before publishing. Publishing includes every draft change, moves existing Live conversations to the new version, and expires unexecuted approvals. Stopping running answers and updating Slack cards are best-effort cleanup, and a failure does not undo publication.
Publish the agent with agent_publish and { "agentId": "<agentId>" }, then reread the map with dependency_map and { "workflowId": "<workflowId>" }.
If deleting the agent itself is intended, agent_delete with { "agentId": "<agentId>" } is another exit. It takes no confirmation parameter. It revokes Live access. Conversations and history are retained but inaccessible, and the assistant tools cannot restore the agent.
After handling callers, use Workflows → Support desk’s card menu → Delete and confirm, or call workflow_delete. It deletes without another tool confirmation.
{ "workflowId": "<workflowId>" }Deletion hides the workflow before it cleans up deployed triggers. A cleanup error can mean the workflow is already deleted. Reread the workflow list, then retry deletion with the same ID to finish the cleanup. Stored history remains, but neither the app nor definition restore undeletes the workflow. Inspect remaining Live callers from the earlier map.