Skip to main content

Connect Oracle NetSuite SuiteQL records and Webflow CMS entries in our serverless environment

Use this JavaScript template to Get records from Oracle NetSuite SuiteQL using them to create Webflow CMS entries


Get records from Oracle NetSuite SuiteQL

Used integrations:
class AxiosOauth10ASourceOracleNetsuiteSqlQuery {
async init() {
// TODO: Create your axios oauth10a credential with netsuite information:
// More info at

// To get your Netsuite credentials, see the help topic Getting Started with Token-based Authentication (
// More info at:
// You should get this parameters: consumer_key, consumer_secret_key, token, token_secret and realm

// Check this documentation to build the base url (
// It should be something like:
this.axiosClient = yepcode.integration.axiosOauth10a(

async fetch(publish, done) {
// TODO: Check SuiteQL docs to know how to write this SQL query
const suiteQLQuery = `
employee.entityid AS entityidRAW,
employee.firstname AS firstnameRAW,
employee.lastname AS lastnameRAW
employee.expenselimit >= 5000
// Max limit value is 1000
const limit = 1000;

let offset = 0;
let hasMore = true;
while (hasMore === true) {
const {
data: {
} = await
for (const item of sqlResult.items) {
await publish(item);
hasMore = sqlResult.hasMore;
offset = offset + limit;

async close() {}

buildSQLQueryBody(suiteQLQuery) {
const sanitizedQuery = suiteQLQuery
.replace(/\t/g, " ")
.replace(/\r?\n|\r/gm, "");
return `{"q": "${sanitizedQuery}" }`;

Create Webflow CMS entries

Used integrations:
class WebflowTargetCreateCmsEntry {
async init() {
// TODO: Create your webflow credential
// More info at
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:
// More info about the request at:
async consume(item) {
const cmsEntryFields = {
slug: item.slug,
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.slug) {
// obj[] = 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: {
_archived: false,
_draft: false,
}, {
live: "true"
} // TODO: Set to false if you don't want to publish the CMS entry
} catch (error) {
console.error(`There has been an error creating CMS entry`, error);
throw error;

async close() {}

Find related recipes

  • Oracle NetSuite
  • Webflow


These recipes are a good starting point for you to build your own YepCode processes and solve your integration and automation problems.

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 with a NodeJS engine.

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.

Ask us for help to solve your integration problem

Recipes may be used in a self service approach cloning them to one YepCode account, but if you are looking for a turnkey approach, our team may help you.