import asana from "../../asana.app.mjs";
import constants from "../common/constants.mjs";
export default {
key: "asana-create-project",
name: "Create Project",
description: "Create a new project in a workspace or team. [See the documentation](https://developers.asana.com/docs/create-a-project)",
version: "0.10.0",
type: "action",
props: {
asana,
workspace: {
label: "Workspace",
description: "Gid of a workspace.",
type: "string",
propDefinition: [
asana,
"workspaces",
],
},
name: {
label: "Name",
description: "Name of the project. This is generally a short sentence fragment that fits on a line in the UI for maximum readability. However, it can be longer.",
type: "string",
},
notes: {
label: "Notes",
description: "Free-form textual information associated with the project (ie., its description).",
type: "string",
},
text: {
label: "Text",
description: "The text content of the status update.",
type: "string",
},
color: {
label: "Color",
description: "The color associated with the status update.",
type: "string",
options: constants.COLORS,
optional: true,
},
title: {
label: "Title",
description: "The title of the project status update.",
type: "string",
optional: true,
},
default_view: {
label: "Default View",
description: "The default view (list, board, calendar, or timeline) of a project.",
type: "string",
options: [
"list",
"board",
"calendar",
"timeline",
],
default: "calendar",
optional: true,
},
public: {
label: "Public",
description: "True if the project is public to its team.",
type: "boolean",
optional: true,
default: false,
},
archived: {
label: "Archived",
description: "Archived projects do not show in the UI by default and may be treated differently for queries.",
type: "boolean",
optional: true,
default: false,
},
due_on: {
label: "Due On",
description: "The day on which this project is due. This takes a date with format YYYY-MM-DD.",
type: "string",
optional: true,
},
start_on: {
label: "Start On",
description: "The day on which work for this project begins. This takes a date with format YYYY-MM-DD. `Due On` must be present in the request when setting or unsetting the `Start On` parameter. Additionally, `Start On` and `Due On` cannot be the same date.",
type: "string",
optional: true,
},
followers: {
label: "Followers",
description: "Comma separated string of users. Followers are a subset of members who have opted in to receive \"tasks added\" notifications for a project.",
type: "string[]",
optional: true,
propDefinition: [
asana,
"users",
({ workspace }) => ({
workspace,
}),
],
},
html_notes: {
label: "HTML Notes",
description: "The notes of the project with formatting as HTML.",
type: "string",
optional: true,
},
owner: {
label: "Owner",
description: "The current owner of the project.",
type: "string",
optional: true,
propDefinition: [
asana,
"users",
({ workspace }) => ({
workspace,
}),
],
},
},
async run({ $ }) {
const response = await this.asana._makeRequest({
path: "projects",
method: "post",
data: {
data: {
name: this.name,
notes: this.notes,
text: this.text,
color: this.color,
workspace: this.workspace,
default_view: this.default_view,
title: this.title,
public: this.public,
archived: this.archived,
due_on: this.due_on,
start_on: this.start_on,
followers: this.followers,
html_notes: this.html_notes,
owner: this.owner,
},
},
$,
});
$.export("$summary", "Successfully created project");
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.