Actions are the individual steps that make up your application’s workflows. Each action is designed to run in a specific context: on the user’s browser (Frontend) or on the Saasio backend (Server). Understanding this is key to building powerful logic.
Navigation Actions
Navigation Actions
Data & Database Actions
Data & Database Actions
These actions interact with your project’s data stores. They can be triggered from the Frontend or Server but the core logic is always executed securely on the Server.
Create new data
Purpose: Adds a new row of data to a specified Data Table. This is the primary way to save new information, such as a new user signing up or a user creating a new post.
Configuration Steps
- Select Target Table: Choose the Data Table where the new record should be created (e.g.,
Users). - Define Fields to Create: Map each column in your table to the value you want to store. The value can be static (e.g., a fixed string) or dynamic (e.g., the input from a form field).
Handling the Response
This is an asynchronous action. Use state variables to manage the result in your UI:- Result: Select a state variable to store the newly created row, including its unique
idand timestamps. The state’s data type must match the Data Table (e.g.,Users). - Error: Select a
Text (string)state variable to hold any error messages if the creation fails. - Is Loading: Select a
Booleanstate variable that istruewhile the action is in progress.
Update existing data
Purpose: Modifies one or more existing rows in a Data Table based on specific criteria. Use this for actions like saving changes to a user’s profile.
Configuration Steps
- Select Target Table: Choose the Data Table you want to update (e.g.,
Users). - Set Conditions (WHERE Clause): Define the rules to find the specific row(s) to update. For example, “Find the user where ‘ID’ is equal to the current user’s ID”.
- Define Fields to Update: Provide the new values for only the columns you want to change.
Handling the Response
- Result: Select a state variable to store the updated row(s). Note: This action always returns a list (array) of records, even if only one row was updated. Your state variable must be configured as a
Listof the matching Data Table type. - Error: Select a
Text (string)state variable to hold any error messages. - Is Loading: Select a
Booleanstate variable to track the update process.
Delete data
Purpose: Permanently removes one or more rows from a Data Table. This action is irreversible and should be used with caution.
Configuration Steps
- Select Target Table: Choose the Data Table to delete from.
- Set Conditions (WHERE Clause): Define the rules to find the correct row(s) to delete.
If you leave the conditions empty, this action will delete all rows in the table.
Handling the Response
- Result: This action does not return any data. The rows are permanently deleted. You do not need to set a Result state.
- Error: Select a
Text (string)state variable to hold any error messages if the deletion fails. - Is Loading: Select a
Booleanstate variable to provide UI feedback while the deletion is in progress.
Run Redis command
Purpose: Executes a command directly on your project’s Redis instance for advanced caching and real-time features.
Configuration Steps
- Select Data Type: Choose the Redis data type you want to work with (
String,Hash,List,Set, orJson). - Select Redis Command: A new dropdown will show commands specific to the selected data type (e.g.,
Set,Get). - Provide Command Parameters: Fill in the required inputs for the command, such as the
keyandvalue.
Handling the Response
- Result: Select a state variable to store the output of the command. The state’s data type must match the command’s expected output.
- Error: Select a
Text (string)state variable to hold any error messages. - Is Loading: Select a
Booleanstate variable to track the command’s progress.
State & Storage Actions
State & Storage Actions
These actions manage data within the application’s state or the browser’s local storage.
Set data in state
Purpose: Updates the value of a state variable. This action can be used on both the Frontend (to update the UI) and the Server (in API Routes, to pass data between actions).Key Parameters:
Target State: The state variable you want to update.New Value: The new value to be stored.
Set data in local storage
Purpose: Stores a key-value pair in the user’s browser, which persists after they close the page. This is a Frontend-only action.Key Parameter:
Items to Store: Define thekeyandvaluefor each item to store.
Set params
Purpose: Adds or updates query parameters in the page’s URL without reloading. This is a Frontend-only action.
Account Actions
Account Actions
These actions handle user authentication.
Login with credentials
Purpose: Authenticates a user with their email and password.
Sign up and Login with credentials
Purpose: Creates a new user account and automatically logs them in.
Logout
Purpose: Ends the current user’s session and logs them out.
UI & Element Actions
UI & Element Actions
Actions that directly manipulate elements on the page and run exclusively on the Frontend.
Show / Hide element
Purpose: Changes the visibility of a specific UI element.Key Parameter:
Target Element: The element to show, hide, or toggle.
Scroll to element
Purpose: Smoothly scrolls the page to bring a specific element into view.Key Parameter:
Target Element: The element to scroll to.
Change page title
Purpose: Dynamically updates the title of the current page in the browser tab.Key Parameter:
New Title: The new string for the page title.
Conditional Logic
Conditional Logic
The Conditioner can be used to control the flow of logic in any workflow.
Conditioner
Purpose: Evaluates a condition and then runs different sequences of actions. This can be used on both the Frontend and Server.Key Parameters:
Condition to Check: A dynamic expression that must resolve totrueorfalse.Actions if True/Actions if False: The workflows to run for each outcome.
Utility & Custom Actions
Utility & Custom Actions
A collection of powerful actions for handling files, sending emails, validating data, and adding custom logic to your workflows.
Send Email
Purpose: Sends an email using a pre-configured email template.Key Parameters:
Template: Select one of your pre-designed Email Templates.Display Name: The name of the sender that the recipient will see.Send To: The recipient’s email address.Preview: The dynamic data to inject into your email template (e.g., a user’s name or an order number).
Handling the Response
Error: Select aTextstate variable to hold any error messages if the email fails to send.Is loading: Select aBooleanstate variable to track the sending process.
Validate Data
Purpose: Checks if a piece of data matches a pre-defined structure or
rules (a Zod Schema). This action can be used on both the Frontend and
Server.Key Parameters:
Schema: Select the Zod Schema you want to validate against.Data: The data object you want to validate.Is Valid Data: Select aBooleanstate variable that will be set totrueif the data is valid, orfalseif it is not.
Handling the Response
Error: Select aTextstate variable to store any specific validation error messages.Is loading: Select aBooleanstate variable to track the validation process.
Powered by Zod: Data validation in Saasio is powered by Zod
V4, allowing for robust and type-safe schema definitions.
Show toast message
Purpose: Displays a small, temporary notification message (a “toast”) to
the user. This is a Frontend-only action.Key Parameters:
Toast Type: The style of the notification:Success,Error, orInfo.Toast Position: Where on the screen the toast should appear.Message: The text content to display in the toast.Properties: Advanced JSON configuration for things likeduration(in milliseconds).
This action uses the react-hot-toast library.
Trigger Function
Purpose: Executes a custom function that you’ve defined in the function section under the Data tab. This can be used on both the Frontend and Server.Key Parameters:
Function: Select the pre-defined function you want to run from the dropdown.Result: Select a state variable to store the output or return value of the function.
Copy to clipboard
Purpose: Copies a specified piece of text or image to the user’s
clipboard. This is a Frontend-only action.
Download file
Purpose: Prompts the user’s browser to download a file. This is a
Frontend-only action.Key Parameters:
File format: The format of your source data (e.g.,text,base64,blob).File data: The actual content of the file you want to make downloadable.File MIME type: The type of the file, which tells the browser how to handle it (e.g.,application/pdf,image/png).File name: The desired name for the downloaded file.
Export to CSV
Purpose: Converts an array of data into a CSV file and prompts the user to
download it. This is a Frontend-only action.Key Parameters:
File name: The desired name for the downloaded.csvfile (the extension is added automatically).CSV data: The array of objects that you want to convert to CSV format.
Print in console (debug)
Purpose: Logs a value to the browser’s developer console. Essential for debugging and a Frontend-only action.
Change theme
Purpose: Switches the application’s visual theme (e.g., from light to dark mode). This is a Frontend-only action.
Wait
Purpose: Pauses the workflow for a specified amount of time before executing the next action. This can be used on both the Frontend and Server.Key Parameter:
Wait (seconds): The number of seconds the workflow should pause before continuing.
API & SDKs
API & SDKs
Actions for connecting to external APIs and leveraging powerful, natively integrated AI models.
Make an API call
Purpose: Executes a pre-configured API endpoint from your “Data” tab. This
is your primary tool for interacting with any third-party API.
AI SDK
Purpose: Provides a suite of actions that connect directly to generative AI models, powered by the Vercel AI SDK. These actions allow you to build powerful AI-driven features directly into your workflows.
Available AI SDK Actions:
- Generate Object: Sends a prompt and receives a structured JSON object from an AI model.
- Generate Text: Sends a prompt and receives a block of text in response.
- Stream Object: Sends a prompt and receives a structured JSON object back as a real-time stream.
- Stream Text: Sends a prompt and receives a text response as a real-time stream, perfect for chatbot-style “typing” effects.
- Generate Image: Sends a prompt to an image generation model and receives an image.
- Generate Speech: Converts a piece of text into spoken audio.
- Transcribe: Converts an audio file into a text transcript.
- Embedding: Converts text into a vector embedding for use in AI-powered search or similarity tasks.
Events & Analytics Actions
Events & Analytics Actions
Actions for sending tracking events to analytics and marketing platforms. These are Frontend-only actions.
Send Google Tag Manager event
Purpose: Pushes a custom event to the Google Tag Manager data layer, allowing you to trigger tags.
Send Google Analytics event
Purpose: Sends event data directly to Google Analytics (GA4) for tracking user interactions and conversions.