Key Terms in Domino

Learn what the jargon means

Domino is an automation platform that helps you connect Web3's most popular on- and off-chain Apps. This guide will walk you through the key concepts to help you get started with Domino.

Automation

An Automation is an automated workflow that connects Apps. Each Automation consists of a trigger and one or more actions. When you enable your Automation, it will run the action steps every time the trigger event occurs.

Automation Builder

The Automation Builder is a user-friendly interface that allows you to automate a workflow from scratch. In the Automation Builder, you can set up a trigger and one or more actions.

Explore (Automation library)

The Automation library, also known as Explore, is a collection of pre-made automations for various use cases. You can browse and choose from the best automations built by our team and start using them with just one click.

Trigger

A Trigger is an event that starts an Automation. For example, if you want to automatically buy an NFT when it is listed 50% below the floor price, the trigger is 'Token listed'. See the list of Triggers available here

Action

An Action is an event an Automation performs after it is triggered. For example, if you want to automatically buy a token when it is listed 50% below the floor price, the action is 'Buy token'.

Step

Step is simply a collective term for Triggers and Actions.

Variable

Data is passed between automation steps in the form of variables. For example, the "Get token price" action fetches the "Token price" as a variable. You can then pass the "Token price" variable to the "Send Discord message" action to send the token price as a Discord message.

Inputs

Inputs is the data that goes into a Trigger or Action in your Automation. They serve as the parameters or settings required for the specific Action to run. Inputs can be user-defined or received from other parts of the Automation as variables. For example the token address can be an input for the "Get Token Price" action.

Outputs

Outputs is the data that comes out of a Trigger or Action in your Automation. They are generated after the Trigger or Action has been executed and can be used as inputs for subsequent steps within the Automation, allowing you to create complex and interconnected workflows. For example, the Token price from the "Get Token Price" action is an output that can be used as an input for a subsequent Action, such as "Send Discord Message".

Automation Inputs

Automation Inputs is an Input that is specified in the beginning of an Automation or Template.

Automation Inputs allow you to add data in one place and pass that data as a variable to different actions and triggers within your Automation. They simplify the process of creating and reusing Automation templates.

For example, you can use the Send Pendle APY updates to Discord to receive Yield notifications for various Pendle Markets. To change the market you want to get Yield notifications for, Instead of changing the market address in multiple actions, you only need to update the Automation Input. Then, the updated input will automatically be used wherever the market address appears in your Automation. This makes it easier to customize and repurpose your Automations.

Template

Templates are a great way to share your Automations with others. If you have the right permissions, you can even submit your templates to the Automation Library, making them available for the wider community to use and benefit from.

Automation run

An Automation run refers to a single instance when an Automation is executed. It occurs when a trigger event is detected, and the Automation proceeds to carry out its actions. Each Automation run represents a complete cycle of the trigger being activated and the corresponding actions being performed.

An Automation run can have three results: Success - Successful automation run with all actions executed

Warning - Successful automation run with some action(s) hitting a non-breaking issue

Error - Failed automation run with an action hitting a breaking issue

Automation history

Automation history is a log of your Automation activity, including the details of each Automation Run, the data that flows in and out of each step, and any errors or issues that may have occurred during execution. By reviewing your Automation history, you can gain insights into the performance of your Automations, troubleshoot issues, and optimise your Automation logic.