Nodes

Nodes are the building blocks of a flow. Each node performs a specific task — such as calling a cloud API, transforming data, or sending a notification — and passes its output to the next node in the sequence.

After adding a trigger to start your flow, use the plus icon (+) to add nodes. You can chain as many nodes as needed to build your automation.

AWS node Interacts with AWS services directly from your flow. Browse or search for actions across AWS services, configure parameters, require manual approval before execution, and add waiters to pause until a resource reaches a desired state.

GCP node Interacts with Google Cloud services directly from your flow. Browse or search for actions across Google Cloud services, configure parameters, and require manual approval before execution.

HTTP node Makes HTTP requests to external APIs or services. Use it to integrate with third-party systems, fetch data from REST endpoints, or send data to webhooks. Supports custom headers, query parameters, and request bodies.

Filter node Controls which data continues through the flow by evaluating conditions against fields from previous nodes. Use filters to narrow down results — for example, keeping only EC2 instances in a specific region.

Branch node Implements if/else branching logic in a flow. Evaluates a condition and routes execution down different paths based on whether the condition is true or false.

Transform node Reshapes or reformats data between nodes. Use it to rename fields, extract nested values, combine fields, or restructure data to match what the next node expects.

Date/time node Performs date and time calculations on timestamp fields. Add or subtract time intervals, convert between formats, or compute differences — useful for scheduling, filtering by time windows, or normalizing timestamps across APIs.

Notification node Sends data from your flow to email or Slack. Use it to alert stakeholders about cost anomalies, share scheduled reports, or deliver summaries of flow results to the relevant team.

Threads node Creates issues in your configured ITSM tool — such as Jira or Linear — directly from your flow. Automatically log tickets with relevant details when your flow detects an event that needs attention.

LLM node Processes data using large language models powered by OpenAI and AWS Bedrock. Provide a natural-language prompt to interpret, summarize, classify, or transform data from previous nodes — without writing complex flow logic.

Policy node Evaluates resources against a policy — a set of compliance rules for a specific resource type. Use it in scheduled flows to check whether resources (for example, S3 buckets or VMs) meet your organization's standards, and take action if they don't.

SQL node Runs SQL queries against your billing data in DoiT Cloud Intelligence. Useful for data-driven decisions like identifying expensive resources, finding cost trends, or building custom reporting logic within your flow.

Datastore node Stores, retrieves, and updates structured data in a managed data store. Use it to persist data across flow executions, build lookup tables, or track resource state over time — without connecting to an external database.

Code node Runs custom JavaScript or Python code in a secure sandboxed environment. Use it for complex transformations, calculations, or logic that goes beyond what other nodes offer.

You can also add a template — a pre-built group of nodes — to quickly set up common patterns.