Skip to content
ThinkWork ThinkWork

Triggers and Channels

Triggers and channels are how work enters a Space. A user can start a chat thread, an email can arrive at the Space address, a schedule can wake the agent, a webhook can receive an external event, or an integration can route provider work into the Space.

The result is still a Thread. The Space supplies the local context and policy for that thread.

Common entry points

Section titled “Common entry points”
Entry pointWhat happens
ChatA user starts or resumes a thread in a selected Space
EmailCold-contact email from a registered tenant user to the Space address creates or reopens an email thread when enabled
ScheduleA recurring or one-time schedule wakes work in the Space
WebhookAn external POST creates a fresh Space thread, seeds a system trigger message, and wakes work in the Space
IntegrationA connector routes Slack, GitHub, or other provider events into the selected Space

Each entry point keeps channel metadata so operators can tell where the work came from.

Space email

Section titled “Space email”

Space cold-contact email uses the current Space address format:

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

Cold-contact email is accepted only when the Space email trigger is enabled and the sender email matches a registered tenant user. Disabled or deleted Email triggers do not accept cold-contact email. Private Spaces additionally require that user to be a Space member. Archived Spaces do not accept new cold-contact email.

Token-bearing replies to agent-initiated email are different. They continue an existing thread and can work even when cold-contact email is disabled or deleted.

Trigger lifecycle

Section titled “Trigger lifecycle”

Triggers are local to the Space they are configured for. A schedule or webhook attached to a Space wakes the tenant platform agent with that Space’s workspace, knowledge, tools, and policy.

Space webhooks are machine triggers for the Space, not impersonated users. A valid webhook token authorizes the configured webhook to create a fresh Space thread, write a readable system trigger message, and pass the full structured payload to the agent. Private Space membership still controls human access and configuration, but the webhook runtime uses explicit service-trigger authority after the webhook has passed token, enabled, tenant, and Space checks.

If the Space has an automatic thread-start workflow configured, webhook-created threads start that workflow before the platform agent is invoked. If workflow setup fails after the thread exists, the webhook response is accepted with a warning and operators can inspect the warning in webhook delivery history.

For the operator UI, see Admin - Space Triggers.

Section titled “Related pages”