← Mercury + Data Stores integrations

Add or update a single record with Data Stores API on New Transaction from Mercury API

Pipedream makes it easy to connect APIs for Data Stores, Mercury and 1000+ other apps remarkably fast.

Trigger workflow on
New Transaction from the Mercury API
Next, do this
Add or update a single record with the Data Stores API
No credit card required
Into to Pipedream
Watch us build a workflow
Watch us build a workflow
7 min
Watch now ➜

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

Adyen logo
Brex logo
Carta logo
Checkr logo
Chameleon logo
DevRev logo
LinkedIn logo
Netflix logo
New Relic logo
OnDeck logo
Replicated logo
Scale AI logo
Teamwork logo
Warner Bros. logo
Xendit logo

Developers Pipedream

Getting Started

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

  1. Select this integration
  2. Configure the New Transaction trigger
    1. Connect your Mercury account
    2. Configure timer
    3. Select a Account
  3. Configure the Add or update a single record action
    1. Connect your Data Stores account
    2. Configure Data Store
    3. Select a Key
    4. Configure Value
  4. Deploy the workflow
  5. Send a test event to validate your setup
  6. 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

Description:Emits an event for each new transaction in an account.
Version:0.0.2
Key:mercury-new-transaction

Mercury Overview

With the Mercury API, you can build:

  • Applications to read and analyze articles
  • Content supplements such as summaries, image captions, and video transcripts
  • A customizeable newsfeed for your website or application
  • Your own news curation and content discovery tool

Trigger Code

const mercury = require("../../mercury.app.js");
const { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } = require("@pipedream/platform");

module.exports = {
  key: "mercury-new-transaction",
  name: "New Transaction",
  description: "Emits an event for each new transaction in an account.",
  version: "0.0.2",
  dedupe: "unique",
  type: "source",
  props: {
    mercury,
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    account: {
      propDefinition: [
        mercury,
        "account",
      ],
    },
  },
  methods: {
    getMeta(transaction) {
      const {
        id, counterpartyName: summary, postedAt,
      } = transaction;
      const ts = new Date(postedAt).getTime();
      return {
        id,
        summary,
        ts,
      };
    },
  },
  async run() {
    const lastRunTime = this.db.get("lastRunTime")
      ? new Date(this.db.get("lastRunTime"))
      : this.mercury.daysAgo(1);
    const params = {
      limit: 100,
      offset: 0,
      start: lastRunTime.toISOString().split("T")[0],
    };
    let totalTransactions = params.limit;
    while (totalTransactions == params.limit) {
      const results = await this.mercury.getTransactions(this.account, params);
      const { transactions } = results;
      totalTransactions = transactions.length;
      for (const transaction of transactions) {
        this.$emit(transaction, this.getMeta(transaction));
      }
      params.offset += params.limit;
    }
    this.db.set("lastRunTime", new Date());
  },
};

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.
LabelPropTypeDescription
MercurymercuryappThis component uses the Mercury app.
N/Adb$.service.dbThis component uses $.service.db to maintain state between executions.
timer$.interface.timer
AccountaccountstringSelect a value from the drop down menu.

Trigger Authentication

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

In order to get Mercury's API key, log into your Mercury account and go to the Settings page to generate a new one.

Action

Description:Add or update a single record in your [Pipedream Data Store](https://pipedream.com/data-stores/).
Version:0.0.8
Key:data_stores-add-update-record

Data Stores Overview

With the Data Stores API, you can build applications that:

  • Store data for later retrieval
  • Retrieve data from a store
  • Update data in a store
  • Delete data from a store

Action Code

import app from "../../data_stores.app.mjs";

export default {
  key: "data_stores-add-update-record",
  name: "Add or update a single record",
  description: "Add or update a single record in your [Pipedream Data Store](https://pipedream.com/data-stores/).",
  version: "0.0.8",
  type: "action",
  props: {
    app,
    dataStore: {
      propDefinition: [
        app,
        "dataStore",
      ],
    },
    key: {
      propDefinition: [
        app,
        "key",
        ({ dataStore }) => ({
          dataStore,
        }),
      ],
      description: "Enter a key for the record you'd like to create or select an existing key to update.",
    },
    value: {
      propDefinition: [
        app,
        "value",
      ],
    },
  },
  async run({ $ }) {
    const {
      key,
      value,
    } = this;
    const exists = await this.dataStore.has(key);
    const parsedValue = this.app.parseValue(value);
    await this.dataStore.set(key, parsedValue);
    // eslint-disable-next-line multiline-ternary
    $.export("$summary", `Successfully ${exists ? "updated the record for" : "added a new record with the"} key, \`${key}\`.`);
    return {
      key,
      value: parsedValue,
    };
  },
};

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.

LabelPropTypeDescription
Data StoresappappThis component uses the Data Stores app.
Data StoredataStoredata_store

Select an existing Data Store or create a new one.

KeykeystringSelect a value from the drop down menu.
Valuevalueany

Enter a string, object, or array.

Action Authentication

The Data Stores API does not require authentication.

About Data Stores

Use Pipedream Data Stores to manage state throughout your workflows.

More Ways to Connect Data Stores + Mercury

Add or update multiple records with Data Stores API on New Transaction from Mercury API
Mercury + Data Stores
 
Try it
Delete All Records with Data Stores API on New Transaction from Mercury API
Mercury + Data Stores
 
Try it
List keys with Data Stores API on New Transaction from Mercury API
Mercury + Data Stores
 
Try it
List Records with Data Stores API on New Transaction from Mercury API
Mercury + Data Stores
 
Try it
Delete a single record with Data Stores API on New Transaction from Mercury API
Mercury + Data Stores
 
Try it
New Transaction from the Mercury API

Emits an event for each new transaction in an account.

 
Try it
Add or update a single record with the Data Stores API

Add or update a single record in your Pipedream Data Store.

 
Try it
Add or update multiple records with the Data Stores API

Add or update multiple records to your Pipedream Data Store.

 
Try it
Append to record with the Data Stores API

Append to a record in your data store Pipedream Data Store. If the record does not exist, a new record will be created in an array format.

 
Try it
Check for existence of key with the Data Stores API

Check if a key exists in your Pipedream Data Store or create one if it doesn't exist.

 
Try it
Delete a single record with the Data Stores API

Delete a single record in your Pipedream Data Store.

 
Try it