Start

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 deployed chat experiences — no mode switching required.

Built-in outputs

Every Start block always exposes these variables to downstream blocks:

Custom input fields

Use the Inputs panel on the block to define additional typed fields. Each 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}/trigger

curl -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"}}'

{ "executionId": "...", "status": "completed", "outputs": { ... } }

curl -X POST "https://app.scrydon.com/api/v1/workflows/{id}/trigger?async=true" \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{"inputs": {"userId": "123"}}'

{ "executionId": "...", "status": "running" }

The inputs object maps to the custom input fields you defined on the block. The built-in input, conversationId, and files fields are populated automatically by the platform for chat executions.