Ritemark Flows
What if you could chain AI tasks together and run them with a single click?
Flows is Ritemark's visual workflow editor. Instead of running prompts one at a time in the chat, you build a diagram that executes automatically. Create a workflow once, run it whenever you need fresh content.
Opening Flows
Click the Flows icon in the Activity Bar (the vertical bar on the left side of Ritemark). This opens the Flows panel where you manage your workflows.
The Flows editor with a document summarizer workflow
To create a new workflow, click New Flow at the top of the panel. Give it a name that describes what it does.
Understanding Nodes
Flows are built from nodes. Each node does one thing, and you connect them to create a sequence.
Trigger Node
Every flow starts with a Trigger. This is where you define input variables that the rest of the flow can use.
The Trigger node with an input variable defined
Click Add Input to create a variable. Give it a name like topic or document. When you run the flow, you'll be prompted to enter values for these inputs.
LLM Prompt Node
The LLM node sends a prompt to OpenAI and outputs the generated text.
The LLM node configured with a system prompt and user prompt
Configure it with:
- Model: Which GPT model to use
- System Prompt: Sets the AI's behavior and role
- User Prompt: The actual request (can include variables)
Use double curly braces to reference variables: {{topic}} inserts the topic from your Trigger node.
Image Generation Node
Creates images using GPT Image 1.5.
The Image node configured to generate an illustration
The prompt can reference text from previous nodes, so you can generate images based on AI-written descriptions.
Save File Node
Writes content to a file in your workspace.
The Save File node configured to output markdown
Choose the folder, filename, and format (markdown, CSV, or image). The content comes from a connected node.
Claude Code Node
The Claude Code node is different from the other nodes. Instead of sending a single prompt and receiving a single response, it launches an autonomous AI agent that can read files, reason through complex problems, and produce structured output.
The Claude Code node in the Flows editor -- agentic automation, visual style
Configure it with a Task field that describes what you want the agent to accomplish. The task can reference variables from upstream nodes using double curly braces, just like the LLM node. For example: "Analyze {{filename}} and identify the three key findings."
The Claude Code node requires the Claude Code CLI to be installed and an ANTHROPIC_API_KEY configured on your machine. This is separate from the OpenAI key used by LLM and Image nodes. See our Set Up Claude Code guide for installation steps, or read the full Claude Code Node article for detailed configuration and workflow examples.
Building Your First Flow
Here's how to create a simple document summarizer:
Start by dragging a Trigger node onto the canvas. Add an input called document with type "File". This lets you select a file when running the flow.
Next, add an LLM Prompt node. Connect the Trigger's output to the LLM's input by dragging between the handles. Configure the LLM with a system prompt like "You are a document summarizer" and a user prompt like "Summarize this: {{document}}".
Finally, add a Save File node. Connect the LLM's output to it. Set the filename to summary.md and format to Markdown.
Click Run Flow, select a document, and watch the summary appear in your workspace.
Success: You've just built your first workflow. The same pattern works for any multi-step AI task.
Running Flows
Click Run Flow in the toolbar. If your Trigger has inputs without default values, you'll be prompted to enter them.
The execution panel shows real-time progress:
- Which node is currently running
- Output from completed nodes
- Any errors that occur
- Total execution time
Each node makes API calls, so complex flows take longer. Image generation is slower than text generation.
Tips for Better Flows
Start simple. Build a 3-node flow (Trigger, LLM, Save File) before attempting complex workflows. Make sure each piece works before adding more.
Use descriptive names. Name your variables clearly: blog_topic is better than t. Future you will thank present you.
Test incrementally. Run your flow after adding each node. It's easier to debug when you know which step failed.
Use Auto-arrange. Click the layout button to automatically organize messy node arrangements.
Configuring API Keys
Flows uses two different API providers depending on the node type. LLM and Image nodes require an OpenAI API key, while the Claude Code node requires an Anthropic API key.
To configure your OpenAI key, open Command Palette with Cmd+Shift+P and run "Ritemark: Configure OpenAI API Key". You can also access settings from the gear icon in the Flows sidebar.
For the Claude Code node, set the ANTHROPIC_API_KEY environment variable in your shell profile. See Set Up Claude Code for detailed instructions.
Where Flows Are Saved
Your workflows live in .ritemark/flows/ inside your workspace. Each flow is a JSON file containing node definitions, connections, and configurations.
You can share flows by copying these files. Others can place them in their own .ritemark/flows/ folder to use them.
Troubleshooting
Flow won't run: Check that all nodes are connected (no orphaned nodes), the Trigger node is present, and your OpenAI API key is configured.
LLM returns error: Verify your API key is valid and you have available credits. Review your prompt for issues.
Image generation fails: GPT Image 1.5 requires specific API access. Check that your account has it enabled. Try a simpler prompt if content filters might be triggered.
Claude Code node fails: Make sure the Claude Code CLI is installed (claude --version in terminal) and your ANTHROPIC_API_KEY is set. This is a different key from the OpenAI key used by LLM nodes.
Nodes won't connect: Drag from output handles (right side) to input handles (left side). Not all node types can connect to each other.
Quick Reference
| Action | How |
|---|---|
| Create new flow | Flows panel > New Flow |
| Add node | Drag from palette to canvas |
| Connect nodes | Drag output handle to input handle |
| Configure node | Click node, edit in right panel |
| Run flow | Click Run Flow button |
| Undo/Redo | Cmd+Z / Cmd+Shift+Z |
| Delete node | Select and press Delete |
| Auto-arrange | Click Auto-arrange button |
Need Help?
If you run into issues with Flows, check that your API keys are configured correctly (OpenAI for LLM/Image nodes, Anthropic for Claude Code). For detailed Claude Code setup, see the Claude Code Node guide. For other problems, visit our troubleshooting guide or reach out via the feedback form in the app.
Happy automating!