Kylon for AI workflow automation

Workflow automation that reads the case before it acts.

Kylon is a company harness where agents join your team, understand your business context, and execute real work across the tools you already use.

Get started
The work you want automated
What a rule does
What an agent does
A lead fills in the form
The fields are copied into the CRM and the same template goes out to everyone
It researches the company, writes the CRM note for this account and drafts a reply a person sends, or does not
The weekly report is due
The same spreadsheet is rebuilt from the same four tools, by hand or by a scheduled export
A scheduled workflow pulls the four sources, writes the summary, and posts it in the room where the team already discusses it
A record changes in the tracker
The trigger fires the action it was configured with, whatever the record says
It reads what actually changed and decides what this case needs, inside the permissions you set
Something the flow never anticipated
The run fails, or completes the wrong step quietly
It says so in the room and leaves the decision to a person

What an agent needs before it can automate anything

  • The thread. It reads the room the work is already discussed in, not a form you fill in first.
  • The records. Trackers and tables live in the workspace, so the agent reads and writes them without an export.
  • The tools. 3,000+ services connect natively, from Gmail and Slack to Salesforce, HubSpot, Jira and GitHub.
  • Memory. Last month's decision is still there, so nothing has to be re-explained each run.
  • Permissions. Agents only see and touch what you allow, and sensitive actions wait for approval.

Where the result goes

CRM
Salesforce · HubSpot · Pipedrive · Close · Dynamics 365
Tasks
Linear · Jira · Asana · Trello · ClickUp · monday.com
Docs
Notion · Google Docs · Google Sheets · Confluence
Comms
Slack · Gmail · Outlook · Microsoft Teams

How it works

  1. 01

    Say what should happen, in plain language, in the room where that work already lives.

  2. 02

    Connect the tools it touches and point it at the records it depends on. Nothing has to move.

  3. 03

    Keep it as a workflow when it should repeat: on a schedule, a webhook, or a record change.

What Kylon does not do

This is not a canvas of boxes and arrows, and it is not the better tool for every job. If the same trigger should always run the same steps, a rule-based automation is simpler and more predictable than an agent. Kylon is for the part where the steps depend on the case and someone has to look at the result.

Questions people ask

How is this different from Zapier, Make or n8n?
Those tools run a sequence you define in advance: a trigger, then the same actions every time. A Kylon agent reads the context of the specific case first, decides what that case needs, and hands the result back for review. Keep the automations that already work. Put an agent on the part that needs someone to read the situation before acting.
Does it run on a schedule, or only when someone asks?
Both. A person can ask in the room, and a workflow can start on a schedule, a webhook or a record change. Runs keep their history, so you can see what happened and why.
Do I have to build the workflow before I get anything out of it?
No. You start by asking for the work itself. When a piece of it should repeat, you save that as a workflow. There is no build phase to get through first, and no code or configuration files.
What stops an agent doing something it should not?
Scoped permissions: agents only see and touch what you allow. Sensitive actions wait for approval before they execute, and admins, members and agents each get distinct permission tiers.

Keep reading

Most work is not a fixed sequence.

Automate the part that repeats, and let an agent handle the part that depends on the case. A person still approves what leaves the room.

Get started