Get Listings with Bridge Interactive Platform API on New Command Received (Instant) from Discord API

Pipedream makes it easy to connect APIs for Bridge Interactive Platform, Discord and 2,800+ other apps remarkably fast.

Trigger workflow on

New Command Received (Instant) from the Discord API

Next, do this

Get Listings with the Bridge Interactive Platform 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 Discord trigger and Bridge Interactive Platform action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Command Received (Instant) trigger
1. Connect your Discord account
2. Configure Channels
3. Configure discordApphook
4. Configure Commands
Configure the Get Listings action
1. Connect your Bridge Interactive Platform account
2. Configure Dataset
3. Optional- Configure Near
4. Optional- Configure Radius
5. Optional- Configure Box
6. Optional- Configure Poly
7. Optional- Configure Geohash
8. Optional- Select a Sort By
9. Optional- Select a Order
10. Optional- Select one or more Fields
11. Optional- Configure Limit
12. Optional- Configure Offset
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 Command Received (Instant) on Discord

Description:Emit new event for each command posted to one or more channels in a Discord server

Version:0.0.3

Key:discord-new-command-received

View on GitHub

Discord Overview#

The Discord API interacts seamlessly with Pipedream, empowering you to craft customized automations and workflows for your Discord server. With this powerful integration, you can automate tasks like message posting, user management, and notifications, based on a myriad of triggers and actions from different apps. These automations can enhance the Discord experience for community moderators and members, by synchronizing with external tools, organizing community engagement, and streamlining notifications.

Trigger Code#

import discord from "../../discord.app.mjs";
import sampleEmit from "./test-event.mjs";

export default {
  type: "source",
  key: "discord-new-command-received",
  name: "New Command Received (Instant)",
  description: "Emit new event for each command posted to one or more channels in a Discord server",
  version: "0.0.3",
  dedupe: "unique",
  props: {
    discord,
    channels: {
      type: "$.discord.channel[]",
      appProp: "discord",
      label: "Channels",
      description: "Select the channel(s) you'd like to be notified for",
    },
    // eslint-disable-next-line pipedream/props-label,pipedream/props-description
    discordApphook: {
      type: "$.interface.apphook",
      appProp: "discord",
      async eventNames() {
        return this.channels || [];
      },
    },
    commands: {
      label: "Commands",
      description: "List of commands to listen. E.g. `[\"/hi\", \"/hello\"]`",
      type: "string[]",
    },
  },
  async run(event) {
    if (event.guildID != this.discord.$auth.guild_id) {
      return;
    }

    const command = event.content.split(" ")[0];

    if (typeof this.commands === "string") {
      this.commands = JSON.parse(this.commands);
    }

    if (!this.commands.includes(command)) {
      return;
    }

    this.$emit(event, {
      id: event.id,
      summary: `New command posted with ID ${event.id}`,
      ts: Date.parse(event.createdTimestamp),
    });
  },
  sampleEmit,
};

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
Discord	`discord`	`app`	This component uses the Discord app.
Channels	`channels`	`$.discord.channel[]`	Select the channel(s) you'd like to be notified for
	`discordApphook`	`$.interface.apphook`
Commands	`commands`	`string[]`	List of commands to listen. E.g. `["/hi", "/hello"]`

Trigger Authentication#

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

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

botemailidentifyguilds

About Discord#

Use this app to create a Discord source that emits messages from your guild to a Pipedream workflow.

Action#

Get Listings on Bridge Interactive Platform

Description:Get MLS listings from a dataset. [See the documentation](https://bridgedataoutput.com/docs/explorer/mls-data)

Version:0.0.1

Key:bridge_interactive_platform-get-listings

View on GitHub

Action Code#

import bridgeInteractivePlatform from "../../bridge_interactive_platform.app.mjs";
import { ConfigurationError } from "@pipedream/platform";

export default {
  key: "bridge_interactive_platform-get-listings",
  name: "Get Listings",
  description: "Get MLS listings from a dataset. [See the documentation](https://bridgedataoutput.com/docs/explorer/mls-data)",
  version: "0.0.1",
  type: "action",
  props: {
    bridgeInteractivePlatform,
    dataset: {
      propDefinition: [
        bridgeInteractivePlatform,
        "dataset",
      ],
    },
    near: {
      propDefinition: [
        bridgeInteractivePlatform,
        "near",
      ],
    },
    radius: {
      propDefinition: [
        bridgeInteractivePlatform,
        "radius",
      ],
    },
    box: {
      propDefinition: [
        bridgeInteractivePlatform,
        "box",
      ],
    },
    poly: {
      propDefinition: [
        bridgeInteractivePlatform,
        "poly",
      ],
    },
    geohash: {
      propDefinition: [
        bridgeInteractivePlatform,
        "geohash",
      ],
    },
    sortBy: {
      propDefinition: [
        bridgeInteractivePlatform,
        "field",
        (c) => ({
          dataset: c.dataset,
        }),
      ],
      label: "Sort By",
    },
    order: {
      type: "string",
      label: "Order",
      description: "Order of responses",
      optional: true,
      options: [
        "asc",
        "desc",
      ],
    },
    fields: {
      propDefinition: [
        bridgeInteractivePlatform,
        "field",
        (c) => ({
          dataset: c.dataset,
        }),
      ],
      type: "string[]",
      label: "Fields",
      description: "Filters Response fields",
    },
    limit: {
      type: "integer",
      label: "Limit",
      description: "Maximum number of responses",
      optional: true,
    },
    offset: {
      type: "integer",
      label: "Offset",
      description: "Number of responses to skip",
      optional: true,
    },
  },
  async run({ $ }) {
    const coords = {
      near: this.near,
      poly: this.poly,
      box: this.box,
      geohash: this.geohash,
    };

    if (Object.values(coords).filter(Boolean).length > 1) {
      throw new ConfigurationError("Only one of near, poly, box, or geohash can be used");
    }

    const response = await this.bridgeInteractivePlatform.getListings({
      dataset: this.dataset,
      params: {
        near: this.near,
        radius: this.radius,
        box: this.box,
        poly: this.poly,
        geohash: this.geohash,
        sortBy: this.sortBy,
        order: this.order,
        fields: this.fields
          ? this.fields.join(",")
          : undefined,
        limit: this.limit,
        offset: this.offset,
      },
    });
    $.export("$summary", `Found ${response.bundle.length} listings`);
    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
Bridge Interactive Platform	`bridgeInteractivePlatform`	`app`	This component uses the Bridge Interactive Platform app.
Dataset	`dataset`	`string`	The dataset to use for the query
Near	`near`	`string`	Coord or location eg. near=-73.98,40.73 or near=San Diego
Radius	`radius`	`string`	Search Radius in miles, km, or degrees (no units)s
Box	`box`	`string`	Coordinates representing a box eg. box=-112.5,33.75,-123,39
Poly	`poly`	`string`	Minimum 3 pairs of coordinates representing a polygon eg. poly=-112.5,33.75,-123,39,-120,38
Geohash	`geohash`	`string`	Alphanumeric geohash eg. geohash=ezs42
Sort By	`sortBy`	`string`	Select a value from the drop down menu.
Order	`order`	`string`	Select a value from the drop down menu:`ascdesc`
Fields	`fields`	`string[]`	Select a value from the drop down menu.
Limit	`limit`	`integer`	Maximum number of responses
Offset	`offset`	`integer`	Number of responses to skip

Action Authentication#

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