actions/create-or-update-subscriber/create-or-update-subscriber.mjs
import drip from "../../drip.app.mjs"; export default { key: "drip-create-or-update-subscriber", name: "Create Or Update Subscriber", version: "0.0.3", annotations: { destructiveHint: true, openWorldHint: true, readOnlyHint: false, }, description: "Creates a new subscriber. If the email already exists, it will update the existing subscriber. [See the docs here](https://developer.drip.com/?javascript#create-or-update-a-subscriber)", type: "action", props: { drip, email: { propDefinition: [ drip, "email", ], }, visitorUuid: { type: "string", label: "Visitor UUID", description: "The `uuid` for a subscriber's visitor record. Either `email` or `visitor_uuid` must be included.", optional: true, }, newEmail: { type: "string", label: "New Email", description: "A new email address for the subscriber. If provided and a subscriber with the `email` above does not exist, this address will be used to create a new subscriber.", optional: true, }, firstName: { type: "string", label: "First Name", description: "The subscriber's first name.", optional: true, }, lastName: { type: "string", label: "Last Name", description: "The subscriber's last name.", optional: true, }, address1: { type: "string", label: "Address 1", description: "The subscriber's mailing address.", optional: true, }, address2: { type: "string", label: "Address 2", description: "An additional field for the subscriber's mailing address.", optional: true, }, city: { type: "string", label: "City", description: "The city, town, or village in which the subscriber resides.", optional: true, }, state: { type: "string", label: "State", description: "The region in which the subscriber resides. Typically a province, a state, or a prefecture.", optional: true, }, zip: { type: "string", label: "ZIP", description: "The postal code in which the subscriber resides, also known as zip, postcode, Eircode, etc.", optional: true, }, country: { type: "string", label: "Country", description: "The country in which the subscriber resides.", optional: true, }, phone: { type: "string", label: "Phone", description: "The subscriber's primary phone number.", optional: true, }, smsNumber: { type: "string", label: "SMS Number", description: "The subscriber's mobile phone number in E.164 formatting. E.g. \"+16125551212\". Only US-based numbers are supported at this time.", optional: true, }, smsConsent: { type: "boolean", label: "SMS Consent", description: "`true` if the person has granted consent to receive marketing and other communication via SMS; `false` otherwise. Default: false. If you're unsure whether or not you have gained legal SMS consent, check out our [*TCPA requirements article*](https://my.drip.com/docs/manual/sms/compliance-manage-sms-compliance).", optional: true, }, userId: { type: "string", label: "User Id", description: "A unique identifier for the user in your database, such as a primary key.", optional: true, }, timezone: { type: "string", label: "Timezone", description: "The subscriber's time zone (in Olson format). Defaults to `Etc/UTC`", optional: true, }, lifetimeValue: { type: "string", label: "Lifetime Value", description: "The lifetime value of the subscriber (in cents).", optional: true, }, ipAddress: { type: "string", label: "IP Address", description: "The subscriber's ip address E.g. \"111.111.111.11\"", optional: true, }, customFields: { type: "object", label: "Custom Fields", description: "An Object containing custom field data. E.g. { \"shirt_size\": \"Medium\" }", optional: true, }, tags: { type: "string[]", label: "Tags", description: "An Array containing one or more tags. E.g. [\"Customer\", \"SEO\"].", optional: true, }, removeTags: { type: "string[]", label: "Remove Tags", description: "An Array containing one or more tags to be removed from the subscriber. E.g. [\"Customer\", \"SEO\"].", optional: true, }, prospect: { type: "boolean", label: "Prospect", description: "A Boolean specifiying whether we should attach a lead score to the subscriber (when lead scoring is enabled). Defaults to `true`. *Note:* This flag used to be called `potential_lead`, which we will continue to accept for backwards compatibility.", optional: true, }, baseLeadScore: { type: "integer", label: "Base Lead Score", description: "An Integer specifying the starting value for lead score calculation for this subscriber. Defaults to `30`.", optional: true, }, euConsent: { type: "string", label: "EU Consent", description: "A String specifying whether the subscriber `granted` or `denied` *GDPR* consent.", optional: true, options: [ "granted", "denied", ], }, euConsentMessage: { type: "string", label: "EU Consent Message", description: "A String containing the message the subscriber granted or denied their consent to.", optional: true, }, status: { type: "string", label: "Status", description: "A String specifying the subscriber's status: either `active` or `unsubscribed`.", optional: true, options: [ "active", "unsubscribed", ], }, initialStatus: { type: "string", label: "Initial Status", description: "A String specifying the subscriber's known status: either `active` or `unsubscribed`. To be used if subscriber's status is unchanged.", optional: true, options: [ "active", "unsubscribed", ], }, }, async run({ $ }) { const { email, visitorUuid, newEmail, firstName, lastName, address1, address2, city, state, zip, country, phone, smsNumber, smsConsent, userId, timezone, lifetimeValue, ipAddress, customFields, tags, removeTags, prospect, baseLeadScore, euConsent, euConsentMessage, status, initialStatus, } = this; const response = await this.drip.createOrUpdateSubscriber({ $, data: { subscribers: [ { email: email && email.label ? email.label : email, id: email?.value, visitor_uuid: visitorUuid, new_email: newEmail, first_name: firstName, last_name: lastName, address1, address2, city, state, zip, country, phone, sms_number: smsNumber, sms_consent: smsConsent, user_id: userId, time_zone: timezone, lifetime_value: lifetimeValue, ip_address: ipAddress, custom_fields: customFields, tags, remove_tags: removeTags, prospect, base_lead_score: baseLeadScore, eu_consent: euConsent, eu_consent_message: euConsentMessage, status, initial_status: initialStatus, }, ], }, }); $.export("$summary", "Subscriber Successfully created/updated"); 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.