Start
The unified workflow entry point for editor runs, API calls, and workflow-editor conversations.
The Start block is the default trigger for new workflows. A single block handles manual runs from the editor, API calls from external systems, and workflow-editor assistant conversations — no mode switching required.
Built-in outputs
Every Start block always exposes these variables to downstream blocks:
| Variable | Type | Description |
|---|---|---|
<start.input> | string | Editor conversation message or raw input string (API/manual) |
<start.conversationId> | string | Workflow-editor conversation identifier |
<start.files> | files | Workflow-editor or API file attachments |
Custom input fields
Custom inputs are optional. A new Start block has none; select Add Input in the Inputs panel to create the first one. You can delete every custom input when the workflow only needs the built-in fields.
Each custom field you add becomes a variable in downstream blocks:
# A field named "userId" becomes:
<start.userId>
# A field named "reportDate" becomes:
<start.reportDate>Supported field types: text, number, boolean, JSON, file, date.
In the editor, custom fields also appear as a form you can fill in to test the workflow manually without making an API call.
API execution
The public API endpoint is:
POST /api/v1/workflows/{id}/triggercurl -X POST "https://app.scrydon.com/api/v1/workflows/{id}/trigger" \
-H "Authorization: Bearer {token}" \
-H "Content-Type: application/json" \
-d '{"inputs": {"userId": "123", "reportDate": "2026-05-22"}}'The response waits up to 30 seconds for the workflow to complete and returns the result:
{ "executionId": "...", "status": "completed", "outputs": { ... } }If the workflow exceeds 30 seconds, the response is 202 with "status": "running" and you can poll the execution ID for the final result.
The inputs object maps to the custom input fields you defined on the block. The built-in input, conversationId, and files fields remain available for workflow-editor assistant conversations and direct execution. They do not create a public hosted chat deployment.
For automated or scheduled work, use the Schedule or Webhook triggers instead. The Start block is designed for user-initiated runs and direct API calls.