Update Order with ShipHero API on New Contact from Twilio SendGrid API

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

Trigger workflow on

New Contact from the Twilio SendGrid API

Next, do this

Update Order with the ShipHero 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 Twilio SendGrid trigger and ShipHero action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Contact trigger
1. Connect your Twilio SendGrid account
2. Configure timer
Configure the Update Order action
1. Connect your ShipHero account
2. Select a Order ID
3. Optional- Configure Order Number
4. Optional- Configure Partner Order ID
5. Optional- Configure Fulfillment Status
6. Optional- Configure Order Date
7. Optional- Configure Total Tax
8. Optional- Configure Subtotal
9. Optional- Configure Total Discounts
10. Optional- Configure Total Price
11. Optional- Configure Custom Invoice URL
12. Optional- Configure Profile
13. Optional- Configure Packing Note
14. Optional- Configure Required Ship Date
15. Optional- Configure Tags
16. Optional- Configure Priority Flag
17. Optional- Configure Gift Note
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 Contact on Twilio SendGrid

Description:Emit new event when a new contact is created

Version:0.0.7

Key:sendgrid-new-contact

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.

Trigger Code#

import orderBy from "lodash/orderBy.js";
import common from "../common/timer-based.mjs";

export default {
  ...common,
  key: "sendgrid-new-contact",
  name: "New Contact",
  description: "Emit new event when a new contact is created",
  version: "0.0.7",
  type: "source",
  dedupe: "unique",
  hooks: {
    async activate() {
      const currentTimestamp = Date.now();
      const state = {
        processedItems: [],
        lowerTimestamp: currentTimestamp,
        upperTimestamp: currentTimestamp,
      };
      this.db.set("state", state);
    },
  },
  methods: {
    ...common.methods,
    _maxDelayTime() {
      // There is no report from SendGrid as to how much time it takes
      // for a contact to be created and appear in search results, so
      // we're using a rough estimate of 30 minutes here.
      return 30 * 60 * 1000;  // 30 minutes, in milliseconds
    },
    _addDelayOffset(timestamp) {
      return timestamp - this._maxDelayTime();
    },
    _cleanupOldProcessedItems(processedItems, currentTimestamp) {
      return processedItems
        .map((item) => ({
          // We just need to keep track of the record ID and
          // its creation date.
          id: item.id,
          created_at: item.created_at,
        }))
        .filter((item) => {
          const { created_at: createdAt } = item;
          const createdAtTimestamp = Date.parse(createdAt);
          const cutoffTimestamp = this._addDelayOffset(currentTimestamp);
          return createdAtTimestamp > cutoffTimestamp;
        });
    },
    _makeSearchQuery(processedItems, lowerTimestamp, upperTimestamp) {
      const idList = processedItems
        .map((item) => item.id)
        .map((id) => `'${id}'`)
        .join(", ")
      || "''";
      const startTimestamp = this._addDelayOffset(lowerTimestamp);
      const startDate = this.toISOString(startTimestamp);
      const endDate = this.toISOString(upperTimestamp);
      return `
        contact_id NOT IN (${idList}) AND
        created_at BETWEEN
          TIMESTAMP '${startDate}' AND
          TIMESTAMP '${endDate}'
      `;
    },
    generateMeta(data) {
      const {
        item,
        eventTimestamp: ts,
      } = data;
      const {
        id,
        email,
      } = item;
      const slugifiedEmail = this.slugifyEmail(email);
      const summary = `New contact: ${slugifiedEmail}`;
      return {
        id,
        summary,
        ts,
      };
    },
    async processEvent(event) {
      // Transform the timer timestamp to milliseconds
      // to be consistent with how Javascript handles timestamps.
      const eventTimestamp = event.timestamp * 1000;

      // Retrieve the current state of the component.
      const {
        processedItems,
        lowerTimestamp,
        upperTimestamp,
      } = this.db.get("state");

      // Search for contacts within a specific timeframe, excluding
      // items that have already been processed.
      const query = this._makeSearchQuery(processedItems, lowerTimestamp, upperTimestamp);
      const {
        result: items,
        contact_count: contactCount,
      } = await this.sendgrid.searchContacts(query);

      // If no contacts have been retrieved via the API,
      // move the time window forward to possibly capture newer contacts.
      if (contactCount === 0) {
        const newState = {
          processedItems: this._cleanupOldProcessedItems(processedItems, lowerTimestamp),
          lowerTimestamp: upperTimestamp,
          upperTimestamp: eventTimestamp,
        };
        this.db.set("state", newState);
        return;
      }

      // We process the searched records from oldest to newest.
      const itemsToProcess = orderBy(items, "created_at");
      itemsToProcess
        .forEach((item) => {
          const meta = this.generateMeta({
            item,
            eventTimestamp,
          });
          this.$emit(item, meta);
        });

      // Use the timestamp of the last processed record as a lower bound for
      // following searches. This bound will be subjected to an offset so in
      // case older records appear in future search results, but have not
      // appeared until now, can be processed. We only adjust it if it means
      // moving forward, not backwards. Otherwise, we might start retrieving
      // older and older records indefinitely (and we're all about *new*
      // records!)
      const newLowerTimestamp = Math.max(
        lowerTimestamp,
        Date.parse(itemsToProcess[0].created_at),
      );

      // If the total contact count is less than 100, it means that during the
      // next iteration the search results count will most likely be less than
      // 50. In that case, if we extend the upper bound of the search time range
      // we might be able to retrieve more records.
      const newUpperTimestamp = contactCount < 100
        ? eventTimestamp
        : upperTimestamp;

      // The list of processed items can grow indefinitely.
      // Since we don't want to keep track of every processed record
      // ever, we need to clean up this list, removing any records
      // that are no longer relevant.
      const newProcessedItems = this._cleanupOldProcessedItems(
        [
          ...processedItems,
          ...itemsToProcess,
        ],
        newLowerTimestamp,
      );

      // Update the state of the component to reflect the computations
      // made above.
      const newState = {
        processedItems: newProcessedItems,
        lowerTimestamp: newLowerTimestamp,
        upperTimestamp: newUpperTimestamp,
      };
      this.db.set("state", newState);
    },
  },
};

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
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Twilio SendGrid	`sendgrid`	`app`	This component uses the Twilio SendGrid app.
	`timer`	`$.interface.timer`

Trigger Authentication#

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

About Twilio SendGrid#

Send marketing and transactional email through the Twilio SendGrid platform with the Email API, proprietary mail transfer agent, and infrastructure for scalable delivery.

Action#

Update Order on ShipHero

Description:Update an order. [See the documentation](https://developer.shiphero.com/getting-started/)

Version:0.0.1

Key:shiphero-update-order

View on GitHub

ShipHero Overview#

The ShipHero API enables granular control over warehousing and order fulfillment processes, offering endpoints for managing inventory, orders, returns, and shipping. In Pipedream, you can leverage this API to automate routine tasks, sync data across multiple platforms, and trigger actions based on specific events. This can save time, reduce errors, and increase operational efficiency for e-commerce businesses.

Action Code#

import app from "../../shiphero.app.mjs";
import orderMutations from "../../common/mutations/order.mjs";

export default {
  key: "shiphero-update-order",
  name: "Update Order",
  description: "Update an order. [See the documentation](https://developer.shiphero.com/getting-started/)",
  type: "action",
  version: "0.0.1",
  props: {
    app,
    orderId: {
      propDefinition: [
        app,
        "orderId",
      ],
    },
    orderNumber: {
      type: "string",
      label: "Order Number",
      description: "The order number.",
      optional: true,
    },
    partnerOrderId: {
      type: "string",
      label: "Partner Order ID",
      description: "The partner order ID.",
      optional: true,
    },
    fulfillmentStatus: {
      type: "string",
      label: "Fulfillment Status",
      description: "The fulfillment status.",
      optional: true,
    },
    orderDate: {
      type: "string",
      label: "Order Date",
      description: "The order date. A DateTime field type that understand **ISO 8601** strings, besides datetime objects. It supports strings with and without times, as well as using `T` or space as delimiter\nEg.\n- `YYYY-mm-dd`\n- `YYYY-mm-dd HH:MM:SS`\n - `YYYY-mm-ddTHH:MM:SS`",
      optional: true,
    },
    totalTax: {
      type: "string",
      label: "Total Tax",
      description: "The total tax for the order.",
      optional: true,
    },
    subtotal: {
      type: "string",
      label: "Subtotal",
      description: "The subtotal for the order.",
      optional: true,
    },
    totalDiscounts: {
      type: "string",
      label: "Total Discounts",
      description: "The total discounts for the order.",
      optional: true,
    },
    totalPrice: {
      type: "string",
      label: "Total Price",
      description: "The total price for the order.",
      optional: true,
    },
    customInvoiceUrl: {
      type: "string",
      label: "Custom Invoice URL",
      description: "The custom invoice URL for the order.",
      optional: true,
    },
    profile: {
      type: "string",
      label: "Profile",
      description: "The profile for the order.",
      optional: true,
    },
    packingNote: {
      type: "string",
      label: "Packing Note",
      description: "The packing note for the order.",
      optional: true,
    },
    requiredShipDate: {
      type: "string",
      label: "Required Ship Date",
      description: "The required ship date for the order. A DateTime field type that understand **ISO 8601** strings, besides datetime objects. It supports strings with and without times, as well as using `T` or space as delimiter\nEg.\n- `YYYY-mm-dd`\n- `YYYY-mm-dd HH:MM:SS`\n - `YYYY-mm-ddTHH:MM:SS`",
      optional: true,
    },
    tags: {
      type: "string[]",
      label: "Tags",
      description: "The tags for the order.",
      optional: true,
    },
    priorityFlag: {
      type: "boolean",
      label: "Priority Flag",
      description: "The priority flag for the order.",
      optional: true,
    },
    giftNote: {
      type: "string",
      label: "Gift Note",
      description: "The gift note for the order.",
      optional: true,
    },
  },
  methods: {
    updateOrder(variables = {}) {
      return this.app.makeRequest({
        query: orderMutations.updateOrder,
        variables,
      });
    },
  },
  async run({ $: step }) {
    const {
      // eslint-disable-next-line no-unused-vars
      app,
      updateOrder,
      ...variables
    } = this;

    const response = await updateOrder(variables);

    step.export("$summary", `Successfully updated order with request ID \`${response.order_update.request_id}\`.`);

    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
ShipHero	`app`	`app`	This component uses the ShipHero app.
Order ID	`orderId`	`string`	Select a value from the drop down menu.
Order Number	`orderNumber`	`string`	The order number.
Partner Order ID	`partnerOrderId`	`string`	The partner order ID.
Fulfillment Status	`fulfillmentStatus`	`string`	The fulfillment status.
Order Date	`orderDate`	`string`	The order date. A DateTime field type that understand ISO 8601 strings, besides datetime objects. It supports strings with and without times, as well as using `T` or space as delimiter Eg. `YYYY-mm-dd` `YYYY-mm-dd HH:MM:SS` `YYYY-mm-ddTHH:MM:SS`
Total Tax	`totalTax`	`string`	The total tax for the order.
Subtotal	`subtotal`	`string`	The subtotal for the order.
Total Discounts	`totalDiscounts`	`string`	The total discounts for the order.
Total Price	`totalPrice`	`string`	The total price for the order.
Custom Invoice URL	`customInvoiceUrl`	`string`	The custom invoice URL for the order.
Profile	`profile`	`string`	The profile for the order.
Packing Note	`packingNote`	`string`	The packing note for the order.
Required Ship Date	`requiredShipDate`	`string`	The required ship date for the order. A DateTime field type that understand ISO 8601 strings, besides datetime objects. It supports strings with and without times, as well as using `T` or space as delimiter Eg. `YYYY-mm-dd` `YYYY-mm-dd HH:MM:SS` `YYYY-mm-ddTHH:MM:SS`
Tags	`tags`	`string[]`	The tags for the order.
Priority Flag	`priorityFlag`	`boolean`	The priority flag for the order.
Gift Note	`giftNote`	`string`	The gift note for the order.

Action Authentication#

ShipHero uses OAuth authentication. When you connect your ShipHero account, Pipedream will open a popup window where you can sign into ShipHero and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any ShipHero API.

Pipedream requests the following authorization scopes when you connect your account:

Update Order with ShipHero API on New Contact from Twilio SendGrid API

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

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

Developers ♥ Pipedream

1-24of2,400+apps by most popular

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