import { clearObj } from "../../common/utils.mjs";
import mailwizz from "../../mailwizz.app.mjs";
export default {
key: "mailwizz-create-campaign",
name: "Create Campaign",
version: "0.0.1",
description: "Create a new campaign. [See the docs here](https://api-docs.mailwizz.com/?php#create-a-campaign)",
type: "action",
props: {
mailwizz,
name: {
type: "string",
label: "Name",
description: "Campaign name.",
},
type: {
type: "string",
label: "Type",
description: "Campaign type. Default is regular.",
options: [
"autoresponder",
"regular",
],
optional: true,
},
fromName: {
type: "string",
label: "From Name",
description: "The campaign from name.",
},
fromEmail: {
type: "string",
label: "From Email",
description: "The campaign from email address.",
},
subject: {
type: "string",
label: "Subject",
description: "The campaign subject.",
optional: true,
},
toName: {
type: "string",
label: "To Name",
description: "The subscriber for which we record the bounce.",
},
replyTo: {
type: "string",
label: "Reply To",
description: "RThe camapaign reply to email address.",
},
sendAt: {
type: "string",
label: "Send At",
description: "This will use the timezone which customer selected.",
},
listId: {
propDefinition: [
mailwizz,
"listId",
],
},
segmentId: {
propDefinition: [
mailwizz,
"segmentId",
( { listId } ) => ( {
listId,
} ),
],
optional: true,
},
templateId: {
propDefinition: [
mailwizz,
"templateId",
],
},
inlineCSS: {
type: "boolean",
label: "Inline CSS",
description: "Accept inline css",
optional: true,
},
plainText: {
type: "string",
label: "Plain Text",
description: "Do not send to autogenerate as default.",
optional: true,
},
autoPlainText: {
type: "boolean",
label: "Auto Plain Text",
description: "Generate plain text template.",
optional: true,
},
urlTracking: {
type: "boolean",
label: "URL Tracking",
description: "Enable/Disable url tracking.",
optional: true,
},
jsonFeed: {
type: "boolean",
label: "JSON Feed",
description: "Enable/Disable JSON feed.",
optional: true,
},
xmlFeed: {
type: "boolean",
label: "XML Feed",
description: "Enable/Disable XML feed.",
optional: true,
},
plainTextEmail: {
type: "boolean",
label: "Plain Text Email",
description: "Enable/Disable the plain text email.",
optional: true,
},
emailStats: {
type: "string",
label: "Email Stats",
description: "A valid email address where the stats will be sent.",
optional: true,
},
autoresponderEvent: {
type: "string",
label: "Autoresponder Event",
description: "The event that is sent after subscribe or after opening the campaign.",
options: [
"AFTER-SUBSCRIBE",
"AFTER-CAMPAIGN-OPEN",
],
optional: true,
},
autoresponderTimeUnit: {
type: "string",
label: "Autoresponder Time Unit",
description: "The unit that the autoresponder will be based on.",
options: [
"minute",
"hour",
"day",
"week",
"month",
"year",
],
optional: true,
},
autoresponderTimeValue: {
type: "integer",
label: "Autoresponder Time Value",
description: "The unit time value.",
optional: true,
},
autoresponderOpenCampaignId: {
propDefinition: [
mailwizz,
"campaignId",
],
label: "Autoresponder Open Campaign Id",
description: "Id of the camapign, only if event is AFTER-CAMPAIGN-OPEN.",
optional: true,
},
cronjob: {
type: "string",
label: "Cron Job",
description: "If this campaign is advanced recurring, you can set a cron job style frequency.",
optional: true,
},
cronjobEnabled: {
type: "boolean",
label: "Cron Job Enabled",
description: "Enable/Disable cron job frequency.",
optional: true,
},
},
async run ( { $ } ) {
const {
mailwizz,
fromName,
fromEmail,
toName,
replyTo,
sendAt,
listId,
segmentId,
templateId,
inlineCSS,
plainText,
autoPlainText,
urlTracking,
jsonFeed,
xmlFeed,
plainTextEmail,
emailStats,
autoresponderEvent,
autoresponderTimeUnit,
autoresponderTimeValue,
autoresponderOpenCampaignId,
cronjobEnabled,
...data
} = this;
const response = await mailwizz.createCampaign( clearObj( {
data: {
campaign: {
...data,
from_name: fromName,
from_email: fromEmail,
to_name: toName,
reply_to: replyTo,
send_at: sendAt,
list_uid: listId,
segment_uid: segmentId,
template: {
template_uid: templateId,
inline_css: inlineCSS,
plain_text: plainText,
auto_plain_text: autoPlainText,
},
options: {
url_tracking: urlTracking || "no",
json_feed: jsonFeed,
xml_feed: xmlFeed,
plain_text_email: plainTextEmail,
email_stats: emailStats,
autoresponder_event: autoresponderEvent,
autoresponder_time_unit: autoresponderTimeUnit,
autoresponder_time_value: autoresponderTimeValue,
autoresponder_open_campaign_id: autoresponderOpenCampaignId,
cronjob_enabled: cronjobEnabled,
},
},
},
} ) );
$.export( "$summary", `Campaign with id ${response.campaign_uid} was successfully created!` );
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.