Tool definitions
A declared tool with a JSON schema and an implementation. The agent decides when to call it; you decide which agents may.
An agent is only as useful as what it can reach
Soria is a multi-system platform. It reads from, writes to and is triggered by the tools your organisation already depends on — without you replacing any of them.
Four ways Soria connects
Every integration below lands in one of these four shapes. That's what keeps the platform extensible without a fork per client.
MCP servers
Attach a Model Context Protocol server, with OAuth, and the agent reaches everything that server exposes.
Webhooks
Any system posts an event and an agent wakes up, runs its instructions and acts. Every run is logged with its status.
Cron jobs
Recurring work on the cadence you set — every thirty minutes through monthly — for syncs, audits, digests and reminder campaigns.
Microsoft 365
Deep in the Microsoft stack
LS2 Innovation is a Microsoft partner in higher education, with Teams and Microsoft 365 integrations running in production at post-secondary institutions. Soria inherits that ground.
- Microsoft TeamsAgents published as a Teams app, with adaptive cards, suggested actions and proactive messages into chats and channels.
- SharePointIndex a site or specific document libraries as a knowledge source, so agents follow content your teams already maintain.
- Outlook & calendarsRead availability, create meetings and send messages as part of an agent's work.
- Entra ID single sign-onInstitutional identity, with directory groups mapped onto Soria roles and permissions.
- Team and meeting eventsWebhook subscriptions on teams, team membership and online-meeting recordings drive event-based agents.
Education systems
The systems a post-secondary institution actually runs
Soria sits beside your systems of record rather than above them. It reads what it needs, writes only where you allow it, and links back to the authoritative source.
Moodle & your LMS
Publish an agent as a web app inside the course environment, or reachable standalone for people without an LMS account. Deliver notifications where students already look.
SIS / ERP / PGI
Read-only signals — enrolment, cycle, program, key dates — to give an agent context, plus extraction, matching and syncing for operational agents.
Academic calendar
Milestone dates drive what a contextual agent surfaces and when reminders go out. Manual entry works where no integration exists.
Ticketing & service desk
A native Freshdesk integration syncs ticket history and relays conversations, so escalation from an agent lands in the queue your team already works.
Document sources
Policies, regulations, procedures and guides — uploaded with version history, or indexed in place from SharePoint.
Your internal APIs
Anything with an HTTP endpoint becomes a tool. Declare the schema, scope who can call it, and the agent uses it when the conversation warrants.
Control
Connected does not mean unrestricted
Every connection is scoped, logged and revocable. An integration is a permission you grant, not a door you leave open.
- Per-agent tool grantsTools are grouped, and each organisation and each agent gets only the groups it needs.
- Act on behalf of a personAn agent can authenticate the user before taking an action, so a tool call inherits that person's rights rather than a service account's.
- Every call is loggedTool invocations, webhook runs and scheduled executions all appear in run logs with their status.
- Access rules respected on retrievalIndexed documents keep their source permissions, so an agent never surfaces a file to someone who couldn't open it.
Tell us what you run
Name your LMS, your SIS and your service desk. We'll show you where the agent plugs in and what it can do on day one.
Book a Demo