import { parseObject } from "../../common/utils.mjs";
import yespo from "../../yespo.app.mjs";
export default {
key: "yespo-add-update-contact",
name: "Add or Update Contact",
description: "Adds a new contact or updates an existing one. [See the documentation](https://docs.yespo.io/reference/addcontact-1)",
version: "0.0.1",
type: "action",
props: {
yespo,
firstName: {
type: "string",
label: "First Name",
description: "Contact's first name.",
optional: true,
},
lastName: {
type: "string",
label: "Last Name",
description: "Contact's last name.",
optional: true,
},
channels: {
type: "string[]",
label: "Channels",
description: "Channels for the contact. For example: `[ { \"device\": { \"appId\": \"83b77a49-fc28-409b-aeaa-68c9d544ab9d\", \"deviceModel\": \"iPhone\", \"os\": \"iOS\", \"locale\": \"en_UK\", \"clientVersion\": \"native\", \"appVersion\": \"1.23.45\", \"active\": true }, \"type\": \"email\", \"value\": \"pipedream@test.com\" } ]`. [See the documentation to further information](https://docs.yespo.io/reference/addcontact-1)",
},
addressRegion: {
type: "string",
label: "Region",
description: "The address region.",
optional: true,
},
addressTown: {
type: "string",
label: "Town",
description: "The address city.",
optional: true,
},
address: {
type: "string",
label: "Address",
description: "The address line.",
optional: true,
},
addressPostcode: {
type: "string",
label: "Postcode",
description: "Postal/ZIP code.",
optional: true,
},
additionalFields: {
type: "object",
label: "Additional Fields",
description: "Values of the additional fields for a contact. Keys are additional field ID.",
optional: true,
},
addressBookId: {
type: "string",
label: "Address Book Id",
description: "The address book unique identifier.",
optional: true,
},
contactId: {
propDefinition: [
yespo,
"contactId",
],
optional: true,
},
externalCustomerId: {
type: "string",
label: "External Customer Id",
description: "External contact id.",
optional: true,
},
contactKey: {
type: "string",
label: "Contact Key",
description: "Contact's key.",
optional: true,
},
languageCode: {
type: "string",
label: "Language Code",
description: "Language code for the contact.",
optional: true,
},
timeZone: {
type: "string",
label: "TimeZone",
description: "The contact's time zone. See [TZ database name](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).",
optional: true,
},
},
async run({ $ }) {
const fields = [];
if (this.additionalFields) {
for (const [
key,
value,
] of Object.entries(this.additionalFields)) {
fields.push({
[key]: value,
});
}
}
const data = {
firstName: this.firstName,
lastName: this.lastName,
channels: this.channels && parseObject(this.channels),
address: {
region: this.addressRegion,
town: this.addressTown,
address: this.address,
postcode: this.addressPostcode,
},
addressBookId: this.addressBookId,
contactId: this.contactId,
externalCustomerId: this.externalCustomerId,
contactKey: this.contactKey,
languageCode: this.languageCode,
timeZone: this.timeZone,
fields,
};
const response = await this.yespo.addOrUpdateContact({
$,
data,
});
$.export("$summary", `Successfully added or updated the contact with Id: ${response.id}`);
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.