cc @Houston Searcy on this one!

All these asks should be complete and live now @Jorge Vargas

Thanks @Houston Searcy, confirmed on our side. create_email_template, update_email_template, email_template_id on update_pipeline_action, and get_pipeline_action are all there, and list_pipeline_actions now flags broken_reference. That covers the whole ask, and it means we can finally repair the dead "Send email Unknown" branches in Deals and Investors.

Next gap, same shape. We can now read a pipeline's entire workflow and edit its stages (create / rename / reorder), but not the steps inside them. We're restructuring our Investors pipeline: collapsing three follow-up stages into one and rebalancing close probability. None of it can be done over the API:

1. Create and delete stage actions, including child actions (send_email, set_variable, move_to_stage, record_task_completed), with position and wait_days.
2. Edit an action's data. update_pipeline_action only takes email_template_id, wait_days and automate. We need to change a set_variable value (probability 20 → 35) and a move_to_stage target.
3. Delete a stage, with a required destination for the prospects in it, and the same consequences/acknowledge flow reorder_pipeline_stages already has. Today a merge leaves two empty stages on the board.

With those three, the restructure becomes one scripted, reviewable change instead of an afternoon in the builder.

Still open from the original post, if you get to them: a warning before deleting a template that actions still reference, and email templates in the audit log.

Nudge on the three asks from my 18/09 reply, @Houston Searcy @Woody Butler — the one that actually blocks us is creating and deleting stage actions over the API.

Concrete: we are restructuring the Investors pipeline so that one Follow-up stage carries the whole ladder — send 4.1, wait, send 4.2, drop probability to 25, wait, send 4.3, drop to 15, then exit to Retry / Unresponsive. The probability drops have to be line items inside the stage, because the point is that probability falls as a prospect progresses through the stage without answering.

What the MCP gives me today for stage actions is list_pipeline_actions, get_pipeline_action and update_pipeline_action (only email_template_id, wait_days, automate). So I can read the whole workflow and repair a broken template reference, but I cannot add a set_variable step, cannot add a second send_email step, and cannot change the value inside an existing set_variable (ours still says 20 where we need 35). create_pipeline_stage exists; there is no equivalent for the actions inside a stage.

Net effect: an agent can design and audit a pipeline end to end and then has to hand the last 20% back to a human in the builder. We are doing exactly that this week, by hand, for a change that is otherwise one scripted pass.

Priority order if it helps you scope it:
1. create_pipeline_action / delete_pipeline_action, including child actions (send_email, set_variable, move_to_stage, record_task_completed) with position, parent_id and wait_days.
2. data writes on update_pipeline_action — at minimum the value of a set_variable and the stage_id of a move_to_stage.
3. Delete a stage, with a required destination for the prospects in it.

Happy to be a test account for any of it.

Sorry Jorge this fell off my radar, I'll take a stab at this today