Get Delivery Order Status with Dachser API on New Webhook Event (Instant) from Supabase API

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

Trigger workflow on

New Webhook Event (Instant) from the Supabase API

Next, do this

Get Delivery Order Status with the Dachser 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 Dachser 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 Get Delivery Order Status action
1. Connect your Dachser account
2. Configure info
3. Optional- Configure Reference Number 1
4. Optional- Configure Reference Number 2
5. Optional- Configure Reference Number 3
6. Optional- Configure Purchase Order Number
7. Optional- Configure Delivery Order Date
8. Optional- Configure Event Code
9. Optional- Configure Customer ID
10. Optional- Configure Accept-Language
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.6

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.6",
  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#

Get Delivery Order Status on Dachser

Description:Retrieve the delivery order status using reference and customer details. [See the documentation](https://api-portal.dachser.com/bi.b2b.portal/api/library/deliveryorderstatus?6)

Version:0.0.1

Key:dachser-get-delivery-order-status

View on GitHub

Action Code#

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

export default {
  name: "Get Delivery Order Status",
  description: "Retrieve the delivery order status using reference and customer details. [See the documentation](https://api-portal.dachser.com/bi.b2b.portal/api/library/deliveryorderstatus?6)",
  key: "dachser-get-delivery-order-status",
  version: "0.0.1",
  type: "action",
  props: {
    app,
    info: {
      type: "alert",
      alertType: "info",
      content: "At least one shipment reference or an order date is necessary to get the status.",
    },
    referenceNumber1: {
      type: "string",
      label: "Reference Number 1",
      description: "Reference number 1.",
      optional: true,
    },
    referenceNumber2: {
      type: "string",
      label: "Reference Number 2",
      description: "Reference number 2.",
      optional: true,
    },
    referenceNumber3: {
      type: "string",
      label: "Reference Number 3",
      description: "Reference number 3.",
      optional: true,
    },
    purchaseOrderNumber: {
      type: "string",
      label: "Purchase Order Number",
      description: "Purchase order number.",
      optional: true,
    },
    deliveryOrderDate: {
      type: "string",
      label: "Delivery Order Date",
      description: "Delivery order date in `YYYY-MM-DD` format.",
      optional: true,
    },
    eventCode: {
      type: "string",
      label: "Event Code",
      description: "Event code.",
      optional: true,
    },
    customerId: {
      propDefinition: [
        app,
        "customerId",
      ],
    },
    acceptLanguage: {
      propDefinition: [
        app,
        "acceptLanguage",
      ],
    },
  },
  async run({ $ }) {
    const {
      app,
      acceptLanguage,
      referenceNumber1,
      referenceNumber2,
      referenceNumber3,
      purchaseOrderNumber,
      deliveryOrderDate,
      eventCode,
      customerId,
    } = this;

    const response = await app.getDeliveryOrderStatus({
      $,
      params: {
        "reference-number1": referenceNumber1,
        "reference-number2": referenceNumber2,
        "reference-number3": referenceNumber3,
        "purchase-order-number": purchaseOrderNumber,
        "delivery-order-date": deliveryOrderDate,
        "event-code": eventCode,
        "customer-id": customerId,
      },
      headers: {
        "Accept-Language": acceptLanguage,
      },
    });

    $.export("$summary", `Successfully retrieved delivery order status for \`${response.deliveryOrders?.length ?? 0}\` delivery orders.`);

    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
Dachser	`app`	`app`	This component uses the Dachser app.
Reference Number 1	`referenceNumber1`	`string`	Reference number 1.
Reference Number 2	`referenceNumber2`	`string`	Reference number 2.
Reference Number 3	`referenceNumber3`	`string`	Reference number 3.
Purchase Order Number	`purchaseOrderNumber`	`string`	Purchase order number.
Delivery Order Date	`deliveryOrderDate`	`string`	Delivery order date in `YYYY-MM-DD` format.
Event Code	`eventCode`	`string`	Event code.
Customer ID	`customerId`	`string`	Your Dachser customer identifier. Separate multiple values by comma.
Accept-Language	`acceptLanguage`	`string`	Translation of service code descriptions. (ISO 639-1 standard language codes.) Examples: `en-US`, `de-DE`, `fr-FR`.

Action Authentication#

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

About Dachser#

DACHSER logistics processes

More Ways to Connect Dachser + Supabase#

Other Popular Integrations#

Get Shipment Status with Dachser API on New Row Added from Supabase API

Supabase + Dachser

Try it

Get Shipment Status with Dachser API on New Webhook Event (Instant) from Supabase API

Supabase + Dachser

Try it

Get Delivery Order Status with Dachser API on New Row Added from Supabase API

Supabase + Dachser

Try it

Get Shipment History with Dachser API on New Row Added from Supabase API

Supabase + Dachser

Try it

Get Shipment History with Dachser API on New Webhook Event (Instant) from Supabase API

Supabase + Dachser

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