Sign Up
Loading...

Commands in Twidget

Watch the walkthrough

Commands

Explore the command builder and assemble a workflow from commands.

Recorded with an earlier Twidget interface. Names, control locations and available options may differ; use the linked documentation for current guidance.

Watch tutorial (3:32)

Browse all video tutorials

Commands are the building blocks of Twidget's no-code platform. They function like code statements and can perform various operations such as creating and updating variables, loops, conditionals, retrieving and manipulating data in the datastore, and much more.

Creating a Command

  1. Navigate to the Commands section of your builder.

  2. Click on Add Command. This will open a sidebar.

  3. In the sidebar, you can:

    • Select the command you want to add.

    • Use the search bar to find a specific command.

    • Access your custom functions as commands.

Inputs and Outputs

When you add a command, some commands will require inputs, while others provide outputs that you can use in other commands.

  • To see a comprehensive list of built-in commands and their details, click here.

Managing Commands

Viewing Commands

You can view all your commands and preview their inputs and output variable

Adding Descriptions

For better understanding and managing your business logic, you can add custom descriptions to commands.

Editing Commands

To edit any existing command:

  1. Click on the command you want to edit.

  2. Change its inputs/outputs as needed.

  3. Save your changes.

Get help while editing

When a command has a guide, select the help icon beside its name in the editor header. Its label is View documentation. The guide opens in the documentation panel, keeping your unfinished command changes.

This example shows the help icon beside Has Record, above the command's input and output controls.

Close the documentation panel to continue editing, then save the command when you are ready. Opening a guide does not save or publish your changes.

Deleting Commands

You can delete a command by selecting it and choosing the delete option.

Nested Commands

Some commands allow you to add child commands, for example:

  • Loops: Iterate over a set of items and execute commands for each item.

  • Conditionals: Execute commands based on specified conditions.

Special Commands

  • Return Commands: These commands will halt the execution of the current function, event, or endpoint.

By leveraging these commands, you can create complex workflows and business logic without writing a single line of code.

Related Topics

Test suites

Test a customer journey across several endpoints in a single ordered run. For example: sign in, create an order, retrieve it, then check its status. Every run shares its own isolated database across its steps. Your workspace records are not changed by those database actions. This version supports is...

Safer Releases

Move a reviewed set of published workflows from a Dev workspace to a Prod workspace. Releases let you review the changes together, keep a release history and review a rollback if you need to restore the previous workflows. Prepare your workspaces. Use two existing workspaces in the same organization...

Testing

To pause an isolated test and move through commands, see [Live debugging](/docs/builder/live-debugging). In Twidget, you can easily test your endpoints and functions directly within our code builder. This guide will walk you through the steps to efficiently test your functions to ensure they meet yo...

Dynamic variables in JSON and text

Build JSON bodies and messages using values from your workflow. The Insert variable picker lets you choose inputs, earlier command results, nested object fields and list items without typing their references. Choose a nested field or list item. 1. Open a command value or function output and choose J...

Live debugging

Pause an isolated editor test before a command runs, move through it one step at a time, and inspect its recorded outputs. Use this to find where a calculation or decision begins to differ from what you expected. Start a debug test. 1. Open a server function, endpoint or event and choose Test. 2. Ch...