Skip to main content

Introduction to Data² Rush

As a system grows in functionality and complexity, it's common for applications built with Data² UI to become insufficient to meet the system's new needs, such as integrations and automations.

What is Rush​

To handle these cases, Data² offers a set of tools called Data² Rush.

Rush is another way to interact with systems built on Data² in response to external events.

warning

Unlike the Application, which runs in your browser, Rush runs in a fully isolated and secure environment.

This creates some restrictions, such as not being able to directly access the user's browser Interface States, or what the user is currently seeing.

Use cases​

Some use cases that can be handled with Rush are:

  • Integrations with third-party services through Webhooks.
  • Sending reports by email at a set time.

External triggers​

External triggers are events that can occur outside the Data² system and, when they occur, trigger the execution of a Rush.

The currently supported triggers are:

  • HTTP requests.
  • Scheduled execution (scheduling).
  • Receiving emails.

Common points across all "Rushes"​

The "Rushes" share some common points:

  • They have a handler parameter where you define what will be executed when the trigger occurs.
  • They have execution logs that can be turned on or off. These logs are useful for debugging and developing your Rush. Since it uses Data² Table internally, pricing follows Data² Table's pricing model.
  • They have versioning.