> For the complete documentation index, see [llms.txt](https://readme.directual.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://readme.directual.com/scenarios/editing-scenarios/system-steps/link-scenario-step.md).

# Link scenario step

![](/files/-MYuPaKuTTmPlFBqM1rh)

**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

<figure><img src="/files/ffFzFEosM41z64JLoER2" alt=""><figcaption></figcaption></figure>

* **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)

<figure><img src="/files/mLRO3sh45VjoysVjBA4y" alt=""><figcaption></figcaption></figure>

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 %}

<figure><img src="/files/rakYkkpoK7cHxtmNsrNo" alt=""><figcaption></figcaption></figure>

#### Set the sync/async mode

If you want, you may run the called scenario [synchronically](/scenarios/synchronic-scenarios-1.md). In the sync mode the step will wait until the linked scenario is finished.

<figure><img src="/files/lRQrMYIjm7vdOdsBvYp4" alt=""><figcaption></figcaption></figure>

#### 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](/template-system/basics-of-template-system.md) and [JS-evaluation](/template-system/evaluating-as-js-expression.md))

<figure><img src="/files/YFCslMgI32Vc9DMZeVD0" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://readme.directual.com/scenarios/editing-scenarios/system-steps/link-scenario-step.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.