Skip to content

Tiny changes in 0.5.0 (DOC-103) and updated trigger documentation (DOC-101) #151

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 12, 2025
Merged

Tiny changes in 0.5.0 (DOC-103) and updated trigger documentation (DOC-101) #151

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8152143
New Terraform action
gorohoroh Sep 12, 2025
3faeb26
Updating trigger info (DOC-101)
gorohoroh Sep 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file modified images/scheduling-triggers.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified images/workflow-editor-select-trigger-group.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified images/workflow-editor-select-trigger.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
2 changes: 1 addition & 1 deletion workflow-management/actions.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ These are integration actions that provide various ways to make and request chan
* **Google Cloud**: execute Google Cloud CLI commands.
* IaC integrations:
* **AWS CloudFormation**: update or delete resources in a CloudFormation template.
* **Terraform**: update or delete resources in a Terraform template.
* **Terraform**: update or delete resources in a Terraform template, modify Terraform variables files.
* Other integrations:
* **Snowflake**: add rows to Snowflake tables.
* **GitHub**: retrieve file content, create pull requests, or trigger GitHub Actions runs.
Expand Down
3 changes: 2 additions & 1 deletion workflow-management/building-workflows.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,9 +48,10 @@ When you create a new workflow, the editor creates an empty stub trigger. Click
After selecting a group, choose a specific trigger within that group:
![Selecting a trigger](/images/workflow-editor-select-trigger.png)

OpenOps provides around 10 triggers divided into several groups:
OpenOps provides over 10 triggers divided into several groups:
* **Schedule**: *Every X minutes*, *Every hour*, *Every day*, *Every week*, *Every month*, *Cron expression*.
* **Jira Cloud**: *New issue*, *Updated issue*.
* **Linear**: *New issue*, *Updated issue*, *Removed issue*.
* **Webhook**: *Catch webhook*.

Some triggers are used more often than others. For most of your scenarios, you will probably use one of the triggers in the **Schedule** group, setting your workflows to run at a predetermined interval. For details on schedule triggers, see [Scheduling](/workflow-management/scheduling/).
Expand Down
2 changes: 1 addition & 1 deletion workflow-management/scheduling.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ description: 'How to schedule workflows to run automatically'
icon: 'calendar'
---

Every workflow starts with a trigger. OpenOps provides multiple triggers, enabling you to start workflows upon catching a webhook, or on creation or update of a Jira Cloud issue.
Every workflow starts with a trigger. OpenOps provides multiple triggers, enabling you to start workflows upon catching a webhook or depending on issue-related events in Jira Cloud or Linear.

For many of your scenarios, you will probably use one of the triggers in the **Schedule** group, setting your workflows to run at a predetermined interval.

Expand Down