actions/create-page-from-database/create-page-from-database.mjs
import pick from "lodash-es/pick.js"; import NOTION_ICONS from "../../common/notion-icons.mjs"; import utils from "../../common/utils.mjs"; import notion from "../../notion.app.mjs"; import base from "../common/base-page-builder.mjs"; export default { ...base, key: "notion-create-page-from-database", name: "Create Page from Data Source", description: "Create a page from a data source. [See the documentation](https://developers.notion.com/reference/post-page)", version: "2.0.0", annotations: { destructiveHint: false, openWorldHint: true, readOnlyHint: false, }, type: "action", props: { notion, parentDataSource: { propDefinition: [ notion, "dataSourceId", ], label: "Parent Data Source ID", description: "Select a parent data source or provide a data source ID", }, templateType: { type: "string", label: "Template Type", description: "The type of template to use for the page. [See the documentation](https://developers.notion.com/docs/creating-pages-from-templates) for more information.", options: [ { label: "No template. Provided children and properties are immediately applied.", value: "none", }, { label: "Applies the data source's default template to the newly created page. `children` cannot be specified in the create page request.", value: "default", }, { label: "Indicates which exact template to apply to the newly created page. children cannot be specified in the create page request.", value: "template_id", }, ], reloadProps: true, }, propertyTypes: { propDefinition: [ notion, "propertyTypes", (c) => ({ parentId: c.parentDataSource, parentType: "data_source", }), ], description: "Select one or more page properties. Willl override properties set in the `Properties` prop below.", reloadProps: true, }, properties: { type: "object", label: "Properties", description: "The values of the page's properties. The schema must match the parent data source's properties. [See the documentation](https://developers.notion.com/reference/property-object) for information on various property types. Example: `{ \"Tags\": [ \"tag1\" ], \"Link\": \"https://pipedream.com\" }`", optional: true, }, icon: { type: "string", label: "Icon Emoji", description: "Page Icon [Emoji](https://developers.notion.com/reference/emoji-object)", options: NOTION_ICONS, optional: true, }, cover: { type: "string", label: "Cover URL", description: "Cover [External URL](https://developers.notion.com/reference/file-object#external-file-objects)", optional: true, }, pageContent: { propDefinition: [ notion, "pageContent", ], }, }, async additionalProps() { switch (this.templateType) { case "none": const { properties } = await this.notion.retrieveDataSource(this.parentDataSource); const selectedProperties = pick(properties, this.propertyTypes); return { alert: { type: "alert", alertType: "info", content: "This action will create an empty page by default. To add content, use the `Page Content` prop below.", }, ...this.buildAdditionalProps({ properties: selectedProperties, }), }; case "default": return { alert: { type: "alert", alertType: "info", content: "This action will create a page using the data source's default template. Using the `Page Content` prop below will `not` apply to the page.", }, }; case "template_id": return { templateId: { type: "string", label: "Template ID", description: "The ID of the template to use for the page. [See the documentation](https://developers.notion.com/docs/creating-pages-from-templates) for more information.", options: async({ prevContext }) => { const params = { data_source_id: this.parentDataSource, }; if (prevContext?.nCursor) { params.start_cursor = prevContext.nCursor; } const { templates, next_cursor: nCursor, } = await this.notion.listTemplates(params); return { options: templates.map(({ name: label, id: value, }) => ({ label, value, })), context: { nCursor, }, }; }, }, alert: { type: "alert", alertType: "info", content: "This action will create a page using the selected template. Using the `Page Content` prop below will `not` apply to the page.", }, }; } }, methods: { ...base.methods, buildPage(parentDataSource) { const meta = this.buildDataSourceMeta(parentDataSource); this.properties = utils.parseObject(this.properties); const properties = this.buildPageProperties(parentDataSource.properties); const children = this.createBlocks(this.pageContent); return { ...meta, properties, children, }; }, }, async run({ $ }) { const MAX_BLOCKS = 100; const parentPage = await this.notion.retrieveDataSource(this.parentDataSource); const { children, ...page } = this.buildPage(parentPage); const data = this.templateId ? { template: { type: this.templateType, template_id: this.templateId, }, } : { children: children.slice(0, MAX_BLOCKS), }; const response = await this.notion.createPage({ ...data, ...page, parent: { data_source_id: this.parentDataSource, }, }); let remainingBlocks = children.slice(MAX_BLOCKS); while (remainingBlocks.length > 0) { await this.notion.appendBlock(response.id, remainingBlocks.slice(0, MAX_BLOCKS)); remainingBlocks = remainingBlocks.slice(MAX_BLOCKS); } $.export("$summary", "Created page successfully"); 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.