Automation– Workflows Without Coding
Link ERP, CRM, chat and support with visual workflows. You write no code, but you keep full control of your data.
Request a demoAt a glance
- Visual workflow builder
- 400+ integrations
- Event triggers (webhooks)
- Scheduled flows
- Visual low-code editor
- Self-hosted
Features at a glance
Automate your processes with little code, from new CRM leads to incident alerts. It works for small tasks and for long chains of events. It all runs on your own servers.
Visual Workflows
Build workflows by drag and drop in the editor. Branches, loops and error handling are built in. The source code is open to view (fair code).
Event Triggers
A workflow starts as soon as an event comes in. It can come from a web call (webhook), a queue or the message bus.
Scheduled Tasks
Recurring tasks run on a fixed schedule, for example every Monday at eight. Use it for reports, sync jobs or batch work.
Connect Other Programs
A workflow can call any REST API. You control the headers, auth and payload. If a call fails, it tries again.
Custom Functions
For special cases, write short JavaScript functions. They cover what no built-in node can handle. This lets you shape data and rules exactly.
Credential Vault
All keys and credentials for other services are stored encrypted in one place. You can also load them from a vault at runtime.
Technology & integration
The workflows sit at the heart of the automation layer. A message bus, a gateway and a rule router come with them. They pass events from every service on to the workflows. So the whole platform reacts reliably to events.
- • Runs on your own servers
- • Message bus for events
- • Rule router that forwards events
- • Central login (single sign-on via OIDC)
- • Its own database
- • Runs in containers or on Kubernetes
Technical foundation
SecTepe.Comm uses proven open-source building blocks. n8n runs the workflows, and NATS JetStream forms the message bus. PostgreSQL is the database, OpenBao the vault for credentials. It all runs with Docker or on Kubernetes.
Your benefits
- Automate processes without tying up developers
- No vendor lock-in
- Connect new services in days, not months
- Event-driven architecture
- Data stays on your infrastructure
- Low-cost alternative to Zapier & Make
How Comm automation works in practice
Automation in SecTepe.Comm has two layers. A rule router handles common event flows with short rules. The workflow engine takes over when a process needs many steps or its own logic. Both work with events from the message bus of the platform.
How the pieces fit together
- A gateway accepts web calls (webhooks). They come from sources such as the SIEM, the mail server, chat and the workflows. It turns them into one event format and puts them on the message bus.
- The rule router checks each event against its rules. A rule can write a log entry, call a web address or send a new event.
- The workflow engine runs the longer processes. It receives events and reports results back to the bus.
- Events also reach the notification center in the web interface. Each user only sees events meant for them, their group or their role.
Typical scenarios
- New staff: A new user in the central sign-in starts the onboarding workflow. The IT team gets a notice.
- Security alerts: Serious alerts from the SIEM go to a chat room.
- Renewing credentials: Ready-made workflows renew key credentials for mail and database every three months. The new values go into the vault.
- Data subject requests: One workflow gathers the data of a person from mail, file storage and the password manager. It bundles the export and files it in the document archive.
Operation and control
The workflow engine runs on your own servers and has its own database. Central sign-in protects the editor. Telemetry, version checks and the template gallery are switched off. Stored credentials are encrypted with a key you set yourself.
The shipped workflows are imported for you. The rule router only calls addresses on an allow list. If that list is empty, no call goes out. Failed calls wait in a separate queue. Your IT team can check them there and send them again later.
Common questions
Can I test a rule before it goes live? Yes. The rule router has a test mode. You send in an event and see which rules match and what they would do. Nothing is executed.
Can I change the built-in rules? Yes. Put your own rules in a separate folder. A rule with the same ID replaces the default one. The router reloads all rules while it keeps running.
Do tenants stay apart? Yes. With several tenants, each event carries the tenant name. The router reads the tenant only from there. A rule cannot send events to another tenant.
Ready for automation?
Let's find the processes that pay off most. Then we turn them into live automations you can measure.
How we work with you
We want to work with you for the long run, not just deliver once. Our way of working has four steps. So you always know what comes next, who does what and what you get.
1. Free initial conversation
We learn where you stand and what you want. In 30 to 45 minutes we check if we are a good fit. We show you options and answer your questions. There is no obligation.
2. Current state review
We check where you stand today: tech, processes and rules. You get a list of strengths and gaps, sorted by urgency. Our offer is based on it.
3. Delivery with a dedicated lead
An experienced lead guides you through the project. You get clear goals, an open plan for time and cost, and a status every week. All results are written down and belong to you.
4. Running and reviewing
After the project we stay with you. We run systems for you, check them at set times and keep track of open tasks. When new threats or new rules come up, we get in touch.
Common questions
We hear these questions most often in a first call. For anything else, write to hello@sectepe.de or give us a call.
- How do we start working with SecTepe?
- Every project starts with a free first call. Then you get an offer with scope, timeline and result. If you like, we start small with a pilot. That way you get to know us before the real work starts.
- What company sizes and sectors do you support?
- We work for small and mid-sized firms, for parts of large groups and for operators of critical infrastructure (KRITIS). Often that means industry, trades, health, banks, energy and public bodies. Our focus is mid-sized firms in Germany, Austria and Switzerland.
- Do you work on site, remotely or hybrid?
- Both. Reviews, advice and most services run remotely from German data centers. For workshops, training and emergencies we come to you, mainly in North Rhine-Westphalia, the Rhineland and the Ruhr area. We travel further when needed.
- Which standards and regulations do you cover?
- We work to ISO 27001:2022, BSI IT-Grundschutz, TISAX, B3S KRITIS, NIS2 and DORA, plus sector-specific rules. Our methods build on known frameworks such as NIST CSF, MITRE ATT&CK, OWASP and OSSTMM. We combine them to fit each project.
- How do you protect the confidentiality of my data?
- By contract and by technology. Before every project, both sides sign a non-disclosure agreement. Your data stays in German data centers. Every access needs a second login factor and is checked one by one. Our whole team is bound to secrecy by contract and under the GDPR.