- Recipes
- Google BigQuery to Webflow CMS entries
Connect Google BigQuery and Webflow CMS entries in our serverless environment
Use this template to Read rows from Google BigQuery table using them to create Webflow CMS entries.
Share
Read rows from Google BigQuery table
Used integrations:
JavaScript
Python
class GoogleBigquerySourceSelect {
async init() {
// TODO: Create your google-bigquery credential
// More info at https://yepcode.io/docs/integrations/google-bigquery/#credential-configuration
this.googleBigQuery = yepcode.integration.googleBigQuery(
"your-google-bigquery-credential-name"
);
}
async fetch(publish, done) {
// TODO: Customize your query
const query = `SELECT *
FROM \`your_db.your_schema.your_table_name\`
LIMIT 10`;
// for all options, see https://cloud.google.com/bigquery/docs/reference/rest/v2/jobs/query
const options = {
query: query,
// Location must match that of the dataset(s) referenced in the query.
location: "US",
};
// run the query as a job
const [job] = await this.googleBigQuery.createQueryJob(options);
console.log(`Job ${job.id} started.`);
// wait for the query to finish
const [rows] = await job.getQueryResults();
for (const row of rows) {
await publish(row);
}
done();
}
async close() {}
}
class GoogleBigquerySourceSelect:
def setup(self):
# TODO: Create your BigQuery credential:
# More info at https://yepcode.io/docs/integrations/google-bigquery/#credential-configuration
self.big_query_client = yepcode.integration.googleBigQuery(
"your-bigquery-credential-name"
)
def generator(self):
# TODO: Customize dataset and table ids and query content
dataset_id = "dataset_id"
table_id = "table_id"
query = (
f"SELECT * FROM `{self.big_query_client.project}.{dataset_id}.{table_id}`"
)
query_job = self.big_query_client.query(query)
rows = query_job.result()
for row in rows:
yield row
def close(self):
pass
Do you need help solving this integration with YepCode?
Let's talkCreate Webflow CMS entries
Used integrations:
JavaScript
Python
class WebflowTargetCreateCmsEntry {
async init() {
// TODO: Create your webflow credential
// More info at https://yepcode.io/docs/integrations/webflow/#credential-configuration
this.webflow = yepcode.integration.webflow("your-webflow-credential-name");
}
// TODO: Customize your collection id and the request params with your item content
// See how to find your collection id: https://www.briantsdawson.com/blog/webflow-api-how-to-get-site-collection-and-item-ids-for-zapier-and-parabola-use
// More info about the request at: https://developers.webflow.com/#create-collection-item
async consume(item) {
const cmsEntryFields = {
slug: item.slug,
name: item.name,
content: item.content,
};
// TODO: Take into account that Webflow keeps one internal identifier for each attribute
// and this internal identifier doesn't get changed when you rename the attribute name.
// This may cause some weird and unexpected Validation errors
// If you want to implement a mapping from the attribute name (visible on the webflow UI),
// and the internal identifier (slug), you may use this piece of code:
// const collection = await this.webflow.collection({
// collectionId: "your-collection-id",
// });
// const collectionSlugsByNameMapping = collection.fields.reduce(
// (obj, field, i) => {
// // Only save the mappings where name is not the same as slug
// if (field.name !== field.slug) {
// obj[field.name] = field.slug;
// }
// return obj;
// },
// {}
// );
// // Translate different slug and names
// for (const [name, slug] of Object.entries(collectionSlugsByNameMapping)) {
// cmsEntryFields[slug] = cmsEntryFields[name];
// delete cmsEntryFields[name];
// }
try {
await this.webflow.createItem({
collectionId: "your-collection-id",
fields: {
...cmsEntryFields,
_archived: false,
_draft: false,
},
});
} catch (error) {
console.error(`There has been an error creating CMS entry`, error);
console.error(error.response.data);
throw error;
}
}
async close() {}
}
Comming soon
We are releasing new Python recipes every week
FAQs
YepCode is a SaaS platform that allows to create, execute and monitor integrations and automations using source code in a serverless environment.
We like to call it the Zapier for developers, since we bring all the agility and benefits of NoCode tools (avoid server provisioning, environment configuration, deployments,...), but with all the power of being able to use a programming language like JavaScript or Python.
These recipes are a good starting point for you to build your own YepCode processes and solve your integration and automation problems.
You only have to fill the sign up form and your account will be created with our FREE plan (no credit card required).
YepCode has been created with a clear enterprise approach (multi-tenant environment, team management, high security and auditing standards, IdP integrations, on-premise options,...) so we can be the Swiss army knife of any team of engineering, especially those that need to extract or send information to external systems, and where a certain dynamism or adaptation to change is necessary in that process.
Sure! You just need to do some configuration to allow YepCode servers to connect to that service. Check our docs page to get more information.