ELI
Resources
Product · Provisioning

Provision and offboard.

Type what you need done. ELI runs the access change across your connected tools and shows you every result.

Ask ELI

One prompt, sixteen tools.

“Onboard Sara to the marketing stack.” ELI works out which tools that means, checks what each vendor’s API supports on your plan, and runs the invites — confirming with you before anything writes.

ELI·ACTIONS
onboard sara@acme.com to the marketing stack
Google Workspace
Google Workspace
invite_user
Done
Slack
Slack
invite_user
Done
GitHub
GitHub
invite_user
Done
Linear
Linear
invite_user
Running…
Notion
Notion
invite_user
Queued
16 tools · every result writes to the activity feed
Connector contract

One contract across every vendor

Each native integration follows the same eight-method contract, so an action means the same thing whether it runs against Google Workspace or Linear.

  • ReadList users, seats, roles, and billing from each vendor
  • WriteInvite, deactivate, change role, reduce seats, cancel licenses
  • Plan-awareSupported actions and account requirements shown up front
  • ConfirmEvery write action is shown for confirmation before it runs
  • TrailVendor, action, actor, and outcome land in the activity feed
01

Know what each API can actually do

Capabilities vary by vendor and plan. ELI shows supported actions and account requirements up front instead of presenting a button that will fail later.

02

Confirm write actions

Ask ELI to invite, deactivate, or change a role. The requested action is shown for confirmation before it runs through the connected vendor.

03

Keep an activity trail

Connector and agent actions write back to the workspace activity feed with the vendor, action, actor, and outcome attached.

Ready to run your first action?