← HTTP / Webhook + Gitlab integrations

Create Epic with Gitlab API on New Requests from HTTP / Webhook API

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

Trigger workflow on
New Requests from the HTTP / Webhook API
Next, do this
Create Epic with the Gitlab 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 Gitlab 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 Create Epic action
    1. Connect your Gitlab account
    2. Select a Group ID
    3. Optional- Select a Epic Internal ID
    4. Configure Title
    5. Optional- Select one or more Labels
    6. Optional- Configure Description
    7. Optional- Configure Color
    8. Optional- Configure Confidential
    9. Optional- Configure Created at
    10. Optional- Configure Start Date Is Fixed
    11. Optional- Configure Due Date Is Fixed
  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:Creates a new epic. [See docs](https://docs.gitlab.com/ee/api/epics.html#new-epic)
Version:0.0.1
Key:gitlab-create-epic

Gitlab Overview

Gitlab API allows developers to access the functionality of Gitlab. With the
Gitlab API, developers can integrate Gitlab with other applications, create
custom applications, or automate tasks.

Some examples of what you can build using the Gitlab API include:

  • Automate tasks such as creating and managing repositories
  • Integrate Gitlab with other applications such as your chat application
  • Create custom applications on top of Gitlab

Action Code

import lodash from "lodash";
import gitlab from "../../gitlab.app.mjs";

export default {
  key: "gitlab-create-epic",
  name: "Create Epic",
  description: "Creates a new epic. [See docs](https://docs.gitlab.com/ee/api/epics.html#new-epic)",
  version: "0.0.1",
  type: "action",
  props: {
    gitlab,
    groupPath: {
      propDefinition: [
        gitlab,
        "groupPath",
      ],
    },
    parent_id: {
      propDefinition: [
        gitlab,
        "epicId",
        (c) => ({
          groupPath: c.groupPath,
        }),
      ],
    },
    title: {
      propDefinition: [
        gitlab,
        "title",
      ],
      description: "The title of the epic",
    },
    labels: {
      propDefinition: [
        gitlab,
        "groupLabels",
        (c) => ({
          groupPath: c.groupPath,
        }),
      ],
    },
    description: {
      propDefinition: [
        gitlab,
        "description",
      ],
      description: "The description of the issue",
    },
    color: {
      propDefinition: [
        gitlab,
        "color",
      ],
    },
    confidential: {
      propDefinition: [
        gitlab,
        "confidential",
      ],
    },
    created_at: {
      propDefinition: [
        gitlab,
        "created_at",
      ],
    },
    start_date_is_fixed: {
      propDefinition: [
        gitlab,
        "start_date_is_fixed",
      ],
      reloadProps: true,
    },
    due_date_is_fixed: {
      propDefinition: [
        gitlab,
        "due_date_is_fixed",
      ],
      reloadProps: true,
    },
  },
  async additionalProps() {
    const props = {};
    if (this.start_date_is_fixed) {
      props.start_date_fixed = {
        type: "string",
        label: "Start date fixed",
        description: "The fixed start date of an epic (in GitLab 11.3 and later)",
      };
    }
    if (this.due_date_is_fixed) {
      props.due_date_fixed = {
        type: "string",
        label: "Due date fixed",
        description: "The fixed due date of an epic (in GitLab 11.3 and later)",
      };
    }
    return props;
  },
  async run({ $ }) {
    const opts = lodash.pickBy(lodash.pick(this, [
      "parent_id",
      "title",
      "labels",
      "description",
      "color",
      "confidential",
      "created_at",
      "start_date_is_fixed",
      "due_date_is_fixed",
      "start_date_fixed",
      "due_date_fixed",
    ]));
    opts.labels = opts.labels?.join();

    const response = await this.gitlab.createEpic(this.groupPath, this.title, opts);
    $.export("$summary", `Created epic ${this.title}`);
    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
GitlabgitlabappThis component uses the Gitlab app.
Group IDgroupPathstringSelect a value from the drop down menu.
Epic Internal IDparent_idstringSelect a value from the drop down menu.
Titletitlestring

The title of the epic

Labelslabelsstring[]Select a value from the drop down menu.
Descriptiondescriptionstring

The description of the issue

Colorcolorstring

The color of the epic. Introduced in GitLab 14.8, behind a feature flag named epic_highlight_color (disabled by default)

Confidentialconfidentialboolean

Whether the epic should be confidential

Created atcreated_atstring

When the epic was created. Date time string, ISO 8601 formatted, for example 2016-03-11T03:45:40Z . Requires administrator or project/group owner privileges (available in GitLab 13.5 and later)

Start Date Is Fixedstart_date_is_fixedboolean

Whether start date should be sourced from start_date_fixed or from milestones (in GitLab 11.3 and later)

Due Date Is Fixeddue_date_is_fixedboolean

Whether due date should be sourced from due_date_fixed or from milestones (in GitLab 11.3 and later)

Action Authentication

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

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

apiread_userread_repositorywrite_repositoryread_registrysudoopenidprofileemail

About Gitlab

Project planning and source code management

More Ways to Connect Gitlab + HTTP / Webhook

Edit Issue with Gitlab API on New Requests (Payload Only) from HTTP / Webhook API
HTTP / Webhook + Gitlab
 
Try it
Edit Issue with Gitlab API on New Requests from HTTP / Webhook API
HTTP / Webhook + Gitlab
 
Try it
Create Branch with Gitlab API on New Requests (Payload Only) from HTTP / Webhook API
HTTP / Webhook + Gitlab
 
Try it
Create Branch with Gitlab API on New Requests from HTTP / Webhook API
HTTP / Webhook + Gitlab
 
Try it
Get Issue with Gitlab API on New Requests (Payload Only) from HTTP / Webhook API
HTTP / Webhook + Gitlab
 
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 Gitlab API

Emit new event when a new commit is pushed to a branch

 
Try it
New Branch (Instant) from the Gitlab API

Emit new event when a new branch is created

 
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