Skip to main content
  • Recipes
  • Xata to Travelperk employees

Connect Xata and Travelperk employees in our serverless environment

Use this template to Read rows from Xata table using them to create employees using Travelperk API.

Use this recipeNeed help?
Share

Read rows from Xata table

Used integrations:
class HttpSourceXataQuery {
    async init() {
        // TODO: Create your http credential with xata information:
        // More info at https://yepcode.io/docs/integrations/http/#credential-configuration
        // baseUrl: Your Xata.io base url https://${your-workspace}.${your-zone}.xata.sh/db'
        // HTTP Headers: { "Authorization": "Bearer <your-xata-api-key>" }
        this.httpClient = yepcode.integration.http(
            "your-http-xata-credential-name"
        );
    }

    async fetch(publish, done) {
        // TODO: Set your table endpoint parameters
        // You may check API documentation for more details
        // https://xata.io/docs/overview
        const database = "<your-database>";
        const branch = "<your-branch>";
        const table = "<your-table>";
        const pagination = {
            page: {
                size: 15
            }
        };

        await this.httpClient
            .post(`/${database}:${branch}/tables/${table}/query`, pagination)
            .then(({
                data
            }) => {
                for (const row of data.records) {
                    publish(row);
                }
            })
            .catch((error) => {
                console.error(
                    `An error was thrown retrieving data`,
                    error.response.data
                );
                throw error;
            });

        done();
    }

    async close() {}
}

Do you need help solving this integration with YepCode?

Let's talk

Create employees using Travelperk API

Used integrations:
class HttpTargetTravelperkCreateEmployee {
    async init() {
        // TODO: Create your http credential with travelperk information:
        // More info at https://yepcode.io/docs/integrations/http/#credential-configuration
        // baseUrl: https://app.travelperk.com/api/v2/scim
        // HTTP Headers: { "Authorization": "apikey <YOUR API KEY>" }
        this.httpClient = yepcode.integration.http(
            "your-http-travelperk-scim-credential-name"
        );
    }

    async consume(item) {
        // TODO: Customize your request checking the API documentation:
        // https://developers.travelperk.com/reference/create-a-new-user
        await this.httpClient.post("/Users", {
            schemas: [
                "urn:ietf:params:scim:schemas:core:2.0:User",
                "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User",
                "urn:ietf:params:scim:schemas:extension:travelperk:2.0:User",
            ],
            // TODO: map your fields from item
            name: {
                givenName: item.first_name,
                familyName: item.last_name,
                middleName: "",
                honorificPrefix: "",
            },
            locale: "en",
            preferredLanguage: "en",
            title: "Manager",
            externalId: "123455667",
            groups: [],
            active: true,
            userName: "marlaen.col@mycompany.com",
            phoneNumbers: [{
                value: "+34 6412345",
                type: "work",
            }, ],
            "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
                costCenter: "Marketing",
            },
            "urn:ietf:params:scim:schemas:extension:travelperk:2.0:User": {
                gender: "M",
                dateOfBirth: "1980-02-02",
                travelPolicy: "Marketing travel policy",
                invoiceProfiles: [{
                    value: "My Company Ltd",
                }, ],
                company: "MyCompany USA, Ltd",
                emergencyContact: {
                    name: "Jane Goodie",
                    phone: "+34 9874637",
                },
                approvers: [{
                    value: "123",
                    condition: "out_of_policy",
                }, ],
                countryOfResidence: "ES",
                travelDocuments: [{
                    documentType: "passport",
                    documentNumber: "abcedf12345",
                    givenName: "Josh",
                    middleName: "",
                    familyName: "Smith",
                    gender: "M",
                    issuingCountry: "ES",
                    issuingDate: "1999-12-05",
                    expirationDate: "2042-09-08",
                    citizenship: "ES",
                }, ],
            },
        });
    }

    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.