Block 1 - Set_Variables
- Type / Role
- n8n-nodes-base.set - set
- Config choices
- Version 3.4
This workflow is provided as-is. Please review and test before using in production.
POML → Prompt/Messages (No Deps) What this does Tu...
n8n-nodes-base.set, n8n-nodes-base.code, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatopenai, n8n-nodes-base.stickynote, n8n-nodes-base.manualtrigger
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by RealSimple Solutions.
Original n8n.io sourceTurns POML markup into either a single Markdown prompt or chat-style messages[] — using a zero-dependency n8n Code node. It supports variable substitution (via context), basic components (headings, lists, code, images, tables, line breaks), and optional schema-driven validation using componentSpec + attributeSpec.
Created by Real Simple Solutions as an n8n template friendly POML compiler (no dependencies) for full POML feature parity.
Teams who author prompts in POML and want a template-safe way to turn them into either a single Markdown prompt or chat-style messages—without installing external modules. Works on n8n Cloud and self-hosted.
This workflow converts POML into:
prompt (Markdown) for single-shot models, ormessages[] (system|user|assistant) for chat APIs when speakerMode is true.It supports variable substitution via a context object ({{dot.path}}), lists, headings, code blocks, images (incl. base64 → data: URL), tables from JSON (records/columns), and basic message components.
componentSpec (allowed attrs per tag), attributeSpec (typing/coercion), and optional context.prompt or messages[].> Add a yellow Sticky Note that includes this description and any setup links. Use additional neutral sticky notes to explain each step.
Import the template.
Open the first Set node and paste your componentSpec, attributeSpec, and context (examples included).
In the Code node, choose:
speakerMode: true to get messages[], or false for a single prompt.listStyle: dash | star | plus | decimal | latin.Run → inspect prompt/messages in the output.
<system-msg>, <user-msg>, <ai-msg>) in your POML when using speakerMode: true.componentSpec/attributeSpec to validate or coerce additional tags/attributes.context (e.g., bulleted, csv) for display, or add a small Set node to build them on the fly.This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Convert POML to AI-Ready Prompts & Chat Messages with Zero Dependencies |
|---|---|
| Complexity | intermediate |
| Nodes | 10 |
| Categories | Engineering, Multimodal AI |
| Author | RealSimple Solutions |
| Published | 19 Aug 2025 |
Use the JSON export at /data/workflows/7609/7609.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
POML → Prompt/Messages (No Deps) What this does Tu...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Engineering, Multimodal AI use case.