Slack

61/100 — 6.9% of calls failing, against a 2% degraded threshold. 2 further penalty applied.

• −26Error rate6.9% of calls failing, against a 2% degraded threshold.
• −5Latency890ms mean round trip, above the 800ms threshold.
• −8Rate ceilingPeak consumption reached 98% of the 60/min ceiling.

Method

⬡OAuth 2.0

Credential

oauth_····758a

Last verified

10h ago

Principal

AI-EOS Platform · Slack Technologies

Expires

321h

Scopes held

4/4

• →Send messagesmessage.send

  Post into a channel or a direct message.

• →Manage channelschannel.manage

  Create and archive channels to mirror the Hub.

• ←Receive messagesmessage.receive

  Ingest replies back into the Communication Hub.

• ←Read presencepresence.read

  Know whether a human is available before escalating.

Modules request capabilities, never connectors. A capability offered by two connectors gives the requesting module a fallback it does not have to know about.

• Workflow Completedworkflow.completed

  A workflow reached its final stage with every gate cleared.

  Raised by workflows · see the fan-out chain

• Workflow Blockedworkflow.blocked

  A workflow stalled on a dependency or an unapproved gate.

  Raised by workflows · see the fan-out chain

• Approval Requestedapproval.requested

  A gate opened and is waiting on an executive seat.

  Raised by workflows · see the fan-out chain

• Critical Recommendationdecision.critical

  The advisory layer raised something at critical priority.

  Raised by decision-engine · see the fan-out chain

• Alert Raisedalert.raised

  A threshold was crossed anywhere in the estate.

  Raised by decision-engine · see the fan-out chain

• Broadcast Sentmessage.broadcast

  An executive announcement went out to the estate.

  Raised by communications · see the fan-out chain

• Github pull request mergedgithub.pull_request.merged

  Topic not registered — nothing will route it.

  Raised by integrations · see the fan-out chain

• Github release publishedgithub.release.published

  Topic not registered — nothing will route it.

  Raised by integrations · see the fan-out chain

• Github workflow completedgithub.workflow.completed

  Topic not registered — nothing will route it.

  Raised by integrations · see the fan-out chain

• Google permission grantedgoogle.permission.granted

  Topic not registered — nothing will route it.

  Raised by integrations · see the fan-out chain

• Google document publishedgoogle.document.published

  Topic not registered — nothing will route it.

  Raised by integrations · see the fan-out chain

Name

AI-EOS

Publisher ID

aeos

Platform vendor

Slack Technologies

Support

operations@ai-eos.internal

Published by the platform itself. These manifests ship with the build rather than being fetched.

Slack Technologies owns the platform this plugin reaches. AI-EOS authored the manifest.

Installed

1.0.0

Published

1.0.0

Minimum platform

1.0.0

Compatibility

Compatible

Manifest schema

1.0

First published

16 months ago

Requires platform 1.0.0 or newer. This build is 1.0.0.

• 1.0.0major · 6 months ago
  • First stable release. Six subscribed topics, all answered by message.send.
  • The connector that made the first-outbound-capability fallback worth naming.

AI-EOS permissions are what this plugin may do insidethe platform, resolved against the API Gateway’s own table. Scopes are what the external platform is asked to allow. They are different systems and neither substitutes for the other.

• company:read4 roles

  Companies, departments, executives and the knowledge graph projection.

• workflow:read4 roles

  Workflows, stages, tasks and approval gates.

• agent:read4 roles

  The agent roster and its derived state.

• analytics:read4 roles

  Enterprise Intelligence read models and the Decision Engine's outputs.

Declares no dependencies. It can be installed against an empty estate.

Whether each is satisfied is resolved against the live estate at install time, not here.

Authentication

OAuth 2.0

Credential storage

Never stored

External scopes

4

AI-EOS permissions

4

Minimum role

viewer

Inbound deliveries

Signature verified

Tenant isolation

Installation state is tenant-scoped

A plugin is a data literal. Nothing in the marketplace executes plugin code, and a plugin cannot bypass the Authentication Manager, the Integration Hub, the API Gateway or a permission check, because it has no code path — the host performs every transition.

The credential is referenced by a masked hint (oauth_····758a) and nothing else. The auth state type has no field a credential fits in, so the guarantee is enforced by the type checker rather than by convention.

Data leaving AI-EOS

2 capabilities

Data entering AI-EOS

2 capabilities

Modules served

4

Event topics received

11

Direction is declared per capability, so what this plugin can send and what it can receive are both enumerable rather than a matter of trust. It reaches only the modules listed above, and only through capabilities the Integration Hub resolves.

• Setup guide →
• Vendor API reference →

• ✉/api/integrations/slack/eventsactive7,420 in · 2% failed · 6h ago

  Forwards workflow.completed, workflow.blocked, approval.requested

• warnGateway2h agoError rate at 6.9% over the trailing window. The gateway is applying backoff.
• infoSync2h agoSynchronisation completed — 120,960 records reconciled in 24h.
• infoGateway57m ago24,192 gateway calls in 24h at 890ms mean latency.
• infoRegistry3d agoConnector v1.0.0 installed against manifest schema 1.0.

Roadmap

• ◇Slash commands that launch a workflow from Slack
• ◇Approval gates cleared from a message action

What this connector would gain next. Mirrors the Future Integrations list every module carries in the Navigator registry.