StepResponseDto

Fields

Field	Type	Required	Description	Example
controls	ControlsMetadataDto	:heavy_check_mark:	Controls metadata for the step
controlValues	Map<String, Object>	:heavy_minus_sign:	Control values for the step (alias for controls.values)
providerOverrides	Map<String, Map\<String, Object>>	:heavy_minus_sign:	Per-provider content overrides keyed by providerId. Stored separately from controlValues and merged over the default body at send time. Keys are ChatProviderIdEnum / ToolProviderIdEnum values (e.g. slack, whatsapp-business, pagerduty).	{ "slack": { "text": "{{payload.title}}", "blocks": [ { "type": "divider" } ] }, "whatsapp-business": { "type": "text", "text": { "body": "{{payload.title}}" } }, "pagerduty": { "severity": "warning", "source": "novu", "summary": "{{payload.title}}" } }
variables	Map<String, Object>	:heavy_check_mark:	JSON Schema for variables, follows the JSON Schema standard
stepId	String	:heavy_check_mark:	Unique identifier of the step
id	String	:heavy_check_mark:	Database identifier of the step
name	String	:heavy_check_mark:	Name of the step
slug	String	:heavy_check_mark:	Slug of the step
type	StepTypeEnum	:heavy_check_mark:	Type of the step
origin	ResourceOriginEnum	:heavy_check_mark:	Origin of the layout
workflowId	String	:heavy_check_mark:	Workflow identifier
workflowDatabaseId	String	:heavy_check_mark:	Workflow database identifier
issues	Optional<StepIssuesDto>	:heavy_minus_sign:	Issues associated with the step
stepResolverHash	Optional<String>	:heavy_minus_sign:	Hash identifying the deployed Cloudflare Worker for this step