# Invoke Secondary Workflows

You can trigger other workflows asynchronously from within a primary workflow using the keyword `lam.asyncExecute`, allowing for more complex automation scenarios without waiting for the secondary workflow to complete.

Imagine you have an e-commerce application with two workflows:

1. `process-new-order`: Handles new orders, inventory updates
2. `customer-communication`: Sends various emails to customers

When a new order comes in, you want to process it immediately but handle customer communications separately.

As a first step of the `process-new-order` workflow, you would invoke the `customer-communication` workflow as follows:

```javascript
return {
  "lam.asyncExecute": [
    {
      "lam.workflowId": 39, // customer-communication workflow id
      "lam.payload": { /* payload data */ }
    }
  ]
}
```

You can also invoke multiple workflows asynchronously by appending to the `lam.asyncExecute` array.


---

# Agent Instructions: 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:

```
GET https://docs.laminar.run/building-an-integration/advanced/workflows/invoke-secondary-workflows.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.