You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pick one trigger per workflow to define how it starts:
10
+
Use the Start block for everything originating from the editor, deploy-to-API, or deploy-to-chat experiences. Other triggers remain available for event-driven workflows:
11
11
12
12
<Cards>
13
-
<Cardtitle="API"href="/triggers/api">
14
-
HTTP endpoint that maps JSON bodies into workflow inputs
13
+
<Cardtitle="Start"href="/triggers/start">
14
+
Unified entry point that supports editor runs, API deployments and chat deployments
Typed manual input used in editor runs and child workflows
21
-
</Card>
22
-
<Cardtitle="Manual"href="/triggers/manual">
23
-
On-demand runs with no additional data
16
+
<Cardtitle="Webhook"href="/triggers/webhook">
17
+
Receive external webhook payloads
24
18
</Card>
25
19
<Cardtitle="Schedule"href="/triggers/schedule">
26
20
Cron or interval based execution
27
21
</Card>
28
-
<Cardtitle="Webhook"href="/triggers/webhook">
29
-
Receive external webhook payloads
30
-
</Card>
31
22
</Cards>
32
23
33
24
## Quick Comparison
34
25
35
26
| Trigger | Start condition |
36
27
|---------|-----------------|
37
-
|**API**| Authenticated HTTP POST |
38
-
|**Chat**| Chat deployment message |
39
-
|**Input Form**| On manual submit in editor or parent workflow |
40
-
|**Manual**| Run button in editor |
28
+
|**Start**| Editor runs, deploy-to-API requests, or chat messages |
41
29
|**Schedule**| Timer managed in schedule modal |
42
30
|**Webhook**| On inbound HTTP request |
43
31
32
+
> The Start block always exposes `input`, `conversationId`, and `files` fields. Add custom fields to the input format for additional structured data.
33
+
44
34
## Using Triggers
45
35
46
-
1. Drop the trigger block in the start slot.
36
+
1. Drop the Start block in the start slot (or an alternate trigger like Webhook/Schedule).
47
37
2. Configure any required schema or auth.
48
38
3. Connect the block to the rest of the workflow.
49
39
50
40
> Deployments power every trigger. Update the workflow, redeploy, and all trigger entry points pick up the new snapshot. Learn more in [Execution → Deployment Snapshots](/execution).
51
41
52
-
Legacy Starter blocks remain for existing flows but no longer appear in new builds.
Copy file name to clipboardExpand all lines: apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/control-bar/components/deploy-modal/deploy-modal.tsx
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -121,12 +121,12 @@ export function DeployModal({
- In production, the curl would come in as e.g. curl -X POST -H "X-API-Key: $SIM_API_KEY" -H "Content-Type: application/json" -d '{"paramName":"example"}' https://www.staging.sim.ai/api/workflows/9e7e4f26-fc5e-4659-b270-7ea474b14f4a/execute -- If user asks to test via API, you might need to clarify the API key.
0 commit comments