Skip to content

Commit 409d016

Browse files
authoredFeb 27, 2025··
Update apps.md
1 parent d72f394 commit 409d016

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed
 

‎docs/apps.md

+5-3
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Apps are the heavy lifters of [workflows](/docs/workflows) within Shuffle. They
2525

2626
A subset of available apps can be found at [https://shuffler.io/apps](https://shuffler.io/apps).
2727

28-
![Apps view 1](https://github.com/frikky/shuffle-docs/blob/master/assets/apps-view-1.png?raw=true)
28+
![Apps view 1](https://github.com/user-attachments/assets/71b1fc24-a49b-46e3-bdc2-a4286c94498e)
2929

3030
## How they work
3131
Apps are the primary building blocks in workflows. Apps can be auto-generated from [OpenAPI](https://swagger.io/specification/) specifications or using Shuffle's app sdk. To enforce stability and usability, we use a versioning system to prevent sudden updates to apps.
@@ -37,9 +37,11 @@ PS: In a future iteration, focus will move to an optional hybrid execution model
3737
### Actions
3838
An app can perform more than one task based on predefined actions. These actions are defined by the developer, and are reusable and modifiable by the user of the app. An action should (for now) be a one-to-one representation of the function to run, and usually has arguments for authentication with the target application. Actions can contain multiple arguments.
3939

40-
You can see what actions an app has by going to /apps, then finding the app you're looking for.
40+
You can view an app's actions by selecting the app and clicking the edit icon.
4141

42-
![Apps view 2](https://github.com/frikky/shuffle-docs/blob/master/assets/apps-view-2.png?raw=true)
42+
![Apps view 2](https://github.com/user-attachments/assets/3c995872-2a86-4951-a794-5958863a36b5)
43+
44+
![Actions View](https://github.com/user-attachments/assets/7ac431fa-be38-4f88-993a-95d45ed35aae)
4345

4446
### Arguments
4547
Arguments are the variables used to perform an action. Arguments with an orange dot next to them are required, with yellow ones being optional. Arguments should have example text to to indicate the expected value. The first arguments of an app are _usually_ related to authentication or the target URL, where we suggest using [variables](/docs/workflows#variables)

0 commit comments

Comments
 (0)
Please sign in to comment.