Digi Arabia Marketing Team
Business Problem:
Teams managing large, complex automation setups — such as multi-step patient communication flows integrated with Hospital Information Systems — face a significant bottleneck: every workflow must be created and edited manually through the visual UI builder. Even minor changes to existing flows require going step-by-step through the builder, making iteration slow and error-prone at scale. There is currently no way to manage workflows programmatically, whether via API, MCP Server, or AI-assisted tooling.
Desired Outcome:
  1. Expose workflow management operations via a respond.io MCP Server and/or API, covering the full CRUD surface that currently exists only in the UI - Specifically, the requested MCP tools include list_workflows, create_workflow, update_workflow_step, and clone_workflow.
  2. AI-assisted workflow implementation — a native integration path (e.g., via Claude) that can translate natural-language instructions into valid workflow configurations, accelerating setup for teams building at scale.
Workaround:
Workflows can currently be exported as a JSON file and re-imported to duplicate or transfer them across workspaces. In theory, the exported JSON could be edited externally and re-imported to simulate a programmatic update. However, this is impractical for external systems or AI to generate valid JSON reliably without reverse-engineering. There is no API endpoint to import a workflow programmatically, so a human must still complete the final step manually.