Get Transactions with Plaid API on New Requests (Payload Only) from HTTP / Webhook API

Pipedream makes it easy to connect APIs for Plaid, HTTP / Webhook and 2,900+ other apps remarkably fast.

Trigger workflow on

New Requests (Payload Only) from the HTTP / Webhook API

Next, do this

Get Transactions with the Plaid 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 HTTP / Webhook trigger and Plaid action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Requests (Payload Only) trigger
1. Connect your HTTP / Webhook account
Configure the Get Transactions action
1. Connect your Plaid account
2. Configure Access Token
3. Configure Start Date
4. Configure End Date
5. Optional- Select one or more Account IDs
6. Optional- Configure Include Original Description
7. Optional- Configure Days Requested
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 Requests (Payload Only) on HTTP / Webhook

Description:Get a URL and emit the HTTP body as an event on every request

Version:0.1.1

Key:http-new-requests-payload-only

View on GitHub

HTTP / Webhook Overview#

Build, test, and send HTTP requests without code using your Pipedream workflows. The HTTP / Webhook action is a tool to build HTTP requests with a Postman-like graphical interface.

Point and click HTTP requests

Define the target URL, HTTP verb, headers, query parameters, and payload body without writing custom code.

$A screenshot of Pipedream's HTTP Request Configuration interface with a GET request type selected. The request URL is set to 'https://api.openai.com/v1/models'. The 'Auth' tab is highlighted, indicating that authentication is required for this request. In the headers section, there are two headers configured: 'User-Agent' is set to 'pipedream/1', and 'Authorization' is set to 'Bearer {{openai_api_key}}', showing how the OpenAI account's API key is dynamically inserted into the headers to handle authentication automatically.$

Here's an example workflow that uses the HTTP / Webhook action to send an authenticated API request to OpenAI.

Focus on integrating, not authenticating

This action can also use your connected accounts with third-party APIs. Selecting an integrated app will automatically update the request’s headers to authenticate with the app properly, and even inject your token dynamically.

Pipedream integrates with thousands of APIs, but if you can’t find a Pipedream integration simply use Environment Variables in your request headers to authenticate with.

Compatible with no code actions or Node.js and Python

The HTTP/Webhook action exports HTTP response data for use in subsequent workflow steps, enabling easy data transformation, further API calls, database storage, and more.

Response data is available for both coded (Node.js, Python) and no-code steps within your workflow.

Trigger Code#

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

// Core HTTP component
// Returns a 200 OK response, emits the HTTP payload as an event
export default {
  key: "http-new-requests-payload-only",
  name: "New Requests (Payload Only)",
  // eslint-disable-next-line
  description: "Get a URL and emit the HTTP body as an event on every request",
  version: "0.1.1",
  type: "source",
  props: {
    // eslint-disable-next-line
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    http,
  },
  async run(event) {
    const { body } = event;
    this.httpInterface.respond({
      status: 200,
      body,
    });
    // Emit the HTTP payload
    this.$emit({
      body,
    });
  },
};

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	`httpInterface`	`$.interface.http`	This component uses `$.interface.http` to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the `run()` method of the component.
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.

Trigger Authentication#

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook#

Get a unique URL where you can send HTTP or webhook requests

Action#

Get Transactions on Plaid

Description:Retrieves user-authorized transaction data for a specified date range. [See the documentation](https://plaid.com/docs/api/products/transactions/#transactionsget)

Version:0.0.2

Key:plaid-get-transactions

View on GitHub

Plaid Overview#

The Plaid API offers a multitude of financial data operations, enabling developers to manage and interact with user bank accounts, transactions, identity info, and more, all within a secure and compliant ecosystem. Integrating Plaid with Pipedream can unlock powerful automations, like syncing transaction data to accounting software, verifying user identities for KYC compliance, and automating financial alerts or reporting.

Action Code#

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

export default {
  key: "plaid-get-transactions",
  name: "Get Transactions",
  description: "Retrieves user-authorized transaction data for a specified date range. [See the documentation](https://plaid.com/docs/api/products/transactions/#transactionsget)",
  version: "0.0.2",
  annotations: {
    destructiveHint: false,
    openWorldHint: true,
    readOnlyHint: true,
  },
  type: "action",
  props: {
    app,
    accessToken: {
      propDefinition: [
        app,
        "accessToken",
      ],
    },
    startDate: {
      propDefinition: [
        app,
        "startDate",
      ],
    },
    endDate: {
      propDefinition: [
        app,
        "endDate",
      ],
    },
    accountIds: {
      type: "string[]",
      label: "Account IDs",
      description: "A list of `account_ids` to retrieve for the Item. Note: An error will be returned if a provided `account_id` is not associated with the Item.",
      propDefinition: [
        app,
        "accountId",
        ({ accessToken }) => ({
          accessToken,
        }),
      ],
    },
    includeOriginalDescription: {
      type: "boolean",
      label: "Include Original Description",
      description: "Include the raw unparsed transaction description from the financial institution.",
      default: false,
      optional: true,
    },
    daysRequested: {
      type: "integer",
      label: "Days Requested",
      description: "Number of days of transaction history to request from the financial institution. Only applies when Transactions product hasn't been initialized. Min: 1, Max: 730, Default: 90.",
      min: 1,
      max: 730,
      optional: true,
    },
  },
  async run({ $ }) {
    const {
      app,
      accessToken,
      startDate,
      endDate,
      accountIds,
      includeOriginalDescription,
      daysRequested,
    } = this;

    const options = {};

    if (accountIds?.length) {
      options.account_ids = accountIds;
    }

    if (includeOriginalDescription !== undefined) {
      options.include_original_description = includeOriginalDescription;
    }

    if (daysRequested) {
      options.days_requested = daysRequested;
    }

    const transactions = await app.paginate({
      resourcesFn: app.getTransactions,
      resourcesFnArgs: {
        access_token: accessToken,
        start_date: startDate,
        end_date: endDate,
        ...(Object.keys(options).length > 0 && {
          options,
        }),
      },
      resourceName: "transactions",
    });

    const transactionCount = transactions?.length || 0;
    $.export("$summary", `Successfully retrieved ${transactionCount} transactions from ${startDate} to ${endDate}`);

    return transactions;
  },
};

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
Plaid	`app`	`app`	This component uses the Plaid app.
Access Token	`accessToken`	`string`	The access token associated with the Item data is being requested for.
Start Date	`startDate`	`string`	The earliest date for which to fetch transaction data. Dates should be formatted as `YYYY-MM-DD`.
End Date	`endDate`	`string`	The latest date for which to fetch transaction data. Dates should be formatted as `YYYY-MM-DD`.
Account IDs	`accountIds`	`string[]`	Select a value from the drop down menu.
Include Original Description	`includeOriginalDescription`	`boolean`	Include the raw unparsed transaction description from the financial institution.
Days Requested	`daysRequested`	`integer`	Number of days of transaction history to request from the financial institution. Only applies when Transactions product hasn't been initialized. Min: 1, Max: 730, Default: 90.

Action Authentication#

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

Find your client ID and client secret in your Plaid Keys settings and enter them below.

You develop Plaid apps in different environments. Please choose the environment below (you can change this at https://pipedream.com/accounts at any time).

About Plaid#

Connect to users' bank accounts.

More Ways to Connect Plaid + HTTP / Webhook#

Other Popular Integrations#

Send any HTTP Request with HTTP / Webhook API on New Event (Instant) from Plaid API

Plaid + HTTP / Webhook