Skip to content
ThinkWork ThinkWork

Triggers

Triggers is the Space Studio tab for work that starts or wakes inside a Space. It shows Schedule, Webhook, and Email trigger rows in one table.

Route: /spaces/:spaceId/triggers

Trigger types

Section titled “Trigger types”
TypePurpose
ScheduleRecurring or one-time work in the Space
WebhookExternal POSTs that create fresh Space threads and wake work in the Space
EmailCold-contact inbound email to the Space address

The table shows each trigger’s name, type, description, status, and last run time when available.

Space webhooks

Section titled “Space webhooks”

A Webhook trigger exposes the generic webhook endpoint for the Space. Each accepted POST creates a fresh thread in that Space and inserts a readable system trigger message before the tenant platform agent is invoked. The full webhook payload remains available to the agent as structured context without dumping raw JSON into the opening transcript message.

Webhook-created threads also participate in the Space’s automatic thread-start workflow when one is configured. A Customer Space with Customer Onboarding enabled, for example, receives the onboarding goal and checklist on the webhook-created thread.

If ThinkWork creates the thread but cannot finish workflow initialization, the webhook returns an accepted-with-warning response instead of a retry-inducing failure. Operators can open the webhook delivery history from Admin Webhooks to see the created thread id, HTTP status, and warning message.

Add menu

Section titled “Add menu”

Use the Add menu in the header:

  • Schedule opens the schedule form.
  • Webhook opens the webhook form.
  • Email creates or recreates the Space email trigger.

Email is backed by a Space setting, not a separate backend entity. When deleted, it does not appear as a table row. When enabled or disabled, it appears as a single Email row with a copyable Space address. Clicking that row opens the management dialog for changing the address prefix, disabling or re-enabling the trigger, or deleting the trigger.

Space email address

Section titled “Space email address”

Space cold-contact email uses:

<space-slug>@<tenant-slug>.thinkwork.ai

Changing the prefix changes the Space slug-backed address and automatically preserves the Space source files under the new slug prefix. It does not require per-address SES rule changes.

Cold-contact delivery requires the Email trigger to be enabled and the sender email to match a registered tenant user. Private Spaces also require that user to be a Space member. Disabled or deleted Email triggers do not accept cold-contact email. Token-bearing replies to agent-initiated emails are not the same as cold-contact email and can continue existing conversations even when cold-contact email is disabled or deleted.

Section titled “Related pages”