Plugins declare capabilities, settings, connections, executors, and required grants before a workflow may call them.
Inside the module
See the working surface, step by step.
Use the controls to inspect the current application interface. Any arrow or step selection stops the automatic tour and leaves your chosen screenshot in place.
What it covers
Focused functions. Shared project truth.
The module has a clear operating boundary while remaining connected to the people, agents, automation, and evidence around it.
-
Catalogue and lifecycle
Browse installed and available plugins with source, trust, version, installation, and activation state.
-
Built-in integration paths
Use bundled Gmail, Microsoft 365 mail, and Docker integrations when the corresponding service and credentials are configured.
-
Manifest validation
Install packages from the catalogue or ZIP and validate declared capabilities before activation.
-
Least-privilege grants
Approve only the workspace, storage, project-structure, HTTP, OAuth, secret, or host-tool access an integration requires.
-
Typed workflow executors
Expose approved operations to workflows with predictable inputs, outputs, and side-effect boundaries.
-
Preview and evidence
Use deterministic previews for validation, require approval before external writes, and inspect lifecycle and execution logs.
How it connects
Integrations become governed workflow capabilities.
A plugin supplies a typed executor. A Workflow validates and routes the call. Project and Process context define why it runs, while approvals and logs preserve who authorized the external effect.