import { customProps } from "../../common/constants.mjs";
import { parseObject } from "../../common/utils.mjs";
import outreach from "../../outreach.app.mjs";
export default {
key: "outreach-create-account",
name: "Create Account",
description: "Creates an account within Outreach. [See the documentation](https://developers.outreach.io/api/reference/tag/Account/#tag/Account/paths/~1accounts/post)",
version: "0.0.2",
annotations: {
destructiveHint: false,
openWorldHint: true,
readOnlyHint: false,
},
type: "action",
props: {
outreach,
buyerIntentScore: {
type: "string",
label: "Buyer Intent Score",
description: "A custom score given to measure the quality of the account.",
optional: true,
},
companyType: {
type: "string",
label: "Company Type",
description: "A description of the company's type (e.g. \"Public Company\").",
optional: true,
},
customId: {
type: "string",
label: "Custom Id",
description: "A custom ID for the account, often referencing an ID in an external system.",
optional: true,
},
description: {
type: "string",
label: "Description",
description: "A custom description of the account.",
optional: true,
},
domain: {
type: "string",
label: "Domain",
description: "The company's website domain (e.g. \"www.acme.com\").",
optional: true,
},
externalSource: {
type: "string",
label: "External Source",
description: "The source of the resource's creation (e.g. \"outreach-api\").",
optional: true,
},
followers: {
type: "integer",
label: "Followers",
description: "The number of followers the company has listed on social media.",
optional: true,
},
foundedAt: {
type: "string",
label: "Founded At",
description: "The founding date of the company. Format: 'YYYY-MM-DDTHH:MM:SS.UUUZ'",
optional: true,
},
industry: {
type: "string",
label: "Industry",
description: "A description of the company's industry (e.g. \"Manufacturing\").",
optional: true,
},
linkedInEmployees: {
type: "integer",
label: "Linked In Employees",
description: "The number of employees listed on the company's LinkedIn URL.",
optional: true,
},
linkedInUrl: {
type: "string",
label: "LinkedIn URL",
description: "The company's LinkedIn URL.",
optional: true,
},
locality: {
type: "string",
label: "Locality",
description: "The company's primary geographic region (e.g. \"Eastern USA\").",
optional: true,
},
name: {
type: "string",
label: "Name",
description: "The name of the company (e.g. \"Acme Corporation\").",
},
named: {
type: "boolean",
label: "Named",
description: "A boolean value determining whether this is a \"named\" account or not. Only named accounts will show up on the collection index.",
optional: true,
},
naturalName: {
type: "string",
label: "Natural Name",
description: "The natural name of the company (e.g. \"Acme\").",
optional: true,
},
numberOfEmployees: {
type: "integer",
label: "Number Of Employees",
description: "The number of employees working at the company.",
optional: true,
},
sharingTeamId: {
propDefinition: [
outreach,
"sharingTeamId",
],
optional: true,
},
tags: {
type: "string[]",
label: "Tags",
description: "A list of tag values associated with the account (e.g. [\"Enterprise\", \"Tier 1\"]).",
optional: true,
},
websiteUrl: {
type: "string",
label: "Website URL",
description: "The company's website URL (e.g. \"https://www.acme.com/contact\").",
optional: true,
},
...customProps,
},
async run({ $ }) {
const {
outreach,
buyerIntentScore,
tags,
...data
} = this;
const response = await outreach.createAccount({
$,
data: {
data: {
attributes: {
buyerIntentScore: buyerIntentScore && parseFloat(buyerIntentScore),
tags: tags && parseObject(tags),
...data,
},
type: "account",
},
},
});
$.export("$summary", `Successfully created account with Id: ${response.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.