- Recipes
- Dremio to Webflow CMS entries
Connect Dremio and Webflow CMS entries in our serverless environment
Use this template to Read data from Dremio using them to create Webflow CMS entries.
Share
Read data from Dremio
Used integrations:
- JavaScript
- Python
class HttpSourceDremioSelect {
async init() {
// TODO: Create your http credential with dremio information:
// More info at https://yepcode.io/docs/integrations/http/#credential-configuration
// Official docs: https://docs.dremio.com/cloud/reference/api/
this.httpClient = yepcode.integration.http("your-dremio-credential-name");
}
async fetch(publish, done) {
// TODO: Customize your select query
// Double-quotation marks within a SQL statement need to be escaped
const query = 'SELECT * FROM path_to_your_dataset."your_dataset_name"';
// Use the SQL API to submit queries. The response contains the ID for the job associated with the SQL query
// Official docs: https://docs.dremio.com/cloud/reference/api/sql
const projectId = "<your-dremio-project-id>";
const {
data: job
} = this.httpClient.post(`${projectId}/sql`, {
sql: query,
});
// Use the Job API to check the job status. Jobs final status are COMPLETED, FAILED and CANCELED
// Official docs: https://docs.dremio.com/cloud/reference/api/job/
const finalJobStates = ["COMPLETED", "FAILED", "CANCELED"];
let jobInfoResponse = null;
do {
jobInfoResponse = await this.httpClient.get(
`${this.projectId}/job/${job.id}`
);
} while (!finalJobStates.includes(jobInfoResponse.data.jobState));
const {
data: jobInfo
} = jobInfoResponse;
// When the job is finished, if it's been completed, get the result from Job Results endpoint
// Official docs: https://docs.dremio.com/cloud/reference/api/job/job-results/
// Otherwise, show the job status
if (jobInfo.jobState === "COMPLETED") {
const {
data: result
} = await this.httpClient.get(
`${this.projectId}/job/${job.id}/results`
);
publish(result.rows);
} else if (jobInfo.jobState === "FAILED") {
publish(`Uups! Something was wrong: ${jobInfo.errorMessage}`);
} else {
publish(`The job's been cancelled: ${jobInfo.cancellationReason}`);
}
done();
}
async close() {}
}
class HttpSourceDremioSelect:
def setup(self):
## TODO: Create your http credential with dremio information
## More info at https://yepcode.io/docs/integrations/http/#credential-configuration
## Official docs: https://docs.dremio.com/cloud/reference/api/
self.session = yepcode.integration.http(
"your-dremio-credential-name"
)
def generator(self):
## TODO: Customize your select query
## Double-quotation marks withing a SQL statement need to be escaped
query = 'SELECT * FROM path_to_your_dataset."your_dataset_name"'
## Use the SQL API to submit queries. The response contains the ID for the job ssociated with the SQL query
## Official docs: https://docs.dremio.com/cloud/reference/api/sql
project_id = "<your-dremio-project-id>"
query_response = self.session.post(
f"{project_id}/sql",
json={"sql" : query}
)
job_id = query_response.json()['id']
## Use the Job API to check the job status. Jobs final status are COMPLETED, FAILED and CANCELED
## Official docs: https://docs.dremio.com/cloud/reference/api/job/
job_state = 'INIT'
job_info_response = None
FINAL_JOB_STATES = ['COMPLETED', 'FAILED', 'CANCELED']
while job_state not in FINAL_JOB_STATES:
job_info_response = self.session.get(f"{project_id}/job/{job_id}")
job_state = job_info_response.json()['jobState']
## When the job is finished, if it's been completed, get the result from Job Results endpoint
## Official docs: https://docs.dremio.com/cloud/reference/api/job/job-results/
## Otherwise, show the job status
if job_state == 'COMPLETED':
job_result_response = self.session.get(f"{project_id}/job/{job_id}/results")
rows = job_result_response.json()['rows']
for row in rows:
yield row
elif job_state == 'FAILED':
yield f"Uups! Something was wrong: {job_info_response.json()['errorMessage']}"
else:
yield f"The job's been cancelled: {job_info_response.json()['cancellationReason']}"
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 enables the creation, execution and monitoring of 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 an excellent starting point for creating your own YepCode processes and solving complex integration and automation problems.
You only have to complete 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 focus, offering a multi-tenant environment, team management capabilities, high security and auditing standards, Identity Provider (IdP) integrations, and on-premise options. It serves as the Swiss army knife for engineering teams, especially those requiring the extraction or transmission of information to external systems. It excels in scenarios demanding flexibility and adaptability to change within the process.
Sure! You only need to configure YepCode servers to establish a connection with that service. Check our docs page to get more information.