Node Configuration

Every node in a blueprint needs to be configured before it can run. This page explains how to set up nodes, manage credentials, use expressions, and track message deliveries.

Configuring a node

When you select a node on the canvas, the Node Settings panel opens on the right. Here you'll find:

• Node name -- a label for this step (used to reference its output in expressions)
• Required fields -- inputs the node needs to function (marked with an indicator)
• Optional fields -- additional settings for advanced behavior
• Credential selector -- for nodes that connect to external services
• Value mode toggle -- switch between a literal (fixed) value and a dynamic expression

Fill in the required fields, choose your value modes, and the node is ready.

Credentials

Credentials store sensitive values like API keys, tokens, and passwords securely. Instead of typing secrets directly into node fields, you create a credential once and select it from a dropdown.

Key behaviors:

• Credentials are scoped to a workspace -- your staging and prod credentials are separate
• Credential values are stored securely and never shown again after creation
• You select credentials from a dropdown in the node settings panel

Creating a credential:

1. In the node settings, click the credential dropdown
2. Choose Create new credential
3. Enter a name (e.g., sendgrid-prod) and the secret value
4. Save -- the credential is now available for any node in that workspace

Recommendations:

• Create separate credentials per workspace (staging vs prod)
• Rotate credentials regularly (every 60-90 days)
• Revoke unused credentials promptly
• Never paste secrets into chat, tickets, or version control

Expressions

Expressions let you use dynamic values in node fields -- pulling data from the trigger input or from upstream nodes.

When to use expressions:

• Map a value from one node's output into another node's input
• Build dynamic strings (like URLs or message bodies)
• Apply simple logic or transformations

How to use them:

1. In a node field, switch to Expression mode using the value mode toggle
2. Write your expression or use the variable picker
3. Reference upstream data using paths like nodes.myNode.output.email

Example expressions:

Expression	Result
nodes.trigger.output.customerName	The customer name from the trigger payload
'Order #' + nodes.trigger.output.orderId	A formatted string like "Order #12345"
nodes.httpRequest.output.status === 200	true if the HTTP request succeeded

What you can reference:

• $prev / input -- output from the previous node
• nodes.* -- output from any named node in the blueprint
• helpers.* -- built-in helper functions

Deterministic expressions

Orqio blocks non-deterministic operations (like Date.now() or Math.random()) inside expressions to keep workflow runs reproducible. If you need time-based values, pass them in through the trigger payload or use a dedicated node.

Deliveries

When a node sends a message (email, SMS, push notification), Orqio tracks the delivery -- whether the message was successfully sent, delivered, opened, or failed.

What delivery tracking covers:

• Sent -- the message was handed off to the provider (e.g., SendGrid, Twilio)
• Delivered -- the provider confirmed delivery to the recipient
• Failed -- the message could not be delivered (invalid address, provider error)
• Opened/Clicked -- the recipient engaged with the message (when supported)

Delivery status is visible in the workflow execution report for each node. See Reports for details on how to review execution results.

Configuring delivery nodes:

1. Add a delivery node (e.g., Send Email, Send SMS) to your blueprint
2. Select a template or write content inline
3. Choose a credential for the delivery provider
4. Map recipient fields using expressions (e.g., nodes.trigger.output.email)
5. Optionally configure retry behavior for failed deliveries

Validation

The editor validates your node configuration as you work. Look for:

• Required field indicators -- fields that must be filled before the blueprint can run
• Expression errors -- invalid references or syntax issues
• Credential warnings -- missing or misconfigured credentials

Fix all validation issues before running or publishing your blueprint.

Best practices

• Name nodes descriptively. Use names like fetch-order-details instead of HTTP Request 1. Good names make expressions more readable.
• Keep expressions simple. If an expression is getting complex, break the logic into multiple nodes.
• Test with Run once. Always validate node configuration with test data before publishing.
• Check deliveries. After running a workflow, review the delivery status in the execution report to confirm messages were sent successfully.