Workflows, integrations, AI — one system that takes routine work off your plate.
Approvals run with deadlines and escalation, events reach Microsoft Teams as interactive cards or flow into your systems via signed webhooks, and the AI assistant makes the first move — always within real user permissions, never without your consent. Instead of copy-and-paste and silent automation: one data foundation on which automation stays verifiable.
Three building blocks, one principle: less manual work
Each building block removes a different kind of routine from your team — together they automate everyday project work without you giving up control. Every card leads to the full detail page.
How it all connects
Events are the connecting backbone: whatever happens in your projects starts processes, informs your systems and gives the AI its context — on one data foundation.
An event occurs
A risk escalates, a request comes in: the matching workflow starts automatically — filtered by your conditions, with a deadline and a defined escalation.
Go to workflow automationBeyond system boundaries
The same event appears as an interactive card in Microsoft Teams or flows into your third-party systems via signed webhooks and the REST API.
Go to integrationsAI makes the first move
Ace summarizes, answers status questions and drafts records — every writing action only after your confirmation, within your permissions.
Go to the AI assistantBack in everyday project work
The result: completed tasks, up-to-date reports and a team with time for what matters — right inside your project management.
Go to project managementThe automation itself stays traceable too: automatic process starts run under a dedicated system actor, every webhook delivery is logged, every AI usage appears in the token audit — and a tenant-wide kill switch stops the AI entirely if in doubt.
The right entry point for every role
Governance, IT and everyday project work ask different questions of automation — every role gets its answer.
PMO & governance
Standardized approvals with deadlines and escalation, complete audit trails and AI usage with budgets and roles — automation that stands up to scrutiny.
IT & system owners
Open standards instead of a black box: an open REST API, signed webhooks, CMIS and S3 — and processes whose automation does not end at the system boundary.
Project leads & teams
Less status hunting, less copy-and-paste: answers in seconds, tasks completed right in Teams, standard processes from the template gallery.
Frequently asked questions about automation & AI in WORKSPACE.PM
The answers to the questions that matter most before rollout.
No. Processes are built in the visual editor via drag-and-drop — with twelve node types, understandable for business and IT alike, plus a template gallery instead of a blank canvas. Administration deliberately sits with your administrators or process owners: that keeps whatever runs automatically in the system's name under control.
No — control is built in. Every step has a deadline, a reminder and a defined escalation, decision permissions are validated server-side, every process instance shows its step timeline, and every change to a process definition is recorded in the version history. The AI assistant only ever acts after your confirmation — up to a tenant-wide kill switch.
Yes, that is the core principle: files can land in your own SharePoint, a CMIS-capable DMS or S3-compatible storage, events flow into your systems via signed webhooks or the REST API, and further tools connect via Zapier or the MCP endpoint. Before anything goes live, a connection check with a write test validates your configuration.
You decide which model does the work: with your own key for Claude, OpenAI, Gemini, DeepSeek or Mistral — or with locally operated models in your own infrastructure. Alternatively, managed mode starts on credits without your own AI contract. In every case the assistant only answers within the permissions of the person asking, and usage is recorded per user in the token audit.
Yes. Many teams start with a template from the gallery or the Trello import and add integrations and AI later. Because everything builds on the same events, the blocks interlock immediately: the same event that starts a workflow internally can trigger a Teams card — and the assistant knows about it on request.
Let the routine run itself — free for 14 days
Workflow engine, interfaces and AI assistant at full depth, no credit card. Activate a first template, connect Teams, ask Ace — within minutes.