Actions29
Requirement → Search
AI-generatedSummary
Searches eRS Cloud requirements by sending a user-supplied JSON filter body to the eRS API and returns the matching requirements.
Inputs
- authentication — Credential type: OAuth2 (recommended, default) or Access Token.
- searchBodyJson (required) — Search body as valid JSON, following the filter syntax in the eRS Cloud API docs (https://apidocs.eresourcescheduler.cloud). Defaults to an empty object.
- requestOptions — Optional request settings: Batching (items per batch, default 50, -1 disables; batch interval, default 1000 ms), Ignore SSL Issues, Proxy URL (optionally with credentials), and Timeout (default 10000 ms).
Output shape
Requirement records returned by the eRS search endpoint for the supplied filter, emitted as workflow items.
The source pack contains only signature-level or empty modules for the search implementation, so the exact response shape, pagination and result limits are not confirmed. See the eRS API docs for the record fields.
Examples
Example 1: Find requirements matching specific criteria and feed them into later nodes.
Authentication: OAuth2; Search Body (JSON): a filter object written per the eRS API docs; leave Request Options at defaults.
Example 2: Search from behind a corporate proxy with a slow API.
Set Request Options: Proxy to http://myproxy:3128 and Timeout to 30000; provide the filter JSON in Search Body.