> For the complete documentation index, see [llms.txt](https://university.mindstudio.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.mindstudio.ai/building-ai-agents/blocks-reference/run-node-n8n.md).

# Run Node (n8n)

Trigger an n8n workflow from MindStudio

## Configuration 

### Webhook URL

Enter the webhook URL that will trigger the workflow. For information on creating webhooks with n8n [visit there documentation.](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.webhook/)

### Data

Add the data you want to send to n8n using **Key Value pairs**. This section can include variables. 

### Output Variable

Save the results of the request to a variable. Example: `n8n_request`

## Advanced Settings

### HTTP Method

Select the method you want to use in the request. Options include:

* **GET:** Retrieve data without modifying any underlying resources.
* **POST:** Create or update a resource.
* **PATCH:** Make partial updates to an existing resource.
* **PUT:** Update an entire resource.
* **DELETE:** Remove a specified resource.
* **HEAD:** Retrieve only the header information.

### Authentication

Select the authentication type. Options include:

* **None** 
* **Basic Auth**
  * This requires you to include a **username** and **password**.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://university.mindstudio.ai/building-ai-agents/blocks-reference/run-node-n8n.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.