import app from "../../stripe.app.mjs";
import utils from "../../common/utils.mjs";
export default {
key: "stripe-update-payment-intent",
name: "Update a Payment Intent",
type: "action",
version: "0.1.2",
description: "Update a payment intent. [See the documentation](https://stripe.com/docs/api/payment_intents/update).",
props: {
app,
id: {
propDefinition: [
app,
"paymentIntent",
],
optional: false,
},
amount: {
propDefinition: [
app,
"amount",
],
},
country: {
propDefinition: [
app,
"country",
],
},
currency: {
propDefinition: [
app,
"currency",
({ country }) => ({
country,
}),
],
default: "",
},
customer: {
propDefinition: [
app,
"customer",
],
},
description: {
propDefinition: [
app,
"description",
],
},
metadata: {
propDefinition: [
app,
"metadata",
],
},
paymentMethod: {
propDefinition: [
app,
"paymentMethod",
({ customer }) => ({
customer,
}),
],
},
receiptEmail: {
type: "string",
label: "Receipt Email",
description: "Email address that the receipt for the resulting payment will be sent to. If receipt_email is specified for a payment in live mode, a receipt will be sent regardless of your email settings.",
},
setupFutureUsage: {
propDefinition: [
app,
"setupFutureUsage",
],
},
shippingAddressCity: {
label: "Shipping - Address - City",
propDefinition: [
app,
"addressCity",
],
},
shippingAddressCountry: {
label: "Shipping - Address - Country",
propDefinition: [
app,
"addressCountry",
],
},
shippingAddressLine1: {
label: "Shipping - Address - Line 1",
propDefinition: [
app,
"addressLine1",
],
},
shippingAddressLine2: {
label: "Shipping - Address - Line 2",
propDefinition: [
app,
"addressLine2",
],
},
shippingAddressPostalCode: {
label: "Shipping - Address - Postal Code",
propDefinition: [
app,
"addressPostalCode",
],
},
shippingAddressState: {
label: "Shipping - Address - State",
propDefinition: [
app,
"addressState",
],
},
shippingName: {
propDefinition: [
app,
"shippingName",
],
},
shippingCarrier: {
propDefinition: [
app,
"shippingCarrier",
],
},
shippingPhone: {
propDefinition: [
app,
"shippingPhone",
],
},
shippingTrackingNumber: {
propDefinition: [
app,
"shippingTrackingNumber",
],
},
statementDescriptor: {
propDefinition: [
app,
"statementDescriptor",
],
},
statementDescriptorSuffix: {
propDefinition: [
app,
"statementDescriptorSuffix",
],
},
paymentMethodTypes: {
propDefinition: [
app,
"paymentMethodTypes",
],
},
},
methods: {
getOtherParams() {
const {
shippingAddressCity,
shippingAddressCountry,
shippingAddressLine1,
shippingAddressLine2,
shippingAddressPostalCode,
shippingAddressState,
shippingName,
shippingCarrier,
shippingPhone,
shippingTrackingNumber,
statementDescriptor,
statementDescriptorSuffix,
} = this;
const hasShippingData = shippingAddressCity
|| shippingAddressCountry
|| shippingAddressLine1
|| shippingAddressLine2
|| shippingAddressPostalCode
|| shippingAddressState
|| shippingName
|| shippingCarrier
|| shippingPhone
|| shippingTrackingNumber;
return {
...(hasShippingData && {
shipping: {
address: {
city: shippingAddressCity,
country: shippingAddressCountry,
line1: shippingAddressLine1,
line2: shippingAddressLine2,
postal_code: shippingAddressPostalCode,
state: shippingAddressState,
},
name: shippingName,
carrier: shippingCarrier,
phone: shippingPhone,
tracking_number: shippingTrackingNumber,
},
}),
...(statementDescriptor && {
statement_descriptor: statementDescriptor?.slice(0, 21) || undefined,
}),
...(statementDescriptorSuffix && {
statement_descriptor_suffix: statementDescriptorSuffix?.slice(0, 21) || undefined,
}),
};
},
},
async run({ $ }) {
const {
app,
id,
amount,
currency,
customer,
description,
metadata,
paymentMethod,
receiptEmail,
setupFutureUsage,
paymentMethodTypes,
} = this;
const resp = await app.sdk().paymentIntents.update(id, {
amount,
currency,
metadata: utils.parseJson(metadata),
customer,
description,
payment_method: paymentMethod,
receipt_email: receiptEmail,
setup_future_usage: setupFutureUsage,
payment_method_types: paymentMethodTypes,
...this.getOtherParams(),
});
$.export("$summary", `Successfully updated the payment intent, \`${resp.description || resp.id}\`.`);
return resp;
},
};
Chase Roberts@chsrbrts@benedictevans If you haven’t used @pipedream yet, then you haven’t lived.
✨Ellie Day✨@heyelliedayEvaluation update: @pipedream has quite literally been a dream to work with! I’m excited to leverage this tool for all the various workflows I need to write. I’m currently at 11k invocations a day from the initial workflows I’ve written in the past couple weeks.
Michael Braedley@MBraedleyUpdate: I got it working properly, and it's working so well that I'm dropping IFTTT. @pipedream can do everything that IFTTT basic can, and most (if not all things) IFTTT pro can for free or at a reasonable price if you need it. I am recommending it for basically any power user.
Thomas Cutting@mrthomascuttingWant quick+dirty integrations for a serverless workflow - @pipedream is my new go-to 😃
Matthew Roberts@mattdotrobertsday 013 - finally hit node js. This is the secret sauce of taking #nocode projects that one step further. Pumped about getting deeper into @pipedream now
Kenneth Auchenberg 💭@auchenbergYahoo Pipes is back! Kinda 😍 @pipedream
Raymond Camden 🥑@raymondcamdenAwesome video by the @pipedream folks showing real time twitter sentiment analysis integrated with Google Sheets. This is where Pipedream *really* shines, connecting systems together in easy workflows.
Nacho Caballero@nachocaballeroI couldn't recommend @pipedream more. It's an amazing service to integrate different APIs. Much more powerful than Zapier and more user-friendly than AWS Lambda. I'm very proud to wear this t-shirt #NoCode
Jason Snow@jyksnwDeveloped a working prototype environmental sensor IoT solution with @particle Photon, @pipedream, and @MongoDB with full graphing and alerting in less than a day! All amazing technology, will def. be exploring these more.
Steven Terrana@steven_terrana@burgwyn you've inspired me to finally set up my own blog. I'll make sure my first blog post explains the tech behind the setup. think @obsdmd + @GatsbyJS + @pipedream.
🚄 James Augeri, PhD@DotDotJamesWant to low-code your back end, need more horsepower than @Bubble / @KnackHQ, or just miss Yahoo! Pipes? Check out @PipeDream
Sébastien Chopin@AtinuxGitHub issues should be like @linear_app for maintainers. Looking forward more integrations with GH actions or tools like @pipedream 👀
Raul@raul_predescuIf you're a dev and not using @pipedream, you're missing out. Been using it for months, daily. FREE for devs. Plenty of integrations and good limits. Absolutely love it.
Bruno Skvorc@bitfallsSo @pipedream is pretty amazing. In 3 minutes I just made a flow which adds @rickastley's Never Gonna Give You Up to my @spotify playlist whenever a new pull request arrives in an old repo of mine.
Zach Lanich@ZachLanichUm, wow 🤯 @pipedream
Steven Bell@bellontechI just used @pipedream to build a Shopify App. Wow, they make small backed tasks easy.
Jay Hack 🎩🇺🇸@_jayhack_Very impressed with this bad boi - it reminds me of a @PalantirTech internal tool, but geared towards integrations instead of data analysis and far more customizable. Great expectations here 🚀🤩
Tree Sturgeon 🔥🚴♂️🌳@philsturgeonFor context this is day 2 of a really challenging and stupid migration from Notion to @airtable with disparate/missing data. It's going better than expected and thanks to @pipedream I don't have to bother the iOS dev to add W3W.