Runn icon

Runn

Interact with Runn.io API

Actions21

Overview

This node interacts with a service managing people, clients, and projects. Specifically for the People - Update operation, it updates details of an existing person in the system by specifying their ID or email along with new attribute values. This is useful in scenarios where you need to keep your contact or personnel records up-to-date automatically, such as syncing employee information from HR systems or updating customer profiles.

Practical examples:

  • Automatically update a person's name or email after receiving updated data from a CRM.
  • Archive or unarchive a person based on changes in their status.
  • Perform dry runs to simulate updates without affecting live data.

Properties

Name Meaning
ID or Email The unique identifier or email of the person to update. At least one must be provided.
First Name The person's first name. Required when updating a person.
Last Name The person's last name. Required when updating a person.
Email The person's email address.
Is Archived? Boolean flag indicating whether the person should be marked as archived (true) or active (false).
Dry Run If enabled, simulates the update operation without making actual changes in the system.
Options Additional optional parameters (empty in this context).

Output

The node outputs an array containing JSON objects representing the updated person(s). Each object includes the updated fields reflecting the changes made. If the "Dry Run" option is enabled, the output simulates what would happen without applying changes.

If an error occurs and "Continue On Fail" is enabled, the output will contain an error message inside the JSON field.

No binary data output is involved.

Dependencies

  • Requires connection to the external Runn API service.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The node depends on internal helper modules for handling operations related to people, clients, and projects.

Troubleshooting

  • Common issues:

    • Providing neither ID nor Email will cause the operation to fail because the target person cannot be identified.
    • Missing required fields like First Name or Last Name when updating may result in validation errors.
    • Network or authentication failures can prevent successful API calls.

  • Error messages:

    • "Unsupported resource": Occurs if an invalid resource is specified; ensure "people" is selected.
    • API errors returned from the external service will be propagated unless "Continue On Fail" is enabled.

  • Resolutions:

    • Verify that either ID or Email is provided.
    • Check that all required fields are filled.
    • Confirm API credentials and network connectivity.
    • Use "Dry Run" mode to test changes safely before applying them.

Links and References

Discussion