Product · Skills & workflows

Teach it your business logic.

A chatbot answers questions. Give yours skills and it starts doing things — checking an order, booking a slot, calling your API — then wire those skills into workflows that run the moment an event lands.

Start free trial →Start with Skill Sets

No credit card required · 7-day free trial

“Where’s my order?”

A skill you teachLook up an order.

Find the customer’s order in your system and return its delivery status.

In conversationThe agent knows when to use it.
In a workflowAn event puts it to work.
Teach an action once. Put it to work.Illustrative example
Skill Sets

A marketplace of ready-made skills.

Find ready-made actions at skillsets.cloodot.com. Install a set, add your keys, and enable it for your agent. Test it in the playground, then keep it current with versioned updates.

A head start on the everyday.
Orders & returnsLook up an order. Start a return.
AppointmentsFind a time. Book the slot.
Your own systemConnect the logic that makes you, you.

Choose a set. Add your keys. Try it out.

Start with a skill that already knows the job.Illustrative example

Explore, install, enable

Three tabs — Installed, Explore, and My Skill Sets. Find a set that matches your stack, install it in a click, then turn it on for your persona.

Configured, not coded

Each set asks only for what it needs — an endpoint, an API key — then it is ready to use. No editor, no deploy step.

Versioned and tracked

Every set is versioned and updates in place, and skill usage is logged — so you can see which ones earn their keep and stay on recent releases.

Build your own

Plain language first. Code when you need it.

Describe when the agent should use your skill, define its inputs and outputs, then write the JavaScript that does the work. A live validator checks it before you ship.

Tell it when to help.

“Use this skill when a customer asks where their order is.”

Give it the logic.
Input   → order number
Handler → look up delivery
Output  → status + tracking link
A result the agent can explain.
Your business logic becomes something the agent can do.Illustrative example

Typed in, typed out

Parameters and responses are JSON Schema, so the agent extracts the right inputs and knows exactly what shape comes back.

Search or Execute

Search skills are read-only lookups that return data for the reply; Execute skills create, update, or book — the ones with side effects.

Dashboard, MCP, or API

Build in the visual editor with live validation, or manage Skill Sets programmatically from the Cloodot MCP server or the Developer API.

Workflows

If this happens, do that.

Start with an event: a new conversation, a label, or a webhook. Add conditions, delays, and actions. Your installed skills become steps in the same flow.

When this happensA conversation gets a refund label
Does it need a person?
YesAssign to Returns
NoRun your return skill

Conditions, delays, and actions — in one flow.

One event sets the right work in motion.Illustrative example

One trigger, many paths

Start on a new conversation, an assignment, a resolve, a star, a label change, or an incoming webhook — then branch True or False on conditions.

Actions that do the work

Send a message or WhatsApp template, assign to a teammate or a persona, add labels, auto-extract sentiment, or run an installed skill — they appear here too.

Versioned and testable

Test with sample data before you publish, watch every run in the log, and retry or roll back. Each save is a new version; only one is live at a time.

Safe by design

Powerful actions, on a short leash.

Every skill runs in an isolated sandbox with CPU and memory limits. You provide the configuration and secrets; required fields are checked before it can run.

Isolated execution
Your skill runs here.With defined CPU and memory limits.
Required fields checked Secrets kept separate

Connected on your terms.Using the credentials you provide.

Useful access. Clear boundaries.Illustrative example

Isolated execution

Each skill runs sandboxed with strict CPU and memory limits, and blocked APIs — eval, require, import, process — are rejected at validation.

Secrets kept separate

API keys and tokens arrive in input.secrets, masked in the UI, never folded into ordinary config a skill can log by accident.

Your keys, your rules

Use scoped credentials with the minimum permissions, prefer verified authors, and revoke keys the moment you uninstall a set.

Outcomes

Automation that earns its keep.

65%
Reduction in manual workload once skills and workflows absorb the repetitive operations.
37%
Average increase in revenue from digital channels once the agent can act, not just answer.
28pts
Boost in CSAT from faster, smarter first responses, measured across global deployments.

Cloodot’s AI now handles the flood of WhatsApp queries across our stores and routes only what needs a person to the team. Faster replies, more sales, fewer agents on the clock.

Akhil · MyG

Skills & workflows, answered.

What's the difference between a skill and a workflow?
A skill is an action the agent can take mid-conversation — check an order, book a slot, call your API — deciding for itself when to reach for it. A workflow is event-driven automation: it starts on a trigger like a new conversation or a label being added, then branches on conditions, waits with delays, and runs actions. Your installed skills show up inside workflows as actions too, so the two work together.
Do I have to write code?
Mostly no. Install a Skill Set from the marketplace, drop in your keys, and enable it — no editor. Build a workflow from a template and wire it visually, and hit any REST endpoint with the Simple API Request node without a line of code. Code is the escape hatch: skills are JavaScript handler functions when you need custom logic the marketplace doesn't cover.
How do skills reach my own systems?
Each skill is a handler function that receives the configuration and secrets you set at install, plus the parameters the agent extracted from the conversation. It calls your API, and returns a result the agent speaks back. Sensitive values arrive separately in input.secrets, never mixed into ordinary config. Workflows can also call any endpoint directly with the Simple API Request node.
Is it safe to give a skill my API keys?
Skills run in an isolated sandbox with strict CPU and memory limits, and blocked APIs like eval, require, and process are rejected before a skill can deploy. Secrets you enter are stored on Cloodot and passed to the skill code at runtime, so before installing a third-party Skill Set: review the author and look for the verified badge, use scoped credentials with the minimum permissions, and rotate or revoke them when you uninstall.
What can trigger a workflow?
A new conversation, an AI or human agent being assigned, a conversation opened, resolved, or starred, a label added or removed, or an incoming webhook from an external system. From the trigger you branch True/False on conditions like channel, labels, or message text, pause with delay nodes, and run actions — then test with sample data and watch every run in the log.
The rest of the platform

Better together.

01Unified inboxEvery channel, one tray.02AI agentIt thinks. It acts. It asks.03CopilotAI at your team’s elbow.05CampaignsBroadcasts that read like DMs.06AnalyticsKnow what your inbox knows.
See it on your own inbox

Try the whole thing, today.

Start free. Connect a channel, train an agent on your own content, and you'll have a working deployment in your inbox the same afternoon.

Start free trial →Sign in