Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
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-action-generate-sample-data.png
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
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
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
1 change: 1 addition & 0 deletions workflow-management/actions.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -117,4 +117,5 @@ These actions help store and share information collected during workflow runs.
* **OpenOps Tables**: create and update records in [tables](/reporting-analytics/tables/).
* **SFTP**: create or read files on a remote server via SFTP.
* **Storage**: store data in and read it from your OpenOps installation's key-value storage. The storage is accessible at run, workflow, and project levels.
* **Microsoft Outlook**: send, forward, reply to, find, and move emails.
* **SMTP**: send emails.
2 changes: 2 additions & 0 deletions workflow-management/building-workflows.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,8 @@ 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*.
* **IMAP**: *New email*.
* **Microsoft Outlook**: *New email*.
* **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
3 changes: 2 additions & 1 deletion workflow-management/human-in-the-loop.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ To request approvals through a communication channel other than Slack, use the *

In this case, here's how you can create the approval part of your workflow:
1. Add the **Create Approval Links** action from the **Approval** group. This action generates two links: one for approval and the other for disapproval.
2. Add an action to message a stakeholder the two links. You can use **Send Email** under **SMTP** or one of the actions in the **Microsoft Teams** group.
2. Add an action to message a stakeholder the two links. You can use **Send Email** from the **SMTP** group, **Send Email** from the **Microsoft Outlook** group, or one of the actions in the **Microsoft Teams** group.
3. Add the **Wait For Approval** action from the **Approval** group. Once the stakeholder clicks a link, this action updates the approval status accordingly.
4. Add the **Condition** action to take steps in case of approval or disapproval.

Expand All @@ -58,3 +58,4 @@ Besides approvals, you can also send notifications about completed workflows or
* **Send Channel Message** and **Send Chat Message** under **Microsoft Teams**:
![Microsoft Teams actions](/images/hitl-teams-actions.png)
* Actions in the **Jira Cloud** group, such as **Change Issue Status** and **Add Issue Comment**.
* Actions to send emails under **SMTP** and **Microsoft Outlook**.