← HTTP / Webhook + BitBucket integrations

Get File From Repository with BitBucket API on New Requests from HTTP / Webhook API

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

Trigger workflow on
New Requests from the HTTP / Webhook API
Next, do this
Get File From Repository with the BitBucket 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 BitBucket 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 trigger
    1. Optional- Configure Body Only
    2. Optional- Configure Response Status Code
    3. Optional- Configure Response Content-Type
    4. Optional- Configure Response Body
    5. Connect your HTTP / Webhook account
  3. Configure the Get File From Repository action
    1. Connect your BitBucket account
    2. Select a Workspace
    3. Select a Repository
    4. Configure Filename
  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 full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.
Version:0.1.1
Key:http-new-requests

Trigger Code

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

// Core HTTP component
export default {
  key: "http-new-requests",
  name: "New Requests",
  description: "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.",
  version: "0.1.1",
  type: "source",
  props: {
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    emitBodyOnly: {
      type: "boolean",
      label: "Body Only",
      description: "This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.",
      optional: true,
      default: false,
    },
    resStatusCode: {
      type: "string",
      label: "Response Status Code",
      description: "The status code to return in the HTTP response",
      optional: true,
      default: "200",
    },
    resContentType: {
      type: "string",
      label: "Response Content-Type",
      description: "The `Content-Type` of the body returned in the HTTP response",
      optional: true,
      default: "application/json",
    },
    resBody: {
      type: "string",
      label: "Response Body",
      description: "The body to return in the HTTP response",
      optional: true,
      default: "{ \"success\": true }",
    },
    http,
  },
  async run(event) {
    const summary = `${event.method} ${event.path}`;

    this.httpInterface.respond({
      status: this.resStatusCode,
      body: this.resBody,
      headers: {
        "content-type": this.resContentType,
      },
    });

    if (this.emitBodyOnly) {
      this.$emit(event.body, {
        summary,
      });
    } else {
      this.$emit(event, {
        summary,
      });
    }
  },
};

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.
Body OnlyemitBodyOnlyboolean

This source emits an event representing the full HTTP request by default. Select true to emit the body only.

Response Status CoderesStatusCodestring

The status code to return in the HTTP response

Response Content-TyperesContentTypestring

The Content-Type of the body returned in the HTTP response

Response BodyresBodystring

The body to return in the HTTP response

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:Gets the actual file contents of a download artifact and not the artifact's metadata. [See docs here](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-downloads/#api-repositories-workspace-repo-slug-downloads-filename-get)
Version:0.1.3
Key:bitbucket-get-file-from-repository

BitBucket Overview

With the BitBucket API, you can programmatically interact with BitBucket, via
REST calls. This allows you to build apps and integrations on top of BitBucket,
customize and automate your workflows, and much more.

Here are some examples of what you can build with the BitBucket API:

  • Build integrations with 3rd party applications, such as CI/CD tools, chat
    applications, etc.
  • Create custom workflows and automate tasks
  • Build applications that interact with BitBucket (for example, a tool that
    helps you find repositories or users)
  • and much more!

Action Code

import base from "../common/base.mjs";
const { bitbucket } = base.props;

export default {
  key: "bitbucket-get-file-from-repository",
  name: "Get File From Repository",
  description: "Gets the actual file contents of a download artifact and not the artifact's metadata. [See docs here](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-downloads/#api-repositories-workspace-repo-slug-downloads-filename-get)",
  version: "0.1.3",
  type: "action",
  props: {
    ...base.props,
    repositoryId: {
      propDefinition: [
        bitbucket,
        "repository",
        (c) => ({
          workspaceId: c.workspaceId,
        }),
      ],
    },
    filename: {
      label: "Filename",
      description: "Name of the file to download.",
      type: "string",
    },
  },
  async run({ $ }) {
    const {
      workspaceId,
      repositoryId,
      filename,
    } = this;

    const response = this.bitbucket.getRepositoryFile({
      workspaceId,
      repositoryId,
      filename,
    });

    $.export("$summary", "Successfully retrieved repository file");

    return response;
  },
};

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
BitBucketbitbucketappThis component uses the BitBucket app.
WorkspaceworkspaceIdstringSelect a value from the drop down menu.
RepositoryrepositoryIdstringSelect a value from the drop down menu.
Filenamefilenamestring

Name of the file to download.

Action Authentication

BitBucket uses OAuth authentication. When you connect your BitBucket account, Pipedream will open a popup window where you can sign into BitBucket and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any BitBucket API.

Pipedream requests the following authorization scopes when you connect your account:

accountaccount:writeteam:writerepository:writepullrequest:writesnippet:writeissue:writeemailwikiwebhook

About BitBucket

Version control repository hosting service

More Ways to Connect BitBucket + HTTP / Webhook

Creates a new issue with BitBucket API on New Requests (Payload Only) from HTTP / Webhook API
HTTP / Webhook + BitBucket
 
Try it
Creates a new issue with BitBucket API on New Requests from HTTP / Webhook API
HTTP / Webhook + BitBucket
 
Try it
Create Issue Comment with BitBucket API on New Requests (Payload Only) from HTTP / Webhook API
HTTP / Webhook + BitBucket
 
Try it
Create Issue Comment with BitBucket API on New Requests from HTTP / Webhook API
HTTP / Webhook + BitBucket
 
Try it
Create Snippet Comment with BitBucket API on New Requests (Payload Only) from HTTP / Webhook API
HTTP / Webhook + BitBucket
 
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
New Commit (Instant) from the BitBucket API

Emit new event when a new commit is pushed to a branch. See docs here

 
Try it
New Pull Request (Instant) from the BitBucket API

Emit new event when a new pull request is created in a repository. See docs here

 
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