Hi ​@TMathew 

For us to have more info, post screenshots showing what you are referring to.

Hi ​@TMathew 

Just came across this and spotted you reached out to our Support team about this and they were able to help get it sorted. Seems the solution was to use custom pill mapping to manually select the summary field. I’ll share the details of the solution here in case it’s helpful to others that might be having similar issues:

{{305256882__agent_response__response_text__summary}}

If it’s helpful you can learn more about custom pill mapping to select fields here:

I’ll go ahead and mark this as the best answer for now as their suggestion appears to have done the trick. Feel free to reach back out if we can help with anything else though. Until then, happy Zapping!

Yes, it worked for me but I asked a follow-up question and waiting for the reply. 

Can you please let me know how to obtain this?

{{305256882__agent_response__response_text__summary}}

In my case I am not sure how you got the above. In case if I am creating another agent for different usecase how can I get the output?

Hi ​@TMathew,

To access a specific dynamic field like {{305256882__agent_response__response_text__summary}} in Zapier, ensure that the action step generating it—typically from an integrated app like a chatbot—is correctly configured to return detailed output fields. When creating a new agent, set it up similarly by enabling relevant data outputs and mapping those fields in Zapier. After setup, test the Zap to confirm the desired data is being captured accurately.

Let us know if you need further assistance. We're here to help.

Hey ​@TMathew, happy to help answer that! 

The {{305256882__agent_response__response_text__summary}} is known as a “custom pill”. It’s the internal reference for the field itself. It’s normally used in cases where the test data in a Zap isn’t providing the same fields that are output when a Zap in switched on and running live. 

It’s made up of two parts the Node ID of the trigger or action where the field is located and the Field Name. 

You can obtain the Node ID e.g. “305256882” from the page URL when editing a Zap. For example:


And you’d obtain the field name part e.g. “agent_response__response_text__summary” from looking at the field name that is returned by the Agent action in a live run of the Zap.

I’d recommend checking out this guide which explains it in more detail:

Hope that helps to clarify things. Let us know if you have any further questions, want to make sure you’re all set!