Oracle PeopleSoft and Zendesk integration

What moves between them

Employee and vendor records flow from PeopleSoft into Zendesk on a schedule you set. Employees in PeopleSoft become users (potential agents) in Zendesk, carrying department and email address. Vendors become organizations in Zendesk so your support team can reference them when handling inquiries. Because PeopleSoft is behind your firewall and offers no webhooks, ml-connector polls the employee and vendor tables on your schedule, matching by unique ID and updating Zendesk records whenever PeopleSoft data changes. Terminations in PeopleSoft deactivate the corresponding Zendesk user so former employees no longer have access.

How ml-connector handles it

ml-connector stores both credential sets encrypted and manages the Basic Auth session for PeopleSoft and the OAuth2 bearer token for Zendesk. Because PeopleSoft requires a customer-specific hostname and port with optional VPN access, ml-connector accepts the full base URL and hostname per customer and validates connectivity before sync begins. It polls PeopleSoft employee and vendor data using date-range filters to reduce load on your on-premise system, handles the REST response format from PeopleSoft, and transforms employees and vendors into Zendesk users and organizations. Email addresses are preserved where they exist; missing data is flagged in the audit log so you can decide whether to fill it manually. Rate limits from Zendesk OAuth are respected with exponential backoff and retry. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized financial services company runs Oracle PeopleSoft on-premise for accounting and HR, and Zendesk in the cloud for customer support. Before the integration, the HR team exported the employee directory every month and manually updated Zendesk user lists, and the procurement team manually created Zendesk organizations for key vendors so the support team could reference them during customer calls. With PeopleSoft and Zendesk connected, new hires appear in Zendesk within minutes of being added to PeopleSoft, terminated employees are automatically deactivated in Zendesk, and the top 50 vendors are synced as organizations that support agents can search by name. The support team no longer waits for manual updates and has a current vendor reference at hand.

What you can do

• •Sync employees from PeopleSoft to Zendesk users, carrying department, title, and email address so support agents have current HR context.
• •Create and update Zendesk organizations from PeopleSoft vendor records so your support team can reference vendors during customer calls.
• •Deactivate Zendesk users when employees are terminated in PeopleSoft to keep agent rosters accurate and secure.
• •Handle PeopleSoft's hostname-specific REST endpoints and Basic Auth or OAuth2 session management so ml-connector works across unique customer environments.
• •Poll PeopleSoft with date-range filters on your schedule, with retries and a full audit trail on every record, safe for replay.

Questions

Does Oracle PeopleSoft support webhooks for this integration?

No. PeopleSoft on-premise has no webhooks for cloud connectors. ml-connector polls employee and vendor tables on a schedule you control, using date-range filters to minimize load on your on-premise system. If you have Integration Broker async publishing enabled, ml-connector can also listen for PeopleSoft business events at a registered HTTP endpoint.

How does ml-connector handle PeopleSoft's customer-specific hostname and firewall?

ml-connector accepts the full base URL (hostname, port, and node name) for your PeopleSoft environment. If your system is behind a firewall, you must whitelist the ml-connector IP address or expose PeopleSoft via a reverse proxy. ml-connector tests connectivity at the start of each sync cycle and logs failures so firewall issues are caught early.

What happens to Zendesk users and organizations when the PeopleSoft record is deleted?

ml-connector does not delete Zendesk records. When an employee is terminated in PeopleSoft, the corresponding Zendesk user is deactivated so they lose agent access. When a vendor is removed from PeopleSoft, the Zendesk organization remains but is marked inactive in ml-connector's audit log so you can investigate before removing it from Zendesk if needed.