Genesys Cloud - Developer Community!

Hi everyone,

I have a question regarding the "Wait for Input" action in Architect.

I would like to store the exact user input provided during the "Wait for Input" block into a variable, so I can use it later in the flow or send it to an external integration/API.

What is the best way to capture and persist the user response from this action?
Is there a built-in variable for the input text/value, or do I need to configure something specific?

Thanks in advance!

Hi Giovanna,

You are right to question it. The Wait for Input action does not expose a generic "raw input variable" in the same way many people expect.

In Digital Bot Flows, the most reliable/native way to capture and persist user input is usually through:

• Ask for Intent
• Ask for Slot
• or custom slot configuration

Those actions were designed to store customer responses into variables/entities that can later be reused in:

• Data Actions
• participant data
• API calls
• flow logic

Wait for Input is more focused on waiting for a customer interaction/event and routing the flow behavior, especially in custom knowledge handling scenarios.

One important detail from the documentation:
when using custom knowledge handling, Wait for Input can store matched knowledge search results into a variable like:

Flow.searchResults

But this is the knowledge match collection, not necessarily the literal raw text the customer typed.

So if your goal is:
"capture exactly what the customer entered and reuse it later"

then using an Ask for Slot or Ask for Intent approach is usually the better design pattern instead of relying only on Wait for Input.

Hi everyone,

I have a question regarding the "Wait for Input" action in Architect.

I would like to store the exact user input provided during the "Wait for Input" block into a variable, so I can use it later in the flow or send it to an external integration/API.

What is the best way to capture and persist the user response from this action?
Is there a built-in variable for the input text/value, or do I need to configure something specific?

Thanks in advance!

Perfeito, entendi o ponto.

O meu cenário é um pouco diferente porque eu realmente preciso utilizar o bloco "Wait for Input" no fluxo.

A ideia é:

• o cliente envia a primeira mensagem;

• o "Wait for Input" captura essa interação inicial;

• dependendo do conteúdo enviado, eu direciono o fluxo.

Se a intenção encontrada estiver relacionada à base de conhecimento, então eu aciono a Knowledge Base dentro do próprio fluxo.
Caso contrário, sigo outro caminho no fluxo com base exatamente no input inicial enviado pelo cliente.

Por isso minha dúvida era justamente sobre conseguir persistir/reutilizar o texto digitado no "Wait for Input", já que preciso utilizar esse mesmo input posteriormente na lógica do fluxo.

No meu caso, eu não consigo substituir totalmente por "Ask for Intent" ou "Ask for Slot", porque o "Wait for Input" faz parte da estratégia de roteamento inicial do atendimento.

------------------------------
Giovanna Rebizzi
Desenvolvedora

Original Message:
Sent: 05-13-2026 17:49
From: Gabriel Garcia
Subject: How to store user input from "Wait for Input" action in Architect?

Hi Giovanna,

You are right to question it. The Wait for Input action does not expose a generic "raw input variable" in the same way many people expect.

In Digital Bot Flows, the most reliable/native way to capture and persist user input is usually through:

• Ask for Intent
• Ask for Slot
• or custom slot configuration

Those actions were designed to store customer responses into variables/entities that can later be reused in:

• Data Actions
• participant data
• API calls
• flow logic

Wait for Input is more focused on waiting for a customer interaction/event and routing the flow behavior, especially in custom knowledge handling scenarios.

One important detail from the documentation:
when using custom knowledge handling, Wait for Input can store matched knowledge search results into a variable like:

Flow.searchResults

But this is the knowledge match collection, not necessarily the literal raw text the customer typed.

So if your goal is:
"capture exactly what the customer entered and reuse it later"

then using an Ask for Slot or Ask for Intent approach is usually the better design pattern instead of relying only on Wait for Input.

------------------------------
Gabriel Garcia
NA

Original Message:
Sent: 05-13-2026 17:21
From: Giovanna Rebizzi
Subject: How to store user input from "Wait for Input" action in Architect?

Hi everyone,

I have a question regarding the "Wait for Input" action in Architect.

I would like to store the exact user input provided during the "Wait for Input" block into a variable, so I can use it later in the flow or send it to an external integration/API.

What is the best way to capture and persist the user response from this action?
Is there a built-in variable for the input text/value, or do I need to configure something specific?

Thanks in advance!

#Architect

------------------------------
Giovanna Rebizzi
Desenvolvedora
------------------------------

Perfeito, entendi o ponto.

O meu cenário é um pouco diferente porque eu realmente preciso utilizar o bloco "Wait for Input" no fluxo.

A ideia é:

• o cliente envia a primeira mensagem;

• o "Wait for Input" captura essa interação inicial;

• dependendo do conteúdo enviado, eu direciono o fluxo.

Se a intenção encontrada estiver relacionada à base de conhecimento, então eu aciono a Knowledge Base dentro do próprio fluxo.
Caso contrário, sigo outro caminho no fluxo com base exatamente no input inicial enviado pelo cliente.

Por isso minha dúvida era justamente sobre conseguir persistir/reutilizar o texto digitado no "Wait for Input", já que preciso utilizar esse mesmo input posteriormente na lógica do fluxo.

No meu caso, eu não consigo substituir totalmente por "Ask for Intent" ou "Ask for Slot", porque o "Wait for Input" faz parte da estratégia de roteamento inicial do atendimento.

Hi Giovanna,

You are right to question it. The Wait for Input action does not expose a generic "raw input variable" in the same way many people expect.

In Digital Bot Flows, the most reliable/native way to capture and persist user input is usually through:

• Ask for Intent
• Ask for Slot
• or custom slot configuration

Those actions were designed to store customer responses into variables/entities that can later be reused in:

• Data Actions
• participant data
• API calls
• flow logic

Wait for Input is more focused on waiting for a customer interaction/event and routing the flow behavior, especially in custom knowledge handling scenarios.

One important detail from the documentation:
when using custom knowledge handling, Wait for Input can store matched knowledge search results into a variable like:

Flow.searchResults

But this is the knowledge match collection, not necessarily the literal raw text the customer typed.

So if your goal is:
"capture exactly what the customer entered and reuse it later"

then using an Ask for Slot or Ask for Intent approach is usually the better design pattern instead of relying only on Wait for Input.

Hi everyone,

I have a question regarding the "Wait for Input" action in Architect.

I would like to store the exact user input provided during the "Wait for Input" block into a variable, so I can use it later in the flow or send it to an external integration/API.

What is the best way to capture and persist the user response from this action?
Is there a built-in variable for the input text/value, or do I need to configure something specific?

Thanks in advance!

Hi Giovanna,

You are right to question it. The Wait for Input action does not expose a generic "raw input variable" in the same way many people expect.

In Digital Bot Flows, the most reliable/native way to capture and persist user input is usually through:

• Ask for Intent
• Ask for Slot
• or custom slot configuration

Those actions were designed to store customer responses into variables/entities that can later be reused in:

• Data Actions
• participant data
• API calls
• flow logic

Wait for Input is more focused on waiting for a customer interaction/event and routing the flow behavior, especially in custom knowledge handling scenarios.

One important detail from the documentation:
when using custom knowledge handling, Wait for Input can store matched knowledge search results into a variable like:

Flow.searchResults

But this is the knowledge match collection, not necessarily the literal raw text the customer typed.

So if your goal is:
"capture exactly what the customer entered and reuse it later"

then using an Ask for Slot or Ask for Intent approach is usually the better design pattern instead of relying only on Wait for Input.

Hi everyone,

I have a question regarding the "Wait for Input" action in Architect.

I would like to store the exact user input provided during the "Wait for Input" block into a variable, so I can use it later in the flow or send it to an external integration/API.

What is the best way to capture and persist the user response from this action?
Is there a built-in variable for the input text/value, or do I need to configure something specific?

Thanks in advance!