Using Transform Nodes (Plaintext Mode)

Use plaintext transforms for flexible text templating and simple data mapping.

Overview

A Transform node in Plaintext mode gives you a single free-form text area. You write a template using {{ }} expressions, and the node outputs the rendered string. Optionally, you can ask Spojit to parse that string as JSON so downstream nodes receive a structured object.

Plaintext mode is the fastest path between two steps when you just need to glue some values together: build a message body, assemble a URL, or hand-craft a JSON payload for a connector that does not have a typed schema.

When to Use Plaintext Mode

• Composing email or chat message bodies from prior step output.
• Building API request bodies for a generic HTTP connector.
• Producing a single string that downstream steps consume as-is.
• Quickly extracting one or two fields without defining a full structured schema.

Configuration

1. Drop a Transform node onto the canvas.
2. In the properties panel, set the mode to Plaintext.
3. Write your template in the text area, using {{ step.field }} expressions to interpolate values.
4. Optionally enable Parse as JSON if the rendered string is JSON and downstream nodes need it as an object.

Configuration Reference

• Mode - set to Plaintext.
• Template - the free-form text with embedded {{ }} expressions.
• Parse as JSON - when enabled, the output is parsed before being passed downstream. Invalid JSON fails the step.

Usage Examples

• Order confirmation body - Hello {{ step1.customer.first_name }}, your order #{{ step1.order_number }} shipped via {{ step2.carrier }}.
• JSON payload for a generic webhook - render a small JSON object, enable Parse as JSON, then pass the result to a Connector node.

Tips

• Use plaintext mode for output that is fundamentally text. Use Structured mode when the output is an object with named typed fields.
• Keep templates readable - line breaks in the editor map to line breaks in the output, which matters for email bodies.
• If you only need a single value, reference it directly downstream with a template expression instead of adding a transform.

Common Pitfalls

• Enabling Parse as JSON on output that is not valid JSON (stray commas, unquoted keys) fails the step at runtime.
• Mixing text with a template expression coerces everything to a string. If you need to preserve a number or object, reference the value alone.
• Referencing a step that has not run yet (wrong branch, wrong order) renders an empty value silently.

Related Articles

• Using Transform Nodes (Structured Mode)
• Working with Variables and Templates
• Using Send Email Nodes
• Using Connector Nodes in Direct Mode
• Using Condition Nodes

Learn More

• Transform node documentation