Use an available event source
Event support depends on the connected provider and workspace configuration. Start from the event types offered in the product. A webhook or channel message is a source of input, not proof that its sender may authorize an external write.
Keep the event specific
Name the record type and the change that should start work. Avoid broad triggers that react to every update. Include a stable record identifier so the task can refer to the event it is handling.
Avoid loops and duplicate work
Write down which workflow owns each external action. If a task changes the same record that triggered it, exclude its own completed updates where the provider supports that distinction.
Test before relying on it
Use a sample event with a safe output and inspect the run. Check missing fields and repeated delivery. Confirm an external write before retrying a task whose result is uncertain.
Open the relevant screen
Use Event triggers in the active workspace. Sign in if needed. Check the workspace name before changing shared settings, connections, or billing.
If a control is unavailable, ask the workspace administrator or contact support. Include the screen, the action you tried, and the approximate time. Keep credentials and private customer material out of the request.