What is a Trigger?

Triggers are the basis of the execution of any workflow. Each trigger node serves as a starting point for your workflow, allowing you to automate processes based on specific events or schedules.

Once we have built and tested the workflow, we can link ways to initiate this workflow. We can do this under the “Connect” tab.

What are Trigger Nodes?

Trigger nodes play a pivotal role in BuildShip as they are the catalysts responsible for initiating the execution of a workflow. Think of them as the "starting points" that kickstart the entire automation process.

How to setup a Trigger?

Go to the Connect tab and select the trigger most suitable for your use-case.

To create a simple API, just pick the REST API Call Trigger.

• Fill out the required inputs in the Setup section.
• Hit Connect.
• Once your trigger has successfully been connected, you'll be able to access additional settings to configure your workflow inputs and outputs.

Workflow Inputs Schema set up

The Workflow inputs schema option lists all of your workflow inputs (required/optional). The Inputs for your workflow have already been defined in the Workflow Inputs.

Click on the (x) icon to open the context menu. The Trigger Data object is the output values returned by the trigger you've added. Each trigger returns a different set of outputs, for example: REST API Call Trigger returns Query, Headers, and Body for each incoming request.

Workflow Output set up

The Workflow output section let's you define the format and values of the response your workflow will return. The Outputs for your workflow have already been defined in the Output Node in your workflow.

This section let's you access the Flow Output object which contains the workflow outputs, if applicable for the selected trigger.

Get Data

Imagine you have a trigger set up, but you're not sure what the incoming request looks like to map it to the inputs in your workflow. To make things easier, we can make use of the Get Data feature in the post-setup preview screen.

The Get Data feature let's you fetch the latest request to the set up endpoint and define your Workflow Input Schema based on the request.

How to use Get Data?

• Make sure to Connect your Trigger
• The trigger supports the Get Data feature if you see it on the preview tab after the trigger has been connected.
• If its an integration-based trigger, like the Stripe, Lemon Squeezy, Supabase, etc. we can either go to the respective developer dashboard to send a dummy webhook request (if supported), or trigger the event which calls this webhook.

• In case of an API-based trigger, just copy over the endpoint in the to your front-end client or API Testing Platform like Postman, or Hoppscotch. Send a request to the given endpoint.

Once a request is found delivered to the endpoint, you'll be displayed a tree structure of the properties received in the request. Select the required inputs for your workflow and click on “Add inputs to schema”. This would automatically add the selected properties as inputs to your workflow auto-mapped.

Supported Triggers

Below you'll find detailed explaination and examples of our most popular Triggers types:

Rest API Triggers

Rest API Call→Firebase Auth Request Trigger→Rest API File Upload Trigger→Rest API File Upload (Auth) Trigger→

Scheduled Triggers

Scheduled Cron→Scheduled Interval→

Database Triggers

Rowy Trigger→Supabase Trigger→MongoDB Trigger→

Payment Triggers

Stripe Trigger→Lemon Squeezy Trigger→RevenueCat Trigger→

Bot Triggers

Telegram Bot→WhatsApp Bot→

Integration Triggers

BuildShip Trigger→Email Trigger→GitHub Trigger→Notion Trigger→Webflow Trigger→YouTube Trigger→