Oracle PeopleSoft and Slack integration

What moves between them

The main flow runs from Oracle PeopleSoft into Slack. ml-connector polls PeopleSoft at a schedule you control, typically daily or on-demand, for new or changed employee records including hires, terminations, job changes, and compensation updates. Each new employee generates a notification message posted to a designated Slack channel for HR or management, with details about the employee, their job, their manager, and their start date. Terminations and job changes also trigger Slack notifications so the team is kept in sync with PeopleSoft's current employee roster.

How ml-connector handles it

ml-connector accepts the PeopleSoft instance hostname, port, and node name (since each customer's environment is self-hosted and unique), authenticates with either HTTP Basic Auth credentials or an OAuth2 Bearer token depending on the PeopleTools version in use, and polls PeopleSoft's employee directory and job service operations on a configurable schedule. The connector filters results by date range to find only records changed since the last sync, avoiding duplicate processing. Each employee record found in PeopleSoft is transformed into a Slack message with formatted blocks showing the employee name, job title, department, and start or end date, then posted to the designated Slack channel using the chat.postMessage method. The message includes a timestamp and reference to the source PeopleSoft employee ID so you can trace any record back to its origin. If a Slack message fails to post, ml-connector retries with exponential backoff up to 3 times before surfacing an error, and every message and retry is logged in the audit trail. PeopleSoft has no standard pagination or published rate limits, so ml-connector respects customer bandwidth by using date filters and configurable sync intervals rather than querying all employees on every run.

A real-world example

A mid-sized professional services firm uses Oracle PeopleSoft on-premise to manage their 400-person workforce across three offices. Before the integration, new hires and terminations were handled manually - the HR team updated PeopleSoft, then sent email announcements that often were delayed and incomplete. With PeopleSoft and Slack connected, each new hire automatically triggers a message in the new-team-members channel with the employee's name, start date, and department, and terminations are announced to hr-staff. The office managers can now see staffing changes in Slack the same day they happen in PeopleSoft, and on-boarding tasks are kicked off faster because the rest of the company is notified immediately.

What you can do

• •Post employee hire, termination, and job change notifications to Slack channels when changes occur in Oracle PeopleSoft.
• •Transform PeopleSoft employee records into formatted Slack messages showing employee name, job title, department, manager, and effective date.
• •Poll Oracle PeopleSoft on a schedule you control with date-range filters to find only changed records since the last sync.
• •Authenticate Oracle PeopleSoft with HTTP Basic Auth or OAuth2 Bearer token, and Slack with OAuth2 bot tokens.
• •Track every employee notification sent with a full audit trail, including Slack message IDs and timestamps for traceability.

Questions

How often does the integration sync employee changes from PeopleSoft to Slack?

ml-connector polls Oracle PeopleSoft on a schedule you configure, typically daily, weekly, or on-demand. Each poll uses date filters to find only employee records changed since the last run, so only new hires, terminations, and job changes trigger Slack notifications. There are no webhooks in PeopleSoft, so polling is the standard approach.

Which PeopleSoft employee fields appear in the Slack notification?

The default notification includes the employee name, employee ID, job title, department, manager name, and the effective date of the change (hire date or termination date). You can customize which fields appear in the Slack message by configuring the message template for your workspace.

What happens if a Slack message fails to post?

ml-connector retries the message with exponential backoff up to 3 times. If all retries fail, the error is logged in the audit trail so you can investigate and manually post the notification or replay the sync. Every message attempt and result is recorded so you have a complete history of what was sent to Slack.