> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/rewst-documentation/documentation/automations/nodes.md).

# Nodes

{% hint style="info" %}
Ask the Rewst Agent to explain any node in Rewst. This documentation exists to help you get started, but in-platform questions and learning are the fastest way to achieve automation.
{% endhint %}

*Nodes* are all of the items that can be added to the Workflow Builder Canvas to build a workflow. They appear in the left side menu of the Workflow Builder and are dragged and dropped onto the Canvas. 

<figure><img src="https://3039672601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fh0G0em3PH6aDfPoI5XpN%2Fuploads%2FulmU8cBsf9Za0gUpbeHW%2Fscreen_recording.gif?alt=media&amp;token=090db4f7-586c-4812-98d8-91229dbecf79" alt="A video displays of a user dragging items from the left side of a screen, a long list of rectangular icons, to the center of the screen, and releasing the mouse to place them. The screen is a dark blue and the dragged items vary in colors depending on their type."><figcaption><p>Nodes, being dragged onto the Workflow Builder Canvas</p></figcaption></figure>

## Types of nodes

### Integration nodes&#x20;

After you install an integration in Rewst, nodes for that specific integration will appear in the left side menu of the Workflow Builder Canvas.

### Built-in nodes

These are the nodes are stock inside the Rewst Workflow Builder itself. You can drag any of them onto the Canvas without needing to first install an integration. Types of Built-in nodes include:

{% content-ref url="/pages/JwAnVAHDhqE9ZtQDzX6M" %}
[Nodes: Triggers](/rewst-documentation/documentation/automations/nodes/nodes-triggers.md)
{% endcontent-ref %}

{% content-ref url="/pages/27ztelCxRCWn8lmMEtvh" %}
[Nodes: Actions](/rewst-documentation/documentation/automations/nodes/nodes-actions.md)
{% endcontent-ref %}

{% content-ref url="/pages/m2u7tkgGuOEUBPVX6jgL" %}
[Nodes: Data](/rewst-documentation/documentation/automations/nodes/nodes-data.md)
{% endcontent-ref %}

{% content-ref url="/pages/6BuB2iSyfc8RU4hFnGG4" %}
[Nodes: AI](/rewst-documentation/documentation/automations/nodes/nodes-ai.md)
{% endcontent-ref %}


---

# 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://docs.rewst.help/rewst-documentation/documentation/automations/nodes.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.