Skip to main content

Connect AWS Redshift and Webflow CMS entries in our serverless environment

Use this template to Read rows from AWS Redshift table using them to create Webflow CMS entries.

Share

Read rows from AWS Redshift table

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

// TODO: Customize the command to be executed
// More info at https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/clients/client-redshift-data/interfaces/executestatementcommandinput.html
const {
Id
} = await this.awsRedshift.send(
new ExecuteStatementCommand({
ClusterIdentifier: "your-cluster-identifier",
Database: "your-database-name",
DbUser: "your-database-user",
Sql: "SELECT * FROM your-table-name;",
})
);
this.statementId = Id;
await this._awaitStatementToFinish();
}

async fetch(publish, done) {
let nextToken;
// if result is returned paginated, iterate to publish entire statement result
do {
const result = await this.awsRedshift.send(
new GetStatementResultCommand({
Id: this.statementId,
NextToken: nextToken,
})
);
nextToken = result.NextToken;
for (const record of result.Records) {
// Each record come as a list of record cells
// More info at https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/clients/client-redshift-data/interfaces/getstatementresultcommandoutput.html

// TODO: Customize record columns mapping to the item that will be published
const item = {
id: record.id,
...record
};

await publish(item);
}
} while (nextToken);
done();
}

async close() {}

_awaitStatementToFinish() {
return new Promise((resolve, reject) => {
const describeStatementCommand = new DescribeStatementCommand({
Id: this.statementId,
});

// Configure interval to check statement status
const intervalId = setInterval(async () => {
const result = await this.awsRedshift.send(describeStatementCommand);
if (result.Status === "FINISHED") {
clearInterval(intervalId);
resolve();
return;
}

if (result.Status === "FAILED" || result.Status === "ABORTED") {
clearInterval(intervalId);
reject();
return;
}
}, 1000);
});
}
}

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 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.