Create Employee with Personio API on New Transaction Created from Ramp API

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

Trigger workflow on

New Transaction Created from the Ramp 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 Ramp 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 Transaction Created trigger
1. Connect your Ramp account
2. Configure timer
3. Optional- Select a Department ID
4. Optional- Select a Location ID
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 Transaction Created on Ramp

Description:Emit new event for each new transaction created in Ramp.

Version:0.0.2

Key:ramp-new-transaction-created

View on GitHub

Ramp Overview#

The Ramp API provides programmatic access to financial and accounting functionalities, allowing for the management of company cards, transactions, and reporting. By leveraging the Ramp API within Pipedream, you can automate intricate finance operations, synchronize transaction data with accounting software, trigger notifications based on spending activities, and analyze financial data in real-time, integrating with other services for enhanced financial workflows.

Trigger Code#

import common from "../common/base.mjs";
import sampleEmit from "./test-event.mjs";

export default {
  ...common,
  key: "ramp-new-transaction-created",
  name: "New Transaction Created",
  description: "Emit new event for each new transaction created in Ramp.",
  version: "0.0.2",
  type: "source",
  dedupe: "unique",
  props: {
    ...common.props,
    departmentId: {
      propDefinition: [
        common.props.ramp,
        "departmentId",
      ],
    },
    locationId: {
      propDefinition: [
        common.props.ramp,
        "locationId",
      ],
    },
  },
  methods: {
    ...common.methods,
    _getLatestTransactionId() {
      return this.db.get("latestTransactionId");
    },
    _setLatestTransactionId(id) {
      this.db.set("latestTransactionId", id);
    },
    getResourceFn() {
      return this.ramp.listTransactions;
    },
    getParams() {
      const latestTransactionId = this._getLatestTransactionId();
      const params = {
        order_by_date_asc: true,
        department_id: this.departmentId,
        location_id: this.locationId,
      };
      if (latestTransactionId) {
        params.start = latestTransactionId;
      }
      return params;
    },
    generateMeta(transaction) {
      return {
        id: transaction.id,
        summary: `New Transaction ID: ${transaction.id}`,
        ts: Date.parse(transaction.user_transaction_time),
      };
    },
    emitResults(results, max) {
      if (max && results.length > max) {
        results = results.slice(-1 * max);
      }
      this._setLatestTransactionId(results[results.length - 1].id);
      results.reverse().forEach((transaction) => {
        const meta = this.generateMeta(transaction);
        this.$emit(transaction, meta);
      });
    },
  },
  sampleEmit,
};

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
Ramp	`ramp`	`app`	This component uses the Ramp app.
	`timer`	`$.interface.timer`
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Department ID	`departmentId`	`string`	Select a value from the drop down menu.
Location ID	`locationId`	`string`	Select a value from the drop down menu.

Trigger Authentication#

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

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

transactions:readcards:readcards:writespend_programs:readspend_programs:writeusers:readusers:writelocations:readlocations:writelimits:readlimits:writedepartments:readdepartments:writebusiness:readreceipts:readtransfers:readvendors:readmerchants:readaccounting:readreceipts:write

About Ramp#

The Corporate Card That Helps You Spend Less

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: