Send Reaction with LoopMessage API on New Query Results from Snowflake API

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

Trigger workflow on

New Query Results from the Snowflake API

Next, do this

Send Reaction with the LoopMessage API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

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

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a Snowflake trigger and LoopMessage action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Query Results trigger
1. Connect your Snowflake account
2. Configure timer
3. Configure SQL Query
4. Optional- Configure Primary key
5. Optional- Configure Emit individual events
Configure the Send Reaction action
1. Connect your LoopMessage account
2. Configure Recipient
3. Configure Text
4. Optional- Configure Sender Name
5. Optional- Configure Status Callback
6. Optional- Configure Status Callback Header
7. Configure Message ID
8. Select a Reaction
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 Query Results on Snowflake

Description:Run a SQL query on a schedule, triggering a workflow for each row of results

Version:0.1.13

Key:snowflake-query-results

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";
import { v4 as uuidv4 } from "uuid";

export default {
  ...common,
  type: "source",
  key: "snowflake-query-results",
  name: "New Query Results",
  // eslint-disable-next-line
  description: "Run a SQL query on a schedule, triggering a workflow for each row of results",
  version: "0.1.13",
  props: {
    ...common.props,
    sqlQuery: {
      type: "string",
      label: "SQL Query",
      description: "Run this query on a schedule, triggering the workflow for each row of results",
    },
    // Ordering props correctly
    timer: common.props.timer,
    dedupeKey: {
      type: "string",
      label: "Primary key",
      description: "The column in your query to use for de-duplication. Duplicate rows won't trigger your workflow",
      optional: true,
    },
    emitIndividualEvents: {
      propDefinition: [
        common.props.snowflake,
        "emitIndividualEvents",
      ],
    },
  },
  methods: {
    ...common.methods,
    generateMeta(data) {
      const {
        row: { [this.dedupeKey]: id = uuidv4() },
        timestamp: ts,
      } = data;
      const summary = `New event (ID: ${id})`;
      return {
        id,
        summary,
        ts,
      };
    },
    generateMetaForCollection(data) {
      const { timestamp: ts } = data;
      const id = uuidv4();
      const summary = `New event (ID: ${id})`;
      return {
        id,
        summary,
        ts,
      };
    },
    getStatement() {
      return {
        sqlText: this.sqlQuery,
      };
    },
  },
};

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 changes on this schedule
SQL Query	`sqlQuery`	`string`	Run this query on a schedule, triggering the workflow for each row of results
Primary key	`dedupeKey`	`string`	The column in your query to use for de-duplication. Duplicate rows won't trigger your workflow
Emit individual events	`emitIndividualEvents`	`boolean`	Defaults to `true`, triggering workflows on each record in the result set. Set to `false` to emit records in batch (advanced)

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 Reaction on LoopMessage

Description:Action to submit your request to the sending queue. When a request in the queue will be ready to send a reaction in iMessage, an attempt will be made to deliver it to the recipient. [See the documentation](https://docs.loopmessage.com/imessage-conversation-api/messaging/send-message#send-reaction)

Version:0.0.2

Key:loopmessage-send-reaction

View on GitHub

LoopMessage Overview#

The LoopMessage API offers you the ability to send, receive, and manage messages within your applications. Through Pipedream's integration, you can harness this API to automate communication processes, organize message flows, and even connect to various data sources or other APIs to create complex messaging workflows. With Pipedream, you can trigger actions based on events, schedule messages, and interact with users in real-time without managing servers or infrastructure.

Action Code#

import common from "../common/send-message.mjs";
import constants from "../../common/constants.mjs";

export default {
  ...common,
  key: "loopmessage-send-reaction",
  name: "Send Reaction",
  description: "Action to submit your request to the sending queue. When a request in the queue will be ready to send a reaction in iMessage, an attempt will be made to deliver it to the recipient. [See the documentation](https://docs.loopmessage.com/imessage-conversation-api/messaging/send-message#send-reaction)",
  type: "action",
  version: "0.0.2",
  props: {
    ...common.props,
    messageId: {
      type: "string",
      label: "Message ID",
      description: "The ID of the message to react to. You can get it from the webhook trigger.",
    },
    reaction: {
      type: "string",
      label: "Reaction",
      description: "Reactions that starts with `-` mean *remove* it from the message. You can check the [Apple guide](https://support.apple.com/HT206894) about reactions and tapbacks.",
      options: constants.REACTIONS,
    },
  },
  methods: {
    ...common.methods,
    getSummary(response) {
      return `Successfully sent a reaction to with ID \`${response.message_id}\``;
    },
  },
};

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
LoopMessage	`app`	`app`	This component uses the LoopMessage app.
Recipient	`recipient`	`string`	The recipient of the message. This can be a phone number or email address.
Text	`text`	`string`	The text of the message.
Sender Name	`senderName`	`string`	Your dedicated sender name. This parameter will be ignored if you send a request to a recipient who is added as a Sandbox contact. If you've connected a phone number, you'll need to keep passing your original sender name. DON'T use a phone number as a value for this parameter.
Status Callback	`statusCallback`	`string`	The URL that will receive status updates for this message. Check the Webhooks section for details. Max length is 256 characters.
Status Callback Header	`statusCallbackHeader`	`string`	The custom Authorization header will be contained in the callback request. Max length is 256 characters.
Message ID	`messageId`	`string`	The ID of the message to react to. You can get it from the webhook trigger.
Reaction	`reaction`	`string`	Select a value from the drop down menu:`lovelikedislikelaughexlaimquestion-love-like-dislike-laugh-exlaim-question`

Action Authentication#

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

About LoopMessage#

iMessage API for two-way communication

More Ways to Connect LoopMessage + Snowflake#

Other Popular Integrations#

Send Reaction with LoopMessage API on New, Updated, or Deleted Warehouse from Snowflake API

Snowflake + LoopMessage

Try it

Send Reaction with LoopMessage API on New Deleted Role from Snowflake API

Snowflake + LoopMessage

Try it

Send Reaction with LoopMessage API on New Deleted User from Snowflake API

Snowflake + LoopMessage

Try it

Send Reaction with LoopMessage API on Failed Task in Schema from Snowflake API

Snowflake + LoopMessage

Try it

Send Reaction with LoopMessage API on New Database from Snowflake API

Snowflake + LoopMessage

Try it

Popular Triggers#

New Row from the Snowflake API

Emit new event when a row is added to a table

Try it

New Query Results from the Snowflake API

Run a SQL query on a schedule, triggering a workflow for each row of results

Try it

Failed Task in Schema from the Snowflake API

Emit new events when a task fails in a database schema

Try it

New Database from the Snowflake API

Emit new event when a database is created

Try it

New Deleted Role from the Snowflake API

Emit new event when a role is deleted

Try it

Popular Actions#

Insert Multiple Rows with the Snowflake API

Insert multiple rows into a table

Try it

Insert Single Row with the Snowflake API

Insert a row into a table

Try it

Send Reaction with the LoopMessage API

Action to submit your request to the sending queue. When a request in the queue will be ready to send a reaction in iMessage, an attempt will be made to deliver it to the recipient. See the documentation

Try it

Send Text Message with the LoopMessage API

Action to send a text in iMessage to an individual recipient. See the documentation

Try it