import app from "../../stripe.app.mjs";
import utils from "../../common/utils.mjs";
export default {
key: "stripe-create-customer",
name: "Create a Customer",
type: "action",
version: "0.1.2",
description: "Create a customer. [See the documentation](https://stripe.com/docs/api/customers/create).",
props: {
app,
name: {
description: "The customer's full name or business name.",
propDefinition: [
app,
"name",
],
},
description: {
propDefinition: [
app,
"description",
],
},
email: {
propDefinition: [
app,
"email",
],
},
addressCity: {
propDefinition: [
app,
"addressCity",
],
},
addressCountry: {
propDefinition: [
app,
"addressCountry",
],
},
addressLine1: {
propDefinition: [
app,
"addressLine1",
],
},
addressLine2: {
propDefinition: [
app,
"addressLine2",
],
},
addressPostalCode: {
propDefinition: [
app,
"addressPostalCode",
],
},
addressState: {
propDefinition: [
app,
"addressState",
],
},
metadata: {
propDefinition: [
app,
"metadata",
],
},
paymentMethodType: {
type: "string",
label: "Payment Method Type",
description: "The type of payment method to create",
propDefinition: [
app,
"paymentMethodTypes",
],
},
paymentMethod: {
propDefinition: [
app,
"paymentMethod",
({ paymentMethodType }) => ({
type: paymentMethodType,
}),
],
},
phone: {
propDefinition: [
app,
"phone",
],
},
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",
],
},
shippingPhone: {
propDefinition: [
app,
"shippingPhone",
],
},
taxIpAddress: {
type: "string",
label: "Tax - IP Address",
description: "A recent IP address of the customer used for tax reporting and tax location inference. Stripe recommends updating the IP address when a new PaymentMethod is attached or the address field on the customer is updated. We recommend against updating this field more frequently since it could result in unexpected tax location/reporting outcomes.",
optional: true,
},
taxValidateLocation: {
type: "string",
label: "Tax - Validate Location",
description: "A flag that indicates when Stripe should validate the customer tax location. Defaults to deferred.",
options: [
"deferred",
"immediately",
],
optional: true,
},
balance: {
type: "integer",
label: "Balance",
description: "An integer amount in cents that represents the customer's current balance, which affect the customer's future invoices. A negative amount represents a credit that decreases the amount due on an invoice; a positive amount increases the amount due on an invoice.",
optional: true,
},
cashBalanceSettingsReconciliationMode: {
type: "string",
label: "Cash Balance Settings - Reconciliation Mode",
description: "Controls how funds transferred by the customer are applied to payment intents and invoices. Valid options are automatic, manual, or merchant_default. For more information about these reconciliation modes, see Reconciliation.",
options: [
"automatic",
"manual",
"merchant_default",
],
optional: true,
},
invoicePrefix: {
type: "string",
label: "Invoice Prefix",
description: "The prefix for the customer used to generate unique invoice numbers. Must be 3–12 uppercase letters or numbers.",
optional: true,
},
invoiceSettingsCustomFields: {
type: "string[]",
label: "Invoice Settings - Custom Fields",
description: "The list of up to 4 default custom fields to be displayed on invoices for this customer. When updating, pass an empty string to remove previously-defined fields.",
optional: true,
},
invoiceSettingsDefaultPaymentMethod: {
type: "string",
label: "Invoice Settings - Default Payment Method",
description: "ID of a payment method that's attached to the customer, to be used as the customer's default payment method for subscriptions and invoices.",
optional: true,
},
invoiceSettingsRenderingOptionsAmountTaxDisplay: {
type: "string",
label: "Invoice Settings - Rendering Options - Amount Tax Display",
description: "How line-item prices and amounts will be displayed with respect to tax on invoice PDFs. One of exclude_tax or include_inclusive_tax. include_inclusive_tax will include inclusive tax (and exclude exclusive tax) in invoice PDF amounts. exclude_tax will exclude all tax (inclusive and exclusive alike) from invoice PDF amounts.",
options: [
"exclude_tax",
"include_inclusive_tax",
],
optional: true,
},
nextInvoiceSequence: {
type: "integer",
label: "Next Invoice Sequence",
description: "The sequence to be used on the customer's next invoice. Defaults to 1.",
optional: true,
default: 1,
},
preferredLocales: {
type: "string[]",
label: "Preferred Locales",
description: "Customer's preferred languages, ordered by preference.",
optional: true,
},
source: {
type: "string",
label: "Source",
description: "When using payment sources created via the Token or Sources APIs, passing source will create a new source object, make it the new customer default source, and delete the old customer default if one exists. If you want to add additional sources instead of replacing the existing default, use the card creation API. Whenever you attach a card to a customer, Stripe will automatically validate the card.",
optional: true,
},
taxExempt: {
type: "string",
label: "Tax Exempt",
description: "The customer's tax exemption. One of none, exempt, or reverse.",
options: [
"none",
"exempt",
"reverse",
],
optional: true,
},
taxIdData: {
type: "string[]",
label: "Tax ID Data",
description: "The customer's tax IDs. [See the documentation](https://docs.stripe.com/api/customers/create#create_customer-tax_id_data).",
optional: true,
},
testClock: {
type: "string",
label: "Test Clock",
description: "ID of the test clock to attach to the customer.",
optional: true,
},
},
methods: {
getOtherParams() {
const {
addressCity,
addressCountry,
addressLine1,
addressLine2,
addressPostalCode,
addressState,
shippingAddressCity,
shippingAddressCountry,
shippingAddressLine1,
shippingAddressLine2,
shippingAddressPostalCode,
shippingAddressState,
shippingName,
shippingPhone,
taxIpAddress,
taxValidateLocation,
cashBalanceSettingsReconciliationMode,
invoiceSettingsCustomFields,
invoiceSettingsDefaultPaymentMethod,
invoiceSettingsRenderingOptionsAmountTaxDisplay,
} = this;
const hasAddressData = addressCity
|| addressCountry
|| addressLine1
|| addressLine2
|| addressPostalCode
|| addressState;
const hasShippingData = shippingAddressCity
|| shippingAddressCountry
|| shippingAddressLine1
|| shippingAddressLine2
|| shippingAddressPostalCode
|| shippingAddressState
|| shippingName
|| shippingPhone;
const hasTaxData = taxIpAddress || taxValidateLocation;
const hasInvoiceSettings = invoiceSettingsCustomFields
|| invoiceSettingsDefaultPaymentMethod
|| invoiceSettingsRenderingOptionsAmountTaxDisplay;
return {
...(hasAddressData && {
address: {
city: addressCity,
country: addressCountry,
line1: addressLine1,
line2: addressLine2,
postal_code: addressPostalCode,
state: addressState,
},
}),
...(hasShippingData && {
shipping: {
address: {
city: shippingAddressCity,
country: shippingAddressCountry,
line1: shippingAddressLine1,
line2: shippingAddressLine2,
postal_code: shippingAddressPostalCode,
state: shippingAddressState,
},
name: shippingName,
phone: shippingPhone,
},
}),
...(hasTaxData && {
tax: {
ip_address: taxIpAddress,
validate_location: taxValidateLocation,
},
}),
...(cashBalanceSettingsReconciliationMode && {
cash_balance: {
settings: {
reconciliation_mode: cashBalanceSettingsReconciliationMode,
},
},
}),
...(hasInvoiceSettings && {
invoice_settings: {
custom_fields: invoiceSettingsCustomFields,
default_payment_method: invoiceSettingsDefaultPaymentMethod,
rendering_options: {
amount_tax_display: invoiceSettingsRenderingOptionsAmountTaxDisplay,
},
},
}),
};
},
},
async run({ $ }) {
const {
app,
name,
description,
email,
metadata,
paymentMethod,
phone,
balance,
invoicePrefix,
nextInvoiceSequence,
preferredLocales,
source,
taxExempt,
taxIdData,
testClock,
getOtherParams,
} = this;
const resp = await app.sdk().customers.create({
name,
description,
email,
metadata,
payment_method: paymentMethod,
phone,
balance,
invoice_prefix: invoicePrefix,
next_invoice_sequence: nextInvoiceSequence,
preferred_locales: preferredLocales,
source,
tax_exempt: taxExempt,
tax_id_data: utils.parseArray(taxIdData),
test_clock: testClock,
...getOtherParams(),
});
$.export("$summary", `Successfully created a new customer with ID \`${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.