Sign Up
Loading...

Event Builder

The Event Builder in Twidget allows you to automate workflows by creating and scheduling events. These events can execute a series of commands when triggered, giving you the ability to automate various tasks without writing a single line of code.

Creating an Event

Steps to Build an Event

  1. Navigate to the Events Page:

    • From your dashboard, locate and click on the "Events" tab to open the events page.
  2. Create Event:

    • Click the "Create Event" button positioned in the top right corner to open the create event sidebar.
  1. Enter Event Details:

    • Name: Input a name for your event.

    • Description (Optional): Provide a description to explain the purpose of this event.

Scheduling an Event

  1. Select a Schedule:

    • On the events page, identify the event you want to schedule and click on the schedule to open the "Edit Schedule" sidebar.
  1. Schedule Options:

    • Timezone: Choose the timezone used for every schedule date and time.

    • Starts On: Choose the start date and time for when your event may begin.

    • Frequency: Decide whether the event runs:

      • Once

      • On repeat

    • Repetition Details (If on repeat):

      • Choose Every interval and a frequency, or On selected weekdays.

      • For selected weekdays, choose Run on days and At local time. For weekdays at 9 AM, select Weekdays and enter 09:00.

      • Calendar schedules follow the selected timezone, including daylight-saving changes. A skipped local time is skipped; a repeated local time runs once. Missed runs are not replayed.

    • End Settings:

      • Whether the event ends or continues indefinitely.
    • Active Status:

      • Toggle to enable or disable the event. You can change the event's active status at any time.

Event Commands

Events use a command builder similar to endpoints and functions. When an event is triggered, it will process a series of specified commands in sequence.

Key Points:

  • Inputs and results: Scheduled runs have no caller-supplied payload, but events can define inputs for supported invocations. For database change triggers, add an Object input named trigger. Events do not return an HTTP response; inspect their execution results in Event History.

  • Command Execution: When the event is triggered, it runs through its designated commands as defined.

This flexibility allows you to string together multiple actions seamlessly, ensuring that your workflows are both efficient and effective.

Related Topics