> ## Documentation Index
> Fetch the complete documentation index at: https://developers.redo.com/llms.txt
> Use this file to discover all available pages before exploring further.
# MarketingAutomationStepInsertInput
> Insert a step. Pass after (parent) or before (existing child), not both. A/B parents require variantId. Condition parents require branch TRUE or FALSE. Pass exactly one typed payload. Which payloads the automation's trigger accepts is listed per trigger in marketingAutomationCatalog; any other returns STEP_NOT_INSERTABLE.
MarketingAutomationAbTestStepInput}>
[MarketingAutomationAbTestVariantInput!]}>
Existing variant id.
Merchant-facing name.
First step on this arm.
Share of traffic, typically summing to 100.
Insert on the outgoing edge of this parent step.
Insert immediately before this child. The child must have exactly one incoming edge.
MarketingAutomationConditionBranch}>
Which condition arm to attach to.
MarketingAutomationConditionStepInput}>
MarketingAutomationConditionExpressionInput}>
MarketingAutomationExistingSegmentConditionInput} />
MarketingAutomationInlineSegmentConditionInput} />
MarketingAutomationTriggerDataConditionInput} />
First step when the expression does not match.
First step when the expression matches.
MarketingAutomationEndStepInput}>
MarketingAutomationManageCustomerTagsStepInput}>
MarketingAutomationTagOperation} />
Customer tag ids: each tag's `id` or `legacyId`.
MarketingAutomationManageStaticSegmentStepInput}>
MarketingAutomationTagOperation} />
The static segment's `id` or `legacyId`.
MarketingAutomationSendEmailStepInput}>
Insertable only when the trigger schema has an Email field (not SMS signup).
The email template this send is copied from: its `id` or `legacyId`. Its trigger must match the automation's.
The email template to send: its `id`, or its `legacyId` from an earlier version of the Redo API. Its trigger must match the automation's.
MarketingAutomationSendSmsStepInput}>
Insertable only when the trigger schema has a Phone field (not email signup, HSA, or extended warranty).
The SMS template to send: its `id`, or its `legacyId` from an earlier version of the Redo API. Its trigger must match the automation's.
MarketingAutomationSendWebhookStepInput}>
Insert requires an http or https destinationUrl and a payload.
MarketingAutomationWebhookAuthType} />
[MarketingAutomationSendWebhookHeaderInput!]}>
Replaces the stored header list. Include every header's value.
Header name. Letters, numbers, hyphens, and underscores only.
Header value. Write-only; reads do not return it.
MarketingAutomationSendWebhookOAuth2ConfigInput}>
Required on insert when authType is OAUTH2\_CLIENT\_CREDENTIALS, including clientSecret.
Write-only. Omit on update to keep the stored secret. Never returned.
MarketingAutomationStartAgentConversationStepInput}>
Start a Commerce Agent conversation. Insertable when Commerce Agent is enabled, the trigger supports it, and the trigger schema has an Email or Phone field. Requires strategyId.
MarketingAutomationCommerceAgentChannelInput}>
SMS only. Reach customers who have not subscribed through Recover. Defaults to false.
MarketingAutomationCommerceAgentChannelKind!} required />
SMS only. Defaults to true. False needs extendedOutreach true.
A CommerceAgentStrategy id from this store. Required on insert.
Which A/B variant arm to attach to.
MarketingAutomationWaitStepInput}>
MarketingAutomationWaitTimeUnit} />
MarketingAutomationWaitForEventStepInput}>
JSON} />
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.