Triggers for cloud workspaces
A task in a cloud workspace can start on a schedule, when a webhook arrives, when a ticket changes, or when someone asks for it. This page explains each trigger and shows how to combine them with your connectors to run multi-step processes while your laptop is closed.
How a cloud task runs
- A task is instructions plus triggers. Each run starts a new conversation that sees only the saved instructions and the details of what started it. It cannot see the chat where you created the task.
- It runs as the workspace owner. The run uses the owner's skills, connectors and permissions, and the same approval rules as the owner's chats. A trigger never grants extra access.
- Outside content is data, not instructions. A ticket, webhook body or document is checked before the agent sees it, and the agent treats it as information to act on, not as orders.
- A run can wait for you. If it needs an approval or an answer, it pauses and shows under Needs attention, and you are emailed. A scheduled task does not start a new run while its previous run is still open, so answer the waiting run or choose Dismiss on it.
Set up a trigger
The quickest route is to ask. In a conversation with the workspace, say "Every weekday at 07:30 London time, do this", and the agent saves the task and confirms the schedule and what each run will do. You can also edit a task in Harriet Desktop under Automations, or on the web under Workflows with the Cloud automations tag selected.
The task editor shows the schedule first, then one row for each other trigger. A task can have several triggers at once. Press Run now at any time to start one by hand.
Move an automation to another workspace
In Harriet Desktop you can move an automation from one cloud workspace to another, from your computer to a cloud workspace, or the other way round. It also works between workspaces that use different engines, such as one on the Claude engine and one on the standard engine.
- Open Automations and the ⋯ menu. Select Move to… on the automation. For a cloud automation, only the workspace owner sees it.
- Choose where it goes. The list has workspaces on this computer and cloud workspaces you own. Select Continue in chat.
- Send the message. Harriet opens a new chat in that workspace with a message ready to send. It holds the original automation and tells the assistant how to rebuild it. Read it, add anything you want, then send it.
- Answer one question if something is missing. The assistant rebuilds the automation for that workspace and shows what it needs against what the workspace has: skills, connectors, files and the model. If anything is missing, it asks whether to fix it now, save the automation paused, or stop.
- Choose what happens to the original. When the new automation is running, Harriet pauses the original and shows a banner on the Automations page with Delete original and Keep it.
Harriet looks for the new automation about once a minute while Harriet Desktop is open, and again when you open Automations. Until then the original keeps running.
What changes on the way
- The schedule keeps its meaning. A schedule on your computer runs in your computer's time zone, and a cloud schedule has its own. The assistant converts between them and tells you what it did.
- The model is not copied. Model names differ between engines, so the new automation uses the destination workspace's default. The assistant tells you which model the original used.
- Files are checked, not guessed. If the automation refers to a file that is not in the new workspace, the assistant asks you to add it.
- Only the schedule moves to your computer. Triggers from tickets, chat, new documents and webhooks need a cloud workspace, and an automation on your computer runs only while Harriet Desktop is open.
Run history, saved versions and the flow diagram stay with the original. A webhook gets a new address in the new workspace, so update whatever calls the old one.
If the new automation is saved paused, for example because a connector is missing, the original keeps running. The banner offers Pause original for when you are ready.
The triggers
| Trigger | Starts when | The run receives |
|---|---|---|
| Schedule | The time you set arrives | The time the run was due |
| Webhook | Another system sends a request to the task's address | The body of that request |
| Ticket Events | A ticket arrives, or a new message or internal message is added | The ticket and the new message. Later messages on the same ticket continue the same conversation. |
| From Chat & Ticket | Someone you allow asks for the task in chat or from a ticket | A summary of their request |
| New knowledge document | A document is added to the knowledge library | The new document |
Ticket Events can be narrowed to Inboxes to watch, SLA tags to watch and Only messages matching a pattern. New knowledge document can be narrowed to Groups to match, and it fires when a document is created, not each time one is edited. For From Chat & Ticket, choose Allowed groups or Anyone in the organisation. Starting a task this way does not give the person access to your workspace. Turn on Require owner approval before running to review each request first, and give the task a short description so chat knows when to offer it.
Webhooks in detail
Turn on Enable webhook trigger and save. The Webhook URL then appears for you, the workspace owner, and nobody else. Treat it like a password: anyone who has it can start the task.
curl -X POST "<your-task-webhook-url>" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: deal-48213" \
-d '{"deal_id": "48213", "account": "Meridian Properties", "stage": "closed-won"}'
- The body can be any JSON, up to 1 MB. Text that is not JSON arrives as plain content.
- Acknowledgement status is the reply Harriet sends once the request is accepted:
200,202(the default) or204. The work then continues in the background, so the sender is not told how it turned out. - Retries. Have the sender include a stable
Idempotency-Key, such as the record's ID. The same key with the same body returns the same run. The same key with a different body is rejected. Without the header, every request starts a run.
An idempotency key stops duplicate runs, not duplicate actions in other systems. Write the instructions so the run checks for an existing record before it creates one.
Related pages
- Orchestrating processes in cloud workspaces shows triggers and connectors working together.
- Cloud workspaces covers sharing and the safety checks.
- Working in a shared workspace covers what collaborators can do with tasks.
- Port a workflow to cloud agents moves an existing workflow into a cloud task.