Create Incident with LinearB API on New Webhook Event (Instant) from Supabase API

Pipedream makes it easy to connect APIs for LinearB, Supabase and 2,400+ other apps remarkably fast.

Trigger workflow on

New Webhook Event (Instant) from the Supabase API

Next, do this

Create Incident with the LinearB API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

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

Select this integration
Configure the New Webhook Event (Instant) trigger
1. Connect your Supabase account
2. Configure Table
3. Optional- Configure Row Identifier
Configure the Create Incident action
1. Connect your LinearB account
2. Configure Provider ID
3. Configure HTTP URL
4. Configure Title
5. Configure Issued At
6. Optional- Configure Started At
7. Optional- Configure Ended At
8. Optional- Configure Git Ref
9. Optional- Configure Teams
10. Optional- Configure Services
11. Optional- Configure Repository URLs
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available 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#

New Webhook Event (Instant) on Supabase

Description:Emit new event for every `insert`, `update`, or `delete` operation in a table. This source requires user configuration using the Supabase website. More information in the README. [Also see documentation here](https://supabase.com/docs/guides/database/webhooks#creating-a-webhook)

Version:0.0.5

Key:supabase-new-webhook-event

View on GitHub

Supabase Overview#

Supabase is a real-time backend-as-a-service that provides developers with a suite of tools to quickly build and scale their applications. It offers database storage, authentication, instant APIs, and real-time subscriptions. With the Supabase API, you can perform CRUD operations on your database, manage users, and listen to database changes in real time. When integrated with Pipedream, you can automate workflows that react to these database events, synchronize data across multiple services, or streamline user management processes.

Trigger Code#

import base from "../common/base.mjs";
import constants from "../../common/constants.mjs";

export default {
  key: "supabase-new-webhook-event",
  name: "New Webhook Event (Instant)",
  description: "Emit new event for every `insert`, `update`, or `delete` operation in a table. This source requires user configuration using the Supabase website. More information in the README. [Also see documentation here](https://supabase.com/docs/guides/database/webhooks#creating-a-webhook)",
  version: "0.0.5",
  type: "source",
  props: {
    ...base.props,
    http: {
      type: "$.interface.http",
    },
  },
  hooks: {
    async deploy() {
      const client = await this.supabase._client();
      const query = client
        .from(this.table)
        .select()
        .range(0, constants.HISTORICAL_EVENT_LIMIT);
      const { data } = await query;
      for (const row of data) {
        this.$emit({
          record: row,
        }, {
          summary: "Historical row in table",
        });
      }
    },
  },
  async run(event) {
    const { body: data } = event;
    let summary = `New ${data.type} event in table`;
    if (data.record?.[this.rowIdentifier]) {
      summary = `${summary}: ${data.record[this.rowIdentifier]}`;
    }
    this.$emit(data, {
      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.

Label	Prop	Type	Description
Supabase	`supabase`	`app`	This component uses the Supabase app.
Table	`table`	`string`	The name of the table to watch for new rows
Row Identifier	`rowIdentifier`	`string`	The column name to use as the row identifier
N/A	`http`	`$.interface.http`	This 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.

Trigger Authentication#

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

Supabase provides a Service Key to get started. You can find the service_role in the API Settings page.

Finding the Supabase subdomain

About Supabase#

Supabase is an open source Firebase alternative.

Action#

Create Incident on LinearB

Description:Create a new incident within the LinearB platform. [See the documentation](https://docs.linearb.io/api-incidents/#create-incident)

Version:0.0.1

Key:linearb-create-incident

View on GitHub

LinearB Overview#

The LinearB API serves as a bridge between LinearB's project management insights and your preferred platforms, offering the ability to automate workflows, generate reports, and trigger actions based on project metrics. With Pipedream, these capabilities can be harnessed to create custom workflows that respond to events within LinearB, such as changes in project status or team performance metrics. The data can be pushed to various services, such as communication tools, databases, or other project management apps to enhance visibility and coordination across your team.

Action Code#

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

export default {
  key: "linearb-create-incident",
  name: "Create Incident",
  description: "Create a new incident within the LinearB platform. [See the documentation](https://docs.linearb.io/api-incidents/#create-incident)",
  version: "0.0.1",
  type: "action",
  props: {
    app,
    providerId: {
      type: "string",
      label: "Provider ID",
      description: "The unique identifier of the incident in your incident management provider. Eg. `provider_internal_id1`",
    },
    httpUrl: {
      type: "string",
      label: "HTTP URL",
      description: "The URL of your incident management provider. The combination `http_url/provider_key` should open the incident in your PM provider. Eg. `http://myprovider.io/1`",
    },
    title: {
      type: "string",
      label: "Title",
      description: "The title of the incident",
    },
    issuedAt: {
      type: "string",
      label: "Issued At",
      description: "The specific time when the incident was logged and officially opened. (timestamp ISO 8601 format). Eg. `2019-09-26T07:58:30.996`",
    },
    startedAt: {
      type: "string",
      label: "Started At",
      description: "The specific time when work on the incident commenced. (timestamp ISO 8601 format). Eg. `2019-09-26T07:58:30.996`",
      optional: true,
    },
    endedAt: {
      type: "string",
      label: "Ended At",
      description: "The specific time when the incident was successfully resolved. (timestamp ISO 8601 format). Eg. `2019-09-26T07:58:30.996`",
      optional: true,
    },
    gitRef: {
      type: "string",
      label: "Git Ref",
      description: "The Git reference of the release responsible for causing this incident, Eg. commit short or long sha or tag name (Eg. commit short or long sha/tag name).",
      optional: true,
    },
    teams: {
      type: "string[]",
      label: "Teams",
      description: "The list of LinearB teams names related to this incident. (lowercase only)",
      optional: true,
    },
    services: {
      type: "string[]",
      label: "Services",
      description: "The list of LinearB services related to this incident.",
      optional: true,
    },
    repositoryUrls: {
      type: "string[]",
      label: "Repository URLs",
      description: "The list of repos urls related to this incident. Eg. `https://github.com/myorg/repo1.git`",
      optional: true,
    },
  },
  methods: {
    createIncident(args = {}) {
      return this.app.post({
        path: "/incidents",
        ...args,
      });
    },
  },
  async run({ $ }) {
    const {
      createIncident,
      providerId,
      httpUrl,
      title,
      issuedAt,
      startedAt,
      endedAt,
      gitRef,
      teams,
      services,
      repositoryUrls,
    } = this;

    const response = await createIncident({
      $,
      data: {
        provider_id: providerId,
        http_url: httpUrl,
        title,
        issued_at: issuedAt,
        started_at: startedAt,
        ended_at: endedAt,
        git_ref: gitRef,
        teams,
        services,
        repository_urls: repositoryUrls,
      },
    });

    $.export("$summary", "Successfully created incident");
    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.

Label	Prop	Type	Description
LinearB	`app`	`app`	This component uses the LinearB app.
Provider ID	`providerId`	`string`	The unique identifier of the incident in your incident management provider. Eg. `provider_internal_id1`
HTTP URL	`httpUrl`	`string`	The URL of your incident management provider. The combination `http_url/provider_key` should open the incident in your PM provider. Eg. `http://myprovider.io/1`
Title	`title`	`string`	The title of the incident
Issued At	`issuedAt`	`string`	The specific time when the incident was logged and officially opened. (timestamp ISO 8601 format). Eg. `2019-09-26T07:58:30.996`
Started At	`startedAt`	`string`	The specific time when work on the incident commenced. (timestamp ISO 8601 format). Eg. `2019-09-26T07:58:30.996`
Ended At	`endedAt`	`string`	The specific time when the incident was successfully resolved. (timestamp ISO 8601 format). Eg. `2019-09-26T07:58:30.996`
Git Ref	`gitRef`	`string`	The Git reference of the release responsible for causing this incident, Eg. commit short or long sha or tag name (Eg. commit short or long sha/tag name).
Teams	`teams`	`string[]`	The list of LinearB teams names related to this incident. (lowercase only)
Services	`services`	`string[]`	The list of LinearB services related to this incident.
Repository URLs	`repositoryUrls`	`string[]`	The list of repos urls related to this incident. Eg. `https://github.com/myorg/repo1.git`

Action Authentication#

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

About LinearB#

The Software Delivery Management Platform for engineering leaders to streamline operations and align R&D investments to deliver business results

More Ways to Connect LinearB + Supabase#

Other Popular Integrations#

Create Incident with LinearB API on New Row Added from Supabase API

Supabase + LinearB

Try it

Delete Row with Supabase API on New Deploy Created from LinearB API

LinearB + Supabase

Try it

Insert Row with Supabase API on New Deploy Created from LinearB API

LinearB + Supabase

Try it

Remote Procedure Call with Supabase API on New Deploy Created from LinearB API

LinearB + Supabase

Try it

Update Row with Supabase API on New Deploy Created from LinearB API

LinearB + Supabase

Try it

Popular Triggers#

New Row Added from the Supabase API

Emit new event for every new row added in a table. See documentation here

Try it

New Webhook Event (Instant) from the Supabase API

Emit new event for every insert, update, or delete operation in a table. This source requires user configuration using the Supabase website. More information in the README. Also see documentation here

Try it

New Deploy Created from the LinearB API

Emit new event when a new deploy is created in LinearB. See the documentation

Try it