Issue Virtual Card with Ramp API on New Requests from HTTP / Webhook API

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

Trigger workflow on

New Requests from the HTTP / Webhook API

Next, do this

Issue Virtual Card with the Ramp 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 Ramp 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 trigger
1. Optional- Configure Body Only
2. Optional- Configure Response Status Code
3. Optional- Configure Response Content-Type
4. Optional- Configure Response Body
5. Connect your HTTP / Webhook account
Configure the Issue Virtual Card action
1. Connect your Ramp account
2. Configure Virtual Card Name
3. Select a User ID
4. Configure Link to Existing Spend Program
5. Optional- Select a Spend Program ID
6. Optional- Select one or more Allowed Categories
7. Optional- Select one or more Blocked Categories
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 on HTTP / Webhook

Description:Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.

Version:0.1.1

Key:http-new-requests

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
export default {
  key: "http-new-requests",
  name: "New Requests",
  description: "Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.",
  version: "0.1.1",
  type: "source",
  props: {
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    emitBodyOnly: {
      type: "boolean",
      label: "Body Only",
      description: "This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.",
      optional: true,
      default: false,
    },
    resStatusCode: {
      type: "string",
      label: "Response Status Code",
      description: "The status code to return in the HTTP response",
      optional: true,
      default: "200",
    },
    resContentType: {
      type: "string",
      label: "Response Content-Type",
      description: "The `Content-Type` of the body returned in the HTTP response",
      optional: true,
      default: "application/json",
    },
    resBody: {
      type: "string",
      label: "Response Body",
      description: "The body to return in the HTTP response",
      optional: true,
      default: "{ \"success\": true }",
    },
    http,
  },
  async run(event) {
    const summary = `${event.method} ${event.path}`;

    this.httpInterface.respond({
      status: this.resStatusCode,
      body: this.resBody,
      headers: {
        "content-type": this.resContentType,
      },
    });

    if (this.emitBodyOnly) {
      this.$emit(event.body, {
        summary,
      });
    } else {
      this.$emit(event, {
        summary,
      });
    }
  },
};

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.
Body Only	`emitBodyOnly`	`boolean`	This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.
Response Status Code	`resStatusCode`	`string`	The status code to return in the HTTP response
Response Content-Type	`resContentType`	`string`	The `Content-Type` of the body returned in the HTTP response
Response Body	`resBody`	`string`	The body to return in the HTTP response
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#

Issue Virtual Card on Ramp

Description:Creates a new virtual card for a given user. [See the documentation](https://docs.ramp.com/developer-api/v1/reference/rest/limits#post-developer-v1-limits-deferred)

Version:0.0.3

Key:ramp-issue-virtual-card

View on GitHub

Ramp Overview#

The Ramp API provides programmatic access to financial and accounting functionalities, allowing for the management of company cards, transactions, and reporting. By leveraging the Ramp API within Pipedream, you can automate intricate finance operations, synchronize transaction data with accounting software, trigger notifications based on spending activities, and analyze financial data in real-time, integrating with other services for enhanced financial workflows.

Action Code#

import ramp from "../../ramp.app.mjs";
import { v4 as uuidv4 } from "uuid";

export default {
  key: "ramp-issue-virtual-card",
  name: "Issue Virtual Card",
  description: "Creates a new virtual card for a given user. [See the documentation](https://docs.ramp.com/developer-api/v1/reference/rest/limits#post-developer-v1-limits-deferred)",
  version: "0.0.3",
  type: "action",
  props: {
    ramp,
    displayName: {
      type: "string",
      label: "Virtual Card Name",
      description: "The name of the virtual card",
    },
    userId: {
      propDefinition: [
        ramp,
        "userId",
      ],
    },
    linkToSpendProgram: {
      type: "boolean",
      label: "Link to Existing Spend Program",
      description: "Whether to link the card to an existing spend program",
      reloadProps: true,
    },
    spendProgramId: {
      propDefinition: [
        ramp,
        "spendProgramId",
      ],
      hidden: true,
    },
    allowedCategories: {
      propDefinition: [
        ramp,
        "allowedCategories",
      ],
      hidden: true,
    },
    blockedCategories: {
      propDefinition: [
        ramp,
        "blockedCategories",
      ],
      hidden: true,
    },
  },
  async additionalProps(props) {
    const newProps = {};
    if (this.linkToSpendProgram === undefined) {
      return newProps;
    }
    if (this.linkToSpendProgram) {
      props.spendProgramId.hidden = false;
    } else if (this.linkToSpendProgram === false) {
      props.spendProgramId.hidden = true;
      props.allowedCategories.hidden = false;
      props.blockedCategories.hidden = false;
      newProps.primaryCardEnabled = {
        type: "boolean",
        label: "Primary Card Enabled",
        description: "Dictates whether the user's physical card can be linked to this limit",
      };
      newProps.reimbursementsEnabled = {
        type: "boolean",
        label: "Reimbursements Enabled",
        description: "Dictates whether reimbursements can be submitted against this limit",
      };
      newProps.isShareable = {
        type: "boolean",
        label: "Is Shareable",
        description: "Dictates whether the spend limit is shareable among multiple users",
        optional: true,
      };
    }
    newProps.limit = {
      type: "string",
      label: "Total Limit per Interval (USD)",
      description: "Total amount limit per interval in USD",
    };
    newProps.interval = {
      type: "string",
      label: "Interval",
      description: "Time interval to apply limit to",
      options: [
        "ANNUAL",
        "DAILY",
        "MONTHLY",
        "QUARTERLY",
        "TERTIARY",
        "TOTAL",
        "WEEKLY",
        "YEARLY",
      ],
    };
    newProps.transactionAmountLimit = {
      type: "string",
      label: "Maximum Spend per Transaction (USD)",
      description: "Max amount per transaction in USD",
      optional: true,
    };
    return newProps;
  },
  methods: {
    formatUSD(amount) {
      if (!amount) {
        return undefined;
      }
      return +(amount.split("$").pop()) * 100;
    },
  },
  async run({ $ }) {
    const response = await this.ramp.createLimit({
      $,
      data: {
        idempotency_key: uuidv4(),
        display_name: this.displayName,
        user_id: this.userId,
        spend_program_id: this.spendProgramId,
        permitted_spend_types: !this.linkToSpendProgram
          ? {
            primary_card_enabled: this.primaryCardEnabled,
            reimbursements_enabled: this.reimbursementsEnabled,
          }
          : undefined,
        spending_restrictions: !this.spendProgramId
          ? {
            limit: {
              amount: this.formatUSD(this.limit),
            },
            interval: this.interval,
            transaction_amount_limit: this.transactionAmountLimit
              ? {
                amount: this.formatUSD(this.transactionAmountLimit),
              }
              : undefined,
            allowed_categories: this.allowedCategories,
            blocked_categories: this.blockedCategories,
          }
          : undefined,
        is_shareable: this.isShareable,
      },
    });
    $.export("$summary", `Successfully created new limit 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
Ramp	`ramp`	`app`	This component uses the Ramp app.
Virtual Card Name	`displayName`	`string`	The name of the virtual card
User ID	`userId`	`string`	Select a value from the drop down menu.
Link to Existing Spend Program	`linkToSpendProgram`	`boolean`	Whether to link the card to an existing spend program

Action Authentication#

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

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

transactions:readcards:readcards:writespend_programs:readspend_programs:writeusers:readusers:writelocations:readlocations:writelimits:readlimits:writedepartments:readdepartments:writebusiness:readreceipts:readtransfers:readvendors:readmerchants:readaccounting:readreceipts:write

About Ramp#

The Corporate Card That Helps You Spend Less

More Ways to Connect Ramp + HTTP / Webhook#

Other Popular Integrations#

Create User Invite with Ramp API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Ramp