# The Workflow API

<details>

<summary>Help us improve this article</summary>

This article is part of a significant update to the Bubble manual and your feedback is critical to our efforts to continuously enhance our written documentation.\
\
We would greatly appreciate if you could take a moment to let us know your thoughts on the quality of it. Thank you for your support!\
\
[Give feedback on this article](https://docs.google.com/forms/d/e/1FAIpQLSfe7eaYVxkqTa_nn3QE6VObCxWB1hgh6sHUQGQ0Eit8JlAS7g/viewform?usp=pp_url\&entry.619913899=https://manual.bubble.io/help-guides/apis-connect-to-other-apps/the-bubble-api/the-workflow-api\&entry.80834677=The+Workflow+API)

</details>

## **What is the Workflow API?**

The Workflow API is the part of Bubble's [built-in API](#user-content-fn-1)[^1] that lets you set up workflows that can be triggered from an external application or system by sending an API request or by scheduling an API workflow in your app.

By constructing [API Workflows](#user-content-fn-2)[^2] just like you construct regular workflows on a page, you can make Bubble perform any kind of action or sequence of actions based on a request that can include parameters.

For example, let's imagine you have a customer contact form on a website that's not part of your Bubble application. By sending an API request from that platform that includes parameters like name, email and phone number, you can use an API Workflow to create a new lead or register a new user in your Bubble app.

API Workflows also lets your app respond to webhooks[^3] in other systems. For example, whenever a payment is made successfully in Stripe, you can set up a webhook in Stripe to trigger a workflow in your Bubble app so that any needed action can be taken immediately.

### What's the difference between API Workflows and Backend Workflows?

As you start working in the Backend Workflow section of Bubble you may find the two terms used in different contexts. While they are certainly related, they don't carry the exact same meaning:

* **Backend Workflows** encompass all the different events that you can add in the Backend Workflow editor:
  * API Workflows
  * Backend Triggers
  * Recurring Events
  * Custom Events
* **API Workflows** refer specifically to the Workflows that you add by using the *New API Workflow* command in the editor. They are referred to as API Workflows whether they are public[^4] or not.

<figure><img src="https://34394582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M5sbzwG7CljeZdkntrL%2Fuploads%2F41GtHrybmGkkfa48Kk8f%2Fbackend-workflows.png?alt=media&#x26;token=d48a14e2-6864-4d81-9c91-3602d7d6d431" alt=""><figcaption><p>Backend Workflows is a collective term for all the different events you can create in the Backend Editor.</p></figcaption></figure>

## **Activating the Workflow API**

To activate API Workflows, go to Settings - API and check the *Enable Workflow API and Backend Workflow*. This exposes all workflows that have *Expose as a public workflow* checked.

This also reveals your application's Workflow API root URL.

<figure><img src="https://34394582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M5sbzwG7CljeZdkntrL%2Fuploads%2FfHlMmESlz4YRLlVllWiM%2Fenable-workflow-api-bubble.png?alt=media&#x26;token=5f0db313-e018-4234-bf11-d4321ea6aded" alt=""><figcaption></figcaption></figure>

## **Accessing the backend workflow editor**

When the Workflow API has been enabled in your application’s settings, you can navigate to the virtual page *Backend workflows* by:

1. Click the page navigator in the upper left corner of the Bubble editor
2. Click the *Backend workflows* link at the very bottom of the list

<figure><img src="https://34394582-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M5sbzwG7CljeZdkntrL%2Fuploads%2FV2d1WtW8WFLd3cHREIq1%2Faccessing-backend-workflows-bubble.png?alt=media&#x26;token=baf4d88b-54b5-4732-a0b9-8078da0148ab" alt=""><figcaption></figcaption></figure>

## Continue reading

{% content-ref url="the-workflow-api/api-workflows" %}
[api-workflows](https://manual.bubble.io/~/revisions/SyQfIehozTbPqLjDmQAZ/help-guides/integrations/api/the-bubble-api/the-workflow-api/api-workflows)
{% endcontent-ref %}

{% content-ref url="the-workflow-api/workflow-api-privacy-rules" %}
[workflow-api-privacy-rules](https://manual.bubble.io/~/revisions/SyQfIehozTbPqLjDmQAZ/help-guides/integrations/api/the-bubble-api/the-workflow-api/workflow-api-privacy-rules)
{% endcontent-ref %}

{% content-ref url="the-workflow-api/workflow-api-endpoints" %}
[workflow-api-endpoints](https://manual.bubble.io/~/revisions/SyQfIehozTbPqLjDmQAZ/help-guides/integrations/api/the-bubble-api/the-workflow-api/workflow-api-endpoints)
{% endcontent-ref %}

[^1]: The Bubble API lets you set up a platform to accept incoming API requests to access your database or to trigger workflows.\
    \
    Article: [The Bubble API](https://manual.bubble.io/~/revisions/SyQfIehozTbPqLjDmQAZ/help-guides/integrations/api/the-bubble-api)

[^2]: An API Workflow is a Workflow that you can choose to expose to external apps to be able to trigger.\
    \
    Article: [API Workflows](https://manual.bubble.io/~/revisions/SyQfIehozTbPqLjDmQAZ/help-guides/integrations/api/the-bubble-api/the-workflow-api/api-workflows)

[^3]: A webhook is a way for an app to provide other applications with real-time information. It allows one app to send data to another app when certain events happen.

[^4]: A public API Workflow refers to any API Workflow that has the *Expose as a public API flow* box checked.\
    \
    Article section: [Exposing an API Workflow](https://manual.bubble.io/~/revisions/SyQfIehozTbPqLjDmQAZ/help-guides/integrations/api/the-bubble-api/broken-reference)
