Actions (event-driven automation): improved triggers, webhook support, and scheduling options
evaluating
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:
- Allow users to clone actions from the UI, providing a quick and convenient feature enhancement.
- Enable users to specify additional fields in action calls, such as the run name (supported by the API).
- Add additional Actions triggers, including cron/scheduled hooks, pipeline lifecycle events (start, complete, fail), and changes in data.
- Add additional Actions responses, including running a script/function.
- Implement the ability to import/export actions as JSON, providing users an easy way to manage and share actions.
These enhancements will enhance user experiences and make managing actions in Seqera platform more versatile and user-friendly.
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.
Rob Newman
Merged in a post:
Workflow Run Web Callbacks
C
Coral reef Lamprey
The post-script allows us to run a curl command after a run, but it'd be nice to have this as an actually supported feature - to be able to provide a URL to be called after the run with the status (success/failure) of the run.
Drew DiPalma
updated the status to
planned
E
Enthusiastic Planarian
Merged in a post:
Scheduled and manual triggers for Actions
Currently, Seqera platform has two types of actions: Github actions, triggered upon every push to a branch, and internal actions, triggered via an API request to an endpoint. External events trigger these actions. However, Nextflow is domain-independent and can be employed for automating various tasks, including routine data collation/transformation and report creation from specific sources.
Intended Outcome:
To make Actions more versatile, are considering following enhancements:
- Scheduling Capability: Enable users to trigger an action on specific data or at defined intervals, such as minutes, hours, or days.
- User-Friendly Trigger: Allow users to trigger actions directly from within the Tower UI, simplifying access for non-technical users.
- Action Timeout: Provide the ability to set a timeout for actions to handle failure scenarios more effectively.
Load More
→