Workflow Tools

​

Overview

​

When to Use

• Business logic is well-defined and consistent
• You need visual traceability for debugging
• Non-developers need to build or maintain tools
• Processes involve multiple sequential steps
• You want built-in monitoring and audit logs

​

Good Fit Examples

​

Tool Creation

​

Create a New Tool

1. Log in to your account and click Tools from the list of modules.
2. On the Tools page, click Create a new tool. The New tool dialog box is displayed.
3. Enter a name and a brief description for the tool and click Create. The tool is created, and the Tool Flow option is displayed. You can start creating your tool flow immediately.

​

Tool Templates

• Pre-built templates — Ready-to-deploy flows with pre-configured integrations (for example, an email auto-replier or automated grading system).
• Customizable templates — Node-based flows you can tailor to your business needs using the various node types on the canvas.

• Quick setup — Significantly reduces deployment time and costs.
• Customizable — Retain essential prebuilt elements and remove unnecessary ones.
• Seamless integration — Import directly into existing flows and automate key actions within minutes.
• Enhanced developer experience — Eliminate repetitive tasks with minimal coding effort.

​

Tools Library Marketplace

​

Access and Install a Tool Template

1. Log in and click Tools from the list of modules.
2. Click Tools on the top navigation bar.
3. If adding your first tool, click Tool templates. Otherwise, on the All Tools or My Tools tab, click Tool Templates to access the Tools Library/Marketplace.
4. Scroll to the Tools section. Use the left filter to select Categories and Tasks.
5. Click the required template to view its information window, which includes the template name, description, compatible LLM model, configuration status, prebuilt flow preview, related templates, and developer details.
6. Click Install to connect to the Marketplace and import the template along with its pre-configured flow.

• After it is installed, the template shows in My Tools.
• A PDF document with key details (input/output, environment variables, usage guide, key components) is displayed for download.
• The first installation retains the original template name and description.
• Reinstalling the same template appends a unique sequential number: Tool Template Name_<sequential-number> (for example, Automatic grading system_1743151769005).
• Canvas-level errors may appear on fresh installations (for example, unconnected AI nodes or empty API nodes). Click the warning icon to view and fix errors.

​

Managing a Tool Template

1. Open the Tools dashboard and click the required tool.
2. Click Configurations in the left navigation menu.
3. Make the required changes or proceed to delete the tool.

1. Scroll to the Delete tool section on the Configurations page.
2. Click Proceed to delete, then confirm by clicking Delete.

​

View and Manage Tool Flow

1. Click the required tool template on the Tools dashboard.
2. Click Go to Flow. The prebuilt flow is displayed on the canvas.
3. Manage nodes and their configurations, edit input and output, and run the flow to customize as needed.

​

Import a Tool

​

Import to Create a New Tool

1. Log in and click Tools from the list of modules.
2. Click the Tools tab on the top navigation bar.
3. Click Import Tool (or the Import tool icon on the Tools dashboard if tools already exist).
4. In the Import tool window, provide: Required:
   • Tool Name — Provide a unique name to avoid conflicts with existing tools.
   • Flow definition file — Upload flow_definition.json. Includes the tool`s canvas definitions (node definitions) and AI node configurations, including prompts, hyperparameters, and timeout information.
   Optional:
   • App definition file — Upload app_definition.json. Includes general tool version information and guardrails.
   • Environment variable file — Upload env_variables.json. Includes environment variables set for the tool.
5. Click Import. The system redirects you to the Tool Flow page. Click Go to flow to access the canvas.

• The tool is listed under All tools and My tools with status In Development.
• Node types, descriptions, input/output variables, scanners, and sync/async setup are preserved.
• If the AI nodes model doesnt match available models in the current account, the model field is left empty but all prompt definitions are imported.
• API keys are not transferred during import.
• The imported tool cannot be shared with other users.

​

Import Best Practices

• Export first — Always export the current tool version before importing to ensure all configurations are available.
• Check environment dependencies — Verify that the correct model is available, linked tools exist by the same name for auto-linking, and environment variables and configuration files are compatible.
• Import in order — Import the parent tool and any associated versions in order, and ensure there are no conflicts with existing tools.

​

Tool Flow

​

Overview

​

Interface

​

Node Types

​

Control Nodes

​

Action Nodes

​

AI Nodes

​

Managing Nodes

​

Add Nodes

1. Drag from the bottom panel — Scroll through available node types and drag them onto the canvas.
2. Use the left panel (Assets) — Select and place preconfigured nodes directly onto the canvas.
3. Use the blue plus icon (+) on a node — Hover over the grey dot on any node to reveal the blue + icon. Click to choose:
   • Add new node — Instantly places and connects a new node.
   • Add existing node — Select a previously added node.

​

Rename Nodes

1. Right-click the node on the canvas.
2. Select Rename from the context menu.
3. Enter the new name in the Node Name field of the configuration panel.

​

Delete Nodes

​

Rearrange Nodes

• Auto Arrange — Right-click the canvas and select Auto arrange to automatically reposition all nodes for a cleaner layout.
• Show/Hide UI or Grid — Right-click the canvas to toggle visual elements.

​

Connecting Nodes

• Canvas-based (visual) — Drag and drop to connect nodes directly on the canvas.
• Node configuration panel — Define success and failure paths from the node`s property panel.

​

Sequential vs. Parallel Execution

​

Designing Sequential Flows

1. Hover over the blue + icon or grey connector dot on the source node.
2. Click and drag a line to the destination node.

1. Hover over the node, click the blue + icon, and choose Add New or Add Existing. The node is added and connected in sequence.

1. Click the node to open the Configuration Panel on the right.
2. Go to the Connections tab.
3. Under On Success or On Failure, use the dropdown to add a new node or connect to an existing, unused node.

• All paths must converge at an End Node.
• Sequential chains are arranged left to right for clarity.
• Logs display outputs in the exact order nodes are triggered, making debugging easier.
• Only one connection can exist per outcome (On Success or On Failure) in a sequential flow—any additional connections are treated as parallel branches.

​

Designing Parallel Flows

• Simple Parallel — A single node branches to multiple child nodes running independently. Use when tasks can occur simultaneously without dependencies.
• Nested Parallel — A parallel branch contains its own parallel branches. Useful for multi-step logic where each level does independent work.
• Conditional + Parallel — Combine condition nodes with parallel execution. Based on logic (for example, if/else), different sets of parallel branches are triggered.

1. Hover over the node and click the blue + icon.
2. Select Add new or Add existing to add multiple nodes as parallel branches.

1. Drag from the source node to another node on the canvas. Repeat from the same parent to form additional parallel branches.

1. Click the node and open the Configuration Panel.
2. Go to the Connections tab.
3. Use the On Success or On Failure dropdowns and click + Parallel Node to add more branches.

Limits and rules:

• Maximum 10 outgoing connections from a single node.
• No duplicate connections from the same parent node.
• No backward loops—connecting a node to an earlier node in the flow is blocked to prevent logic cycles.

• All branches from a node run at the same time.
• The flow waits for all parallel branches to complete before moving to the next step.
• End node outputs from all branches are combined before passing to the next node.
• The canvas layout expands automatically to fit multiple branches.
• Logs show branch-specific outputs grouped under the parent node, labeled (A, B, C) for each path.

​

Manage and Remove Connections

1. Click the arrow/line between two nodes.
2. Click the Delete icon. The nodes remain on the canvas but are no longer linked.

1. Open the panel by selecting a node.
2. In the Connections tab, click the Delete icon next to the connection to remove.

​

Manage Input and Output

• Input Variables — Provide initial data to the flow. Accessible immediately after the Start node using the syntax: context.steps.Start.inputVariable
• Output Variables — Store and return derived values from the flow. Set in any node; for example, in the End node, assign results using: {{context.steps.AInode.output}}

​

Add Input Variables

1. Click Manage I/O at the top of the Tool flow canvas, or click the Start node. The Manage Input & Output dialog is displayed.
2. On the Input tab, click + Add input variable.
3. Provide a Name (key) for the input variable (for example, Product_ID).
4. Select a Type from the dropdown:
   • Text, Number, or Boolean — An optional Default value field appears.
   • Remote file — A File URL timeout field appears. Set the timeout between 5 minutes and 7 days (default: 5 minutes).
   • List of values (Enum) — Add predefined allowed values via Add Values +. Enable Default value to select from defined values. The system validates input against enum values and displays an error for invalid entries.
   • JSON — A schema editor appears. Define the JSON schema and ensure the default value matches the schema. If the JSON is invalid, execution fails with an error.
5. Enable the Mandatory toggle if the field is required.
6. Click Save. The input variable appears on the Input tab.

​

Add Output Variables

1. Click Manage I/O at the top of the canvas.
2. On the Output tab, click + Add output variable.
3. Provide a Name (key) and select a Type: String, Number, JSON, or Boolean.
4. Click Save.

​

Building a Workflow

​

Step 1: Create the Tool

1. Navigate to Tools → + New Tool
2. Select Workflow Tool
3. Enter name and description:

name: get_weather
description: |
  Retrieves current weather conditions for a specified location.
  Returns temperature, conditions, and forecast summary.

​

Step 2: Define Input Parameters

parameters:
  location:
    type: string
    description: City name or coordinates
    required: true

  units:
    type: string
    enum: [celsius, fahrenheit]
    default: celsius

​

Step 3: Build the Flow

​

Step 4: Configure Nodes

url: https://api.weather.com/v1/current
method: GET
headers:
  Authorization: Bearer {{env.WEATHER_API_KEY}}
query_params:
  q: "{{input.location}}"
  units: "{{input.units}}"

return {
  temperature: response.main.temp,
  condition: response.weather[0].description,
  humidity: response.main.humidity,
  location: response.name
}

​

Step 5: Define Output

output:
  type: object
  properties:
    temperature:
      type: number
    condition:
      type: string
    humidity:
      type: number
    location:
      type: string

​

Step 6: Test

1. Click the Run flow icon at the upper right corner of the canvas.
2. Provide sample input values in the Run dialog.
3. Click the Debug icon to open the debug log and monitor execution.
4. Review the execution trace, output, and any errors.
5. For a successful flow, copy output results using the Copy icon.

​

Step 7: Deploy

​

Running and Testing Flows

• Successful flow — Copy output using the Copy icon. Overall runtime is displayed.
• Flow errors — An error message is displayed; the output key appears empty with JSON-formatted failure output.

​

Debug Log

• Flow input values — The values provided for input variables.
• Flow-level log details — Overview of flow initiation and progress.
• Node-level information — Success or failure status per node, with links to additional details.
• Tool calling details — Logs of any tools called during execution (AI nodes only), including inputs (JSON), responses, and errors. A separate panel shows detailed tool traces.
• Node metrics per node:
  • Initiated On — Timestamp when the node was triggered.
  • Executed On — Timestamp when execution completed.
  • Total Time Taken — Duration of node execution.
  • Tokens — Token usage (AI nodes only).

​

Time Metrics for API and AI Nodes

• Node processing time — Time to complete execution.
• API Response time — Time waiting for the external API response.

• Node paused at — Timestamp when the node paused waiting for response.
• Node resumed at — Timestamp when the node resumed after receiving response.
• Total wait time — Duration between pausing and resuming.
• Node processing time — Time spent processing after resuming.

• Node processing time — Time to complete execution.
• LLM response time — Time for the connected model to return a response.

​

Conditions and Branching

// Comparisons
input.amount > 100
response.status === "success"

// Logical operators
input.priority === "high" && input.urgent === true

// String operations
input.email.includes("@company.com")

​

Loops

loop:
  collection: "{{response.items}}"
  item_variable: current_item
  max_iterations: 100

​

Error Handling

error_handling:
  on_error: continue  # or: stop, retry
  retry:
    attempts: 3
    delay_ms: 1000
  fallback:
    node: error_handler

​

Common Node Issues

​

Flow Versions

​

Create a New Version

1. Click the down arrow on the canvas header. The Flow versions dialog is displayed.
2. Click the + icon to save the current version.
3. Enter a Version name and Description, then click Save.

​

Tool Flow Change Log

• Event tracking — Records each change when a user exits a property field in a node, capturing the timestamp, responsible user, and change details.
• Filters — Filter by date range, node type, or specific team member for enhanced searchability.

​

Access the Change Log

1. Open the tool flow for the tool you want to audit.
2. Click the History/Log icon at the top-right corner of the page. The change log panel opens on the right, showing the most recent changes first.

• Timestamp of the change
• Brief description of the change
• Name of the user who made the change

​

Filter the Change Log

• Date filter — Click the Calendar icon to select a specific date range.
• Filter By — Click the Filter icon to filter by User or Node Type. The log updates dynamically based on the selected filters.

​

Execution Modes

​

Synchronous

Request → Execute all nodes → Return response

​

Asynchronous

• Push endpoints — Actively send response data to the client via webhook as soon as it becomes available. Useful when the client needs immediate notification of changes.
• Poll endpoints — The client periodically checks to retrieve response data on its own schedule. Useful when the client only needs updates at specific intervals.

​

Deploy a Tool

​

Deploy a Tool

1. Log in and click Tools from the list of modules.
2. Select the tool you want to deploy.
3. Click Tool endpoint in the left menu.
4. Click Deploy. The Sync and Async poll endpoints are generated.
5. To generate an Async push endpoint:
   1. Click the Async push tab and click Enable/Settings.
   2. In the Sync/Async mode setup popup, enable the Enable async toggle.
   3. Provide the URL of your external application and enter the access token.
   4. Set the timeout:
      • Set timeout — Range: 60–600 seconds (default: 180 seconds).
      • No timeout — Process the request without a time limit.
   5. Click Save. The async push endpoint is created.

​

Redeploy for Flow Changes

1. Go to Tool endpoint in the left navigation.
2. Click Deploy at the top-right corner of the page.

​

Configure a Tool

​

Sync/Async Mode Setup

1. Click Configurations in the left navigation, then click Setup sync/async.
2. In the Sync/Async mode setup popup:
   • Synchronous mode timeout — Range: 60–300 seconds (default: 180 seconds).
   • Asynchronous mode — Enable the Enable async toggle, provide the external application URL, enter the access token, and set the timeout (60–600 seconds, or No timeout).
3. Click Save.
4. Go to Tool endpoint and click Deploy to redeploy with the new mode.

​

Environment Variables

1. Click Configurations in the left navigation, then click Manage environment variables.
2. Click Add or Add variable.
3. Provide:
   • Variable name — Descriptive name.
   • Secure variable — Enable the toggle to mark as a secret.
   • Value — Desired value.
   • Notes (optional) — Usage notes or purpose.
4. Click Save.

url: "{{env.API_BASE_URL}}/endpoint"
headers:
  Authorization: "Bearer {{env.API_KEY}}"

​

Undeploy the Tool

​

Delete the Tool

​

Export a Tool

​

Steps to Export

1. Log in and click Tools from the list of modules.
2. Select the tool you want to export.
3. Click Configurations in the left navigation.
4. Scroll to the Export tool section. The currently deployed version is selected by default.
5. To change, select another version from the dropdown.
6. Click Export. A success message appears after validation and export complete.

​

Import a Tool as a Version

• flow_definition.json
• app_definition.json
• env_variables.json

​

Steps to Import a Tool as a Version

1. Log in and click Tools from the list of modules.
2. Select the parent tool and click Configurations.
3. Scroll to the Import tool section and click Import.
4. (Optional) Select Back up your current tool to preserve the data of the version being replaced. The system automatically exports and saves the .zip package to the designated location.
5. Click Import in the confirmation dialog.
6. In the Import Tool window, upload the required JSON files and click Import.

​

Resolve Conflicting Environment Variables

1. Select the Conflicting variables tab.
2. For each conflict, select Overwrite (use the imported value) or Keep existing (retain the current value).
3. Click Proceed to continue importing.

1. Click the three-dots icon for the variable and select Edit.
2. Update the values and click Save.

​

API Keys

​

Create an API Key

1. Log in and click Tools from the list of modules.
2. Select the required tool from the list.
3. Click API keys in the left panel.
4. Click Create a new API key.
5. Provide a descriptive name for the key and click Generate key.
6. Click Copy and close to save the key to your clipboard. Share this key with authorized users as needed.

​

User Roles and Permissions

​

Invite Users

1. Log in and click Tools from the list of modules.
2. Select the required tool.
3. Click Sharing & Permission in the left navigation bar. Existing collaborators are listed.
4. Click Invite (visible only to account owners). The Invite Users dialog is displayed.
5. Enter users` email addresses and click Invite to grant access.

​

Monitoring and Observability

​

Tool Monitor

• Performance Tracking — Monitor response times, execution patterns, and overall efficiency.
• Dual-View Analytics:
  • All Runs — Comprehensive data on all tool run instances (all endpoint calls).
  • Model Runs — Focused analytics on AI node executions.
• Detailed Metrics — Total runs, average response times (P90 and P99), failure rates.
• API Key Usage Monitoring — Track API key utilization across the tool ecosystem.
• AI Node Analysis — Performance insights per individual AI node.
• Advanced Filtering — Time-based searches and custom filters to drill down into specific scenarios.
• Detailed Run Information — Comprehensive logs and debug information per tool run.

​

Accessing Tool Monitor

1. Log in and click Tools from the list of modules.
2. On the All tools page, click a deployed tool. Tool monitoring is only available for tools deployed in production.
3. Click Tool monitor in the left navigation pane.
4. Click All runs or Model runs to view the respective data.
5. Click any row for detailed run information in the right panel.

​

All Runs Tab

​

Model Runs Tab

​

Viewing Detailed Run Information

• Run ID / Request ID
• Response Time
• Debug icon — Click to view debug log details.
• Input — Input sent to the tool.
• Flow log — Node-level success/failure details, including scanner information for AI nodes.
• Output — Tool output for successful runs, with copy option and token view.

​

Timeout Impact on Endpoints

​

Searching and Filtering

• Manual Search — Use the search box in the top right to find specific runs by keyword.
• Time-based Search — Click the calendar button, select a predefined range (last day, week, month, or year) or set custom dates, then click Apply.
• Custom Filters — Click the Filter icon, click + Add filter, select Column/Operator/Value, and click Apply. Combine multiple filters using AND/OR operators for more precise results.

​

Tool Run Errors

​

Audit Logs

• Event Name — The specific event or action that occurred.
• Category — The module or entity affected.
• User Name — Who performed the action.
• Date and Time — When the event occurred.
• Description — Detailed information about the action.

​

Access Audit Logs

1. Log in and click Tools from the list of modules.
2. On the All tools page, click the desired tool.
3. In the left navigation pane, click Audit logs. The Audit logs page is displayed.
4. Click each row to view more details about the event.

​

Guardrails

guardrails:
  input_scanning: true
  output_scanning: true
  scanners:
    - toxicity
    - pii_detection
    - jailbreak_detection

​

PII Handling

• Before execution, input fields are automatically scanned for declared PII patterns in the application config.
• Inputs identified as PII are masked and passed to the tool in redacted form.
• If the Workflow Tool is granted access to the original PII value, it can securely unredact and use it internally—while monitoring, debugging logs, and execution traces continue to show only masked values.

​

Accessing App Environment Variables

1. Add the variable to a namespace.
2. Associate the namespace with the workflow agent.

​

Tool Creation Scope

​

Tools Library

​

App-Scoped Tools

• App-scoped tools are not shared across other apps.
• Updates to app-scoped or imported tools apply only to the local copy and do not impact the original library tool.
• Ideal for app-specific logic or experimentation.

​

Best Practices

​

Keep Workflows Focused

​

Use Meaningful Names

# Good
get_customer_orders
validate_shipping_address
process_refund_request

# Avoid
workflow_1
helper
do_stuff

​

Handle Errors Gracefully

​

Test Edge Cases

• Invalid inputs
• API failures
• Empty responses
• Timeout scenarios

​

Document Complex Logic

​

Flow Design Tips

• Use parallel structures to speed up independent tasks.
• Use sequential paths when steps depend on the results of prior steps.
• Combine both styles to build hybrid flows for advanced logic.
• Always monitor node limits and watch for visual cues — one line = sequence, branching lines = parallel.
• Regularly use Auto Arrange to clean up the canvas.
• Ensure every logical branch concludes at an End Node.