A source is a tool in your stack that can send backend events to Buildable. There are three types of sources:
- Cloud apps, such as Stripe, Twilio and SendGrid
- Databases, such as MongoDB, PostgreSQL and MySQL
- Servers, such as a web server you run internally
View a full list of all the available event sources using our catalog:
An action is either a custom function (i.e., Serverless, Axios, GraphQL) or a Connection-based function (i.e.,
insert.recordfrom MongoDB). They are used to action a subscribed event.
An event is an action or occurrence recognized by a third-party cloud app, database or internal server. Examples of events are
customer.createdin Stripe or
A Stream (often called an Event Stream) is the centralized list of all events that have been collected from your connected Sources.
A Workflow is a series of actions stitched together to create a reliable flow of logic. Actions within a Workflow can be added, removed, paused, edited, and re-ordered with ease.
Trigger refers to how you decide to trigger the actions within your Workflow. There are two ways to trigger a Workflow in Buildable:
- 2.HTTP Request
Environments refer to the multi-environment nature of a Workflow. By default, each Workflow is given two environments:
- 1.Development and
An easy way to organize your Workflows into categories or chunks of work
Environment Variables are multi-environment keys that are accessible across Buildable. Often, they're used to manage the preferred environment for your third-party app and database account credentials.