Scenario inputs and scenario outputs

{{scenario singular}} inputs and outputs allow you to send data to a {{scenario singular lowercase}} and retrieve data from it scenario inputs allow you to pass data with a predefined structure to a {{scenario singular lowercase}} every time you run it scenario outputs complement {{scenario singular lowercase}} inputs by allowing you to send data from a {{scenario singular lowercase}} with the return output module using {{scenario singular lowercase}} inputs and outputs allows you to use {{scenario plural lowercase}} as functions or tools splitting up a large {{scenario singular lowercase}} that handles a lot of actions into a group of small {{scenario plural lowercase}} , each handling one action or a business function, will make the automation easier to maintain and debug having a {{scenario singular lowercase}} dedicated to a specific action allows you to share the {{scenario singular lowercase}} with other members of your organization they could just call your {{scenario singular lowercase}} in their {{scenario singular lowercase}} and get the results they need imagine a new employee is about to start working in your company you may need to create new accounts for your new employee in several different systems (e g jira, slack, email, miro, etc) to create these accounts, you need the new employee’s name, email, employee id, and maybe some other personal information to automate this action, you can set up a {{scenario singular lowercase}} to create and configure new accounts for your new employee in all the different systems you need however, configuring each account might be a complex task in itself you might need to define the user access permissions or assign the user to teams you can create a {{scenario singular lowercase}} dedicated to each system to make the task easier to manage you can use the name, email, and employee id as your {{scenario singular lowercase}} inputs once you enter and save the employee information to the {{scenario singular lowercase}} , the {{scenario singular lowercase}} runs and triggers {{scenario plural lowercase}} dedicated to setting up an account in each system when each scenario finishes, it reports the status and any additional information to the parent {{scenario singular lowercase}} through {{scenario singular lowercase}} outputs some other cases in which you might use {{scenario singular lowercase}} inputs and outputs syncing information about a new customer in multiple systems adding offline leads to the crm, email lists, and creating a proposal creating a new record/invoice/email/order by providing a set of inputs