# "recycling" script output in a playbook

**URL:** <https://forum.ansible.com/t/recycling-script-output-in-a-playbook/15602>\
**Category:** Ansible Project\
**Created:** [July 3, 2014, 8:00pm UTC](https://forum.ansible.com/t/recycling-script-output-in-a-playbook/15602 "2014-07-03T20:00:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dimon](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@Dimon](https://forum.ansible.com/u/Dimon)\
**Post date:** [July 3, 2014, 8:00pm UTC](https://forum.ansible.com/t/recycling-script-output-in-a-playbook/15602/1 "2014-07-03T20:00:03Z")

</div>

Hi,

I’ve got a script that can produce JSON output and would like to register that output as a variable. I know it sounds lot like module but it isn’t. It’s a generic tool that can operate with or without ansible.

I have come across one post [http://jpmens.net/2012/08/30/ansible-variables-variables-and-more-variables/](http://jpmens.net/2012/08/30/ansible-variables-variables-and-more-variables/) that deals with a similar issue, but it uses Jinja to cut through some filtering:

set t = v.stdout|from\_json

so it can be used later.

Am I stuck with making my script into a module or can I creatively use what I have and avoid writing module.