The Decile MCP can read email templates (list_email_templates, get_email_template) but cannot create or update them. That's the gap I'd most like closed.
Why it matters more than it sounds. An agent connected to Hub can now read a pipeline end to end — stages, actions, queued executions, templates, prospects — and it can write almost everything: prospects, organizations, notes, deal memos, newsletters with full HTML bodies, even Base posts. Email templates are the one piece of workflow content with no write path at all. So an agent can diagnose a broken workflow completely and repair none of it.
Our concrete case: five stage actions in our Deals pipeline point at templates that return 404, and there are more on the Investors money path. Every affected branch is dead — the action renders as "Send email Unknown" and can't fire. With write access this is a ten-minute scripted repair. Without it, it's manual UI work across two pipelines, and presumably across every account where this happened.
What I'm asking for, in priority order:
- Create and update email templates over the API/MCP — name, subject, body, pipeline, attachments.
- Set an action's email_template_id so a broken reference can be re-pointed programmatically. Without this, creating a replacement template doesn't actually repair anything: the new template gets a new id and the action still points at the dead one.
- Read-back of an action's full config, so an agent can verify the repair rather than assume it.
Secondary — the guardrails that would have prevented this: warn before deleting a template that stage actions still reference and offer to re-point them; surface broken references somewhere visible per pipeline instead of only at send time; and include email templates in the audit log, which today covers people, organizations, prospects, funds, capital accounts, chats and users, so there's no way to see who removed a template or when.