Healthcare · 10 pre-built actions
Epic integration with Nexus
Connect Epic scheduling to administrative workflows. Appointment and service request actions let administrative steps around Epic run with approval and a complete record.
Nexus orchestrates administrative and operational steps around the clinical system. Clinical decisions stay with clinicians and the system of record.
Pre-built actions
What you can automate
10 pre-built Epic actions, grouped by what they work on.
10
PRE-BUILT ACTIONS
- 01Appointments actions work with scheduling.
- 02Service Request actions work with service requests.
- 03Other Epic operations use the available interfaces in the same workflow.
Workflow
How it fits into a Nexus workflow
Epic steps run as pre-built actions. A run that uses them starts from a webhook, a schedule, a request in Nexus or another system's trigger source.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the Epic API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
Appointment reminders
Upcoming appointments trigger reminders through approved channels.
Service request follow-up
Service requests create administrative tasks for the right team.
Scheduling exceptions
Conflicts route to scheduling staff for a decision.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
Industry use cases
Processes that use Epic
FAQ
Epic connector questions
- Which Epic actions are pre-built?
- Nexus includes 10 pre-built Epic actions across Appointments (6) and Service Request (4).
- Can Epic start a workflow?
- Runs that use Epic start from a webhook, a schedule or another trigger source. Epic steps run as actions inside the workflow.
- What if the operation I need is not pre-built?
- Use the Epic API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- Healthcare
Governed automation for healthcare operations.
- Oracle Health connector
Appointments, charge items and insurance plans.
- Human-in-the-loop
Where approval belongs in a running workflow.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how Epic fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.