actions/create-email/create-email.mjs
import { LANGUAGE_OPTIONS, OBJECT_TYPE, } from "../../common/constants.mjs"; import { parseObject } from "../../common/utils.mjs"; import hubspot from "../../hubspot.app.mjs"; import common from "../common/common-get-object.mjs"; export default { key: "hubspot-create-email", name: "Create Marketing Email", description: "Create a marketing email in Hubspot. [See the documentation](https://developers.hubspot.com/docs/reference/api/marketing/emails/marketing-emails#post-%2Fmarketing%2Fv3%2Femails%2F)", version: "0.0.8", annotations: { destructiveHint: false, openWorldHint: true, readOnlyHint: false, }, type: "action", props: { hubspot, name: { type: "string", label: "Name", description: "The name of the email", }, campaign: { propDefinition: [ hubspot, "campaignId", ], optional: true, }, customReplyTo: { type: "string", label: "Custom Reply To", description: "The custom reply to address for the email", optional: true, }, fromName: { type: "string", label: "From Name", description: "The name of the sender", optional: true, }, replyTo: { type: "string", label: "Reply To", description: "The reply to address for the email", optional: true, }, limitSendFrequency: { type: "boolean", label: "Limit Send Frequency", description: "Whether to limit the send frequency for the email", optional: true, }, suppressGraymail: { type: "boolean", label: "Suppress Graymail", description: "Whether to suppress graymail for the email", optional: true, }, includeContactLists: { propDefinition: [ hubspot, "lists", ], optional: true, }, excludeContactLists: { propDefinition: [ hubspot, "lists", ], optional: true, }, feedbackSurveyId: { ...common.props.objectId, label: "Feedback Survey ID", description: "Hubspot's internal ID for the feedback survey", optional: true, }, rssData: { type: "object", label: "RSS Data", description: "An object with the RSS data for the email. [See the documentation](https://developers.hubspot.com/docs/reference/api/marketing/emails/marketing-emails#post-%2Fmarketing%2Fv3%2Femails%2F) for more information.", optional: true, }, subject: { type: "string", label: "Subject", description: "The subject of the email", optional: true, }, testing: { type: "object", label: "Testing", description: "An object with the testing data for the email. [See the documentation](https://developers.hubspot.com/docs/reference/api/marketing/emails/marketing-emails#post-%2Fmarketing%2Fv3%2Femails%2F) for more information.", optional: true, }, language: { type: "string", label: "Language", description: "The language of the email", options: LANGUAGE_OPTIONS, optional: true, }, content: { type: "object", label: "Content", description: "An object with the content data for the email. [See the documentation](https://developers.hubspot.com/docs/reference/api/marketing/emails/marketing-emails#post-%2Fmarketing%2Fv3%2Femails%2F) for more information.", optional: true, }, webversion: { type: "object", label: "Webversion", description: "An object with the webversion data for the email. [See the documentation](https://developers.hubspot.com/docs/reference/api/marketing/emails/marketing-emails#post-%2Fmarketing%2Fv3%2Femails%2F) for more information.", optional: true, }, subscriptionDetails: { type: "object", label: "Subscription Details", description: "An object with the subscription details for the email. [See the documentation](https://developers.hubspot.com/docs/reference/api/marketing/emails/marketing-emails#post-%2Fmarketing%2Fv3%2Femails%2F) for more information.", optional: true, }, sendOnPublish: { type: "boolean", label: "Send On Publish", description: "Whether to send the email on publish", optional: true, }, }, methods: { ...common.methods, getObjectType() { return OBJECT_TYPE.FEEDBACK_SUBMISSION; }, }, async run({ $ }) { const response = await this.hubspot.createEmail({ $, data: { name: this.name, campaign: this.campaign, from: { customReplyTo: this.customReplyTo, fromName: this.fromName, replyTo: this.replyTo, }, to: { limitSendFrequency: this.limitSendFrequency, suppressGraymail: this.suppressGraymail, contactLists: { include: parseObject(this.includeContactLists), exclude: parseObject(this.excludeContactLists), }, }, feedbackSurveyId: this.feedbackSurveyId, rssData: parseObject(this.rssData), subject: this.subject, testing: parseObject(this.testing), language: this.language, content: parseObject(this.content), webversion: parseObject(this.webversion), subscriptionDetails: parseObject(this.subscriptionDetails), sendOnPublish: this.sendOnPublish, }, }); $.export("$summary", `Successfully created email 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.