Runn icon

Runn

Interact with Runn.io API

Overview

This node integrates with a service to manage "People" resources, specifically allowing retrieval of a single person's details by their ID or email. The "Get One" operation fetches detailed information about one individual from the external system.

Common scenarios include:

  • Retrieving user profile data for display or further processing.
  • Fetching contact details based on a known identifier.
  • Integrating with CRM or HR systems to pull up-to-date person records.

Example use case: Given an email address, the node fetches the corresponding person's full record to enrich customer data in a workflow.

Properties

Name Meaning
ID or Email The unique identifier or email address of the person to retrieve. This is required.
Options Additional optional parameters to customize the request (currently no specific options).

Output

The node outputs an array containing one item representing the fetched person. Each item's json property holds the person's data as returned by the external API. The structure typically includes fields such as name, email, ID, and other profile details depending on the external service's response.

No binary data output is indicated.

Dependencies

  • Requires connection to the external service's API via an authenticated client instance.
  • Needs an API key or authentication token configured in n8n credentials to authorize requests.
  • Relies on internal helper functions (executePeopleOperation) to perform the actual API call.

Troubleshooting

  • Error: Unsupported resource — Occurs if the resource parameter is set incorrectly; ensure "People" is selected.
  • Error: Missing ID or Email — The operation requires at least one identifier; verify that the input property is provided.
  • API errors — Network issues or invalid credentials can cause failures; check API key validity and network connectivity.
  • If the node is set to continue on fail, errors will be returned inside the output JSON under an error field.

Links and References

  • Refer to the external service's API documentation for the "People" resource to understand available fields and identifiers.
  • n8n documentation on creating custom nodes and handling API credentials.

Discussion