Limits of workflow conditions and triggers and how to work around them
Workflow conditions support positive AND logic only, and there is no trigger for when a Jira or Linear issue is linked to a thread. Both have workarounds.
What conditions cannot do
Conditions can check whether a thread has a given label, channel, priority or other attribute. They cannot:
- Use NOT logic, such as "does not have label".
- Use OR logic between condition groups.
- Check thread custom fields.
To exclude a subset of threads from a workflow, for example threads from a bot channel, label those threads and use a condition on that label instead.
Run a workflow when an issue is linked
There is no built-in trigger for a Jira or Linear issue being linked to a thread. Instead:
- Create a manual workflow, which agents run by hand from the thread.
- Add a Sidekick step that creates or links the issue and applies labels.
- Have your team run that workflow whenever they want an issue created, rather than linking manually and relying on a second automation.
This removes the dependency on a link event and runs the whole sequence, link, label and any downstream action, in one go.
Manual workflows can be run from the thread action bar, or press
Cmd + Kand choose Run workflow.If these limits block your workflow design, contact Plain support to register your use case.