Product

Automation

Chat is one way in. The same agents can run a flow, a repeating prompt, or a webhook without anyone sitting in the thread. History is still there when you come back.

From capability to everyday work

Automation, in practice.

Chat is one way in. The same agents can run a flow, a repeating prompt, or a webhook without anyone sitting in the thread. History is still there when you come back.

Use it for
Work with a known sequence that the team needs to repeat reliably.
Start with
Choose a trigger, connect the required accounts, configure the steps, and test a manual run.
Read the setup guide
Illustrative workflow Sample data
The request

“When a new support issue arrives, classify it and post a team update.”

  1. An event from the connected tool starts the flow.

  2. Run the configured classification and routing steps.

  3. Post the result and inspect the step history.

Support triage flow

Example output
Trigger
New issue event
Classify
Identify the issue category
Notify
Post the update to the selected destination

Flow builder

Connect steps and decisions

Flows are visual workflows: connected steps that call integrations, run AI, branch, loop, or call HTTP. Use them when the work should happen even if nobody is sitting in a chat.

Build from a runbook you already do by hand. Prefer an existing connection over a one-off HTTP call. Keep secrets in Settings, not hard-coded on a node.

Schedules

Run recurring prompts and flows

A schedule is a prompt that starts or continues an agent on a cadence, or a flow run with the inputs that flow expects. Enable, disable, and inspect history from the same place.

Disabled schedules keep their definition so you can turn them back on. Recurring work does not have to live in anyone’s calendar.

Event triggers

Start from a webhook or tool event

A flow can start from a webhook or an event in a connected tool, not only from a person clicking Run. The path is the same: trigger, run, report.

If you need a back-and-forth with a person in the loop, start an agent or mention @kluff in a topic. Flows are for paths you could draw on a whiteboard and run again tomorrow.

Before you try it

Questions for your evaluation.

Work with a known sequence that the team needs to repeat reliably.

Choose a trigger, connect the required accounts, configure the steps, and test a manual run.

Inspect the run history. Scheduled flows run the current draft, so review edits before the next scheduled run.

Unlimited inference.
Company memory.

Connect your tools, ask your first question in a project, and watch memory, spend, and visibility stay in one place—not scattered across personal chats.

$15 / user · Unlimited AI
Q4 launch› Launch dashboard
Sara Castillo

@kluff build a launch dashboard from HubSpot and the Q4 budget sheet. Refresh it every morning.

Kluff

Done. Signups come from HubSpot, spend from the Q4 budget sheet. It refreshes at 7:00 AM.

v2 adds the channel split you asked for.

Maya Ruiz

Can we flag any channel over $40 per trial?

Kluff

Added. Paid social is flagged.

Q4 launch dashboard
Q4 launchHubSpot + Q4 budget sheet · refreshed 7:00 AM
Live
Signups1,284+18% vs last week
Trials started31224% of signups
Spend$8,420of $12,000 budget
Daily signups
MonTueWedThuFriSatSunMonTueWed
Send the renewal to Harbor Foods?

It sends from your Gmail, as you, with the draft attached. Nothing else leaves the project.

SENDGmail · Dana Reyes, Harbor Foods purchasing
ATTACHGoogle Drive · Harbor renewal 2026.docx
Finance check done

Ana Chen confirmed net 45 at 9:18 AM. Your rule: every customer email waits for you.

Sent · logged to the project