Create Employee with Personio API on New Query Results from Snowflake API

Pipedream makes it easy to connect APIs for Personio, Snowflake and 2,400+ other apps remarkably fast.

Trigger workflow on

New Query Results from the Snowflake API

Next, do this

Create Employee with the Personio API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a Snowflake trigger and Personio action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Query Results trigger
1. Connect your Snowflake account
2. Configure timer
3. Configure SQL Query
4. Optional- Configure Primary key
5. Optional- Configure Emit individual events
Configure the Create Employee action
1. Connect your Personio account
2. Configure Email
3. Configure First Name
4. Configure Last Name
5. Optional- Configure Gender
6. Optional- Configure Position
7. Optional- Configure Subcompany
8. Optional- Configure Department
9. Optional- Configure Office
10. Optional- Configure Hire Date
11. Optional- Configure Weekly Working Hours
12. Optional- Select a Status
13. Optional- Select a Supervisor Id
14. Optional- Configure Custom Attributes
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger#

New Query Results on Snowflake

Description:Run a SQL query on a schedule, triggering a workflow for each row of results

Version:0.2.2

Key:snowflake-query-results

View on GitHub

Snowflake Overview#

Snowflake offers a cloud database and related tools to help developers create robust, secure, and scalable data warehouses. See Snowflake's Key Concepts & Architecture.

Getting Started

1. Create a user, role and warehouse in Snowflake

Snowflake recommends you create a new user, role, and warehouse when you integrate a third-party tool like Pipedream. This way, you can control permissions via the user / role, and separate Pipedream compute and costs with the warehouse. You can do this directly in the Snowflake UI.

We recommend you create a read-only account if you only need to query Snowflake. If you need to insert data into Snowflake, add permissions on the appropriate objects after you create your user.

2. Enter those details in Pipedream

Visit https://pipedream.com/accounts. Click the button to Connect an App. Enter the required Snowflake account data.

You'll only need to connect your account once in Pipedream. You can connect this account to multiple workflows to run queries against Snowflake, insert data, and more.

3. Build your first workflow

Visit https://pipedream.com/new to build your first workflow. Pipedream workflows let you connect Snowflake with 1,000+ other apps. You can trigger workflows on Snowflake queries, sending results to Slack, Google Sheets, or any app that exposes an API. Or you can accept data from another app, transform it with Python, Node.js, Go or Bash code, and insert it into Snowflake.

Learn more at Pipedream University.

Trigger Code#

import common from "../common.mjs";
import { v4 as uuidv4 } from "uuid";

export default {
  ...common,
  type: "source",
  key: "snowflake-query-results",
  name: "New Query Results",
  // eslint-disable-next-line
  description: "Run a SQL query on a schedule, triggering a workflow for each row of results",
  version: "0.2.2",
  props: {
    ...common.props,
    sqlQuery: {
      type: "string",
      label: "SQL Query",
      description: "Run this query on a schedule, triggering the workflow for each row of results",
    },
    // Ordering props correctly
    timer: common.props.timer,
    dedupeKey: {
      type: "string",
      label: "Primary key",
      description: "The column in your query to use for de-duplication. Duplicate rows won't trigger your workflow",
      optional: true,
    },
    emitIndividualEvents: {
      propDefinition: [
        common.props.snowflake,
        "emitIndividualEvents",
      ],
    },
  },
  methods: {
    ...common.methods,
    generateMeta(data) {
      const {
        row: { [this.dedupeKey]: id = uuidv4() },
        timestamp: ts,
      } = data;
      const summary = `New event (ID: ${id})`;
      return {
        id,
        summary,
        ts,
      };
    },
    generateMetaForCollection(data) {
      const { timestamp: ts } = data;
      const id = uuidv4();
      const summary = `New event (ID: ${id})`;
      return {
        id,
        summary,
        ts,
      };
    },
    getStatement() {
      return {
        sqlText: this.sqlQuery,
      };
    },
  },
};

Trigger Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
Snowflake	`snowflake`	`app`	This component uses the Snowflake app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`	Watch for changes on this schedule
SQL Query	`sqlQuery`	`string`	Run this query on a schedule, triggering the workflow for each row of results
Primary key	`dedupeKey`	`string`	The column in your query to use for de-duplication. Duplicate rows won't trigger your workflow
Emit individual events	`emitIndividualEvents`	`boolean`	Defaults to `true`, triggering workflows on each record in the result set. Set to `false` to emit records in batch (advanced)

Trigger Authentication#

Snowflake uses API keys for authentication. When you connect your Snowflake account, Pipedream securely stores the keys so you can easily authenticate to Snowflake APIs in both code and no-code steps.

We recommend you create a read-only account if you only need to query Snowflake. If you need to insert data into Snowflake, add permissions on the appropriate objects after you create your user.

About Snowflake#

A data warehouse built for the cloud

Action#

Create Employee on Personio

Description:Creates a new employee. [See the documentation](https://developer.personio.de/reference/post_company-employees)

Version:0.0.1

Key:personio-create-employee

View on GitHub

Personio Overview#

The Personio API provides programmatic access to HR management functions, allowing you to manage employee data, time tracking, payroll, and recruitment processes. With Pipedream, you can leverage this API to create automations and workflows that can streamline HR operations, react to events in Personio in real-time, and connect HR data to other systems seamlessly.

Action Code#

import personio from "../../personio.app.mjs";

export default {
  key: "personio-create-employee",
  name: "Create Employee",
  version: "0.0.1",
  description: "Creates a new employee. [See the documentation](https://developer.personio.de/reference/post_company-employees)",
  type: "action",
  props: {
    personio,
    email: {
      propDefinition: [
        personio,
        "email",
      ],
    },
    firstName: {
      propDefinition: [
        personio,
        "firstName",
      ],
    },
    lastName: {
      propDefinition: [
        personio,
        "lastName",
      ],
    },
    gender: {
      type: "string",
      label: "Gender",
      description: "The gender of the employee.",
      optional: true,
    },
    position: {
      type: "string",
      label: "Position",
      description: "The position of the employee. E.g. **developer**.",
      optional: true,
    },
    subcompany: {
      type: "string",
      label: "Subcompany",
      description: "The subcompany employee belongs to. Should be predefined in Personio. Otherwise will be ignored with showing meta error in the response.",
      optional: true,
    },
    department: {
      type: "string",
      label: "Department",
      description: "The department employee belongs to. Should be predefined in Personio. Otherwise will be ignored with showing meta error in the response.",
      optional: true,
    },
    office: {
      type: "string",
      label: "Office",
      description: "The office employee belongs to. Should be predefined in Personio. Otherwise will be ignored with showing meta error in the response.",
      optional: true,
    },
    hireDate: {
      type: "string",
      label: "Hire Date",
      description: "Employee hire date. Format: \"yyyy-mm-dd\". If `status` is not provided, it will be set to `active` if the hire date is in the past, or to `onboarding` if it's in the future.",
      optional: true,
    },
    weeklyWorkingHours: {
      type: "integer",
      label: "Weekly Working Hours",
      description: "All hours usually worked, including regular overtime.",
      optional: true,
    },
    status: {
      type: "string",
      label: "Status",
      description: "Status of the employee. Overrides the status determined based on the value of `hire_date`.",
      options: [
        "onboarding",
        "active",
        "leave",
        "inactive",
      ],
      optional: true,
    },
    supervisorId: {
      propDefinition: [
        personio,
        "supervisorId",
      ],
      optional: true,
    },
    customAttributes: {
      type: "object",
      label: "Custom Attributes",
      description: "Additional attributes to the employee.",
      optional: true,
    },
  },
  async run({ $ }) {
    const {
      personio,
      firstName,
      lastName,
      hireDate,
      weeklyWorkingHours,
      supervisorId,
      customAttributes,
      ...data
    } = this;

    const response = await personio.createEmployee({
      $,
      data: {
        employee: {
          first_name: firstName,
          last_name: lastName,
          hire_date: hireDate,
          weekly_working_hours: weeklyWorkingHours,
          supervisor_id: supervisorId,
          custom_attributes: customAttributes,
          ...data,
        },
      },
    });

    $.export("$summary", `A new employee with Id: ${response.data?.id} was successfully created!`);
    return response;
  },
};

Action Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

Label	Prop	Type	Description
Personio	`personio`	`app`	This component uses the Personio app.
Email	`email`	`string`	The e-mail field is required for the employee creation. Updating of this field is not currently supported.
First Name	`firstName`	`string`	The first name of the employee.
Last Name	`lastName`	`string`	The last name of the employee.
Gender	`gender`	`string`	The gender of the employee.
Position	`position`	`string`	The position of the employee. E.g. developer.
Subcompany	`subcompany`	`string`	The subcompany employee belongs to. Should be predefined in Personio. Otherwise will be ignored with showing meta error in the response.
Department	`department`	`string`	The department employee belongs to. Should be predefined in Personio. Otherwise will be ignored with showing meta error in the response.
Office	`office`	`string`	The office employee belongs to. Should be predefined in Personio. Otherwise will be ignored with showing meta error in the response.
Hire Date	`hireDate`	`string`	Employee hire date. Format: "yyyy-mm-dd". If `status` is not provided, it will be set to `active` if the hire date is in the past, or to `onboarding` if it's in the future.
Weekly Working Hours	`weeklyWorkingHours`	`integer`	All hours usually worked, including regular overtime.
Status	`status`	`string`	Select a value from the drop down menu:`onboardingactiveleaveinactive`
Supervisor Id	`supervisorId`	`string`	Select a value from the drop down menu.
Custom Attributes	`customAttributes`	`object`	Additional attributes to the employee.

Action Authentication#

Personio uses OAuth authentication. When you connect your Personio account, Pipedream will open a popup window where you can sign into Personio and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Personio API.

Pipedream requests the following authorization scopes when you connect your account: