> For the complete documentation index, see [llms.txt](https://blog.rhinoautomator.com/brians-integration-and-automation-notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blog.rhinoautomator.com/brians-integration-and-automation-notes/automations/teams-notifications-azure-bot/working-with-the-responses.md).

# Working with the Responses

{% hint style="danger" %}
I've migrated the entire blog over to my new website. Please go to [https://rhinoautomator.com](https://rhinoautomator.com/) for more as this will be deleted at some point.
{% endhint %}

Your response handler workflow will get pinged on any "action" the bot can see. Bot installed as an application in a Team, newly created channels for a Team it's already installed in, channel deletion, reactions to posts made, comments made on posts, etc. What I primarily was working to build out was a workflow that will handle the responses to the different action buttons.

To do that, you need to understand the JSON payload that comes with the bot response. The primary part that you're concerned with is the "body":

<figure><img src="https://965055951-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzwHskk220tGpzlbz7txC%2Fuploads%2FrseUEVCxRsHEHnxWh2X4%2Fimage.png?alt=media&amp;token=cfb753fa-0cd3-4d98-877e-ee3e7a3da7fe" alt=""><figcaption><p>Unexpanded JSON sent to Rewst</p></figcaption></figure>

There's quite a bit of useful, acitonable information that you can get from the "body"

<figure><img src="https://965055951-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzwHskk220tGpzlbz7txC%2Fuploads%2FSZWJ9Rc2YcBsl88KwrxD%2Fimage.png?alt=media&amp;token=4b7f891d-30df-4bbf-9e25-ea125999447d" alt=""><figcaption><p>"body" JSON Expanded</p></figcaption></figure>

If you've properly built out your "Action.Submit" "data" fields, then the piece of the "body" that you'll be most interested is "value". Here you'll see the properly formatted approval body needed to send the SME approved service ticket to Azure DevOps

<figure><img src="https://965055951-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzwHskk220tGpzlbz7txC%2Fuploads%2FQfK9RmXlRymHtTjuE7q0%2Fimage.png?alt=media&amp;token=c644945f-7b7e-48d2-9d2d-02b32fa06548" alt=""><figcaption><p>"value" JSON Expanded</p></figcaption></figure>

By building this information into the JSON for the action, you'll be able to pass the information from the response handler workflow to the sub-workflow and action as needed.