Scenario inputs and scenario outputs
inputs and outputs allow you to send data to a and retrieve data from it.
- Scenario inputs allow you to pass data with a predefined structure to a every time you run it.
- Scenario outputs complement inputs by allowing you to send data from a with the Return output module.
Using inputs and outputs allows you to use as functions or tools. Splitting up a large that handles a lot of actions into a group of small , each handling one action or a business function, will make the automation easier to maintain and debug.
Having a dedicated to a specific action allows you to share the with other members of your organization. They could just call your in their 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 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 dedicated to each system to make the task easier to manage.
- You can use the name, email, and employee ID as your inputs.
- Once you enter and save the employee information to the , the runs and triggers dedicated to setting up an account in each system.
- When each scenario finishes, it reports the status and any additional information to the parent through outputs.
Some other cases in which you might use 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