← HTTP / Webhook + Bubble integrations

Bubble with Bubble API on New Requests (Payload Only) from HTTP / Webhook API

Pipedream makes it easy to connect APIs for Bubble, HTTP / Webhook and 900+ other apps remarkably fast.

Trigger workflow on
New Requests (Payload Only) from the HTTP / Webhook API
Next, do this
Bubble with the Bubble API
No credit card required
Into to Pipedream
Watch us build a workflow
Watch us build a workflow
7 min
Watch now ➜
Trusted by 250,000+ developers from startups to Fortune 500 companies:
Trusted by 250,000+ developers from startups to Fortune 500 companies

Developers Pipedream

Getting Started

This integration creates a workflow with a HTTP / Webhook trigger and Bubble action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

  1. Select this integration
  2. Configure the New Requests (Payload Only) trigger
    1. Connect your HTTP / Webhook account
  3. Configure the Bubble action
    1. Connect your Bubble account
  4. Deploy the workflow
  5. Send a test event to validate your setup
  6. Turn on the trigger

Details

This integration uses pre-built, open source components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger

Description:Get a URL and emit the HTTP body as an event on every request
Version:0.1.1
Key:http-new-requests-payload-only

Trigger Code

import http from "../../http.app.mjs";

// Core HTTP component
// Returns a 200 OK response, emits the HTTP payload as an event
export default {
  key: "http-new-requests-payload-only",
  name: "New Requests (Payload Only)",
  // eslint-disable-next-line
  description: "Get a URL and emit the HTTP body as an event on every request",
  version: "0.1.1",
  type: "source",
  props: {
    // eslint-disable-next-line
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    http,
  },
  async run(event) {
    const { body } = event;
    this.httpInterface.respond({
      status: 200,
      body,
    });
    // Emit the HTTP payload
    this.$emit({
      body,
    });
  },
};

Trigger Configuration

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.
LabelPropTypeDescription
N/AhttpInterface$.interface.httpThis component uses $.interface.http to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the run() method of the component.
HTTP / WebhookhttpappThis component uses the HTTP / Webhook app.

Trigger Authentication

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook

Get a unique URL where you can send HTTP or webhook requests

Action

Description:
Version:0.1.1
Key:bubble-bubble

Action Code

// legacy_hash_id: a_YEiwAL
import { axios } from "@pipedream/platform";

export default {
  key: "bubble-bubble",
  name: "Bubble",
  version: "0.1.1",
  type: "action",
  props: {
    bubble: {
      type: "app",
      app: "bubble",
    },
  },
  async run({ $ }) {
  // Since every Bubble API is specific to its associated app, you'll
  // need to modify the code below to work with your API. This code
  // is meant to provide the scaffolding you need to get started.
    return await axios($, {
      url: `${this.bubble.$auth.root_url}`,
      headers: {
        Authorization: `Bearer ${this.bubble.$auth.api_key}`,
      },
    });
  },
};

Action Configuration

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

LabelPropTypeDescription
BubblebubbleappThis component uses the Bubble app.

Action Authentication

Bubble uses API keys for authentication. When you connect your Bubble account, Pipedream securely stores the keys so you can easily authenticate to Bubble APIs in both code and no-code steps.

  1. Activate the Bubble API for your app (within your app, visit Settings -> API). Bubble exposes both a Workflow and a Data API — read about both to understand which one you should enable.

  2. Each API has a unique Root URL. If you activate both the Workflow and the Data API for your application, you'll need to connect each as separate apps in Pipedream, labeling them appropriately in the Nickname field below. You'll also be asked to generate an API key. Enter both of those values in the form below.


The API Bubble exposes for your app is specific to your app. For example, the paths you make HTTP requests against are tied to the names of your Bubble workflows. Because of this, the starter code Pipedream produces for Bubble will not immediately work. You'll need to modify the code to work with your app's endpoints. Bubble generates a Swagger specification specific to your app that should list each of its available endpoints, which should help you develop against it.

About Bubble

Code-free programming language

More Ways to Connect Bubble + HTTP / Webhook

Bubble with Bubble API on New Requests from HTTP / Webhook API
HTTP / Webhook + Bubble
 
Try it
Bubble with Bubble API on New event when the content of the URL changes. from HTTP / Webhook API
HTTP / Webhook + Bubble
 
Try it
New Requests from the HTTP / Webhook API

Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.

 
Try it
New Requests (Payload Only) from the HTTP / Webhook API

Get a URL and emit the HTTP body as an event on every request

 
Try it
New event when the content of the URL changes. from the HTTP / Webhook API

Emit new event when the content of the URL changes.

 
Try it
Send any HTTP Request with the HTTP / Webhook API

Send an HTTP request using any method and URL. Optionally configure query string parameters, headers, and basic auth.

 
Try it
Send GET Request with the HTTP / Webhook API

Send an HTTP GET request to any URL. Optionally configure query string parameters, headers and basic auth.

 
Try it
Send POST Request with the HTTP / Webhook API

Send an HTTP POST request to any URL. Optionally configure query string parameters, headers and basic auth.

 
Try it
Send PUT Request with the HTTP / Webhook API

Send an HTTP PUT request to any URL. Optionally configure query string parameters, headers and basic auth.

 
Try it
Return HTTP Response with the HTTP / Webhook API

Use with an HTTP Source that uses Return a custom response from your workflow as its HTTP Response

 
Try it