Backend Workflows

Your app must be on a paid Bubble plan to use Backend Workflows

Using backend workflows can be ideal and/or necessary in the following situations:

  1. When you have long and complex workflows with a lot of actions

  2. When you need to reuse the same workflow from different parts (pages/reusables) of the application

  3. When you need to run a workflow on a list of things, (i.e., loop through a list)

  4. When you need to schedule a workflow in the future (with the ability to cancel the workflow)

  5. If you want your workflow to run asynchronously. Backend workflows run on Bubble's server, and any workflow on a standard Bubble page which schedules a Backend workflow won't need to wait for the entire (Backend) workflow to finish before moving on to the next step in the front-end workflow.

  6. If you want to create a webhook - or endpoint - to allow other applications to send and receive data from your Bubble app.

For more information on Backend workflows, read Airdev's Bubble Development Guide and Bubble's Manual.

Our template comes with 7 Backend workflows in the following folders.

Verify

  • verify_send: This will create a new verify record in the database and send a code to the user via email or sms

  • verify_check: This endpoint is called when the user submits a code to verify their email or phone number. When run, Canvas will verify whether the code is valid and return true or false

  • verify_delete: Deletes a verify record 15 minutes after it has been created.

Emails

  • send_email_template: This workflow is a template action that can be copied and edited for new email template backend actions.

Canvas

  • update_usersnap - When you start a project with AirDev, we'll use this workflow to enable usersnap testing on your app so you can submit feedback in our client management portal.

Last updated