Most teams start with one workflow — usually the task that annoys them most — see the first runs land, and then expand. This article walks the whole path: connect a tool, build the workflow, test it, and put it live. Plan for 15–30 minutes.
1. Connect a tool
Workflows act on the tools you already use, so the first step is giving Kommit access to one:
- —Open Integrations in the dashboard sidebar.
- —Pick the tool and click Connect. Most connections are a standard OAuth consent screen — you approve, and the connection shows up as ready.
- —The connection belongs to your organization, so any workflow your team builds can use it. See [#supported-ingestion-sources] for what's available today — the list only shows connectors that actually ship.
2. Build the workflow
- —Go to Workflows → New. Start from a template that matches your task (lead triage, invoice reminders, support replies, reporting) or from a blank canvas.
- —Each node on the canvas is one step: read from a connected tool, transform or draft something, write back, or wait for a person. Connect the steps in the order the work actually happens.
- —Put a person on the steps that matter. Add an approval step before anything you wouldn't want sent or changed without a human look — the workflow pauses there and continues when someone approves.
3. Test it
Run the workflow from the builder with a test input. You'll see each step execute in order, what data went in and out of it, and where it stopped for approval. Fix, re-run, repeat until a run looks the way you'd have done it by hand.
4. Put it live
Deploy the workflow. From then on every run — triggered manually or by an event — is logged end to end under Runs, so you can always answer what ran, when, and what it did. Approval requests land with the teammates you assigned.
Common pitfalls
- —Don't wire in data you don't need. A workflow should touch the fields the task requires, nothing more — it keeps the run log clean and your GDPR story simple (see [#gdpr-support]).
- —Don't skip the approval step to "save time." The first weeks of a new workflow are exactly when you want a person confirming the important sends. Loosen it once you trust the runs.
- —Start with one workflow, not five. The teams that stick with automation are the ones that got a single task reliably off someone's plate first.