A project corresponds to a folder or container for organizing your workflows. When you create or add workflow inside a project, all the configurations related to that workflow are also stored inside the project. Every account/organization by default, has a default project. User can choose to create additional projects as per their requirements.
Read more about projects here.
A workflow is a connection between two or more web apps or services. Creating a workflow means defining the steps of a recurring task that you want to automate. For example, whenever a New Lead is created in Salesforce, create a New Task in Wunderlist.
Learn about workflow in-detail here or refer to our step-by-step guide on creating your first workflow.
A trigger is an event that starts a workflow. For example, if your workflow is ‘Whenever a New Lead is created in Salesforce, create a New Task in Wunderlist’, the first part, i.e., ‘New lead in Salesforce’ is the trigger. A workflow can have only one trigger.
Read more about triggers and learn how to set up a trigger in your workflow.
An action specifies the tasks you want the workflow to perform. For example, if your workflow is ‘Whenever a New Lead is created in Salesforce, 'create a New Task in Wunderlist’, the latter part, i.e. ‘create new task in Wunderlist’ is an action. A workflow can have several actions.
Each service has several actions that you can use. For example, Wunderlist has actions like Create List, Create task, Get List Details, Delete Task, etc.
Authorization is the process of granting Built.io Flow the permission to perform certain tasks in third-party apps or services. So, for instance, if you use an action related to Google Mail in your workflow, you will have to first login to your Google mail account, and then authorize Built.io Flow to perform certain tasks on your behalf.
Read Authorization for more details.
‘Conditions’ is a feature that allows you set certain conditions between two actions. The workflow will proceed only if the specified conditions are met.
Refer to Conditions to dig deeper.
Parameters let you set key-value pairs for your workflows. Once you set a parameter, you can use it anywhere in your workflow in a single click. Get started with using Parameters.
Built.io supports incoming webhooks. An incoming webhook is an easy way to receive messages from an external application.
If webhook is enabled for a workflow, Built.io Flow generates a unique webhook URL, which you need to provide to the desired external application. This external application then sends HTTP request with JSON payload, which can be used in your workflow.
To understand how it works, refer to our webhooks guide.
A container is an isolated run-time environment. It contains all the dependencies (configuration files, binaries, system libraries, code, etc.) that it needs to run your workflows smoothly.
Read our guide on Container to learn more.