Skip to main content

Connect CouchDB and Webflow CMS entries in our serverless environment

Use this template to Read documents from CouchDB collection using them to create Webflow CMS entries.

Share

Read documents from CouchDB collection

Used integrations:
class CouchdbSourceFind {
async init() {
// TODO: Create your couchdb credential
// More info at https://yepcode.io/docs/integrations/couchdb/#credential-configuration
this.couchdb = yepcode.integration.couchdb("your-couchdb-credential-name");
}

async fetch(publish, done) {
// TODO: Customize your query.
// See available options at: https://docs.couchdb.org/en/latest/api/database/find.html#db-find
const query = {
selector: {
name: "John Doe",
age: {
$gte: 18
},
},
};
// TODO: Customize your database name
const {
docs
} = await this.couchdb.use("your-db-name").find(query);

for (const doc of docs) {
await publish(doc);
}
done();
}

async close() {}
}

Do you need help solving this integration with YepCode?

Let's talk

Create Webflow CMS entries

Used integrations:
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() {}
}

Other combinations

View recipes

Related recipes

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.