Create Review Decision with Decision Journal API on New Contact from Twilio SendGrid API

Pipedream makes it easy to connect APIs for Decision Journal, Twilio SendGrid and 2,800+ other apps remarkably fast.

Trigger workflow on

New Contact from the Twilio SendGrid API

Next, do this

Create Review Decision with the Decision Journal 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 Decision Journal 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 Create Review Decision action
1. Connect your Decision Journal account
2. Select a Decision ID
3. Configure Accuracy Score
4. Configure Actual Outcome
5. Configure Learnings and Review
6. Select a Status
7. Optional- Configure Skill-Luck Weight
8. Optional- Select a Months to Next Review
9. Optional- Configure Outcome Estimates
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.8

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.8",
  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#

Create Review Decision on Decision Journal

Description:Creates a review for a decision in Decision Journal. [See the documentation](https://openpm.ai/apis/decision-journal#/decisions/{decisionId}/reviews)

Version:0.0.2

Key:decision_journal-create-review-decision

View on GitHub

Decision Journal Overview#

The Decision Journal API allows for the systematic tracking of decisions over time, providing a structured way to log and evaluate past choices. By integrating with Pipedream, users can automate workflows to capture decisions from various sources, set reminders for review, analyze decision patterns, and sync with other productivity tools. This supports improved decision-making processes and personal growth.

Action Code#

import app from "../../decision_journal.app.mjs";
import utils from "../../common/utils.mjs";

export default {
  key: "decision_journal-create-review-decision",
  name: "Create Review Decision",
  description: "Creates a review for a decision in Decision Journal. [See the documentation](https://openpm.ai/apis/decision-journal#/decisions/{decisionId}/reviews)",
  version: "0.0.2",
  annotations: {
    destructiveHint: false,
    openWorldHint: true,
    readOnlyHint: false,
  },
  type: "action",
  props: {
    app,
    decisionId: {
      propDefinition: [
        app,
        "decisionId",
      ],
    },
    accuracyScore: {
      propDefinition: [
        app,
        "accuracyScore",
      ],
    },
    actualOutcome: {
      propDefinition: [
        app,
        "actualOutcome",
      ],
    },
    learningsAndReview: {
      propDefinition: [
        app,
        "learningsAndReview",
      ],
    },
    status: {
      propDefinition: [
        app,
        "status",
      ],
    },
    skillLuckWeight: {
      propDefinition: [
        app,
        "skillLuckWeight",
      ],
    },
    monthsToNextReview: {
      optional: true,
      propDefinition: [
        app,
        "monthsToNextReview",
      ],
    },
    outcomeEstimates: {
      description: "An array of outcome estimates in JSON string format. For each estimate, the format is `{\"text\": \"A description of an outcome estimate\", \"probability\": \"0.50\", \"itHappened\": true }`",
      propDefinition: [
        app,
        "outcomeEstimates",
      ],
    },
  },
  methods: {
    createReview({
      decisionId, ...args
    } = {}) {
      return this.app.post({
        path: `/decisions/${decisionId}/reviews`,
        ...args,
      });
    },
  },
  async run({ $ }) {
    const {
      createReview,
      decisionId,
      tags,
      outcomeEstimates,
      ...data
    } = this;

    const response = await createReview({
      $,
      decisionId,
      data: {
        data: {
          tags: utils.parseArray(tags),
          outcomeEstimates: utils.parseArrayAndMap(outcomeEstimates),
          ...utils.filterProps(data),
        },
      },
    });

    $.export("$summary", `Successfully created a review decision with ID: ${response.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
Decision Journal	`app`	`app`	This component uses the Decision Journal app.
Decision ID	`decisionId`	`string`	Select a value from the drop down menu.
Accuracy Score	`accuracyScore`	`integer`	The accuracy score of the review. A number between `0` and `10`
Actual Outcome	`actualOutcome`	`string`	The actual outcome of the decision
Learnings and Review	`learningsAndReview`	`string`	The learnings and review notes
Status	`status`	`string`	Select a value from the drop down menu:`publisheddraft`
Skill-Luck Weight	`skillLuckWeight`	`string`	A number between `0` and `1` representing the weight of skill vs luck in the outcome
Months to Next Review	`monthsToNextReview`	`integer`	Select a value from the drop down menu:`{ "label": "1 Month", "value": 1 }{ "label": "3 Months", "value": 3 }{ "label": "6 Months", "value": 6 }{ "label": "1 Year", "value": 12 }`
Outcome Estimates	`outcomeEstimates`	`string[]`	An array of outcome estimates in JSON string format. For each estimate, the format is `{"text": "A description of an outcome estimate", "probability": "0.50", "itHappened": true }`

Action Authentication#

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

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

all:readall:write