Connect & ingest
Server-side requests retrieve Workday custom-report data. Date-window controls support labor imports and backfills, while credentials stay in the server environment.
API integrations, databases & automation
Connect the work between your tools.
Custom API integrations, PostgreSQL databases, and connected reporting. Practical experience bringing Workday data into project controls, with access and operational visibility designed into the workflow.
Discuss your projectA useful starting point
Define the decision.
Build the right system.
Start with the manual handoff: exporting a spreadsheet, copying records, or reconciling two tools. Integration scope depends on each system’s API, access permissions, and update limits. Those are checked before implementation.
What we can deliver
- A map of systems, data ownership, permissions, and the workflow to automate.
- API connections, scheduled syncs, or event-driven updates where your systems support them.
- Validation, duplicate handling, error reporting, and a clear recovery process.
- Documentation, operating instructions, and agreed support boundaries.
Selected work / Workday integration
From enterprise records to project decisions.
I built a Workday-to-PostgreSQL integration that brings workforce, project, labor, contract, and invoice data into a project-controls application. The work spans the API connection, data model, reconciliation, and reporting experience.
Map & store
Mapping functions turn source reports into application records. PostgreSQL tables preserve relationships between people, projects, phases, hours, contracts, and invoices. Duplicate handling and conflict-aware updates support repeat imports.
Reconcile & explain
Source time entries are matched to the project hierarchy. Unmatched work remains visible for review, and mapped actuals feed cost and productivity reporting. A useful dashboard needs a traceable path back to its inputs.
Observe & maintain
Sync-run history records status, timing, row counts, and errors. Connection-health tracking distinguishes the latest attempt from the last successful update, giving the operator a place to investigate stale data.
About this example
The integration described above is work I built. The public demo shows an adapted reconciliation workflow with synthetic data; it does not connect to Workday or a client database. Client identities, report addresses, credentials, and operational records are omitted. Workday is the source platform, not a claimed partnership or endorsement. Refresh timing depends on the configured sync process.
See how source records become usable project actuals.
Try the reconciliation demo ↗The data foundation
Design the database
behind the dashboard.
Database design & data engineering
Define how records relate, which system owns each field, and how updates reach the application. The model should support both everyday reporting and the questions that follow it.
- Relational models, stable identifiers, and source-to-destination mappings
- SQL queries, database migrations, and reporting aggregates
- Import validation, duplicate handling, and reconciliation checks
- Refresh history, error visibility, and documented recovery procedures
Access & security
Control who can see
and change the data.
Security-conscious application development
My application work includes authentication guards and project-scoped access checks. For each engagement, I define access boundaries alongside the API and database design, then test the agreed behavior.
- Server-side credential handling and least-privilege access design
- Authentication, role permissions, and project-level authorization
- Input validation and parameterized database operations
- Operational logs that support investigation without exposing secrets
- Documented access, retention, and deployment requirements
Application security engineering is part of the implementation scope. Independent penetration testing and formal compliance certification are separate specialist engagements.
How we work
A clear scope.
A working result.
- 01
Understand
Map the current process, the people involved, and the result you need.
- 02
Build & review
Test a useful first version with your real inputs. Resolve the details together.
- 03
Handoff
Receive the agreed files, documentation, and walkthrough. Define support before launch.
Start a conversation
Let’s make the next step concrete.
Send the problem, the starting point, and the deadline. We’ll define a useful first deliverable together.
Discuss your project