Delete Bounces with Twilio SendGrid API on New Message from AMQP API

Pipedream makes it easy to connect APIs for Twilio SendGrid, AMQP and 2,200+ other apps remarkably fast.

Trigger workflow on

New Message from the AMQP API

Next, do this

Delete Bounces with the Twilio SendGrid 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 AMQP trigger and Twilio SendGrid 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 trigger
1. Connect your AMQP account
2. Configure Timer
3. Configure Receiver Name
4. Configure Queue Name
Configure the Delete Bounces action
1. Connect your Twilio SendGrid account
2. Configure Delete All
3. Optional- Select one or more Emails
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 on AMQP

Description:Emit new event for each new message in an [AMQP 1.0](https://www.amqp.org/sites/amqp.org/files/amqp.pdf) queue. [See the library example here](https://github.com/amqp/rhea-promise#receiving-a-message).

Version:0.0.2

Key:amqp-receive-message

View on GitHub

AMQP Overview#

AMQP (Advanced Message Queuing Protocol) is a flexible protocol designed for high-performance messaging. Integrating the AMQP API within Pipedream workflows allows for robust messaging capabilities between various systems and services. You can use it to queue tasks, run asynchronous job processing, and facilitate communication between different parts of your application or different applications altogether. AMQP's reliability and standardization make it a go-to choice for enterprise-level messaging patterns.

Trigger Code#

import amqp from "../../amqp.app.mjs";
import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";

export default {
  key: "amqp-receive-message",
  name: "New Message",
  description: "Emit new event for each new message in an [AMQP 1.0](https://www.amqp.org/sites/amqp.org/files/amqp.pdf) queue. [See the library example here](https://github.com/amqp/rhea-promise#receiving-a-message).",
  type: "source",
  version: "0.0.2",
  dedupe: "unique",
  props: {
    amqp,
    timer: {
      type: "$.interface.timer",
      label: "Timer",
      description: "The timer to use to schedule the next poll.",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    receiverName: {
      type: "string",
      label: "Receiver Name",
      description: "The name of the receiver. e.g. (`my-receiver`)",
    },
    queueName: {
      propDefinition: [
        amqp,
        "queueName",
      ],
    },
  },
  async run(event) {
    const { timestamp } = event;
    const {
      host,
      port,
      username,
      password,
    } = this.amqp.$auth;

    const {
      receiverName,
      queueName,
    } = this;

    const connection = await this.amqp.openConnection({
      host,
      port,
      username,
      password,
    });

    console.log("Create receiver");
    const receiver = await this.amqp.createReceiver({
      connection,
      name: receiverName,
      source: {
        address: queueName,
      },
      onSessionError: (context) => {
        throw context.session.error ?? "Unknown Session Error";
      },
    });

    try {
      const messages = await this.amqp.onMessageReceiver(receiver);

      messages.forEach((message, idx) => {
        const id = timestamp + idx;
        this.$emit(message, {
          id,
          ts: id,
          summary: `New Message ${message.message_id}`,
        });
      });

    } catch (error) {
      if (error.innerError) {
        console.log("Inner error", JSON.stringify(error.innerError));
      }
      throw error;

    } finally {
      await this.amqp.close(receiver);
      await this.amqp.close(connection);
    }
  },
};

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
AMQP	`amqp`	`app`	This component uses the AMQP app.
Timer	`timer`	`$.interface.timer`	The timer to use to schedule the next poll.
Receiver Name	`receiverName`	`string`	The name of the receiver. e.g. (`my-receiver`)
Queue Name	`queueName`	`string`	The name of the queue to send the message to.

Trigger Authentication#

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

Setting up AMQP requires their users enter their AMQP settings host, post, username, and password in order to connect. For more info, refer to AMQP’s documentation.

About AMQP#

AMQP (Advanced Message Queuing Protocol) Standard is a commonly used messaging protocol used in the open-source application development process.

Action#

Delete Bounces on Twilio SendGrid

Description:Allows you to delete all emails on your bounces list. [See the docs here](https://docs.sendgrid.com/api-reference/bounces-api/delete-bounces)

Version:0.0.3

Key:sendgrid-delete-bounces

View on GitHub

Twilio SendGrid Overview#

The Twilio SendGrid API opens up a world of possibilities for email automation, enabling you to send emails efficiently and track their performance. With this API, you can programmatically create and send personalized email campaigns, manage contacts, and parse inbound emails for data extraction. When you harness the power of Pipedream, you can connect SendGrid to hundreds of other apps to automate workflows, such as triggering email notifications based on specific actions, syncing email stats with your analytics, or handling incoming emails to create tasks or tickets.

Action Code#

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

export default {
  ...common,
  key: "sendgrid-delete-bounces",
  name: "Delete Bounces",
  description: "Allows you to delete all emails on your bounces list. [See the docs here](https://docs.sendgrid.com/api-reference/bounces-api/delete-bounces)",
  version: "0.0.3",
  type: "action",
  props: {
    ...common.props,
    deleteAll: {
      propDefinition: [
        common.props.sendgrid,
        "deleteAll",
      ],
      description: "This parameter allows you to delete every email in your bounce list. This can not be used with the `emails` parameter.",
    },
    emails: {
      propDefinition: [
        common.props.sendgrid,
        "bouncedEmails",
      ],
    },
  },
  async run({ $ }) {
    if (this.deleteAll && this.emails) {
      throw new Error("Must provide only one of `deleteAll` or `emails` parameters.");
    }
    const resp = await this.sendgrid.deleteBounces(this.deleteAll, this.emails);
    $.export("$summary", "Successfully deleted bounces");
    return resp;
  },
};

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
Twilio SendGrid	`sendgrid`	`app`	This component uses the Twilio SendGrid app.
Delete All	`deleteAll`	`boolean`	This parameter allows you to delete every email in your bounce list. This can not be used with the `emails` parameter.
Emails	`emails`	`string[]`	Select a value from the drop down menu.