A form submission becomes a contact and a message
WebhookHubSpot create_contactSlack send message
The form posts to the workflow's own URL. Kolap creates the contact and tells the channel.
Automate the work between your apps
on a schedule or a webhook.
Kolap is a visual workflow builder. Start a flow from a webhook, a cron schedule or by hand, pass the data through conditions and loops, call 14 service connectors, and read every run node by node.
- Early access, by conversation
- 32 nodes, 14 of them service connectors
The problem
The work that falls between your tools
A form comes in. Someone copies the contact into the CRM, opens a ticket and tells the team in chat. Each step takes a minute. Done by hand, the steps happen late, twice or not at all.
A bug report becomes an issue, once
WebhookIf/ElseLinear create_issueSlack send message
Only payloads that match your condition reach the tracker.
A morning digest of open tickets
CronZendesk list_ticketsLoopSlack send message
On a cron schedule Kolap lists the tickets and posts them where the team reads.
A customer message is routed by what it says
WebhookAI PromptSwitch/CaseZendesk create_ticket
The AI Prompt node classifies the text and a Switch sends it down the matching branch.
Four examples of what the nodes can be wired into. They are not templates you must start from.
How it works
From an empty canvas to a flow that runs itself
Four steps, and the last one is the one you will keep coming back to.
- Step 1
Store your tokens once
Put each API token in the secrets vault, encrypted at rest. Any node field can pull a stored secret in by name, so tokens stay out of the flow itself.
- Step 2
Build the flow on the canvas
Drag nodes from the palette, connect them and fill in a form panel for each step. Where a node needs structured input, there is a JSON field.
- Step 3
Choose what starts it
A webhook URL, a five-field cron expression or a manual run. Kolap only lets you switch a workflow on once it has an active trigger.
- Step 4
Read every run
Each run is stored node by node. Watch the log while it runs, then retry, replay or debug from the same screen.
What is in it
The parts, and the numbers behind them
What the engine does today, written as plainly as we can. The integrations page has the full list of operations.
- Triggers
- Webhook (any HTTP method to the workflow's URL), cron (minute, hour, day, month, weekday) and manual runs from the dashboard, the API or the CLI.
- Control flow
- If/Else and Switch/Case branch. Loop and Batch repeat over lists. Delay waits up to five minutes. Sub-Workflow calls another workflow. Error Handler catches a failing step.
- Data
- Transform, Variables, Date/Time, Map/Reduce and Crypto reshape the payload between steps.
- Connectors
- 14 services, an HTTP Request node for anything with an API, an email node and a Database Query node for your own PostgreSQL.
- AI
- An AI Prompt node that calls Anthropic or OpenAI, a generator that drafts a workflow from a description, and a diagnosis of a failed run.
- Runs
- Stored node by node, with a live log stream. Retry a failed run, replay a finished one, run in debug mode or cancel.
- Versions
- Publish a version of a workflow and roll back to it. Duplicate a workflow, or export and import it as JSON.
- Alerts
- Per workflow, send a failure to an email address, a Slack webhook or a webhook of your own.
- Limits you set
- Per workflow: a retention period of 1 to 365 days, a list of fields to redact from the logs, and a cap on executions per minute.
Integrations
14 services, plus HTTP for the rest
Each connector is a node with named operations. The names below are the services the nodes talk to.
- Slack
- GitHub
- Discord
- Notion
- Linear
- Shopify
- Salesforce
- WhatsApp Business
- HubSpot
- Zendesk
- Intercom
- Twilio
- Mailchimp
- Pipedrive
- HTTP Request
- PostgreSQL query
- Anthropic and OpenAI
Kolap is not affiliated with these services and none of them endorses it. Names are used only to say what a node connects to.
Runs
When a run breaks, you see which node broke it
Every run is stored step by step. Open a failed one, read what each node returned, then retry it, replay it or ask Kolap what went wrong.
Early access
Where Kolap fits, and where it stops
A good fit
- Technical teams who would rather click a flow together than maintain a script.
- Flows that start from a webhook or a schedule and touch the services listed above.
- People who want to read exactly what each step did when something fails.
- Anyone willing to tell the founder what is missing.
Not there yet
- Public registration. Access is arranged in a conversation.
- Your own code in a workflow. The Code node is switched off until an isolated executor exists.
- Wait for Approval. The node exists, but an approval cannot be answered yet.
- Sharing one workflow across a team. Each workflow belongs to one account.
Plans
Four plans, two numbers that differ
The catalogue limits executions per day and how many workflows you can hold. Nothing is sold on this website.
Free
To build and try workflows.
$0per month
50 executions per day5 workflows
The 50 runs and 5 workflows are the enforced limits. New accounts also carry a 14-day trial window, see the questions below.
Starter
For small teams running a few flows every day.
$19per month
500 executions per day25 workflows
Billed monthly in US dollars.
Pro
For heavier volume and a larger library of flows.
$79per month
5,000 executions per day100 workflows
Billed monthly in US dollars.
Enterprise
Limits and terms agreed one to one.
Custom
Price and limits are set in a conversation with the founder.
Questions
What people ask first
Not on the list? Ask the founder directly.
Can I sign up today?
Not yet. Kolap is in early access and there is no public registration. Message the founder on WhatsApp, say what you want to automate, and he replies with what is possible today.
What can start a workflow?
A webhook (any HTTP request sent to the workflow's own URL), a cron schedule (due schedules are checked once a minute), or a manual run from the dashboard, the API or the CLI. A workflow can only be switched on once it has an active trigger.
Which apps does it connect to?
14 service connectors: Slack, GitHub, Discord, Notion, Linear, Shopify, Salesforce, WhatsApp Business, HubSpot, Zendesk, Intercom, Twilio, Mailchimp and Pipedrive. An HTTP Request node reaches anything else with an HTTP API, and a Database Query node runs SQL against your own PostgreSQL. The AI Prompt node calls Anthropic or OpenAI.
Where are my API tokens kept?
In a secrets vault, encrypted with AES-256-GCM. Listing your secrets returns the name, the type and the last four characters, never the value.
What happens when a run fails?
The run is recorded node by node, so you can see which step failed and what it returned. You can retry a failed run, replay a finished one or run a workflow in debug mode. Per workflow you can also route a failure to an email address, a Slack webhook or a webhook of your own, and ask Kolap to diagnose the failed run.
Can I run my own code in a workflow?
Not today. The Code node is switched off until it can run in an isolated executor with no access to credentials. Transform, Variables, Date/Time and Map/Reduce cover the usual reshaping, and Map/Reduce expressions run in a restricted interpreter, not through eval.
How much data do you keep?
Payloads and run logs are stored so that you can read your runs. Per workflow you can set a retention period from 1 to 365 days, after which older runs are pruned once a day, and a list of fields that are redacted from the logs.
How is it priced?
The plan catalogue has Free, Starter and Pro, which differ in executions per day and in how many workflows you can hold, plus Enterprise, which is agreed individually. Nothing is sold through this website. Early access is arranged on WhatsApp.
Tell the founder what you want to automate.
Name the apps and what should start the flow. He replies on WhatsApp with what Kolap can do for it today.