The Webex Contact Center Flow Designer activity set

See also

Sources

1. 1
   The article documents roughly 43 activities across the 4 groups.

   Build and manage flows with Flow Designer · activity listings · Checked 2026-09-05
2. 2
   A flow variable marked agent editable lets the agent change its value during the interaction and the system passes the change back to the flow.

   Build and manage flows with Flow Designer · Flow Designer, custom variables agent editable setting · Checked 2026-09-15
3. 3
   A system variable for the entry point identifier is misspelled in the published variable list, so a flow copying it as printed resolves to nothing.

   Build and manage flows with Flow Designer · system variable list · Checked 2026-09-05
4. 4
   A flow variable marked for external override can be changed from Control Hub by an administrator or a supervisor and the change applies immediately to calls already in progress.

   Build and manage flows with Flow Designer · Flow Designer, custom variables and external override · Checked 2026-09-15
5. 5
   Only a small number of activities carry error branches beyond the generic undefined error node.

   Build and manage flows with Flow Designer · activity error branches compared across the set · Checked 2026-09-05
6. 6
   Flow Designer organises its activities into 4 groups: contact handling, flow control, utilities and voice.

   Build and manage flows with Flow Designer · activity group headings · Checked 2026-09-05
7. 7
   Publishing an edited function updates every flow consuming that tagged version immediately.

   Build and manage flows with Flow Designer · Flow Designer, Functions publishing · Checked 2026-09-15
8. 8
   Flow Designer has one general error model: an activity's error path leads to the OnGlobalError event handler and the flow ends.

   Build and manage flows with Flow Designer · error handling section · Checked 2026-09-05
9. 9
   Get Queue Info is the only contact handling activity with 3 named outcome branches: Success Insufficient Information Flow and Failure.

   Build and manage flows with Flow Designer · Flow Designer, Get Queue Info activity · Checked 2026-09-15
10. 10
    The failure code table for the GoTo activity carries output variable names in its failure code column, so the article publishes no GoTo failure codes at all.

    Build and manage flows with Flow Designer · GoTo activity failure code table · Checked 2026-09-05
11. 11
    The HTTP Request activity's output variables are named two incompatible ways in two sections of the same article.disputed

    Build and manage flows with Flow Designer · HTTP Request activity compared across sections · Checked 2026-09-05
12. 12
    JSON variables are capped at 16 KB, limited to 5 per flow, and cannot be passed through flow chaining.

    Build and manage flows with Flow Designer · JSON variable limits · Checked 2026-09-05
13. 13
    The activity set uses at least 5 different label conventions for the same idea of an outcome: Success and Failure on one activity onSuccess and onError on another Handled and Escalated and Error on a third Errored on its successor and True and False on the branching activities.field report

    Build and manage flows with Flow Designer · Flow Designer, activity output ports across the catalogue · Checked 2026-09-15
14. 14
    Platform and release conditions are set per activity rather than by a general rule: some activities are limited to the Next Generation platform, one to Next Generation voice media, and one requires a local gateway alongside the real time media service.

    Build and manage flows with Flow Designer · activity prerequisites across the set · Checked 2026-09-05
15. 15
    The Record activity's own documentation states that the recorded file is unencrypted and warns against recording anything sensitive.

    Build and manage flows with Flow Designer · Record activity · Checked 2026-09-05
16. 16
    A recorded utterance can leave the platform through the HTTP Request activity, because the Record activity produces a file reference that a later activity can send outward.inferred

    Build and manage flows with Flow Designer · Record and HTTP Request activities read together · Checked 2026-09-05
17. 17
    A Recording Control activity uses a Boolean flow variable that overrides the recording policy set at tenant, queue and schedule level, in both directions.

    Build and manage flows with Flow Designer · Recording Control activity · Checked 2026-09-05
18. 18
    Only a small fraction of the article's 133 tables carry a caption element although its own numbering runs past table 30, so a caption search misses most of them.field report

    Build and manage flows with Flow Designer · table markup across the article · Checked 2026-09-05
19. 19
    A flow may contain a maximum of 30 variables in total and that count includes global variables.

    Build and manage flows with Flow Designer · variable limits · Checked 2026-09-05
20. 20
    A flow variable's type is fixed when it is created and cannot be changed afterwards.

    Build and manage flows with Flow Designer · variable types · Checked 2026-09-05
21. 21
    Cisco documents, from both ends, that a Record activity's captured caller audio can be uploaded to an external third-party server or API through the HTTP Request activity.

    Build and manage flows with Flow Designer · HTTP Request step 3, Request Body Value, File sub-option; Record step 8, Output Variables note · Checked 2026-09-05
22. 22
    A second file path for uploading a Record activity's captured caller audio to an external third-party server exists through the HTTP Request activity's Form Data content type, in addition to the File sub-option.

    Build and manage flows with Flow Designer · HTTP Request step 3, Request Body Value, File sub-option; Record step 8, Output Variables note · Checked 2026-09-05
23. 23
    The Set Announcement activity in Flow Designer supports all 3 announcement types.

    Build and manage flows with Flow Designer · Flow Designer, Set Announcement activity · Checked 2026-09-15
24. 24
    A flow can contain a maximum of 30 variables in total, and this count includes all global variables plus flow (custom) variables regardless of whether they are reportable or agent viewable.

    Build and manage flows with Flow Designer · Use variables and expressions / Create Custom Flow Variables · Checked 2026-09-04
25. 25
    Publishing a new version of a function immediately updates the behavior of all flows that consume the tagged version(s) of that function, including live production flows.

    Build and manage flows with Flow Designer · Create and manage functions / Create a function · Checked 2026-09-04
26. 26
    A JSON-type flow variable's value can be up to 16 KB in size.

    Build and manage flows with Flow Designer · Use variables and expressions / Create Custom Flow Variables · Checked 2026-09-04
27. 27
    A flow can contain a maximum of 5 JSON-type variables.

    Build and manage flows with Flow Designer · Use variables and expressions / Create Custom Flow Variables · Checked 2026-09-04
28. 28
    A JSON flow variable cannot be passed through flow chaining, so a value held in one does not reach the flow a GoTo hands off to.

    Build and manage flows with Flow Designer · Flow Designer guide, JSON variable limits · Checked 2026-09-15
29. 29
    If a flow developer does not configure an error handling path for an activity, execution falls back to the path defined in the OnGlobalError event handler.

    Build and manage flows with Flow Designer · Configure error handling · Checked 2026-09-04
30. 30
    Neither the blind transfer nor the bridged transfer activity may be placed in an event flow.

    Build and manage flows with Flow Designer · Flow Designer, Blind Transfer and Bridged Transfer activities · Checked 2026-09-05
31. 31
    Restrictions are stated for some activities and not others: blind transfer is terminal and unsupported for consults, bridged transfer is unsupported in outbound and event flows and for a contact already assigned to an agent, and most activities state none.field report

    Build and manage flows with Flow Designer · Flow Designer, activity catalogue · Checked 2026-09-05
32. 32
    Error handling runs 3 tiers deep: an activity's own error path, then a global error event flow, then the flow ends.

    Build and manage flows with Flow Designer · Flow Designer, configure error handling · Checked 2026-09-05
33. 33
    An event flow is an asynchronous extension of the same flow on its own canvas, with a unique start and end and no activities shared with the main flow.

    Build and manage flows with Flow Designer · Flow Designer, event flows · Checked 2026-09-05
34. 34
    Flow Designer documents 43 activities in 4 groups: 11 contact handling, 7 flow control, 8 utilities and 17 voice.

    Build and manage flows with Flow Designer · Flow Designer, activity catalogue · Checked 2026-09-05
35. 35
    One of the four activities Cisco lists as having no undefined error path documents such a path in its own section, so the catalogue and the activity's own page disagree.disputed

    Build and manage flows with Flow Designer · Flow Designer, configure error handling against the Parse activity · Checked 2026-09-05
36. 36
    Flow Designer names 9 event handlers on the Event flows tab: OnGlobalError AgentAccepted PhoneContactEnded AgentOffered AgentDisconnected CallbackFailed PreDial ContactAniUpdated and OutboundCampaignCallResult.

    Build and manage flows with Flow Designer · Flow Designer, Event flows tab, the event handler list · Checked 2026-09-15
37. 37
    The utilities list misspells the cryptographic hash activity where its own section heading spells it correctly.field report

    Build and manage flows with Flow Designer · Flow Designer, utilities activity list against the activity heading · Checked 2026-09-05
38. 38
    Only 6 Flow Designer activities carry error branches beyond the generic undefined error node: menu, collect digits, virtual agent, virtual agent version 2, queue to agent and cryptographic hash.

    Build and manage flows with Flow Designer · Flow Designer, activity error outputs · Checked 2026-09-15
39. 39
    Flow Designer functions run author-written JavaScript on Node.js 22.x and Python 3.13, described as available in the first phase.

    Build and manage flows with Flow Designer · Create and manage functions, FAQ on supported languages · Checked 2026-09-05
40. 40
    Flow Designer documents a Set Whisper Announcement activity that plays a brief prerecorded message to an agent just before the agent connects with a caller, where the caller hears ringing.

    Build and manage flows with Flow Designer · Flow Designer, Set Whisper Announcement activity · Checked 2026-09-05
41. 41
    The Blind Transfer activity cannot carry flow variables to the destination, because the destination flow is not executed.

    Build and manage flows with Flow Designer · Blind Transfer, second and third paragraphs · Checked 2026-09-05

Documents

Cite this page

WarmTransfer. (2026, September 15). The Webex Contact Center Flow Designer activity set. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-flow-designer-activities

@misc{warmtransfer-wxcc-flow-designer-activities,
  title  = {The Webex Contact Center Flow Designer activity set},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/wxcc-flow-designer-activities},
  note   = {Verified 2026-09-15}
}