Skip to main content
  • Recipes
  • Elasticsearch to Oracle NetSuite journal entries

Connect Elasticsearch and Oracle NetSuite journal entries in our serverless environment

Use this template to Read rows from Elasticsearch table using them to create journal entries using Oracle NetSuite API.

Use this recipeNeed help?
Share

Read rows from Elasticsearch table

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

    async fetch(publish, done) {
        // TODO: customize your query
        const sql = "SELECT * FROM your_table_name";

        const result = await this.elasticsearch.sql.query({
            query: sql,
        });

        result.rows.map((row) => {
            const item = {};
            for (let i = 0; i < row.length; i++) {
                item[result.columns[i].name] = row[i];
            }
            publish(item);
        });
        done();
    }

    async close() {}
}

Do you need help solving this integration with YepCode?

Let's talk

Create journal entries using Oracle NetSuite API

Used integrations:
class AxiosOauth10ATargetOracleNetsuiteCreateJournalEntries {
    async init() {
        // TODO: Create your axios oauth10a credential with netsuite information:
        // More info at https://yepcode.io/docs/integrations/axios-oauth-10-a#credential-configuration

        // To get your Netsuite credentials, see the help topic Getting Started with Token-based Authentication (https://system.netsuite.com/app/help/helpcenter.nl?fid=section_4247337262.html)
        // More info at: https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_161942084079.html
        // You should get this parameters: consumer_key, consumer_secret_key, token, token_secret and realm

        // Check this documentation to build the base url (https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_1546938065.html)
        // It should be something like: https://demo123.suitetalk.api.netsuite.com/services/rest/record/v1/
        this.axiosClient = yepcode.integration.axiosOauth10a(
            "your-axios-oauth-10-a-oracle-netsuite-credential-name"
        );
    }

    async consume(item) {
        // TODO: Customize your request checking the API documentation:
        // https://system.netsuite.com/help/helpcenter/en_US/APIs/REST_API_Browser/record/v1/2021.2/index.html#tag-journalEntry
        // https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_159886587653.html
        await this.axiosClient.post(`/journalEntry`, {
            // TODO: Map item attributes to journal entry fields
            // https://system.netsuite.com/help/helpcenter/en_US/APIs/REST_API_Browser/record/v1/2021.2/index.html#/definitions/journalEntry
            accountingBook: item.accountingBook,
            accountingBookDetail: item.accountingBookDetail,
            approvalStatus: {
                id: item.id,
                refName: item.refName,
            },
            // complete your fields
        });
    }

    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.

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.