Add or update multiple records with Data Stores API on New Transaction from GoCardless Bank Account Data (formerly Nordigen) API

Pipedream makes it easy to connect APIs for Data Stores, GoCardless Bank Account Data (formerly Nordigen) and 2,000+ other apps remarkably fast.

Trigger workflow on

New Transaction from the GoCardless Bank Account Data (formerly Nordigen) API

Next, do this

Add or update multiple records 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 GoCardless Bank Account Data (formerly Nordigen) 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 GoCardless Bank Account Data (formerly Nordigen) account
2. Configure Timer
3. Select a Requisition Id
4. Select a AccountId
Configure the Add or update multiple records action
1. Connect your Data Stores account
2. Configure Data Store
3. Configure Data
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 GoCardless Bank Account Data (formerly Nordigen)

Description:Emit new event when a transaction occurs

Version:1.0.0

Key:nordigen-new-transaction

View on GitHub

GoCardless Bank Account Data (formerly Nordigen) Overview#

The GoCardless Bank Account Data API furnishes you with the ability to access enriched banking data, enabling the creation of financial insights and streamlining customer verification processes. By integrating this API with Pipedream, you can automate various tasks involving bank account transactions and customer data analysis. For instance, you might set up workflows to monitor transactions for accounting purposes, verify customer account details for KYC compliance, or aggregate financial data to provide personalized financial advice.

Trigger Code#

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

export default {
  key: "nordigen-new-transaction",
  name: "New Transaction",
  description: "Emit new event when a transaction occurs",
  version: "1.0.0",
  type: "source",
  dedupe: "unique",
  props: {
    db: "$.service.db",
    nordigen,
    timer: {
      type: "$.interface.timer",
      label: "Timer",
      description: "When should the source check for a new event",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    requisitionId: {
      propDefinition: [
        nordigen,
        "requisitionId",
      ],
    },
    accountId: {
      propDefinition: [
        nordigen,
        "accountId",
        (c) => ({
          requisitionId: c.requisitionId,
        }),
      ],
    },
  },
  methods: {
    _getLastTransactionDate() {
      return this.db.get("lastTransactionDate");
    },
    _setLastTransactionDate(lastTransactionDate) {
      this.db.set("lastTransactionDate", lastTransactionDate);
    },
  },
  async run() {
    let lastTransactionDate = this._getLastTransactionDate();
    const args = lastTransactionDate
      ? {
        params: {
          date_from: lastTransactionDate,
        },
      }
      : {};
    const transactions = await this.nordigen.listTransactions(this.accountId, args);

    transactions.forEach((transaction) => {
      if (!lastTransactionDate
        || Date.parse(transaction.bookingDate) > Date.parse(lastTransactionDate)) {
        lastTransactionDate = transaction.bookingDate;
      }
      this.$emit(transaction, {
        summary: `${transaction.transactionAmount.amount} ${transaction.transactionAmount.currency} - ${transaction.valueDate}`,
        id: transaction.transactionId,
        ts: new Date(),
      });
    });

    this._setLastTransactionDate(lastTransactionDate);
  },
};

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.
GoCardless Bank Account Data (formerly Nordigen)	`nordigen`	`app`	This component uses the GoCardless Bank Account Data (formerly Nordigen) app.
Timer	`timer`	`$.interface.timer`	When should the source check for a new event
Requisition Id	`requisitionId`	`string`	Select a value from the drop down menu.
AccountId	`accountId`	`string`	Select a value from the drop down menu.

Trigger Authentication#

GoCardless Bank Account Data (formerly Nordigen) uses OAuth authentication. When you connect your GoCardless Bank Account Data (formerly Nordigen) account, Pipedream will open a popup window where you can sign into GoCardless Bank Account Data (formerly Nordigen) and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any GoCardless Bank Account Data (formerly Nordigen) API.

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

About GoCardless Bank Account Data (formerly Nordigen)#

The Nordigen product has now been relaunched as GoCardless Bank Account Data.

Action#

Add or update multiple records on Data Stores

Description:Add or update multiple records to your [Pipedream Data Store](https://pipedream.com/data-stores/).

Version:0.0.6

Key:data_stores-add-update-multiple-records

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-add-update-multiple-records",
  name: "Add or update multiple records",
  description: "Add or update multiple records to your [Pipedream Data Store](https://pipedream.com/data-stores/).",
  version: "0.0.6",
  type: "action",
  props: {
    app,
    dataStore: {
      propDefinition: [
        app,
        "dataStore",
      ],
    },
    data: {
      label: "Data",
      type: "object",
      description: "Enter data you'd like to add as key-value pairs, or reference an object from a previous step using a custom expression (e.g., `{{steps.data.$return_value}}`). Note that any keys that are duplicated will get overwritten with the last value entered (so `[{jerry: \"constanza\", jerry: \"seinfeld\"}]` will get stored as `[{jerry: \"seinfeld\"}]`).",
    },
  },
  methods: {
    /**
     * Tries to convert a string to a JSON object or a primitive value.
     * @param {any} value Value to be converted
     * @returns The converted value
     */
    convertString(value) {
      // If type is already primitive non string, return it
      const primitives = [
        "boolean",
        "number",
      ];
      if (primitives.includes(typeof value)) {
        return value;
      }

      // Tries to convert string to possible other primitive types
      if (typeof value === "string") {
        // Convert boolean
        if (value.toLowerCase() === "true") {
          return true;
        }
        if (value.toLowerCase() === "false") {
          return false;
        }

        // Convert number
        if (!isNaN(value)) {
          return parseFloat(value);
        }
      }

      return this.app.evaluate(value);
    },
    /**
     * Add all the key-value pairs in the map object to be used in the data store
     * @param {*} data Data to be parsed
     * @param {Map} map Hashmap to be updated
     */
    populateHashMapOfData(data, map) {
      if (!Array.isArray(data) && typeof(data) === "object") {
        Object.keys(data).forEach((key) => map[key] = this.convertString(data[key]));
        return;
      }

      if (Array.isArray(data)) {
        for (const item of data) {
          this.populateHashMapOfData(item, map);
        }
      }
    },
    getHashMapOfData(data) {
      const map = {};
      this.populateHashMapOfData(data, map);
      return map;
    },
  },
  async run({ $ }) {
    if (typeof this.data === "string") {
      this.data = this.app.evaluate(this.data);
    }
    const map = this.getHashMapOfData(this.data);
    const keys = Object.keys(map);
    const promises = Object.keys(map).map((key) => this.dataStore.set(key, map[key]));
    await Promise.all(promises);
    if (keys.length === 0) {
      $.export("$summary", "No data was added to the data store.");
    } else {
      // eslint-disable-next-line multiline-ternary
      $.export("$summary", `Successfully added or updated ${keys.length} record${keys.length === 1 ? "" : "s"}`);
    }
    return map;
  },
};

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
Data Stores	`app`	`app`	This component uses the Data Stores app.
Data Store	`dataStore`	`data_store`	Select an existing Data Store or create a new one.
Data	`data`	`object`	Enter data you'd like to add as key-value pairs, or reference an object from a previous step using a custom expression (e.g., `{{steps.data.$return_value}}`). Note that any keys that are duplicated will get overwritten with the last value entered (so `[{jerry: "constanza", jerry: "seinfeld"}]` will get stored as `[{jerry: "seinfeld"}]`).