actions/create-scheduled-query/create-scheduled-query.mjs
import { protos } from "@google-cloud/bigquery-data-transfer"; import googleCloud from "../../google_cloud.app.mjs"; import constants from "../../common/constants.mjs"; import regions from "../../common/regions.mjs"; const { CreateTransferConfigRequest, TransferConfig, } = protos.google.cloud.bigquery.datatransfer.v1; export default { key: "google_cloud-create-scheduled-query", name: "Create Scheduled Query", description: "Creates a scheduled query in Google Cloud. [See the documentation](https://cloud.google.com/bigquery/docs/scheduling-queries)", version: "0.0.3", annotations: { destructiveHint: false, openWorldHint: true, readOnlyHint: false, }, type: "action", props: { googleCloud, destinationDatasetId: { label: "Destination Dataset", description: "The name of the dataset to create the table in. If the dataset does not exist, it will be created.", propDefinition: [ googleCloud, "datasetId", ], }, datasetRegion: { type: "string", label: "Dataset Region", description: "The geographic location where the dataset should reside. [See the documentation here](https://cloud.google.com/bigquery/docs/locations#specifying_your_location)", default: "us", options: regions, optional: true, }, displayName: { type: "string", label: "Display Name", description: "The user-friendly display name for the transfer config.", }, query: { type: "string", label: "Query", description: "The GoogleSQL query to execute. Eg. ``SELECT @run_time AS time, * FROM `my_dataset.my_table` LIMIT 1000``. [See the documentation here](https://cloud.google.com/bigquery/docs/scheduling-queries#query_string).", }, schedule: { type: "string", label: "Schedule", description: "Data transfer schedule. If the data source does not support a custom schedule, this should be empty. If it is empty, the default value for the data source will be used. The specified times are in UTC. Examples of valid format: `every 24 hours`, `1st,3rd monday of month 15:30`, `every wed,fri of jan,jun 13:15`, and `first sunday of quarter 00:00`. [See more explanation about the format here](https://cloud.google.com/appengine/docs/flexible/python/scheduling-jobs-with-cron-yaml#the_schedule_format).", optional: true, }, writeDisposition: { type: "string", label: "Write Disposition", description: "The write preference you select determines how your query results are written to an existing destination table. [See the documentation here](https://cloud.google.com/bigquery/docs/scheduling-queries#write_preference).", default: constants.WRITE_DISPOSITION.WRITE_TRUNCATE, options: Object.values(constants.WRITE_DISPOSITION), optional: true, }, destinationTableNameTemplate: { type: "string", label: "Destination Table Name Template", description: "The destination table name template can contain template variables such as ``{run_date}`` or ``{run_time}``. [See the documentation here](https://cloud.google.com/bigquery/docs/scheduling-queries#templating-examples).", optional: true, default: "logs", }, }, methods: { getTransferConfig({ query, writeDisposition, destinationTableNameTemplate, ...args } = {}) { return new TransferConfig({ dataSourceId: constants.DATA_SOURCE_ID.SCHEDULED_QUERY, params: { fields: { query: { stringValue: query, }, destination_table_name_template: { stringValue: destinationTableNameTemplate, }, write_disposition: { stringValue: writeDisposition, }, }, }, ...args, }); }, createTransferConfig(args = {}) { const { googleCloud, getTransferConfig, } = this; const { project_id: projectId, client_email: serviceAccountName, } = googleCloud.authKeyJson(); const client = googleCloud.bigQueryDataTransferClient(); const parent = client.projectPath(projectId); const request = new CreateTransferConfigRequest({ parent, serviceAccountName, transferConfig: getTransferConfig(args), }); return client.createTransferConfig(request); }, }, async run({ $ }) { const { createTransferConfig, ...props } = this; const [ response, ] = await createTransferConfig(props); $.export("$summary", `Scheduled query created with name: \`${response.name}\``); 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.