You've mastered Job, Inputs and Outputs. Let's recap

1. The Script for the Job gets published to the Automation Cloud and is executed remotely.
2. The Job follows the Script, receives inputs, emits outputs and communicates the state change.
3. To incorporate Job inputs into your Script:
   • Specify all the desired input keys in the "Input" panel. For each input key, provide the value – an example piece of data.
   • A list of inputs forms a bundle. Feel free to create a few such bundles to test your automation with various input values for the same set of input keys.
   • Connect your actions with Job inputs via the Value.getInput pipe.
4. A Job can cast as many outputs as you need from any point in the Script. To produce the data, use the output action.
5. Autopilot playback is not a real Automation Job. It's a preview.
   • When a Job runs in the Automation Cloud, it ignores the input snippets (those are for Autopilot only!). Instead, a Job requests all the inputs from a client, your app. It's up to you to provide some or all the information when creating a Job or later.
   • Use the Playback Events panel to learn at what point of the playback your Script consumes each input and emits each output. This should give you a good idea of what happens when you run your Automation Job in the Automation Cloud.
6. Tools for the Job
   • For speedy integration and prototyping, give the JavaScript client library a try.
   • For everything else, integrate with our REST API directly.

You're all set now. Happy automating!