Building Workflows by Talking to Miraxa

Describe what you want in a sentence and let Miraxa scaffold the nodes onto your canvas, then fine-tune the result in the properties panel.

Overview

Miraxa is the intelligent layer across your automation, available as the chat surface on every page of Spojit. In the Workflow Designer it can add, delete, update, and connect nodes on the canvas directly from a plain-language instruction. Instead of dragging each node out of the palette and wiring it by hand, you tell Miraxa the shape of the workflow you want and it builds the first draft for you. Because Miraxa knows the page you are on and the workflow you are editing, it places real node types, references the connectors and tools you already have, and respects the variables that earlier steps produce.

The mental model is build-then-refine. Miraxa is best at scaffolding: getting the right nodes onto the canvas in roughly the right order and connected the right way. You then open each node in the properties panel to set exact field values, pick the precise tool, and map variables. Miraxa gets you to a working skeleton in seconds; the properties panel is where you make it production-ready. If an instruction is ambiguous, Miraxa asks a clarifying question before it changes anything, so you stay in control of what lands on the canvas.

Before You Start

Open a workflow in the Workflow Designer. Miraxa edits the canvas you currently have open, so create or open the workflow first.
Add any connections you plan to reference. If you ask Miraxa to call your Shopify or Slack connector, the connection must already exist so the node can resolve it. See Adding a New Connection.
Know the node names and tool names you want. Miraxa works best when you use real terms like Condition, Send Email, or a tool such as send-message.

Steps

Step 1: Open Miraxa in the designer

With your workflow open in the Workflow Designer, open the Miraxa chat panel. Because you are inside the designer, Miraxa already has context on the workflow name, the nodes on the canvas, and how they are connected. You do not need to paste your workflow into the chat.

Step 2: Describe the workflow in one sentence

Type what you want as a single, specific instruction. Name real node types, connectors, and tools, and reference variables with {{ }}. For example:

Build a workflow that watches a mailhook, extracts the PDF invoice, and posts a summary to Slack.

Miraxa scaffolds the nodes onto the canvas: a Trigger set to Mailhook, an Attachment node to pull the PDF bytes, a step to read the document, and a Connector node for Slack. The more specific your sentence, the closer the first draft is to what you need.

Step 3: Add a single node or branch

You do not have to build the whole workflow at once. Ask for one node at a time and tell Miraxa where to attach it. A precise add-and-connect instruction looks like this:

Add a Condition node that checks if {{ order.total }} is over 100 and connect the true branch to a Send Email node.

Miraxa adds the Condition node, adds a Send Email node, and connects the true output of the condition to it. If you do not say which existing node to connect to, Miraxa asks before wiring anything, so a stray edge never appears.

Step 4: Update or delete nodes by name

Miraxa can change nodes that already exist. Refer to a node by its label or type and state the change you want, for example "rename the Slack node to Post to Ops" or "delete the second Transform node." Miraxa updates the node data or removes the node and any edges that depended on it. If your instruction could match more than one node, Miraxa asks which one you mean rather than guessing.

Step 5: Fine-tune in the properties panel

Once the skeleton is on the canvas, click each node to open the properties panel and set the exact configuration. This is where you choose Direct mode versus Agent mode on a Connector node, pick the precise tool such as create-order or send-message, map inputs to upstream variables, set a Schedule cron expression, or fill in Recipients and Subject on a Send Email node. Miraxa gets the structure right; the properties panel is where you confirm every field. To learn the difference between the two connector modes, ask Miraxa "What is the difference between Agent Mode and Direct Mode?" or read How to Choose Between Agent Mode and Direct Mode.

Step 6: Iterate and verify

Keep refining with follow-up sentences: "add a Human node before the Slack step for approval," or "wire the false branch to a Response node." After each change, review the canvas and the properties panel so the workflow matches your intent. When the structure is right, save and run a test. If a run fails, ask Miraxa "Why did my last run fail?" to investigate from the execution detail.

What Miraxa Can Do on the Canvas

Inside the Workflow Designer, Miraxa can:

Add a node: place a new node of a real type (Trigger, Connector, Transform, Condition, Loop, Parallel, Human, Knowledge, Send Email, Attachment, Subworkflow, Response) onto the canvas.
Delete a node: remove a node you name, along with the edges connected to it.
Update a node: change a node's label or other data you describe.
Connect nodes: draw an edge from one node's output to another node's input, including the true or false output of a Condition node.
Delete a connection: remove an edge between two nodes.

When an instruction does not name the target node or branch, Miraxa asks first so it never wires the wrong thing.

Tips

Be specific. Name the exact node type, connector, and tool, and reference variables with {{ }}. "Add a Connector node for Slack using send-message" beats "send a message somewhere."
Scaffold the whole shape first, then refine. Let Miraxa lay out and connect every node, then walk the canvas node by node in the properties panel.
Build in small increments. Adding one node or one branch per instruction keeps Miraxa's edits easy to review and easy to undo.
Always state where to connect a new node. If you do not, Miraxa pauses to ask, which is correct but slower than telling it up front.

Common Pitfalls

Skipping the properties panel. Miraxa scaffolds structure, not every value. A node it adds may still need its tool, inputs, and variable mappings set before the workflow runs cleanly.
Referencing a connection that does not exist. If you ask Miraxa to call a connector you have not added yet, the node cannot resolve at run time. Add the connection first.
Vague instructions. "Make it email someone" leaves Miraxa guessing on recipients, subject, and where to attach the node. Name the node type and the fields you care about.
Assuming Miraxa picked the right branch. After adding a Condition node, confirm that the true and false outputs go where you intended before saving.