Procedure creation, draft updates, and compilation are authoring operations. Compilation places the content in a workflow preview; it does not enforce each sentence as an execution step, publish the agent, or run a conversation.
Write the procedure
Keep the entry condition, requested information, completion condition, and unavailable-action response explicit. For example:trigger for the condition that makes the procedure relevant. Use content for the instructions after entry. A procedure name is a label, so avoid relying on it to explain the task.
Save and inspect
You need an existing agent, an editablebranch_id, and permission to change the agent.
1
Create the branch resource
Use Create procedure with
type: "free_form", a useful name, your written content, and an explicit trigger. The name accepts up to 200 characters. Set folder_parent_id only when placing it in an existing procedure folder.2
Read the draft back
Keep the returned
procedure_id and read Get procedure draft on the same agent and branch. Compare the stored name, content, type, and trigger with the intended task.3
Make a complete draft update
Update procedure draft requires
name, content, and type. Draft content accepts up to 50,000 characters. Keep type: "free_form"; this operation cannot change a procedure’s type.4
Compile for review
Use Compile procedures. Inspect the returned node’s additional prompt and trigger condition. Save a reviewed workflow separately through versions and drafts if you intend to use it in an agent snapshot.
Frequently asked questions
Can I convert this procedure to structured content?
Can I convert this procedure to structured content?
The draft update rejects type changes. Create a separate structured procedure, review its content, and update any references deliberately.
Does a tool name in the text execute that tool?
Does a tool name in the text execute that tool?
No. Text alone does not establish a tool attachment, authorization, or execution. Review the referenced resource and its availability separately.