Fetch User Data from Bubble API via Manual Trigger

Overview

This workflow provides a simple way to retrieve user data from a Bubble.io application by making an authenticated HTTP request to the Bubble Data API. It is triggered manually, making it ideal for on-demand data retrieval, testing API connectivity, or integrating Bubble data into other n8n workflows.

The workflow is useful for developers or no-code builders who need to pull records from Bubble's built-in database without building a custom backend. It can be extended to handle different objects, filter results, or feed data into other nodes for processing, notifications, or storage.

Nodes and Their Roles

1. On clicking 'execute' (Manual Trigger) — This is the start node. It requires no authentication and simply waits for a user to click the "Execute Workflow" button in the n8n editor. It has no parameters and serves only to kick off the workflow.
2. HTTP Request (HTTP Request node) — This node sends a GET request to the Bubble API endpoint. It uses Header Auth authentication (typically an API key passed in the request header). The configured URL is https://n8n-lessons.bubbleapps.io/version-test/api/1.1/obj/user. This retrieves all user records from the Bubble app. The node's parameters include the URL and the selected authentication method, but no additional options are configured.

Setup Instructions

1. Bubble Account — You need a Bubble.io account with an existing application containing at least one User data type. If you are using the example URL, note that it points to a public demo app; for your own use, replace it with your app's API endpoint.
2. API Key — In your Bubble app, go to Settings → API → Generate a new API key (or copy an existing one). This key will be used for header authentication.
3. n8n Credential — In n8n, create a new credential for the HTTP Request node: choose "Header Auth" as the credential type. Enter the API key as the header value (usually the header name is Authorization and the value is Bearer <your_api_key>). Save the credential and select it in the node.
4. Execute — Click "Execute Workflow" in the n8n editor to test the workflow. The output will contain the list of users from Bubble.

Use Cases and Variations

• Fetch Other Objects — Change the URL path to target other Bubble data types (e.g., /obj/product or /obj/order) to retrieve different collections.
• Filter Results — Add query parameters like ?constraints=[{"key":"email","constraint_type":"equals","value":"[email protected]"}] to filter specific records.
• Trigger on Schedule — Replace the Manual Trigger with a Schedule Trigger to run daily or hourly, combined with a notification node (e.g., Slack or email) to alert when new users are added.
• Process Data — Add a Function node or a Set node to transform the Bubble response, then write the data to Google Sheets, a database, or another API.

{
  "id": "15",
  "name": "Bubble Data Access",
  "nodes": [
    {
      "name": "On clicking 'execute'",
      "type": "n8n-nodes-base.manualTrigger",
      "position": [
        250,
        300
      ],
      "parameters": {},
      "typeVersion": 1
    },
    {
      "name": "HTTP Request",
      "type": "n8n-nodes-base.httpRequest",
      "position": [
        450,
        300
      ],
      "parameters": {
        "url": "https://n8n-lessons.bubbleapps.io/version-test/api/1.1/obj/user",
        "options": {},
        "authentication": "headerAuth"
      },
      "credentials": {
        "httpHeaderAuth": "Bubble n8n Lessons Token"
      },
      "typeVersion": 1
    }
  ],
  "active": false,
  "settings": {},
  "connections": {
    "On clicking 'execute'": {
      "main": [
        [
          {
            "node": "HTTP Request",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  }
}