8
## Default Workflow
9
10
1. Start with `composio execute <slug>` whenever the slug is known.
11
-2. If `execute` says the toolkit is not connected, run `composio link <toolkit>` and retry.
12
-3. If the arguments are unclear, run `composio execute <slug> --get-schema` or `--dry-run` before guessing.
13
-4. Reach for `composio search "<task>"` only when the slug is unknown.
11
+2. If several independent tool calls must happen at once, use `composio execute -p/--parallel` with repeated `<slug> -d <json>` groups.
12
+3. If `execute` says the toolkit is not connected, run `composio link <toolkit>` and retry.
13
+4. If the arguments are unclear, run `composio execute <slug> --get-schema` or `--dry-run` before guessing.
14
+5. Reach for `composio search "<task>"` only when the slug is unknown. `search` accepts one or more queries, so batch related discovery work into a single command when useful.
15
16
## `execute` — Run A Tool
17
38
cat issue.json | composio execute GITHUB_CREATE_AN_ISSUE -d -
39
```
40
41
+Run independent tool calls in parallel:
42
+
43
+```bash
44
+composio execute --parallel \
45
+ GMAIL_SEND_EMAIL -d '{ recipient_email: "a@b.com", subject: "Hi" }' \
46
+ GITHUB_CREATE_AN_ISSUE -d '{ owner: "acme", repo: "app", title: "Bug" }'
47
+```
48
+
49
## `search` — Find The Slug
50
51
```bash
52
composio search "create a github issue"
53
composio search "send an email" --toolkits gmail
54
+composio search "send an email" "create a github issue"
55
+composio search "my emails" "my github issues" --toolkits gmail,github
56
```
57
47
-Read the returned slugs, choose the best match, and move back to `execute`.
58
+Use multiple quoted queries when the user is exploring more than one task or a small cross-app workflow. Read the returned slugs, choose the best match, and move back to `execute`.
59
60
## `link` — Connect An Account
61
92
'
93
```
94
95
+Use top-level `execute --parallel` when the user just needs a few independent tool calls and does not need script logic, loops, or output plumbing.
96
+
97
Fan out with `Promise.all`:
98
99
```bash
119
'
120
```
121
109
-For more patterns — `proxy()` inside scripts, `search()` inside scripts, mixed `execute()` + `proxy()`, and `--dry-run`/`--debug` flags — load [references/power-user-examples.md](references/power-user-examples.md).
122
+For more patterns — multi-query top-level `search`, `proxy()` inside scripts, mixed `execute()` + `proxy()`, and `--dry-run`/`--debug` flags — load [references/power-user-examples.md](references/power-user-examples.md).
123
124
## Auth
125