Skip to main content

Google BigQuery to Personio employees

Read rows from Google BigQuery table using them to create employees using Personio API


Read rows from Google BigQuery table

Used integrations:
class GoogleBigquerySourceSelect {    async init() {        // TODO: Create your google-bigquery credential        // More info at        this.googleBigQuery = yepcode.integration.googleBigQuery(            "your-google-bigquery-credential-name"        );    }    async fetch(publish, done) {        // TODO: Customize your query        const query = `SELECT *      FROM \`your_db.your_schema.your_table_name\`      LIMIT 10`;        // for all options, see        const options = {            query: query,            // Location must match that of the dataset(s) referenced in the query.            location: "US",        };        // run the query as a job        const [job] = await this.googleBigQuery.createQueryJob(options);        console.log(`Job ${} started.`);        // wait for the query to finish        const [rows] = await job.getQueryResults();        for (const row of rows) {            await publish(row);        }        done();    }    async close() {}}

Create employees using Personio API

Used integrations:
class AxiosTargetPersonioCreateEmployee {    async init() {        // initialize an axios client with personio url and credentials file, performing the initial auth:        this.axiosClient = axios.create({            baseURL: "",        });        const {            data: {                bearerToken            },        } = await"/auth", {            // TODO: Customize your client id and secret            client_id: "you_client_id",            client_secret: "you_client_secret",        });        this.bearerToken = bearerToken;    }    async consume(item) {        // TODO: Customize your request checking the API documentation:        //        const response = await            `/company/employees`, {                // TODO: map your fields from item                employee: {                    email:,                    first_name: item.first_name,                    last_name: item.last_name,                    gender: "male",                    position: "developer",                    subcompany: "ACME",                    department: "IT",                    office: "Madrid",                    hire_date: "2020-01-31",                    weekly_working_hours: 40,                    custom_attributes: {                        "dynamic_ {{  field uid  }} ": "German",                    },                },            }, {                headers: {                    Authorization: `Bearer ${this.bearerToken}`,                },            }        );        // A new token is recieved in each request (        this.bearerToken = response.headers.authorization;    }    async close() {}}

Find related recipes

  • Google BigQuery
  • Personio


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.