Runn icon

Runn

Interact with Runn.io API

Overview

This node integrates with a service to manage "People" resources, specifically allowing the creation of new person records. It is useful in scenarios where you want to automate adding personnel data into your system, such as onboarding new employees or contractors. For example, you can use this node to create a new person with their first name, last name, role, email, contract start and end dates, and employment type.

Properties

Name Meaning
First Name The first name of the person to be created (required).
Last Name The last name of the person to be created (required).
Role The role assigned to the person; can be specified by role ID or role name string (required).
Email The email address of the person.
Start Date The start date of the person's contract (first working day). Defaults to today if not set.
End Date The last date of the person's contract.
Employment Type The type of employment for the contract. Options: Empty, Employee, Contractor.
Dry Run If enabled, simulates the operation without making actual changes.

Output

The node outputs an array of JSON objects representing the created person(s). Each object contains the details of the newly created person as returned by the API. If the "Dry Run" option is enabled, no actual creation occurs, but the output simulates what would happen.

No binary data output is involved.

Dependencies

  • Requires connection to the external service's API managing people data.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The node depends on internal helper modules for executing operations related to people.

Troubleshooting

  • Common issues:

    • Missing required fields like First Name, Last Name, or Role will cause errors.
    • Invalid role identifiers may result in API errors.
    • Incorrect date formats for Start Date or End Date could lead to failures.
    • Network or authentication issues with the external API will prevent successful creation.
  • Error messages:

    • "Unsupported resource" error indicates the resource parameter is incorrect.
    • API error messages are passed through; check that credentials and permissions are correct.
    • If "Dry Run" is enabled, no changes occur, so verify this setting if no updates appear.

Links and References

  • Refer to the external service's official API documentation for People resource management.
  • Consult n8n documentation on how to configure API credentials and handle node errors.

Discussion