eRS Actions icon

eRS Actions

Interact with the Ers App API

Actions29

Resource → Update

AI-generated

Summary

Updates an existing resource in eRS by its Resource ID, optionally changing its name and setting user-defined field (UDF) values for the selected resource type.

Inputs

  • authentication — Credential type to use: OAuth2 (recommended, default) or Access Token.
  • resource_type_id (required) — The resource type, chosen from a list loaded from eRS or given as an ID via expression. It determines which UDFs are available.
  • resource_id (required) — Unique ID of the resource to update.
  • first_name — New name for the resource (labelled 'Resource Name').
  • udfFields — Repeatable list of user-defined fields to set. Each entry picks a field (loaded for the chosen resource type) and shows a value input matching the field type: boolean, date/date-time, number, text/email/URL/color, rich text (HTML), single-select, or multi-select.
  • requestOptions — Node-level HTTP options: batching (items per batch, default 50, and interval, default 1000 ms), ignore SSL issues, proxy URL, and timeout (default 10000 ms).

Output shape

Not shown in the provided source. The pack contains only compiled stubs for the update module, so the response shape is unconfirmed. It is presumably the API response for the updated resource, one result per input item.

The runtime implementation of this operation isn't visible in the source, so the exact request and response format can't be confirmed. Batching options suggest one request per input item.

Examples

Example 1: Rename a resource after an HR system change

Select the resource type, set Resource ID to an expression such as {{$json.id}}, and set Resource Name to the new name.

Example 2: Update custom fields on a resource

Select the resource type, enter the Resource ID, then add UDF entries. Choose each field and fill in the value input that matches its type, such as a date or select option.

Links

Discussion