eRS Trigger icon

eRS Trigger

Triggers the workflow when ERS sends a webhook event

eRS Trigger

AI-generated

Summary

Starts a workflow when eRS (eResourceScheduler) sends a webhook event for selected entities (Resource, Project, Booking, Timesheet, Requirement) and event types (Create, Update, Delete). On activation it registers a webhook in eRS and configures its triggers; on deactivation it deletes it.

Inputs

  • authentication — Credential type used for eRS API calls: OAuth2 (default, recommended) or Access Token.
  • entities (required) — Entities to monitor: Resource (1), Project (2), Booking (4), Timesheet (16), Requirement (32).
  • events (required) — Events to trigger on: Create (1), Update (2), Delete (3). Applied to every selected entity.
  • webhook (legacy) — Hidden legacy entities/events settings. Used as a fallback only if the entities or events fields are empty; not shown in the UI.

Output shape

One workflow item per object in the POSTed eRS payload (an array body yields multiple items). The item JSON is the webhook body, with source: "ersApp" added if the payload has no source field.

Challenge requests are answered directly and don't start the workflow. A GET with ?challenge=… returns {challenge}, and a POST whose body contains a challenge field echoes the body back. Other GETs return 'OK'. The webhook path is ersapp, method POST, and it responds immediately (onReceived). Activation fails with an error if no entity or event is selected.

Examples

Example 1: Notify a team when a new booking is created

Authentication: OAuth2; Entities: Booking; Events: Create. Connect a Slack or email node after the trigger.

Example 2: Sync project and resource changes to another system

Entities: Project, Resource; Events: Create, Update, Delete. Route on the payload to update the target system.

Example 3: Audit timesheet changes using a token credential

Authentication: Access Token; Entities: Timesheet; Events: Update, Delete.

Links

Discussion