Watch a Banner agent and an Active Directory agent agree on a student-provisioning mapping in conversation — then watch that one-time negotiation compile into a native Orchestrator workflow that runs on its own. No developer hand-wired a field map.
Watch the Negotiation ↓ Book a MeetingIdentity-verified agents introduce themselves, negotiate the field mapping, and the Studio compiles their agreement into the workflow your team already knows how to run.
“I steward the person record for National Louis University. I provide my data to authorized agents to keep the university’s systems in sync.”
“I create and maintain directory accounts. I accept data only from agents my governance policy authorizes.”
The compiled workflow isn’t locked to a clock. Every integration the agents negotiate can fire on demand, by hand, and on schedule — on the same workflow, at the same time.
A new admit hits Banner and the account exists before the student opens their laptop. Event-driven, not batch-delayed.
Registrar needs a one-off re-sync during orientation week? One click in the Studio. No ticket, no script, no waiting for tonight’s batch.
The nightly safety net still runs. Scheduled execution is one of three modes — not the only one.
Every Connector-Agent carries an identity issued by the QuickLaunch Identity Server and speaks only to agents its governance policy authorizes. The negotiation starts from verified trust, not open endpoints.
The agents’ agreement lands in an Integration Negotiation Record: source operation, target operation, routing, and the field map — a reviewable artifact you approve before anything compiles.
The approved record compiles into a native Orchestrator workflow — the same nodes your team already runs. No LLM on the runtime path; secrets stay in the keychain.
What’s real: the source fields (Banner/Ethos persons), the target attributes (AD), the field map, and the compiled workflow graph are the actual output of the proven compiler — not mock-ups. What’s choreographed: the conversation is a scripted rendering of the agents’ exchange, for a controlled preview. A live-agent version negotiates in real time. This is a standalone concept preview, not the shipping product.
It’s where applications become AI Connector-Agents. Each system on campus — the SIS, the directory, the LMS — is represented by an identity-verified agent that knows its own schema, its own operations, and its own governance rules. Agents negotiate an integration in conversation, and that one-time negotiation compiles into a native QuickLaunch Orchestrator workflow that runs on its own. No developer hand-wires a field map.
Yes — governance is the foundation, not a bolt-on. Every Connector-Agent operates under a governance policy that defines exactly which agents it may exchange data with, and it refuses everything else. Every negotiation produces an Integration Negotiation Record: a structured, human-reviewable artifact capturing the source operation, target operation, routing rules, and the complete field map. Your team approves that record before anything compiles — and because the compile is deterministic, the workflow that runs is exactly the agreement you approved. That’s a durable audit trail from conversation to production.
Through the QuickLaunch Identity Server. Every Connector-Agent is issued its own identity — backed by the same enterprise identity infrastructure that secures campus single sign-on — so agents authenticate to each other with verified credentials, not open endpoints or shared API keys. Identity lifecycle, authorization, and revocation for agents live in the same place your institution already manages identity.
AI negotiates; deterministic code runs. The agents’ agreement compiles into a native Orchestrator workflow of standard nodes — connectors, filters, transforms — with no LLM anywhere on the runtime data path. Student records flow through the same proven workflow engine QuickLaunch customers run today, credentials stay in the keychain — never inline in workflow definitions — and every compile is validated against golden checks. AI speed at design time, deterministic reliability at runtime.
Trigger flexibility. Ellucian Data Connection runs on a schedule only. A QuickLaunch workflow fires three ways — on-demand via webhook the moment an event happens, manually when a person needs a one-off run, and on a schedule as the safety net — on the same workflow, at the same time. When provisioning fires the moment a student is admitted, day-one access stops being a batch-window problem.
Anything QuickLaunch connects to today. The demo pairs Banner — speaking Ellucian Ethos natively — with Active Directory for student provisioning, and the same pattern extends across the QuickLaunch connector catalog: SIS and ERP systems like Banner and Colleague, directories like Active Directory and Entra ID, plus LMS, CRM, cloud, and notification systems. Each connector becomes an agent that stewards its own data.
Always. The Integration Negotiation Record is presented for human approval before anything compiles — every field mapping, every routing rule, both the create and update paths. After approval, the compiled workflow opens in the same Orchestrator canvas your team already uses, so operations staff manage agent-built integrations exactly like every other workflow: same monitoring, same run history, same controls.