Uify Docs
  • Welcome to Uify
  • Getting started
    • Quickstart
  • Editor
    • Visual UI Builder
    • Component Properties
    • Environments & Deployment
  • Writing code
    • Component properties
    • Actions
      • Managing actions
      • Triggers
      • Execution model
      • Preview
    • State variables
    • Exposed variables
    • Type safety
    • Managing usages
    • Console
  • Data Management
    • Data sources
    • Table preview
    • Secrets
  • Integrations
    • BigQuery
    • Google Sheets
    • Microsoft SQL
    • MongoDB
    • MySQL
    • OpenAI
      • Manual mode (chat)
      • Manual mode (complete)
      • Text to structured data
    • Rest API
    • Salesforce
    • Slack
    • Snowflake
  • Collaboration
    • Permissions
  • Component reference
    • Shared properties
    • Button
    • Chart
    • Checkbox
    • Container
    • Data Grid
    • Form
    • Funnel
    • Inputs
    • Modal
    • PDF
    • Radio group
    • Selects
    • Slideout
    • Switch
    • Table
Powered by GitBook
On this page

Was this helpful?

  1. Writing code

Actions

PreviousComponent propertiesNextManaging actions

Last updated 2 years ago

Was this helpful?

Actions are the key ingredient for adding logic to your applications, and for managing interactions with your datasources. Almost like native JavaScript functions, they are small units of code that perform a specific task. They are particularly useful for:

  • Reading and mutating UI component state or app state variables

  • Executing interactions with datasources, like fetching data from a database or API, or writing a file to an AWS S3 bucket

  • Triggering other actions

  • Sending notifications

They could be triggered by UI events which they are associated with, run immediately when the app is loaded, or run periodically at a configured interval. This section covers all you need to know about actions:

  1. : How to create, organize and configure actions

  2. : The internals around how actions are executed and the data they expose after successful or unsuccessful execution

  3. : How to test actions without influencing application state

  4. : Full overview of all events that may trigger actions to be executed

Managing actions
Execution model
Preview
Triggers