The system keeps working when you stop
Rules, templates and workflows take over your follow-up.
- 22:14Appointment confirmation sent to R. van Dijk
- 23:02Reminder scheduled: quote 2481 not viewed yet
- 06:30Daily brief prepared for the whole team
- 07:45Yesterday's work order approved and filed
- 08:01New lead assigned to the colleague with the lightest workload
What does stipt automate? stipt automates follow-up with if-this-then-that rules: pick a trigger (quote viewed, appointment moved, status unchanged too long) and let stipt send a template, create a task or change a status. For those who want more there is a visual workflow builder with webhooks, code and HTTP to external systems.
Templates for everything you send more than once. Emails with variables from the file, WhatsApp templates approved by Meta from within stipt, and tasks ready in one click.
Dear {first_name}, see you then! Reschedule via {plan_link}.
Tasks have templates too: one click and the whole job is laid out, with subtasks and deadlines.
The system spots an unhappy customer before you do. dot estimates how happy each customer is. Your rule decides what happens next.
Two breakdowns in quick succession, no follow-up yet
Below 6: status to Needs attention
Anything can set something in motion. More than thirty events from your own system as a starting point.
Automate in plain language. You do not build rules in a settings screen: you just say what should happen. stipt puts it on the canvas, you confirm, and it runs.
“If a quote is open for a week, send the customer a reminder.”
One sentence in the chat, and the rule is on the canvas.
Quote open for 7 days
dot writes a reminder in your tone
Sent after your approval
Automatic is never invisible. Every run sits in the log, step by step, and can be paused with one click if needed.
- Trigger: quote accepted
- Task created from template
- Message waiting for your approval
The log also explains why a rule did not fire.
Connect stipt to everything else. Webhooks in and out, HTTP with OAuth, a code node for custom logic, and a public API with docs. Whatever comes in through the API triggers the same automations.
- Public API with docs
- API keys with request log
- Webhooks in and out
- Code node for custom logic
- HTTP with OAuth
- Gmail and Microsoft 365
- Run history with replay
Frequently asked questions
Do I need technical knowledge for automation in stipt?
No. You build rules in a wizard with dropdowns, or you tell dot in plain language what you want and confirm the proposal. The visual builder with code and webhooks is there if you want more, but it is not needed for day-to-day work.
Can a rule accidentally send too many messages?
There are guardrails for that. A rule fires at most once per day for the same subject by default, adjustable per rule. Rules that keep calling each other in a chain are stopped automatically, and every run shows up in the log.
Does automation also work for leads that come in through the API?
Yes. A record created or moved to a new status through the API goes through exactly the same rules as a manual change. A lead from an external integration gets the same follow-up as a lead a colleague types in.
Can I connect stipt to other software?
Yes. The workflow builder receives webhooks from other systems and makes HTTP requests to any API. stipt also has outgoing webhooks on status changes and a public REST API with interactive documentation on the developers page.
What happens when a workflow run fails?
Every run is kept in the history, with the input and output of each step. Failed runs can be run again. Incoming webhooks are stored first and processed after, so an error never loses the event: you can replay it.