Start Browser with Anchor Browser API on New Message in Channel from Discord Bot API

Pipedream makes it easy to connect APIs for Anchor Browser, Discord Bot and 2,500+ other apps remarkably fast.

Trigger workflow on

New Message in Channel from the Discord Bot API

Next, do this

Start Browser with the Anchor Browser 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 Bot trigger and Anchor Browser action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Message in Channel trigger
1. Connect your Discord Bot account
2. Select a Guild
3. Select one or more Channels
4. Optional- Configure Emit messages as a single event
5. Configure timer
Configure the Start Browser action
1. Connect your Anchor Browser account
2. Configure Adblock Configuration - Active
3. Configure Adblock Configuration - Popup Blocking Active
4. Configure Captcha Configuration - Active
5. Configure Headless
6. Optional- Configure Proxy Configuration - Type
7. Optional- Configure Proxy Configuration - Active
8. Optional- Configure Recording - Active
9. Select a Profile Name
10. Configure Profile - Persist
11. Configure Viewport - Width
12. Configure Viewport - Height
13. Optional- Configure Timeout
14. Optional- Configure Idle Timeout
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 Message in Channel on Discord Bot

Description:Emit new event for each message posted to one or more channels

Version:0.0.18

Key:discord_bot-new-message-in-channel

View on GitHub

Discord Bot Overview#

The Discord Bot API unlocks the power to interact with Discord users and channels programmatically, making it possible to automate messages, manage servers, and integrate with other services. With Pipedream's serverless platform, you can create complex workflows that respond to events in Discord, process data, and trigger actions in other apps. This opens up opportunities for community engagement, content moderation, analytics, and more, without the overhead of managing infrastructure.

Trigger Code#

import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";
import maxBy from "lodash.maxby";
import common from "../common.mjs";
import sampleEmit from "./test-event.mjs";

const { discord } = common.props;

export default {
  ...common,
  key: "discord_bot-new-message-in-channel",
  name: "New Message in Channel",
  description: "Emit new event for each message posted to one or more channels",
  type: "source",
  version: "0.0.18",

  dedupe: "unique", // Dedupe events based on the Discord message ID
  props: {
    ...common.props,
    db: "$.service.db",
    channels: {
      type: "string[]",
      label: "Channels",
      description: "The channels you'd like to watch for new messages",
      propDefinition: [
        discord,
        "channelId",
        ({ guildId }) => ({
          guildId,
        }),
      ],
    },
    emitEventsInBatch: {
      type: "boolean",
      label: "Emit messages as a single event",
      description:
        "If `true`, all messages are emitted as an array, within a single Pipedream event. Defaults to `false`, emitting each Discord message as its own event in Pipedream",
      optional: true,
      default: false,
    },
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
  },
  async run({ $ }) {
    // We store a cursor to the last message ID
    let lastMessageIDs = this._getLastMessageIDs();

    // If this is our first time running this source,
    // get the last N messages, emit them, and checkpoint
    for (const channelId of this.channels) {
      let lastMessageID;
      let messages = [];

      if (!lastMessageID) {
        messages = await this.discord.getMessages({
          $,
          channelId,
          params: {
            limit: 100,
          },
        });

        lastMessageID = messages.length
          ? maxBy(messages, (message) => message.id).id
          : 1;

      } else {
        let newMessages = [];

        do {
          newMessages = await this.discord.getMessages({
            $,
            channelId,
            params: {
              after: lastMessageIDs[channelId],
            },
          });

          messages = messages.concat(newMessages);

          lastMessageID = newMessages.length
            ? maxBy(newMessages, (message) => message.id).id
            : lastMessageIDs[channelId];

        } while (newMessages.length);
      }

      // Set the new high water mark for the last message ID
      // for this channel
      lastMessageIDs[channelId] = lastMessageID;

      if (!messages.length) {
        console.log(`No new messages in channel ${channelId}`);
        return;
      }

      console.log(`${messages.length} new messages in channel ${channelId}`);

      // Batched emits do not take advantage of the built-in deduper
      if (this.emitEventsInBatch) {
        const suffixChar =
          messages.length > 1
            ? "s"
            : "";

        this.$emit(messages, {
          summary: `${messages.length} new message${suffixChar}`,
          id: lastMessageID,
        });

      } else {
        messages.forEach((message) => {
          this.$emit(message, {
            summary: message.content,
            id: message.id, // dedupes events based on this ID
          });
        });
      }
    }

    // Set the last message ID for the next run
    this._setLastMessageIDs(lastMessageIDs);
  },
  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 Bot	`discord`	`app`	This component uses the Discord Bot app.
Guild	`guildId`	`string`	Select a value from the drop down menu.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Channels	`channels`	`string[]`	Select a value from the drop down menu.
Emit messages as a single event	`emitEventsInBatch`	`boolean`	If `true`, all messages are emitted as an array, within a single Pipedream event. Defaults to `false`, emitting each Discord message as its own event in Pipedream
	`timer`	`$.interface.timer`

Trigger Authentication#

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

This app allows you to use the Discord API using your own Discord bot. If you don't want to use a custom bot, and you just need to use the Discord API, exit this screen and use the Discord app, instead.

If you want to use your own Discord bot, but haven't created one yet, see these instructions or watch this video. You'll need to add this bot to your server(s) to make successful API requests.

Once you've created your bot, you'll find the Bot token within the Bot section of your app. Enter that token below.

About Discord Bot#

Use this app to interact with the Discord API using a bot in your account

Action#

Start Browser on Anchor Browser

Description:Allocates a new browser session for the user, with optional configurations for ad-blocking, captcha solving, proxy usage, and idle timeout. [See the documentation](https://docs.anchorbrowser.io/api-reference/browser-sessions/start-browser).

Version:0.0.1

Key:anchor_browser-start-browser

View on GitHub

Action Code#

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

export default {
  key: "anchor_browser-start-browser",
  name: "Start Browser",
  description: "Allocates a new browser session for the user, with optional configurations for ad-blocking, captcha solving, proxy usage, and idle timeout. [See the documentation](https://docs.anchorbrowser.io/api-reference/browser-sessions/start-browser).",
  version: "0.0.1",
  type: "action",
  props: {
    app,
    adblockConfigActive: {
      type: "boolean",
      label: "Adblock Configuration - Active",
      description: "Whether adblock configuration is active",
    },
    adblockConfigPopupBlockingActive: {
      type: "boolean",
      label: "Adblock Configuration - Popup Blocking Active",
      description: "Whether popup blocking is active",
    },
    captchaConfigActive: {
      type: "boolean",
      label: "Captcha Configuration - Active",
      description: "Whether captcha configuration is active",
    },
    headless: {
      type: "boolean",
      label: "Headless",
      description: "Whether browser should be headless or headfull.",
    },
    proxyConfigType: {
      type: "string",
      label: "Proxy Configuration - Type",
      description: "The type of proxy configuration to use. Eg. `anchor_residential`.",
      optional: true,
    },
    proxyConfigActive: {
      type: "boolean",
      label: "Proxy Configuration - Active",
      description: "Whether proxy configuration is active",
      optional: true,
    },
    recordingActive: {
      type: "boolean",
      label: "Recording - Active",
      description: "Whether recording is active",
      optional: true,
    },
    profileName: {
      description: "The name of the profile to use for the browser session.",
      propDefinition: [
        app,
        "profileName",
      ],
    },
    profilePersist: {
      type: "boolean",
      label: "Profile - Persist",
      description: "Whether the profile should persist after the session ends.",
    },
    viewportWidth: {
      type: "integer",
      label: "Viewport - Width",
      description: "The width of the viewport",
    },
    viewportHeight: {
      type: "integer",
      label: "Viewport - Height",
      description: "The height of the viewport",
    },
    timeout: {
      type: "string",
      label: "Timeout",
      description: "Maximum amount of time (in minutes) for the browser to run, before terminating. Defaults to `-1`, which disables the global timeout mechanism.",
      optional: true,
    },
    idleTimeout: {
      type: "string",
      label: "Idle Timeout",
      description: "The amount of time (in minutes) the session waits for new connections after all others are closed before stopping. Defaults to `1`. Setting it to `-1` let the browser session continue forever [**CAUTION** - Keep track of long living sessions and manually kill them].",
      optional: true,
    },
  },
  methods: {
    startBrowserSession(args = {}) {
      return this.app.post({
        path: "/sessions",
        ...args,
      });
    },
  },
  async run({ $ }) {
    const {
      startBrowserSession,
      adblockConfigActive,
      adblockConfigPopupBlockingActive,
      captchaConfigActive,
      headless,
      proxyConfigType,
      proxyConfigActive,
      recordingActive,
      profileName,
      profilePersist,
      viewportWidth,
      viewportHeight,
      timeout,
      idleTimeout,
    } = this;

    const response = await startBrowserSession({
      $,
      data: {
        adblock_config: {
          active: adblockConfigActive,
          popup_blocking_active: adblockConfigPopupBlockingActive,
        },
        captcha_config: {
          active: captchaConfigActive,
        },
        headless,
        proxy_config: {
          type: proxyConfigType,
          active: proxyConfigActive,
        },
        recording: {
          active: recordingActive,
        },
        profile: {
          name: profileName,
          persist: profilePersist,
        },
        viewport: {
          width: viewportWidth,
          height: viewportHeight,
        },
        timeout,
        idle_timeout: idleTimeout,
      },
    });

    $.export("$summary", "Successfully started browser session.");
    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
Anchor Browser	`app`	`app`	This component uses the Anchor Browser app.
Adblock Configuration - Active	`adblockConfigActive`	`boolean`	Whether adblock configuration is active
Adblock Configuration - Popup Blocking Active	`adblockConfigPopupBlockingActive`	`boolean`	Whether popup blocking is active
Captcha Configuration - Active	`captchaConfigActive`	`boolean`	Whether captcha configuration is active
Headless	`headless`	`boolean`	Whether browser should be headless or headfull.
Proxy Configuration - Type	`proxyConfigType`	`string`	The type of proxy configuration to use. Eg. `anchor_residential`.
Proxy Configuration - Active	`proxyConfigActive`	`boolean`	Whether proxy configuration is active
Recording - Active	`recordingActive`	`boolean`	Whether recording is active
Profile Name	`profileName`	`string`	Select a value from the drop down menu.
Profile - Persist	`profilePersist`	`boolean`	Whether the profile should persist after the session ends.
Viewport - Width	`viewportWidth`	`integer`	The width of the viewport
Viewport - Height	`viewportHeight`	`integer`	The height of the viewport
Timeout	`timeout`	`string`	Maximum amount of time (in minutes) for the browser to run, before terminating. Defaults to `-1`, which disables the global timeout mechanism.
Idle Timeout	`idleTimeout`	`string`	The amount of time (in minutes) the session waits for new connections after all others are closed before stopping. Defaults to `1`. Setting it to `-1` let the browser session continue forever [CAUTION - Keep track of long living sessions and manually kill them].

Action Authentication#

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

About Anchor Browser#

Browser For AI Agents

More Ways to Connect Anchor Browser + Discord Bot#

Other Popular Integrations#

Update Profile with Anchor Browser API on New Guild Member from Discord Bot API

Discord Bot + Anchor Browser

Start Browser with Anchor Browser API on New Message in Channel from Discord Bot API

Pipedream makes it easy to connect APIs for Anchor Browser, Discord Bot and 2,500+ other apps remarkably fast.

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

Developers ♥ Pipedream

1-24of2,500+apps by most popular

1
-
24
of
2,500+
apps by most popular