import { ConfigurationError } from "@pipedream/platform";
import vryno from "../../vryno.app.mjs";
export default {
key: "vryno-create-unique-lead",
name: "Create Unique Lead",
description: "Creates a unique lead in the Vryno system, ensuring no duplication of lead details. [See the documentation](https://vrynotest.ti2.in/docs/api-documentation/how-to-create-a-record-in-any-module-in-vryno-crm/)",
version: "0.0.2",
annotations: {
destructiveHint: false,
openWorldHint: true,
readOnlyHint: false,
},
type: "action",
props: {
vryno,
firstName: {
type: "string",
label: "First Name",
description: "The lead's first name.",
optional: true,
},
name: {
type: "string",
label: "Last Name",
description: "The lead's last name.",
},
email: {
type: "string",
label: "Email",
description: "The lead's email.",
optional: true,
},
phoneNumber: {
type: "string",
label: "Phone Number",
description: "The lead's phone number.",
optional: true,
},
company: {
type: "string",
label: "Company",
description: "The company the lead works for.",
optional: true,
},
website: {
type: "string",
label: "Website",
description: "The lead's website.",
optional: true,
},
ownerId: {
type: "string",
label: "Owner Id",
description: "The user Id related to the lead.You can find the user IDs in your account -> settings -> users & controls -> users, click on some user and the ID will be in URL.",
},
score: {
type: "integer",
label: "Score",
description: "The lead's score.",
optional: true,
},
expectedRevenue: {
type: "integer",
label: "Expected Revenue",
description: "Expected revenue for the lead.",
optional: true,
},
numberOfEmployees: {
type: "integer",
label: "Number Of Employees",
description: "Number of employees at the lead company.",
optional: true,
},
billingAddress: {
type: "string",
label: "Billing Address",
description: "The lead's billing address.",
optional: true,
},
billingCity: {
type: "string",
label: "Billing City",
description: "The lead's billing city.",
optional: true,
},
billingState: {
type: "string",
label: "Billing State",
description: "The lead's billing state.",
optional: true,
},
billingCountry: {
type: "string",
label: "Billing Country",
description: "The lead's billing country.",
optional: true,
},
billingZipcode: {
type: "string",
label: "Billing Zipcode",
description: "The lead's billing zipcode",
optional: true,
},
shippingAddress: {
type: "string",
label: "Shipping Address",
description: "The lead's shipping address.",
optional: true,
},
shippingCity: {
type: "string",
label: "Shipping City",
description: "The lead's shipping city.",
optional: true,
},
shippingState: {
type: "string",
label: "Shipping State",
description: "The lead's shipping state.",
optional: true,
},
shippingCountry: {
type: "string",
label: "Shipping Country",
description: "The lead's shipping country.",
optional: true,
},
shippingZipcode: {
type: "string",
label: "Shipping Zipcode",
description: "The lead's shipping zipcode",
optional: true,
},
description: {
type: "string",
label: "Description",
description: "A brief description about the lead.",
optional: true,
},
},
async run({ $ }) {
if (!this.email && !this.phoneNumber) {
throw new ConfigurationError("You must provide at least either **Email** or **Phone Number**.");
}
const duplicateCheck = await this.vryno.post({
data: {
query: `query {
fetchLead(filters:[${this.email
? `{name: "email", operator:"eq",value:["${this.email}"]},`
: ""}${this.phoneNumber
? `{name: "phoneNumber", operator:"eq",value:["${this.phoneNumber}"]}`
: ""}],
expression:"( ( a ) and b)"){
code
status
message
messageKey
count
data {
id
}
}
}`,
},
});
if (duplicateCheck.data?.fetchLead?.data?.length) {
$.export("$summary", "A lead with the same email and phone number already exists.");
return duplicateCheck.data;
}
const {
vryno,
...data
} = this;
let query = `mutation {
createLead(input: {
`;
for (const [
field,
value,
] of Object.entries(data)) {
query += `${field}:`;
if ([
"score",
"expectedRevenue",
"numberOfEmployees",
].includes(field)) {
query += ` ${value}
`;
} else {
query += ` "${value}"
`;
}
}
query += `}) {
code
message
status
messageKey
data {
id
}
errors
}
}`;
const response = await vryno.post({
$,
data: {
query,
},
});
if (response.data.createLead.code != 200) {
throw new ConfigurationError(response.data.createLead.message);
}
$.export("$summary", `Successfully created new lead with Id: ${response.data.createLead.data.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.