Configure endpoint inputs and use request values in a workflow.
Recorded with an earlier Twidget interface. Names, control locations and available options may differ; use the linked documentation for current guidance.
Watch tutorial (3:04)In Twidget, inputs are essential elements that allow you to configure endpoints and functions. Events do not use inputs.
Endpoint inputs are used to retrieve data from requests. The available types of endpoint inputs are:
Path: Variables that are part of the URL path.
Query: Variables that are part of the query string in the URL.
Header: Information included in the request headers.
Body: Data included in the request body.
Files: Files uploaded in the request. Only endpoint files can be lists.
Function inputs are used to pass data to functions within the platform. They can be of various data types, including:
Text: String data.
Number: Numeric data.
Boolean: True/false values.
Date: Date values.
Object: Complex data structures.
File: File data.
All function inputs can be lists.
Required Inputs: You can mark an input as required. If a required input is not provided, an error will be thrown.
Default Values: Many input types allow you to set a default value that will be used if no input is provided.
Inputs can be referenced throughout the no-code builder. For endpoint inputs, you will need to use specific prefixes:
$body.: For inputs retrieved from the request body.
$headers.: For inputs retrieved from the request headers.
$files.: For files included in the request.
$path.: For variables included in the path.
$query.: For variables included in the query string.
When referencing an input in the value or variable builder, you can:
Select Input as the type.
A dropdown of available inputs will be displayed.
Use the search functionality within the dropdown to quickly find the input you need.
Globals & secrets
Keep shared configuration and private values in one place. Open Global at the top of an endpoint, function or event, or open the manager from Settings. The Variables and Secrets tabs belong to the selected workspace. Use ordinary variables for reusable settings such as a default page size or service...
Realtime channels
Send live updates to your app while your customers are signed in. Use a channel for order progress, notifications or a shared activity feed, instead of asking the app to repeatedly check for changes. Realtime messages are temporary notifications. Keep important information in your database so your a...
Publishing Changes
With Twidget's publishing feature, you can seamlessly push your changes live, ensuring that your updates take effect on the specified endpoint, function, or event. This feature also allows for version control, enabling you to revert and manage different versions of your changes effectively. Steps to...
Commands in Twidget
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...
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...
