01
Map the workflow
Define triggers, records, owners, exceptions, and the consequence of a mistake.
Custom integration scope
Designed around your workflow and permissions
Connect Cornerstone to the workflows around it
Connect Cornerstone to recruiting, onboarding, employee support, and lifecycle workflows.
Typical objects
The records a scoped build may use
- Workers and candidates
- Jobs and applications
- Lifecycle events
- Documents and approvals
Workflow examples
Practical patterns to evaluate
These are design examples, not claimed customer deployments or results.
- 01
Coordinate approved Cornerstone lifecycle events across HR, IT, and managers.
- 02
Prepare recruiter or HR review packets from permission-scoped records.
- 03
Track onboarding or offboarding dependencies without automating employment decisions.
Delivery sequence
Integration work starts with the operating process
02
Confirm access
Check the platform edition, APIs, authentication, scopes, limits, and data policy.
03
Build and test
Implement narrow actions and verify normal, failure, retry, and approval paths.
04
Operate deliberately
Document ownership, logs, escalation, stop controls, and the change process.
Platform consideration
Cornerstone editions, APIs, authentication, permissions, webhooks, limits, and vendor policies must be confirmed during discovery.
Scope before promise
Platform editions, API access, permissions, rate limits, vendor policies, security requirements, and data residency can change what is feasible. CombineApps confirms scope before implementation.
Bring one real workflow
Define what Cornerstone should read, change, and leave for a person
We can map the systems, authority, exception paths, and test cases before deciding how the integration should be built.