Connectors, channels, knowledge sources and automation — one vocabulary for everything that links agents to your systems, people and events, what is true today and what is next.
Connectors reach your systems. Tools are what agents are allowed to do there. Channels are where your people and customers meet the agents. Knowledge sources are what agents read. Automation starts work from events and reports back.
الموصّلات تصل إلى أنظمتك. الأدوات هي ما يُسمح للوكلاء بفعله هناك. القنوات هي حيث يلتقي موظفوك وعملاؤك بالوكلاء. مصادر المعرفة هي ما يقرأه الوكلاء. الأتمتة تبدأ العمل من الأحداث وتُبلغ بالنتائج.
That one sentence is the whole model. Everything that links an agent to the world outside Agentic Workforce ME is one of four integration types, and every type is summarised on the console’s Integrations page (route /tools; the page takes that name in the next console release). The words on these pages are the words the console, the API reference and the product website share — nothing has to be learned twice.
A connector is how Agentic Workforce ME reaches one of your systems — its transport, its authentication and the tools it exposes.
الموصّل هو الطريقة التي يصل بها Agentic Workforce ME إلى أحد أنظمتك: وسيلة النقل والمصادقة والأدوات التي يوفّرها.
Example
An accounts-payable MCP server with invoice.get and payment.record, one connection ("AP service key"), granted to the AP Validator agent, payment.record behind an approval policy.
A channel is where people reach an agent — a web widget, WhatsApp, email, Telegram, Teams, Slack, SMS or the Workspace.
القناة هي حيث يصل الناس إلى الوكيل: ودجت ويب، واتساب، البريد الإلكتروني، تيليجرام، تيمز، سلاك، الرسائل النصية أو مساحة العمل.
Example
A web widget on the citizen portal (embed key hive_pk_…, origin allow-list) and a WhatsApp Cloud API number, both routed to the same published agent.
API
/v1/embed-keys/v1/channels
Console: Channels (also summarised under Integrations → Channels)Channels
Knowledge sources / مصادر المعرفة
A knowledge source is a system agents read rather than act on: its content is indexed into a knowledge base and searched with citations, with source permissions preserved.
مصدر المعرفة هو نظام يقرأه الوكلاء بدل أن يتصرّفوا فيه: يُفهرَس محتواه في قاعدة معرفة ويُبحث فيه مع الاستشهادات، مع الحفاظ على صلاحيات المصدر.
Example
A SharePoint site and a public website indexed into the "Procurement policy" knowledge base; agents cite it through kb.search.
Console: Knowledge → knowledge base → Knowledge sourcesKnowledge sources
Automation / الأتمتة
The event seam: triggers start runs into Agentic Workforce ME, webhooks notify your systems out of Agentic Workforce ME.
المشغّلات والويب هوك الصادر
Example
An invoice.received trigger (kind: webhook) fired by your ERP with an HMAC signature; a run.completed outbound webhook back to the ERP when the agent finishes.
Tools are not a fifth type: they are what a connector exposes and what a grant allows an agent to do — the unit of permission, approval and audit. They are documented with connectors on Connectors, tools & grants.
The same four layers the product website draws: people arrive through channels, agents on your org tree do the work, everything important passes the trust layer, and the systems, knowledge and keys sit at the bottom — searched, granted and unlocked only at the moment of use. Integration types map onto the first and the last layer; the trust layer is what makes them safe.
Layer 1 · Message inChannels — where people reach the workforce
Web widget, WhatsApp, email, Telegram, the Workspace. Every door opens the same kind of run — same agent, same tools, same approvals, same trail. Beside them, triggers start runs from events and schedules instead of a person typing.
Layer 2 · Org tree + written rolesAgents — who does the work
Published agent manifests on your tenant → department → section → unit tree. An agent’s effective tools are the tools its grants allow, and nothing more.
Layer 3 · The trust layerTool Gateway — how work is controlled
One door for every tool call: schema validation, the grant check, the approval policy check, then the audited execution with the connection’s credentials decrypted only for that call. Runs, steps and outbound webhooks are recorded here.
Layer 4 · Knowledge, tools and keysConnectors & knowledge sources — where tools and knowledge live
Connectors (MCP servers, databases, remote agents, HTTP APIs) expose the tools agents act with; knowledge sources (uploads, SharePoint, Confluence, Google Drive, S3, websites) are indexed into knowledge bases agents read with kb.search. The model never holds a credential.
A knowledge source is a system agents read rather than act on: its content is indexed into a knowledge base and searched with citations, with source permissions preserved.
مصدر المعرفة هو نظام يقرأه الوكلاء بدل أن يتصرّفوا فيه: يُفهرَس محتواه في قاعدة معرفة ويُبحث فيه مع الاستشهادات، مع الحفاظ على صلاحيات المصدر.
Default-deny grants. No tool is callable until a grant allows it for a specific agent or org node; the most specific matching grant decides and no match means deny; the manifest can only narrow, never widen. Effective tools = manifest ∩ grants. Read more →
Human approval in the runtime. An approval policy (or a manifest rule) interrupts the run itself — a checkpointed interrupt() — so nothing executes while a named person decides. Database writes are force-gated. Read more →
One audited gateway. Every call passes the Tool Gateway: schema validation, grant check, approval check, execution with credentials decrypted only at that moment, redacted run step, audit row. Read more →
Today: agents consume MCP servers — yours, over Streamable HTTP, with the tools they expose granted per agent (host an MCP server). MCP is a transport one connector kind uses, not a category of its own: a database connector, a remote agent and an HTTP API sit beside it and pass the same gateway.
Next: Agentic Workforce ME as an MCP server, so other agents and IDEs can call your published agents as tools. Not available yet — it is a roadmap item, and it is listed as one below.
Everything in the first list is in production. Everything in the second carries the label Next wherever it appears — in the console, on the website and on these pages — and is never described as available.
The next console release adds a small API under /v1/integrations/* so tooling can see what the Integrations hub sees. Every row below is coming soon — shipping in the next console release — and is listed so you can plan, not so you can call it yet. The phase column is the console’s release order: Now-A lands first (catalog and health checks), Now-B follows (hub payload, attach, connected systems). Every existing endpoint in the REST reference is unchanged.
Method
Path
Phase · status
Purpose
GET
/v1/integrations/catalog
Now-AComing soon
Starter catalog: ready-to-connect connector templates, with registered when the tenant already has one.
POST
/v1/integrations/health/:target_kind/:id/check
Now-AComing soon
On-demand health probe for an MCP server, connection, database connector or remote agent (admin, rate-limited).
GET
/v1/integrations/overview
Now-BComing soon
The hub payload: connectors with health and counts, knowledge sources; channels and automation for admins.
POST
/v1/integrations/attach
Now-BComing soon
One call for wizard step 4: grants + approval policies + draft-manifest merge, optional per-agent publish.
GET
/v1/agents/:id/connected-systems
Now-BComing soon
Per-agent view: each declared tool with Granted / Approval, plus channels, knowledge and triggers.
The console, the website and this portal are checked against the same frozen glossary. If a word here differs from what you see in the console, the console is one release behind.
Retired
Replace with
Where it still lives (allowed)
"Communication gateways"
Channels / القنوات
nowhere in prose
"Connector" for a knowledge source
Knowledge source / مصدر معرفة
API path /v1/knowledge-bases/:id/connectors, table kb_connectors
"Database connectors are a fourth tool source"
"Databases are one connector kind"
nowhere
"MySQL" as a supported database
Postgres, SQL Server, Oracle (MySQL = Next)
nowhere as "true today"
"Tools" as the page/hub name
Integrations / التكاملات
route /tools
"Tool grants" → AR "منح الأدوات" / "المنح"
تصاريح الأدوات / التصاريح
nowhere in new prose — existing Arabic strings in the console and website are being updated
