List keys with Data Stores API on New Transaction from Mercury API

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

Trigger workflow on

New Transaction from the Mercury API

Next, do this

List keys with the Data Stores API

No credit card required

▶

Watch us build a workflow

4 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 Mercury trigger and Data Stores action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Transaction trigger
1. Connect your Mercury account
2. Configure timer
3. Select a Account
Configure the List keys action
1. Connect your Data Stores account
2. Configure Data Store
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 Transaction on Mercury

Description:Emit new event for each transaction in an account.

Version:0.0.3

Key:mercury-new-transaction

View on GitHub

Mercury Overview#

The Mercury API offers a window into banking tailored for startups. With it, you can automate your financial operations, sync transaction data with your accounting software, and monitor your business financial health programmatically. Creating workflows on Pipedream with Mercury's API allows you to connect your banking data with numerous other apps to streamline payments, reconcile transactions, and keep a pulse on your company's money matters.

Trigger Code#

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

export default {
  key: "mercury-new-transaction",
  name: "New Transaction",
  description: "Emit new event for each transaction in an account.",
  version: "0.0.3",
  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({
        ctx: $,
        accountId: 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.

Label	Prop	Type	Description
Mercury	`mercury`	`app`	This component uses the Mercury app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`
Account	`account`	`string`	Select 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.

About Mercury#

Bank

Action#

List keys on Data Stores

Description:List all keys in your [Pipedream Data Store](https://pipedream.com/data-stores/).

Version:0.0.2

Key:data_stores-list-keys

View on GitHub

Data Stores Overview#

Data Stores are a key-value store that allow you to persist state and share data across workflows. You can perform CRUD operations, enabling dynamic data management within your serverless architecture. Use it to save results from API calls, user inputs, or interim data; then read, update, or enrich this data in subsequent steps or workflows. Data Stores simplify stateful logic and cross-workflow communication, making them ideal for tracking process statuses, aggregating metrics, or serving as a simple configuration store.

Action Code#

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

export default {
  key: "data_stores-list-keys",
  name: "List keys",
  description: "List all keys in your [Pipedream Data Store](https://pipedream.com/data-stores/).",
  version: "0.0.2",
  type: "action",
  props: {
    app,
    dataStore: {
      propDefinition: [
        app,
        "dataStore",
      ],
    },
  },
  async run ({ $ }) {
    const keys = await this.dataStore.keys();
    if (keys.length > 0) {
      $.export("$summary", `Found ${keys.length} key(s).`);
    } else {
      $.export("$summary", "No keys found.");
    }
    return keys;
  },
};