Issue Virtual Card with Ramp (Sandbox) API on New Deleted User from Snowflake API

Pipedream makes it easy to connect APIs for Ramp (Sandbox), Snowflake and 2,400+ other apps remarkably fast.

Trigger workflow on

New Deleted User from the Snowflake API

Next, do this

Issue Virtual Card with the Ramp (Sandbox) 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 Snowflake trigger and Ramp (Sandbox) action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Deleted User trigger
1. Connect your Snowflake account
2. Configure timer
Configure the Issue Virtual Card action
1. Connect your Ramp (Sandbox) 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 Deleted User on Snowflake

Description:Emit new event when a user is deleted

Version:0.1.2

Key:snowflake-deleted-user

View on GitHub

Snowflake Overview#

Snowflake offers a cloud database and related tools to help developers create robust, secure, and scalable data warehouses. See Snowflake's Key Concepts & Architecture.

Getting Started

1. Create a user, role and warehouse in Snowflake

Snowflake recommends you create a new user, role, and warehouse when you integrate a third-party tool like Pipedream. This way, you can control permissions via the user / role, and separate Pipedream compute and costs with the warehouse. You can do this directly in the Snowflake UI.

We recommend you create a read-only account if you only need to query Snowflake. If you need to insert data into Snowflake, add permissions on the appropriate objects after you create your user.

2. Enter those details in Pipedream

Visit https://pipedream.com/accounts. Click the button to Connect an App. Enter the required Snowflake account data.

You'll only need to connect your account once in Pipedream. You can connect this account to multiple workflows to run queries against Snowflake, insert data, and more.

3. Build your first workflow

Visit https://pipedream.com/new to build your first workflow. Pipedream workflows let you connect Snowflake with 1,000+ other apps. You can trigger workflows on Snowflake queries, sending results to Slack, Google Sheets, or any app that exposes an API. Or you can accept data from another app, transform it with Python, Node.js, Go or Bash code, and insert it into Snowflake.

Learn more at Pipedream University.

Trigger Code#

import common from "../common-delete.mjs";

export default {
  ...common,
  type: "source",
  key: "snowflake-deleted-user",
  name: "New Deleted User",
  description: "Emit new event when a user is deleted",
  version: "0.1.2",
  methods: {
    ...common.methods,
    getSqlText() {
      return "show users";
    },
  },
};

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
Snowflake	`snowflake`	`app`	This component uses the Snowflake app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`	Monitor for changes on this schedule.

Trigger Authentication#

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

We recommend you create a read-only account if you only need to query Snowflake. If you need to insert data into Snowflake, add permissions on the appropriate objects after you create your user.

About Snowflake#

A data warehouse built for the cloud

Action#

Issue Virtual Card on Ramp (Sandbox)

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.2

Key:ramp_sandbox-issue-virtual-card

View on GitHub

Ramp (Sandbox) Overview#

The Ramp (Sandbox) API provides programmatic access to manage corporate cards and spending in a controlled environment, ideal for testing and development. With this API on Pipedream, developers can automate financial operations, synchronize accounting data, and streamline expense management workflows. Leveraging Pipedream's capabilities, users can integrate Ramp with other services to enhance financial visibility, automate reconciliation processes, and trigger actions based on spending activities.

Action Code#

import ramp from "../../ramp_sandbox.app.mjs";
import issueVirtualCard from "../../../ramp/actions/issue-virtual-card/issue-virtual-card.mjs";

export default {
  ...issueVirtualCard,
  key: "ramp_sandbox-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.2",
  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,
    },
  },
};

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 (Sandbox)	`ramp`	`app`	This component uses the Ramp (Sandbox) 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 (Sandbox) uses OAuth authentication. When you connect your Ramp (Sandbox) account, Pipedream will open a popup window where you can sign into Ramp (Sandbox) 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 (Sandbox) 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