import click2mail2 from "../../click2mail2.app.mjs";
import {
COLOR,
ENVELOPE,
LAYOUT,
MAILCLASS,
PAPERTYPE,
PRINTOPTION,
} from "../../common/constants.mjs";
export default {
key: "click2mail2-create-job",
name: "Create Job",
version: "0.0.1",
description: "Creates a new new job in your account. [See the documentation](https://developers.click2mail.com/reference/post_2).",
type: "action",
props: {
click2mail2,
documentClass: {
propDefinition: [
click2mail2,
"documentClass",
],
},
layout: {
type: "string",
label: "Layout",
description: "The specific type of the product",
options: LAYOUT,
},
envelope: {
type: "string",
label: "Envelope",
description: "If this is an enveloped product this determines the envelope in which the product is to be mailed; otherwise provide no value.",
options: ENVELOPE,
},
color: {
type: "string",
label: "Color",
description: "Print in color or black and white.",
options: COLOR,
},
paperType: {
type: "string",
label: "Paper Type",
description: "Sets the paper the mailing is to be printed on.",
options: PAPERTYPE,
},
printOption: {
type: "string",
label: "Print Option",
description: "Sets simplex or duplex printing.",
options: PRINTOPTION,
},
documentId: {
propDefinition: [
click2mail2,
"documentId",
],
optional: true,
},
addressId: {
propDefinition: [
click2mail2,
"addressId",
],
optional: true,
},
rtnName: {
type: "string",
label: "RTN Name",
description: "Return address Name.",
optional: true,
},
rtnOrganization: {
type: "string",
label: "RTN Organization",
description: "Return address Organization.",
optional: true,
},
rtnaddress1: {
type: "string",
label: "RTN Address1",
description: "Return address line 1.",
optional: true,
},
rtnaddress2: {
type: "string",
label: "RTN Address2",
description: "Return address line 2.",
optional: true,
},
rtnCity: {
type: "string",
label: "RTN City",
description: "Return address City.",
optional: true,
},
rtnState: {
type: "string",
label: "RTN State",
description: "Return address State.",
optional: true,
},
rtnZip: {
type: "string",
label: "RTN Zip",
description: "Return address Zip.",
optional: true,
},
mailClass: {
type: "string",
label: "Mail Class",
description: "Overrides the default of First Class for mailed products.",
options: MAILCLASS,
optional: true,
},
appSignature: {
type: "string",
label: "APP Signature",
description: "This is a short signature to identify orders that come from your app.",
optional: true,
},
projectId: {
propDefinition: [
click2mail2,
"projectId",
],
optional: true,
},
mailingDate: {
type: "string",
label: "Mailing Date",
description: "Used to schedule the mailing date in the future. Format YYYYMMDD. If not provided the order will be mailed on the next available on the next business day. The business day cut off is 8PM EST.",
optional: true,
},
quantity: {
type: "string",
label: "Quantity",
description: "For products that do not use mailing lists. Quantity to print.",
optional: true,
},
jobDocumentId: {
propDefinition: [
click2mail2,
"jobDocumentId",
({ documentId }) => ({
documentId,
}),
],
optional: true,
},
jobAddressId: {
type: "string",
label: "Job Address Id",
description: "Address List Id of the job version.",
optional: true,
},
businessReplyAddressId: {
type: "integer",
label: "Business Reply Address Id",
description: "If you are mailing a business reply mail product use this to specify the busines reply address and permit information already in your account.",
optional: true,
},
courtesyReplyAddressId: {
type: "integer",
label: "Courtesy Reply Address Id",
description: "If you are mailing a courtesy reply mail product use this to specify a courtesy reply address already in your account.",
optional: true,
},
returnAddressId: {
type: "integer",
label: "Return Address Id",
description: "You may use the return address id to specify a return address already in your account.",
optional: true,
},
},
async run({ $ }) {
const {
click2mail2,
...params
} = this;
const response = await click2mail2.create({
$,
path: "jobs",
params: {
productionTime: "Next Day",
...params,
},
});
$.export("$summary", `A new job with Id: ${response.id} 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.