Integrations

Nobody should type a staff list twice.

A new hire appears on Monday and rides on Tuesday. Someone leaves, and their credits stop the same hour. That only works if Rydlnk reads from the systems you already keep accurate.

Connectors

Three kinds of system, one canonical employee.

People come from HR. Shifts come from workforce management. Spend goes back to finance. Rydlnk keeps one employee record and treats every source as a feed into it.

People

WDWorkdayWorkers, departments, cost centers, terminations

BHBambooHRWorkers and employment status

Payroll

ADPADP Workforce NowEmployee master, cost centers, pre-tax benefit codes

PLPaylocityEmployee master and deduction codes

Finance

NSNetSuitePosts the monthly commuter journal via SuiteTalk

Field CRM

SFSalesforceCharge field trips to an account or opportunity

HSHubSpotCharge field trips to a deal

Any system

CSVSFTP / CSVDrop a file, we map the columns once

How a sync runs

Pull, resolve, apply, push.

Pull

Read on a schedule

A nightly full sync plus webhooks for hires, terminations and roster changes. Full sync catches drift; webhooks catch the things that can't wait until morning.

Resolve

Match to a person

Employee number first, work email second. Conflicts go to a review queue instead of quietly creating a duplicate person with a second wallet.

Apply

Move entitlements

A department change moves the cost center. A promotion changes the entitlement rule. A termination freezes the wallet and reclaims unspent credits.

Push

Send spend back

A journal per cost center per period, with seat-level detail attached, posted through the finance connector or exported as CSV.

If you have none of these

A file drop is a perfectly good integration.

Plenty of good employers run their roster in a spreadsheet. Drop a CSV on SFTP, or upload it in the portal, and Rydlnk maps the columns once and remembers. The only fields that genuinely matter are an employee identifier, a home address, a department and a shift time.

The one thing worth getting right early is the home address, because an employee without a geocoded location can't be clustered and quietly disappears from every manifest. The portal surfaces those as a review queue rather than letting them fall through.

Minimum viable columns

employee_no	E-1041	required
full_name	Tendai Moyo	required
department	Production	required
cost_centre	CC-4100	recommended
home_city	Spanish Fork	required
shift_start	2026-07-27 22:00	required
work_email	t.moyo@…	optional