Workday

Configuración

• absencePlanstringObligatorio

  The Workday ID of the absence plan to monitor (e.g., PTO, sick leave, vacation). This can be obtained from 'List Absence Balances' action.

• effectivestring

  Optional: Date for which to retrieve the balance, in yyyy-mm-dd format (e.g., '2025-12-31'). If omitted, monitors the most recent available balance.

• intervalnumber

  Periodic Interval to Check for Updates & Send a Trigger in Minutes

• workerstringObligatorio

  The Workday ID of the worker to monitor. This can be obtained from actions like 'Get Current User' or 'List Workers'.

Payload del evento

• changed_fieldsstring[]

  List of fields that changed (e.g., ['quantity', 'effectiveDate'])

• current_balanceobjectObligatorio

  The current balance details

• previous_balanceobject

  Schema for absence balance details.

• quantity_changenumber

  Change in quantity (positive for increase, negative for decrease)

Instrucciones

**Instructions for Setting Up the Trigger:** - This trigger monitors a specific worker's absence plan balance for changes. - You must provide both a worker ID and an absence plan ID to monitor. - Worker IDs can be obtained from 'Get Current User' or 'List Workers' actions. - Absence Plan IDs can be obtained from 'List Absence Balances' or 'Get Absence Balance' actions. - Optionally specify an effective date to monitor historical balances. - The trigger will detect changes to: - Balance quantity (hours/days available) - Effective date - Position changes - Unit of measurement changes - Date of first absence - Category changes - Any other balance detail fields - On the first poll, no events are triggered (establishes baseline). - Subsequent polls will detect and report any changes to the absence balance.

Configuración

• absencePlanstringObligatorio

  The Workday ID of the absence plan to monitor (e.g., PTO, sick leave, vacation). This can be obtained from 'List Balances' action.

• effectivestring

  Optional: Date for which to retrieve the balance, in yyyy-mm-dd format (e.g., '2025-12-31'). If omitted, monitors the most recent available balance.

• intervalnumber

  Periodic Interval to Check for Updates & Send a Trigger in Minutes

• workerstringObligatorio

  The Workday ID of the worker to monitor. This can be obtained from actions like 'Get Current User' or 'List Workers'.

Payload del evento

• changed_fieldsstring[]

  List of fields that changed (e.g., ['quantity', 'effectiveDate'])

• current_balanceobjectObligatorio

  The current balance details

• event_typestring

  Type of event that occurred

• previous_balanceobject

  Schema for balance details.

Instrucciones

**Instructions for Setting Up the Trigger:** - This trigger monitors a specific worker's absence plan balance for changes. - You must provide both a worker ID and an absence plan ID to monitor. - Worker IDs can be obtained from 'Get Current User' or 'List Workers' actions. - Absence Plan IDs can be obtained from 'List Balances' or 'List Absence Balances' actions. - Optionally specify an effective date to monitor historical balances. - The trigger will detect changes to: - Balance quantity (hours/days available) - Effective date - Position changes - Unit of measurement changes - Date of first absence - Category changes - Any other balance detail fields - On the first poll, no events are triggered (establishes baseline). - Subsequent polls will detect and report any changes to the balance details.

Configuración

• intervalnumber

  Periodic Interval to Check for Updates & Send a Trigger in Minutes

• interview_idstringObligatorio

  The Workday Interview ID (WID) - a unique identifier for the interview. This can be obtained from the List Interviews action. Format: 32-character alphanumeric string.

• limitinteger

  The maximum number of feedback entries to check in each poll (1-100)

Payload del evento

• event_typestring

  Type of event that occurred

• feedback_entryobjectObligatorio

  The feedback entry that was submitted or updated

• interview_idstringObligatorio

  The Workday interview ID this feedback is associated with

Instrucciones

**Instructions for Setting Up the Trigger:** - This trigger monitors feedback entries for a specific interview in Workday Recruiting. - You must provide the Interview ID (WID) to monitor. - The trigger will detect feedback entries submitted or updated after the trigger is set up. - Use the limit parameter to control how many feedback entries to check in each poll (default: 10). - The trigger uses snapshot-based diffing to detect new or modified feedback entries.

Configuración

• intervalnumber

  Periodic Interval to Check for Updates & Send a Trigger in Minutes

• job_posting_idstringObligatorio

  The unique Workday ID of the job posting to monitor. This ID can be obtained from the LIST_JOB_POSTINGS or GET_MY_JOB_POSTINGS actions. Example format: 'JOB-12345' or a UUID-style identifier.

Payload del evento

• changed_fieldsstring[]

  List of field names that changed between snapshots

• current_snapshotobjectObligatorio

  Current state of the job posting

• event_typestring

  Type of event that occurred

• previous_snapshotobject

  Schema representing a snapshot of a job posting's state.

Instrucciones

**Instructions for Setting Up the Trigger:** - This trigger monitors a specific job posting for any changes to its details. - You need to provide the unique Workday ID of the job posting you want to monitor. - The job posting ID can be obtained from the LIST_JOB_POSTINGS or GET_MY_JOB_POSTINGS actions. - The trigger will detect changes to any field including: - Job title, description, and posting title - Department, location, and position - Employment type and experience level - Hiring manager and recruiters - Posting status (Open, Closed, On Hold, etc.) - Posting start and end dates - On first run, the trigger will store the initial state but not fire an event. - Subsequent runs will compare the current state to the previous state and trigger only if changes are detected.

Configuración

• intervalnumber

  Periodic Interval to Check for Updates & Send a Trigger in Minutes

• job_posting_idstringObligatorio

  The Workday ID of the job posting to monitor for questionnaire changes. This ID can be obtained from the LIST_JOB_POSTINGS or GET_MY_JOB_POSTINGS actions.

• questionnaire_typestring[]

  Optional: Filter questionnaires by type (e.g., screening, pre-hire). If not specified, monitors all questionnaire types.

Payload del evento

• changed_fieldsstring[]

  List of top-level fields that changed (e.g., 'questionnaires', 'total_questions')

• current_snapshotobjectObligatorio

  The current questionnaire snapshot

• event_typestring

  Type of event that occurred

• previous_snapshotobject

  Schema representing a snapshot of questionnaires.

• questionnaires_addedinteger

  Number of questionnaires added since last poll

• questionnaires_removedinteger

  Number of questionnaires removed since last poll

• questions_addedinteger

  Number of questions added since last poll

• questions_removedinteger

  Number of questions removed since last poll

Instrucciones

**Instructions for Setting Up the Trigger:** - This trigger monitors a specific job posting's candidate questionnaires for changes. - You must provide the Workday ID of the job posting to monitor. - Job posting IDs can be obtained from 'List Job Postings' or 'Get My Job Postings' actions. - Optionally filter by questionnaire type (e.g., screening, pre-hire). - The trigger will detect: - New questionnaires added to the job posting - Questionnaires removed from the job posting - Changes to existing questionnaires - Questions added or removed within questionnaires - Modifications to question content or structure - On the first poll, no events are triggered (establishes baseline). - Subsequent polls will detect and report any changes to the questionnaires.

Configuración

• categorystring

  Optional: Filter by Workday ID of a specific Time Off Plan, Leave Type, or Absence Table category. Leave empty to monitor all categories.

• effectivestring

  Optional: Retrieve absence balances as of a specific date in yyyy-mm-dd format (e.g., '2024-12-31'). If not specified, uses current date.

• intervalnumber

  Periodic Interval to Check for Updates & Send a Trigger in Minutes

• limitinteger

  Maximum number of balance records to fetch in each poll (1-100). Default is 50.

• workerstringObligatorio

  The Workday ID of the worker to monitor for new absence balances. This can be obtained from actions like 'Get Current User' or 'List Workers'.

Payload del evento

• absence_balanceobjectObligatorio

  The newly detected absence balance record

• event_typestring

  Type of event that occurred

Instrucciones

**Instructions for Setting Up the Trigger:** - This trigger monitors a specific worker's absence balances for new records. - You must provide a worker ID to monitor (obtained from 'Get Current User' or 'List Workers' actions). - Optionally filter by category (Time Off Plan, Leave Type, or Absence Table category ID). - Optionally specify an effective date to monitor balances as of a specific date. - The trigger detects when new absence balance records appear, such as: - New time off plans added to the worker - New leave of absence types becoming available - New absence buckets/categories appearing - Use limit to control how many balance records to check in each poll (default: 50, max: 100). - On the first poll, no events are triggered (establishes baseline). - Subsequent polls will detect and report any new absence balance records. **Examples:** - Monitor all new absence balances: Provide only worker ID - Monitor specific category: Provide worker ID and category ID - Monitor historical balances: Provide worker ID and effective date

Configuración

• intervalnumber

  Periodic Interval to Check for Updates & Send a Trigger in Minutes

• interview_statusstring[]

  Filter interviews by status. Options: AWAITING_ME, COMPLETED, FEEDBACK_COMPLETE, NOT_SCHEDULED, PENDING_FEEDBACK, SCHEDULED, SUBMITTED_FEEDBACK, MAKE_INTERVIEW_DECISION. Leave empty to monitor all statuses.

• limitinteger

  Maximum number of interviews to check in each poll (1-100)

Payload del evento

• event_typestring

  Type of event that occurred

• interviewobjectObligatorio

  The newly scheduled interview

Instrucciones

**Instructions for Setting Up the Trigger:** - This trigger monitors Workday interviews and detects when new interviews are scheduled or created. - You can optionally filter by interview status (e.g., SCHEDULED, PENDING_FEEDBACK). - The trigger will detect interviews created after the trigger is set up. - Use limit to control how many interviews to check in each poll (default: 20, max: 100). - Examples of status filters: - ["SCHEDULED"] - Monitor only scheduled interviews - ["SCHEDULED", "PENDING_FEEDBACK"] - Monitor scheduled and pending feedback interviews - Leave empty to monitor all interview statuses

Configuración

• categorystring[]

  Filter job postings by category IDs. Leave empty to monitor all categories.

• intervalnumber

  Periodic Interval to Check for Updates & Send a Trigger in Minutes

• job_requisitionstring[]

  Filter by specific job requisition IDs. Leave empty to monitor all job postings.

• job_sitestring[]

  Filter job postings by job site IDs. Leave empty to monitor all sites.

• limitinteger

  Maximum number of job postings to fetch in each poll (1-100)

Payload del evento

• event_typestring

  Type of event that occurred

• job_postingobjectObligatorio

  The newly posted job

Instrucciones

**Instructions for Setting Up the Trigger:** - This trigger monitors Workday for newly published job postings. - You can optionally filter by job requisition IDs, categories, or job sites. - The trigger will detect job postings created after the trigger is set up. - Use limit to control how many job postings to check in each poll (default: 20, max: 100). - Examples of filters: - job_requisition: ["JR-12345", "JR-67890"] - Monitor specific requisitions - category: ["CAT-001"] - Monitor specific job categories - job_site: ["SITE-001"] - Monitor specific job sites - Leave all filters empty to monitor all new job postings

Configuración

• intervalnumber

  Periodic Interval to Check for Updates & Send a Trigger in Minutes

• prospect_idstringObligatorio

  The unique Workday ID (WID) of the prospect to monitor. Must be a 32-character hexadecimal string (e.g., 'a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6'). This ID can be obtained from prospect-related actions.

Payload del evento

• changed_fieldsstring[]

  List of field names that changed between snapshots

• current_snapshotobjectObligatorio

  Current state of the prospect profile

• event_typestring

  Type of event that occurred

• previous_snapshotobject

  Schema representing a snapshot of a prospect's core profile state.

Instrucciones

**Instructions for Setting Up the Trigger:** - This trigger monitors a specific prospect profile for any changes to its core details. - You need to provide the unique Workday ID (WID) of the prospect you want to monitor. - The prospect ID must be a 32-character hexadecimal string (e.g., 'a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6'). - The trigger will detect changes to any field including: - Candidate information (email, name, phone) - Contact consent status - Prospect status and type - Source (e.g., LinkedIn, Facebook) - Targeted management level - Referring worker - Candidate tags and pools - On first run, the trigger will store the initial state but not fire an event. - Subsequent runs will compare the current state to the previous state and trigger only if changes are detected.

Configuración

• intervalnumber

  Periodic Interval to Check for Updates & Send a Trigger in Minutes

• limitinteger

  Maximum number of attachments to check in each poll (1-100)

• prospect_idstringObligatorio

  The Workday ID of the prospect to monitor for new resume attachments

Payload del evento

• attachmentobjectObligatorio

  The newly added resume attachment

• event_typestring

  Type of event that occurred

• prospect_idstringObligatorio

  The prospect ID this attachment belongs to

Instrucciones

**Instructions for Setting Up the Trigger:** - This trigger monitors resume attachments for a specific Workday prospect. - You must provide the prospect_id to monitor. - The trigger will detect new resume attachments uploaded after the trigger is set up. - Use limit to control how many attachments to check in each poll (default: 20, max: 100). - When a new resume is uploaded or a new version is added, the trigger will fire.

Configuración

• categorystring

  Optional: Filter by absence type category. Valid values: Leave of Absence Type (17bd6531c90c100016d74f8dfae007d0), Absence Table (17bd6531c90c100016da3f5b554007d2), Time Off (17bd6531c90c100016d4b06f2b8a07ce).

• effectivestring

  Optional: The effective date for which to check eligible absence types, in yyyy-mm-dd format (e.g., '2025-12-31'). If omitted, uses current date.

• intervalnumber

  Periodic Interval to Check for Updates & Send a Trigger in Minutes

• worker_idstringObligatorio

  The Workday ID of the worker to monitor. This can be obtained from actions like 'Get Current User' or 'List Workers'. Note: Due to Workday security permissions, this typically only works for the authenticated user's own worker ID.

Payload del evento

• added_absence_typesobject[]

  List of absence types that the worker became newly eligible for

• event_typestring

  Type of event that occurred

• removed_absence_typesobject[]

  List of absence types that the worker is no longer eligible for

Instrucciones

**Instructions for Setting Up the Trigger:** - This trigger monitors changes to a worker's eligible absence types. - You must provide a worker ID (typically obtained from 'Get Current User' action). - Due to Workday security, this typically only works for the authenticated user's own worker ID. - Optionally filter by absence type category: - Leave of Absence Type: 17bd6531c90c100016d74f8dfae007d0 - Absence Table: 17bd6531c90c100016da3f5b554007d2 - Time Off: 17bd6531c90c100016d4b06f2b8a07ce - Optionally specify an effective date to check eligibility for a specific date. - The trigger will detect when: - New absence types are added (worker becomes eligible) - Absence types are removed (worker becomes ineligible) - On the first poll, no events are triggered (establishes baseline). - Subsequent polls will detect and report any changes to the eligible absence types list.

Configuración

• from_datestring

  Optional: Start date for filtering leaves in yyyy-mm-dd format.

• intervalnumber

  Periodic Interval to Check for Updates & Send a Trigger in Minutes

• leave_typestring[]

  Optional: Filter by specific leave type IDs. Multiple IDs can be specified to monitor multiple types.

• statusstring[]

  Optional: Filter by specific status IDs. Use 'Get Leave Status Values' action to retrieve valid status IDs.

• to_datestring

  Optional: End date for filtering leaves in yyyy-mm-dd format.

• worker_idstringObligatorio

  The Workday ID of the worker to monitor. This can be obtained from actions like 'Get Current User' or 'List Workers'.

Payload del evento

• change_typestringObligatorio

  Type of change: 'created', 'updated', or 'deleted'

• changed_fieldsstring[]

  List of fields that changed for updated records (e.g., ['status', 'estimatedLastDayOfLeave'])

• current_leaveobject

  Schema for leave of absence details.

• leave_idstringObligatorio

  The unique ID of the leave of absence record that changed

• previous_leaveobject

  Schema for leave of absence details.

Instrucciones

**Instructions for Setting Up the Trigger:** - This trigger monitors all leave of absence records for a specific worker. - You must provide a worker ID to monitor. - Worker IDs can be obtained from 'Get Current User' or 'List Workers' actions. - Optionally filter by: - Leave types (use leave type IDs from the system) - Status values (use 'Get Leave Status Values' action) - Date range (fromDate and toDate) - The trigger will detect: - New leave requests (created) - Changes to existing leaves (status, expected return date, actual return date, comments, etc.) - Deleted or rescinded leaves - On the first poll, no events are triggered (establishes baseline). - Subsequent polls will detect and report any changes to leave records. - State is bounded to prevent unlimited growth - only the most recent leaves are tracked.

Configuración

• from_datestring

  Optional: Only monitor leaves starting from this date onwards (yyyy-mm-dd format). Useful for filtering historical leaves.

• intervalnumber

  Periodic Interval to Check for Updates & Send a Trigger in Minutes

• leave_typestring[]

  Optional: Filter by specific leave type IDs (UUIDs). You can specify multiple leave type IDs to monitor specific types of leaves (e.g., Personal Leave, Medical Leave, etc.). Leave empty to monitor all leave types.

• limitinteger

  Maximum number of leave records to fetch in each poll (1-100). Default is 50.

• statusstring[]

  Optional: Filter by leave status IDs (UUIDs). Use the 'Get Leave Status Values' action to retrieve valid status IDs. Common statuses include: Successfully Completed, In Progress, Canceled, Rescinded. Leave empty to monitor all statuses.

• worker_idstringObligatorio

  The Workday ID of the worker to monitor for new leave of absence records. This can be obtained from actions like 'Get Current User' or 'List Workers'.

Payload del evento

• event_typestring

  Type of event that occurred

• leave_of_absenceobjectObligatorio

  The newly created leave of absence record

Instrucciones

**Instructions for Setting Up the Trigger:** - This trigger monitors a specific worker's leaves of absence for new records. - You must provide a worker ID to monitor (obtained from 'Get Current User' or 'List Workers' actions). - Optionally filter by leave type IDs to monitor specific types of leaves (e.g., Medical Leave, Personal Leave). - Optionally filter by status IDs to monitor leaves in specific statuses (e.g., In Progress, Successfully Completed). - Optionally specify a from_date to only monitor leaves starting from a specific date onwards. - The trigger detects when new leave of absence records appear, such as: - New leave requests submitted by the worker - New leaves initiated by HR or managers - Any new leave record added to the worker's profile - Use limit to control how many leave records to check in each poll (default: 50, max: 100). - On the first poll, no events are triggered (establishes baseline). - Subsequent polls will detect and report any new leave of absence records. **Examples:** - Monitor all new leaves: Provide only worker_id - Monitor specific leave type: Provide worker_id and leave_type (list of leave type IDs) - Monitor leaves in specific status: Provide worker_id and status (list of status IDs) - Monitor recent leaves: Provide worker_id and from_date