import { COUNTRY_OPTIONS } from "../../common/constants.mjs";
import { clearObj } from "../../common/utils.mjs";
import digitalriver from "../../digitalriver.app.mjs";
export default {
key: "digitalriver-update-customer-information",
name: "Update Customer Information",
description: "Updates the information for a customer in Digital River. [See the documentation](https://www.digitalriver.com/docs/digital-river-api-reference/#tag/Customers/operation/updateCustomers)",
version: "0.0.1",
type: "action",
props: {
digitalriver,
customerId: {
propDefinition: [
digitalriver,
"customerId",
],
},
email: {
type: "string",
label: "Email",
description: "The customer email address.",
optional: true,
},
line1: {
type: "string",
label: "Shipping Address Line 1",
description: "The first line of the address.",
optional: true,
},
line2: {
type: "string",
label: "Shipping Address Line 2",
description: "The second line of the address.",
optional: true,
},
city: {
type: "string",
label: "Shipping Address City",
description: "The city of the address.",
optional: true,
},
postalCode: {
type: "string",
label: "Shipping Address Postal Code",
description: "The postal code of the address.",
optional: true,
},
state: {
type: "string",
label: "Shipping Address State",
description: "The state, county, province, or region.",
optional: true,
},
country: {
type: "string",
label: "Shipping Address Country",
description: "A [two-letter Alpha-2 country code](https://www.iban.com/country-codes) as described in the [ISO 3166](https://www.iso.org/iso-3166-country-codes.html) international standard.",
options: COUNTRY_OPTIONS,
optional: true,
},
name: {
type: "string",
label: "Shipping Name",
description: "The recipient's name.",
optional: true,
},
phone: {
type: "string",
label: "Shipping Phone",
description: "The recipient's phone number.",
optional: true,
},
shippingEmail: {
type: "string",
label: "Shipping Email",
description: "The recipient's email address.",
optional: true,
},
organization: {
type: "string",
label: "Shipping Organization",
description: "The recipient's organization.",
optional: true,
},
neighborhood: {
type: "string",
label: "Shipping Neighborhood",
description: "The neighborhood of the address.",
optional: true,
},
division: {
type: "string",
label: "Shipping Division",
description: "A division within an organization.",
optional: true,
},
phoneticName: {
type: "string",
label: "Shipping Phonetic Name",
description: "The phonetic spelling of a name.",
optional: true,
},
companyName: {
type: "string",
label: "Tax Certificate Company Name",
description: "The name of the company that holds the certificate.",
optional: true,
},
taxAuthority: {
type: "string",
label: "Tax Certificate Autority",
description: "The issuing state.",
optional: true,
},
startDate: {
type: "string",
label: "Tax Certificate Start Date",
description: "Tax certificate start date.",
optional: true,
},
endDate: {
type: "string",
label: "Tax Certificate End Date",
description: "Tax certificate end date.",
optional: true,
},
fileId: {
propDefinition: [
digitalriver,
"fileId",
],
label: "Tax Certificate File Id",
description: "The identifier of the file that contains the tax certificate.",
optional: true,
},
requestToBeForgotten: {
type: "boolean",
label: "Request To Be Forgotten",
description: "If `true`, indicates this customer has submitted a request to be forgotten.",
optional: true,
},
type: {
type: "string",
label: "Type",
description: "The type of customer.",
options: [
"business",
"individual",
],
optional: true,
},
metadata: {
propDefinition: [
digitalriver,
"metadata",
],
optional: true,
},
locale: {
type: "string",
label: "Locale",
description: "A locale designator that combines the two-letter ISO 639-1 language code with the ISO 3166-1 alpha-2 country code.",
optional: true,
},
enabled: {
type: "boolean",
label: "Enabled",
description: "Usually used to disable the customer. The default is true. If false, attempts to create orders for the customer will fail.",
optional: true,
},
},
async run({ $ }) {
const {
digitalriver,
customerId,
line1,
line2,
city,
postalCode,
state,
country,
name,
phone,
shippingEmail,
organization,
neighborhood,
division,
phoneticName,
companyName,
taxAuthority,
startDate,
endDate,
fileId,
...data
} = this;
const response = await digitalriver.updateCustomer({
$,
customerId,
data: clearObj({
...data,
shipping: {
address: {
line1,
line2,
city,
postalCode,
state,
country,
},
name,
phone,
email: shippingEmail,
organization,
additionalAddressInfo: {
neighborhood,
division,
phoneticName,
},
},
taxCertificate: {
companyName,
taxAuthority,
startDate,
endDate,
fileId,
},
}),
});
$.export("$summary", `Updated customer information for contact ID ${this.customerId}`);
return response;
},
};
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.