import asana from "../../asana.app.mjs";
import common from "../common/common.mjs";
export default {
key: "asana-create-subtask",
name: "Create Subtask",
description: "Creates a new subtask and adds it to the parent task. [See the documentation](https://developers.asana.com/docs/create-a-subtask)",
version: "0.4.0",
type: "action",
props: {
...common.props,
task_gid: {
label: "Task GID",
description: "The task GID to operate on.",
type: "string",
propDefinition: [
asana,
"tasks",
(c) => ({
project: c.project,
}),
],
},
name: {
label: "Name",
description: "Name of the subtask. 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",
},
assignee: {
label: "Assignee",
description: "Gid of a user.",
type: "string",
optional: true,
propDefinition: [
asana,
"users",
({ workspace }) => ({
workspace,
}),
],
},
assignee_section: {
label: "Assignee Section",
description: "The assignee section is a subdivision of a project that groups tasks together in the assignee's \"My Tasks\" list.",
type: "string",
optional: true,
propDefinition: [
asana,
"sections",
(c) => ({
project: c.project,
}),
],
},
completed: {
label: "Completed",
description: "True if the task is currently marked complete, false if not.",
type: "boolean",
optional: true,
},
due_at: {
label: "Due At",
description: "The UTC date and time on which this task is due, or null if the task has no due time. This takes an ISO 8601 date string in UTC and should not be used together with due_on.",
type: "string",
optional: true,
},
due_on: {
label: "Due On",
description: "The localized date on which this task is due, or null if the task has no due date. This takes a date with YYYY-MM-DD format and should not be used together with due_at.",
type: "string",
optional: true,
},
followers: {
label: "Followers",
description: "An array of strings identifying users. These can either be the string \"me\", an email, or the gid of a user.",
type: "string[]",
optional: true,
propDefinition: [
asana,
"users",
({ workspace }) => ({
workspace,
}),
],
},
html_notes: {
label: "HTML Notes",
description: "The notes of the text with formatting as HTML.",
type: "string",
optional: true,
},
notes: {
label: "Notes",
description: "Free-form textual information associated with the task (i.e. its description).",
type: "string",
optional: true,
},
start_on: {
label: "Start On",
description: "The day on which work begins for the task , or null if the task has no start date. This takes a date with YYYY-MM-DD format.",
type: "string",
optional: true,
},
tags: {
propDefinition: [
asana,
"tags",
],
optional: true,
},
},
async run({ $ }) {
const response = await this.asana._makeRequest({
path: `tasks/${this.task_gid}/subtasks`,
method: "post",
data: {
data: {
name: this.name,
assignee: this.assignee,
assignee_section: this.assignee_section,
completed: this.completed,
due_at: this.due_at,
due_on: this.due_on,
followers: this.followers,
html_notes: this.html_notes,
notes: this.notes,
projects: this.project,
start_on: this.start_on,
tags: this.tags,
workspace: this.workspace,
},
},
$,
});
$.export("$summary", "Successfully created subtask");
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.