# Link scenario step
**Link scenario** step throws an object (or a few objects) to scenario.
{% hint style="info" %}
Hint: That step is a great way to use a scenario as a reusable micro-service
{% endhint %}
### Step settings:
#### Choose the object/objects to send
* **Current object**. The object from the scenario will be sent
* **Linked object**. Pick the field type of `link` with the ID of the object to send
* **Array of linked objects**. Pick the field type of `arrayLink` with the array of IDs of the objects to send.
#### Pick the link/arrayLink field (for the 2nd and 3rd options above)
The `link/arrayLink` may be stored among the object fields or in the context variables.
#### Pick the scenario to call
We'll throw the object (objects in case of arrayLink option) to that scenario.
{% hint style="info" %}
1. Note that the called scenario has to be **published** and **started**
2. You choose the scenario that processes the objects of the sent object's structure
{% endhint %}
#### Set the sync/async mode
If you want, you may run the called scenario [synchronically](https://readme.directual.com/scenarios/synchronic-scenarios-1). In the sync mode the step will wait until the linked scenario is finished.
#### Context parameters
If the called scenario has context variables, you'll be able to set the values of those parameters in the **Link scenario** step (using [templating system](https://readme.directual.com/template-system) and [JS-evaluation](https://readme.directual.com/template-system/evaluating-as-js-expression))
