Skip to main content

guidedSellingFlowVersionPublish

BETA: guided selling can still change in ways that break existing integrations. Backwards compatibility is not guaranteed while it is in beta.

Make a draft the version new conversations start on. The previously published version is archived and keeps serving conversations that pinned it. Before the switch, one call that generates nothing asks the model vendor whether it accepts the flow's key and knows the version's model. The opening branches are computed right after the switch, in every language the version offers; the version's warmStatus and warmError report how that went.

Possible errors:

  • GUIDED_SELLING_FLOW_NOT_FOUND_ERROR: no flow with this id in the calling tenant
  • GUIDED_SELLING_FLOW_VERSION_NOT_FOUND_ERROR: the flow has no such version
  • GUIDED_SELLING_FLOW_VERSION_NOT_DRAFT_ERROR: only drafts can be published
  • GUIDED_SELLING_MODEL_UNAVAILABLE_ERROR: the vendor refused the key or does not know the model; the message gives its reason, extensions.reason the code. Nothing was switched. When the vendor cannot answer right now, the version is published anyway

AUTH: Role=[configuration.OWNER]

guidedSellingFlowVersionPublish(
  flowId: ID!
  version: Int!
): GuidedSellingFlowVersion!

Arguments​

guidedSellingFlowVersionPublish.flowId ● ID! non-null scalar​

Unique identifier of the guided selling flow (UUID v7).

guidedSellingFlowVersionPublish.version ● Int! non-null scalar​

Sequential number of the version within its flow, starting at 1.

Type​

GuidedSellingFlowVersion object​

BETA: guided selling can still change in ways that break existing integrations. Backwards compatibility is not guaranteed while it is in beta.

One immutable version of a flow's content. Select content to read what it holds; listings stay light when it is left out.