Creating/modifying entire workflows via script (and AI): is there a supported way?

General Q&A
1

Hi everyone,

I’d like to understand the current state and the plans for building or modifying EasyMorph workflows programmatically, with a focus on AI-assisted development.

What I’ve found so far

  • “Ask AI”, the AI expression generator and the AI-assisted action search are great, but they work at the level of a single action/expression, not a whole workflow.
  • .morph files are XML, and some users already edit them with external AI tools such as Claude Code (see the “Using Claude Code” thread). However, the format isn’t documented, it is “not supposed to be edited manually”, and external edits break the project signature.

My questions

  1. Is there, or is there planned, a supported way to create or modify an entire workflow via script? For example a documented/stable XML schema, a text/JSON representation, an API or SDK, or a command-line tool (e.g. morph-cmd) to generate, validate and re-sign projects.
  2. If not, what’s the recommended approach today for generating .morph files externally? Is there a minimal valid template, guidance on which parts of the XML are safe to touch, and a way to validate a file without opening it in Desktop?
  3. Are there plans for AI-generated workflows inside EasyMorph? For example, describing a process in natural language and getting a draft workflow, or asking the AI to modify an existing one (add a step, change a filter, refactor a module).
  4. Would you consider an MCP server or similar integration, so that external AI assistants can read, build and test workflows (including running them on sample data) in a controlled way?

Why this matters
AI coding assistants are getting very good at writing and editing structured files. A documented, script-friendly project format would let us generate first drafts of workflows, apply bulk changes across many projects, and keep EasyMorph as the place where results are validated on real data.

Has anyone already built something like this? I’d love to hear about your experience.

Thanks!

Claudio

2

Hi Claudio,

We've seen a few EasyMorph customers generating working EasyMorph workflows (.morph files) with Claude and similar AI services. The latest models do a pretty good job.

:information_source: BTW, this Community forum has several hundred example workflows published. Feel free to use them as a reference for AI agents.

Yes, the signature in such generated workflows is broken. You can re-save such a workflow in EasyMorph Desktop to validate the file and sign it digitally. No other application can sign digitally a workflow. This is by design.

You can test whether a .morph file is a valid EasyMorph workflow using the "Project metadata" action. A simple workflow with this action can be run from the command line using CLW (Command-Line Worker) or as a Hub (Server) task.

AI-generated workflows inside EasyMorph are coming in a few months. Prototypes are done and work reasonably well. We're now moving to the product development phase.

Would you consider an MCP server or similar integration, so that external AI assistants can read, build and test workflows (including running them on sample data) in a controlled way?

That's not on the roadmap. Note, however, that EasyMorph workflows can be executed from other applications in a number of ways - CLW, Hub CLI, Hub Task API, etc.

3

Hello,

That’s exactly what we did. We asked Claude to analyze all of our own projects, in addition to EasyMorph’s help pages, the community forum, every published workflow and any reference it could find in the provided solutions. We are now able to have Claude create a .morph file from scratch. We even explained that we don’t want crossing lines between actions and that, if necessary, it should move actions to another group to keep the UI clean and readable. We then review the project and save it so it gets the right signature, because we don’t want to disable that option on our Hub. It’s a huge help on complex projects, but sometimes it’s faster to do the job manually than to explain and define the right context for Claude.

Just to be clear: we only do this to save time. You don’t need AI to use EasyMorph, it’s perfectly approachable on its own :wink:

Regards,

Chris