Event-driven Actions
complete
This is an overarching request for improvements to the Actions feature in Seqera Platform. We aim to improve how actions are supported in Seqera Platform, streamlining user interactions and making them more efficient.
To achieve this goal, we have several objectives:
- Add additional Actions triggers, including cron/scheduled, pipeline lifecycle events (cancelled, complete, fail), and changes in data.
- Add additional Actions responses, including launching an agent.
These enhancements will accelerate automation for deterministic pipeline chains and/or probabilistic/agentic flows.
Andrew Dawson
updated the status to
complete
Shipped with Enterprise 26.2.
Rob Newman
updated the status to
in progress
M
Michael Tansini
updated the status to
planned
Rob Newman
Merged in a post:
Add support for outbound webhooks to Actions
Phil Ewels
Currently, integrating external automation systems with Seqera Platform requires repeatedly polling API endpoints to detect workflow status changes - an inefficient pattern that adds latency, increases API load, and complicates integration logic.
Adding outbound webhook support to Actions would allow users to configure HTTP callbacks triggered on workflow events (e.g., completion, failure, state transitions), enabling push-based architectures.
This would dramatically simplify building automation on top of Platform, whether for alerting, triggering downstream processes, updating external dashboards, or orchestrating multi-step pipelines across systems.
Webhooks are a standard integration primitive that would make Platform a better citizen in modern event-driven automation ecosystems.
D
Damask Crab
+1 for scheduled hooks and run name parameter!
Rob Newman
Merged in a post:
Update Actions endpoints to support specific Pipeline Run name
C
Celestial blue Guppy
Currently the Actions endpoint does not support setting the Pipeline Run name. Please update the Actions endpoints to support setting the Pipeline
run_name
:request body: {
"params": {
"sample_id": "LP6396000-DNA_A03",
"delivery_id": "HZ0003NEWF",
"skip_move_delivery": true,
"run_name": "LP6396000-DNA_A03-HZ0003NEWF"
}
}
Rob Newman
Celestial blue Guppy I will merge this into the generic "Actions improvements" feature request.
I
Imperial red Crane
Native scheduling of routine jobs, upvote!
K
Keen Pony
The most relevant feature I'm interested in would be to expand the JSON structure to support the setting of the
runName
(or workflow run name
as it is called in the UI) - supported by the API.Many thanks
Rob Newman
updated the status to
evaluating
Moving back to evaluating based on prioritization.
Load More
→