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.

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
How it works

Skills that act. Workflows that run them.

Install ready-made skills or write your own, then let events kick off workflows that use them, all inside a sandbox you control.

If this happens, do that. Workflows start from an event, then branch, wait and act, with your skills as steps.

Refund requests
v4 · LiveWhenLabel added: refundIfNeeds a person?ThenAssign to ReturnsRun skillStart a return
YesNo
Less manual work%for support teams, once routine conversations resolve end to end.

Skill Sets, ready made. Install a set, add your key, and your agent can use it.

Shopify ordersInstallCalendar bookingHubSpot contacts

Two kinds of skill. Look things up safely, or create, update and book.

Search reads. Execute acts.

One trigger, many paths. Start from inbox events or any incoming webhook.

New conversationResolvedWebhook receivedAssigned

Plain language first. Code when you need it. Describe when to use it, then write the handler.

Use this whenA customer asks where their order is.
InorderIdOutstatus, tracking
look-up-order.jsChecking
1export default async ({ input }) => {
2 const order = await lookUp(input.orderId)
3 return {
4 status: order.status,
5 tracking: order.trackingUrl,
6 }
7}

On a short leash. Skills run in a sandbox, and keys stay masked secrets.

STORE_API_KEYshpat_9c41e07b4f2a
read_ordersSandboxed
Revoked when you uninstall the 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.
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.