Workflows
Automate processes without writing code
A workflow is a sequence of steps that runs by itself once something triggers it. You assemble it on a canvas: a trigger on the left, the building blocks behind it. Included in every account, at no extra cost.
See pricingIncluded in the account price. Workflows are not an add-on and not a separate product. Every account can use them.
Triggers
Four ways to start a process
Every workflow has exactly one trigger. Which one it is decides when the process starts.
- 01
Manual
By click in the editor. The way to try things out before a process goes live.
- 02
Schedule
At fixed times, via a cron expression with a time zone. For the daily report or the weekly analysis.
- 03
Webhook
On an HTTP call to a dedicated address. This is how your existing systems start a process in skai.
- 04
Event from an integration
An email in Outlook, a mention in Teams, a new Jira ticket, an appointment in Google Calendar, a message in Telegram.
Building blocks
17 node types in five groups
Between the trigger and the result sit the nodes. You can chain and branch them freely; a sync node brings parallel paths back together.
-
AI
- Data extraction: pull name, date, amount and other fields out of a text
- AI agent: open-ended tasks across several steps and tool calls
- Transcription: audio to text
- Image generation from a prompt
- Classification into predefined categories
- Web search with a structured result
-
Control
- If/else: branch on a condition
- Switch: branch on fixed values
- Delay: a configured waiting time
- Sync: bring parallel paths back together
-
Files
- Parse file: read text from PDF, Word or Excel
- Create document: PDF, DOCX or Markdown from a template
- Share file: a time-limited download link, valid for 1 to 720 hours
-
Integrations
- Action: send an email, post a Teams message, create an appointment
- HTTP request to any interface
- URL scraping: read the content of a web page
- Message reply back into the channel that triggered the run
-
Code
- Python in a sandbox, for transformations no building block covers
Human in the loop
Nothing goes out without sign-off
Any action that has an effect outside skai can be tied to a confirmation. The run pauses at that point, the prepared values can be inspected and edited, and only a click triggers the action. Cancelling stops the workflow.
- 1
The run reaches the action and pauses.
- 2
The prepared parameters are ready for review and can be adjusted.
- 3
Confirm runs the action, cancel stops it.
In practice
What organizations build workflows for
-
Email triage
Read incoming mail from Outlook, classify it and answer standard cases directly.
-
Teams requests
Have an AI agent answer mentions in a channel, grounded in your own knowledge base.
-
Jira tickets
Generate a summary for every new ticket and post it as a comment.
-
Meeting preparation
Create a preparation document for every calendar entry.
-
Daily reports
Collect figures on a schedule, produce a document and send it out.
-
Your own systems
A webhook from your line-of-business application starts the processing in skai.
Operation
Who may do what, and what has run
-
Bound to a space
Every workflow belongs to exactly one space. Creating, editing or publishing it requires the "manage workflows" permission there.
-
Draft, published, paused
A draft does not fire. Only the published version runs automatically, and pausing takes it out of service temporarily.
-
Every run traceable
All past executions can be inspected, filtered by workflow, failures and pending sign-offs.
-
Export and import
A process can be saved as a file and recreated in another environment. Credentials are not included, for security reasons.
Workflows are included in the price
There is no surcharge and no tier that unlocks workflows. The account price covers the full feature set.
See pricing
Talk to us
With skai our goal is to make AI accessible and usable. Through layers of abstraction and proven methods, we ensure intuitive use and broad accessibility.
Stefan Henke
Management