Send SMS Message with Esendex API on Failed Task in Schema from Snowflake API

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

Trigger workflow on

Failed Task in Schema from the Snowflake API

Next, do this

Send SMS Message with the Esendex 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 Esendex 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 Send SMS Message action
1. Connect your Esendex account
2. Select a Account Reference
3. Configure To
4. Configure Message
5. Optional- Configure From
6. Optional- Configure Send At
7. Optional- Select a Character Set
8. Optional- Configure Validity
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#

Send SMS Message on Esendex

Description:Send an SMS message to a recipient. [See the documentation](https://developers.esendex.com/api-reference/#messagedispatcher)

Version:0.0.1

Key:esendex-send-sms-message

View on GitHub

Esendex Overview#

The Esendex API enables seamless SMS, Business WhatsApp and voice messaging integration into your applications. On Pipedream, you can harness this API to create serverless workflows that react to various triggers, from inbound messages to scheduled times, and interact with other services to provide a cohesive automation experience.

Action Code#

import esendex from "../../esendex.app.mjs";
import constants from "../../common/constants.mjs";

export default {
  key: "esendex-send-sms-message",
  name: "Send SMS Message",
  description: "Send an SMS message to a recipient. [See the documentation](https://developers.esendex.com/api-reference/#messagedispatcher)",
  version: "0.0.1",
  type: "action",
  props: {
    esendex,
    accountReference: {
      propDefinition: [
        esendex,
        "accountReference",
      ],
    },
    to: {
      type: "string",
      label: "To",
      description: "The phone number to send the message to. E.g. `447700900123`",
    },
    message: {
      type: "string",
      label: "Message",
      description: "The message to send",
    },
    from: {
      type: "string",
      label: "From",
      description: "The default alphanumeric originator that the message appears to originate from. This must be either a valid phone number or an alphanumeric value with a maximum length of 11 characters, that may contain letters, numbers and the following special characters: * $ ? ! ” # % & _ - , @ ' +. Special characters may not work for all networks in France.",
      optional: true,
    },
    sendAt: {
      type: "string",
      label: "Send At",
      description: "The scheduled time to send the messages in this request. The format is `yyyy-MM-ddThh:mm:ssZ` where y=year, M=month, d=day, T=separator, h=hour, m=min and s=seconds. The value is treated as per ISO 8601 semantics, e.g. without time zone information the value is assumed to be the local time of the server, otherwise as an offset from UTC with Z representing a UTC time.",
      optional: true,
    },
    characterSet: {
      type: "string",
      label: "Character Set",
      description: "The character set of the message to be used. Valid values are: GSM, Unicode and Auto. When using Auto the most appropriate character set is automatically detected. The default value is GSM. When using auto, if unicode characters are detected, the number of characters available in a message will change from 160 to 70.",
      options: constants.CHARACTER_SETS,
      optional: true,
    },
    validity: {
      type: "integer",
      label: "Validity",
      description: "The validity period for this message in hours (default to 0 which indicates the MAX allowed). The maximum allowed validity period is 72 hours.",
      optional: true,
    },
  },
  async run({ $ }) {
    const response = await this.esendex.sendMessage({
      $,
      data: {
        accountreference: this.accountReference,
        sendat: this.sendAt,
        messages: [
          {
            to: this.to,
            body: this.message,
            from: this.from,
            type: "SMS",
            characterset: this.characterSet,
            validity: this.validity,
          },
        ],
      },
    });
    $.export("$summary", `Successfully sent SMS message to ${this.to}`);
    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
Esendex	`esendex`	`app`	This component uses the Esendex app.
Account Reference	`accountReference`	`string`	Select a value from the drop down menu.
To	`to`	`string`	The phone number to send the message to. E.g. `447700900123`
Message	`message`	`string`	The message to send
From	`from`	`string`	The default alphanumeric originator that the message appears to originate from. This must be either a valid phone number or an alphanumeric value with a maximum length of 11 characters, that may contain letters, numbers and the following special characters: * $ ? ! ” # % & _ - , @ ' +. Special characters may not work for all networks in France.
Send At	`sendAt`	`string`	The scheduled time to send the messages in this request. The format is `yyyy-MM-ddThh:mm:ssZ` where y=year, M=month, d=day, T=separator, h=hour, m=min and s=seconds. The value is treated as per ISO 8601 semantics, e.g. without time zone information the value is assumed to be the local time of the server, otherwise as an offset from UTC with Z representing a UTC time.
Character Set	`characterSet`	`string`	Select a value from the drop down menu:`GSMUnicodeAuto`
Validity	`validity`	`integer`	The validity period for this message in hours (default to 0 which indicates the MAX allowed). The maximum allowed validity period is 72 hours.