List messages with Sendbird API on Failed Task in Schema from Snowflake API

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

Trigger workflow on

Failed Task in Schema from the Snowflake API

Next, do this

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

Select this integration
Configure the Failed Task in Schema trigger
1. Connect your Snowflake account
2. Configure timer
3. Select a Database
4. Select one or more Schema
5. Optional- Configure Task Name
Configure the List messages action
1. Connect your Sendbird account
2. Configure Application Id
3. Select a Channel Type
4. Select a Channel URL
5. Optional- Configure Message Timestamp
6. Optional- Configure Message Id
7. Optional- Configure Prev Limit
8. Optional- Configure Next Limit
9. Optional- Configure Include
10. Optional- Configure Reverse
11. Optional- Select one or more Sender Ids
12. Optional- Select a Operator Filter
13. Optional- Select a Message Type
14. Optional- Configure Including Removed
15. Optional- Configure With Sorted Meta Array
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#

Failed Task in Schema on Snowflake

Description:Emit new events when a task fails in a database schema

Version:0.1.2

Key:snowflake-failed-task-in-schema

View on GitHub

Snowflake Overview#

Snowflake offers a cloud database and related tools to help developers create robust, secure, and scalable data warehouses. See Snowflake's Key Concepts & Architecture.

Getting Started

1. Create a user, role and warehouse in Snowflake

Snowflake recommends you create a new user, role, and warehouse when you integrate a third-party tool like Pipedream. This way, you can control permissions via the user / role, and separate Pipedream compute and costs with the warehouse. You can do this directly in the Snowflake UI.

We recommend you create a read-only account if you only need to query Snowflake. If you need to insert data into Snowflake, add permissions on the appropriate objects after you create your user.

2. Enter those details in Pipedream

Visit https://pipedream.com/accounts. Click the button to Connect an App. Enter the required Snowflake account data.

You'll only need to connect your account once in Pipedream. You can connect this account to multiple workflows to run queries against Snowflake, insert data, and more.

3. Build your first workflow

Visit https://pipedream.com/new to build your first workflow. Pipedream workflows let you connect Snowflake with 1,000+ other apps. You can trigger workflows on Snowflake queries, sending results to Slack, Google Sheets, or any app that exposes an API. Or you can accept data from another app, transform it with Python, Node.js, Go or Bash code, and insert it into Snowflake.

Learn more at Pipedream University.

Trigger Code#

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

export default {
  ...common,
  props: {
    ...common.props,
    timer: {
      description: "Watch for failed tasks on this schedule",
      type: "$.interface.timer",
      default: {
        intervalSeconds: 15 * 60,
      },
    },
    database: {
      propDefinition: [
        common.props.snowflake,
        "database",
      ],
    },
    schemas: {
      propDefinition: [
        common.props.snowflake,
        "schema",
        (configuredProps) => ({
          database: configuredProps.database,
        }),
      ],
      type: "string[]",
    },
    taskName: {
      type: "string",
      label: "Task Name",
      description: "The name of the task to watch for failures. It allows you to use Regex to match multiple tasks.",
      optional: true,
    },
  },
  type: "source",
  key: "snowflake-failed-task-in-schema",
  // eslint-disable-next-line
  name: "Failed Task in Schema",
  description: "Emit new events when a task fails in a database schema",
  version: "0.1.2",
  async run() {
    await this.emitFailedTasks({
      database: this.database,
      schemas: this.schemas,
      taskName: this.taskName,
    });
  },
};

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
Snowflake	`snowflake`	`app`	This component uses the Snowflake app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`	Watch for failed tasks on this schedule
Database	`database`	`string`	Select a value from the drop down menu.
Schema	`schemas`	`string[]`	Select a value from the drop down menu.
Task Name	`taskName`	`string`	The name of the task to watch for failures. It allows you to use Regex to match multiple tasks.

Trigger Authentication#

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

We recommend you create a read-only account if you only need to query Snowflake. If you need to insert data into Snowflake, add permissions on the appropriate objects after you create your user.

About Snowflake#

A data warehouse built for the cloud

Action#

List messages on Sendbird

Description:Retrieves a list of past messages of a specific channel. [See the docs here](https://sendbird.com/docs/chat/v3/platform-api/message/messaging-basics/list-messages)

Version:0.0.1

Key:sendbird-list-messages

View on GitHub

Sendbird Overview#

The Sendbird API provides programmatic access to advanced chat features, enabling the creation and management of in-app messaging for community forums, customer support, or any other chat-based interaction. By leveraging the Sendbird API on Pipedream, you can automate user management, message and channel handling, and event tracking. Pipedream's serverless platform simplifies these automations, offering a way to integrate chat functionalities with other services, trigger workflows from chat events, and handle real-time data processing without writing extensive infrastructure code.

Action Code#

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

export default {
  key: "sendbird-list-messages",
  name: "List messages",
  description: "Retrieves a list of past messages of a specific channel. [See the docs here](https://sendbird.com/docs/chat/v3/platform-api/message/messaging-basics/list-messages)",
  version: "0.0.1",
  type: "action",
  props: {
    app,
    applicationId: {
      propDefinition: [
        app,
        "applicationId",
      ],
    },
    channelType: {
      propDefinition: [
        app,
        "channelType",
      ],
    },
    channelUrl: {
      propDefinition: [
        app,
        "channelUrl",
        (c) => ({
          applicationId: c.applicationId,
          channelType: c.channelType,
        }),
      ],
    },
    messageTs: {
      propDefinition: [
        app,
        "messageTs",
      ],
    },
    messageId: {
      propDefinition: [
        app,
        "messageId",
      ],
    },
    prevLimit: {
      propDefinition: [
        app,
        "prevLimit",
      ],
    },
    nextLimit: {
      propDefinition: [
        app,
        "nextLimit",
      ],
    },
    include: {
      propDefinition: [
        app,
        "include",
      ],
    },
    reverse: {
      propDefinition: [
        app,
        "reverse",
      ],
    },
    senderIds: {
      propDefinition: [
        app,
        "senderIds",
        (c) => ({
          applicationId: c.applicationId,
        }),
      ],
    },
    operatorFilter: {
      propDefinition: [
        app,
        "operatorFilter",
      ],
    },
    messageType: {
      propDefinition: [
        app,
        "messageType",
      ],
    },
    includingRemoved: {
      propDefinition: [
        app,
        "includingRemoved",
      ],
    },
    withSortedMetaArray: {
      propDefinition: [
        app,
        "withSortedMetaArray",
      ],
    },
  },
  async run({ $ }) {
    if (!this.messageId && !this.messageTs) {
      throw new ConfigurationError("Either `Message Timestamp` or `Message Id` must to be specified.");
    }
    const opts = {
      messageTs: this.messageTs,
      messageId: this.messageId,
      prevLimit: this.prevLimit,
      nextLimit: this.nextLimit,
      include: this.include,
      reverse: this.reverse,
      senderIds: this.senderIds,
      operatorFilter: this.operatorFilter,
      messageType: this.messageType,
      includingRemoved: this.includingRemoved,
      withSortedMetaArray: this.withSortedMetaArray,
    };
    try {
      const { messages } = await this.app.listMessages(
        this.applicationId,
        this.channelType,
        this.channelUrl,
        opts,
      );
      $.export("$summary", `Successfully fetched ${messages.length} messages`);
      return messages;
    } catch (ex) {
      throw new ConfigurationError(ex?.body?.message);
    }
  },
};

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
Sendbird	`app`	`app`	This component uses the Sendbird app.
Application Id	`applicationId`	`string`	Specifies the unique ID of the Application. To find the application ID, sign in to Sendbird Dashboard, go to Settings > Application > General, and then check Application ID.
Channel Type	`channelType`	`string`	Select a value from the drop down menu:`{ "label": "Open Channels", "value": "open_channels" }{ "label": "Group Channels", "value": "group_channels" }`
Channel URL	`channelUrl`	`string`	Select a value from the drop down menu.
Message Timestamp	`messageTs`	`integer`	Specifies the timestamp to be the reference point of the query in Unix milliseconds. Either this or the `Message Id` should be specified.
Message Id	`messageId`	`integer`	Specifies the unique ID of the message to be the reference point of the query. Either this or the `Message Timestamp` should be specified.
Prev Limit	`prevLimit`	`integer`	Specifies the number of previously sent messages to retrieve before `message_ts`. For example, if `message_ts=1484202848298`, then `prev_limit=50` returns 50 messages sent by 1484202848297 (message_ts - 1).
Next Limit	`nextLimit`	`integer`	Specifies the number of sent messages to retrieve after `message_ts`. For example, if `message_ts=1484202848298`, then `next_limit=50` returns 50 messages sent from 1484202848299 (message_ts + 1).
Include	`include`	`boolean`	Determines whether to include messages sent exactly on the specified `message_ts` in the results. (Default: true)
Reverse	`reverse`	`boolean`	Determines whether to sort the results in reverse chronological order. If set to true, messages appear in reverse chronological order where the newest comes first and the oldest last. (Default: false)
Sender Ids	`senderIds`	`string[]`	Select a value from the drop down menu.
Operator Filter	`operatorFilter`	`string`	Select a value from the drop down menu:`{ "label": "All", "value": "all" }{ "label": "Operator", "value": "operator" }{ "label": "Non Operator", "value": "nonoperator" }`
Message Type	`messageType`	`string`	Select a value from the drop down menu:`{ "label": "Message", "value": "MESG" }{ "label": "File", "value": "FILE" }{ "label": "Admin Message", "value": "ADMM" }`
Including Removed	`includingRemoved`	`boolean`	Determines whether to include messages removed from the channel in the results.
With Sorted Meta Array	`withSortedMetaArray`	`boolean`	Determines whether to include the `sorted_metaarray` property in the response.

Action Authentication#

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

To connect Sendbird, you will need to provide two keys.

In your organization's settings, please locate and copy your Organization API Key located in Settings the top-right corner under API Key.
Please navigate to the app that you have created, under "Applications" >> "Settings" >> "API Tokens", please copy your Master API Token.