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

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.

  1. Open Automations and the ⋯ menu. Select Move to… on the automation. For a cloud automation, only the workspace owner sees it.
  2. Choose where it goes. The list has workspaces on this computer and cloud workspaces you own. Select Continue in chat.
  3. 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.
  4. 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.
  5. 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

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

TriggerStarts whenThe run receives
ScheduleThe time you set arrivesThe time the run was due
WebhookAnother system sends a request to the task's addressThe body of that request
Ticket EventsA ticket arrives, or a new message or internal message is addedThe ticket and the new message. Later messages on the same ticket continue the same conversation.
From Chat & TicketSomeone you allow asks for the task in chat or from a ticketA summary of their request
New knowledge documentA document is added to the knowledge libraryThe 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"}'
⚠️

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