Ability to Override Variables Set by Input Form Trigger During Agent Flow

shanaazdeo

I have an Agent that collects dates via an Input Form Trigger at the start of the flow. Later, it checks the user’s calendar for more accurate dates.

Currently there’s no way to overwrite the original Input Form variables mid-flow. I’d like the ability to update those variables dynamically if better data is found, so the Agent can continue using the most accurate values without asking the user again.

If anyone has a workaround for simulating this behavior (e.g. alternate variables, branching, or other patterns), please share.

mcomolli

Hi @shanaazdeo - I think you could use either branching or a think step here. Either way, it'll require a precise definition of what "accurate" means in this case - for the sake of this comment, I'll assume it means "closest to today's date".

Please note that I use the double square bracket notation both to refer to input fields ([[date input field]]) and to prior steps (i.e. [[5. Think]

Branching:

1. trigger
2. … some other steps …
3. check the user's calendar
4. (optional, but may improve accuracy) Think step: "extract the date(s) from the previous step"
   1. Note: this may require writing a more detailed prompt to specify which date(s) to extract from the calendar step
5. branch
   1. Branch 1: "Follow this branch if [[date input field]] is closer to today's date than the date in [[4. Think]]"
      1. This branch will preserve the date from the input field. In all subsequent steps you define on this branch, refer to [[date input field]]
   2. Branch 2: fallback
      1. Since there are only 2 conditions to check, we don't need to specify a condition on this branch!
      2. This branch will "override" the input field. In all subsequent steps you define on this branch, refer to [[4. Think]]

Think step:

After you've retrieved the user's calendar dates, you can try adding a Think step (using the same definition of "accurate" from above) like this:

1. trigger
2. … some other steps …
3. check the user's calendar(optional, but may improve accuracy)
4. Think step: "extract the date(s) from the previous step"
   1. Note: this may require writing a more detailed prompt to specify which date(s) to extract from the calendar step
5. Think step: "Compare [[date input field]] and [[4. Think]] and choose whichever one is closer to today's date. Return the more accurate date with no additional content"
   1. In all subsequent steps that require a date, refer to [[5. Think]]