Node catalog
Nodes are the tools you build an AI Agent with. You add them to the flow from the Nodes library in the canvas, connect them in order, and each one does a single job — start the flow, read a file, extract data, call an external system, branch on a condition, route work to a person, or mark an item complete.
Detailed setup, configuration fields, and examples for each node live on the category pages linked in each section below. Only Available nodes have setup guidance.
Triggers
Every flow starts with exactly one trigger. The trigger starts the flow, ingests the initial input, and injects it as normalized data for the nodes that follow. See Configure triggers for setup and configuration.
| Node | What it does | Inputs → Outputs | Related use cases | Status |
|---|---|---|---|---|
| Manual File Upload | Start a flow by uploading one or more files by hand | Files you upload → the files and a count, available to downstream nodes | On-demand processing; testing any agent | Available |
| Outlook Trigger | Start a flow when a matching email arrives in a connected mailbox | A filtered inbound email → the message and its attachments | Triage and Routing; any email-driven process | Available |
| API Trigger | Start a flow from another system via the Bevaya API | — | Intake triggered from an existing system | Available |
| Recurring Schedule or Timer | Start a flow on a schedule | — | — | Coming Soon |
| SFTP Trigger | Start a flow when files arrive over SFTP | — | — | Coming Soon |
Apps
Bevaya has a growing set of native app nodes ready to use out of the box, and you can connect to virtually any other application via HTTP request using the HTTP node. See App integration nodes for setup and configuration.
| Node | What it does | Inputs → Outputs | Related use cases | Status |
|---|---|---|---|---|
| Outlook: Auth | Authorize the connection to an Outlook mailbox | Connection settings → an authorized session the other Outlook nodes use | Any email-driven process | Available |
| Download Outlook Email | Retrieve an email's contents and attachments | A message reference (from the Outlook trigger) → the email body and its attachment files | Triage and Routing | Available |
| Send Outlook Email | Send an email from the connected mailbox | Recipients, subject, and body → a send confirmation | Acknowledgements; routing correspondence | Available |
| Mark Outlook Email as Read | Mark a message as read | A message reference → confirmation | Inbox management within a flow | Available |
| Move Outlook Email | Move a message to another folder | A message reference and a destination folder → confirmation | Inbox management within a flow | Available |
| Move Outlook Email to Folder | Move a message to a named folder | A message reference and a folder name → confirmation | Inbox management within a flow | Available |
| Search for a Guidewire Claim | Look up an existing claim in Guidewire | Search criteria → matching claim record(s) | Claims processing flows | Available |
| Create a Guidewire Claim | Create a claim record in Guidewire | Claim field values (often from extraction) → the created claim and its identifier | Claims processing flows | Available |
| Update a Guidewire Claim | Update an existing claim in Guidewire | A claim identifier and field values → the updated claim | Claims processing flows | Available |
Utilities
Utility nodes handle the general-purpose work inside a flow — preparing files, checking values, calling APIs, running custom logic, and routing work to a person. See Utility nodes for setup and configuration.
| Node | What it does | Inputs → Outputs | Related use cases | Status |
|---|---|---|---|---|
| Read Files | Prepare ingested files so later nodes can process them | The ingested files → normalized documents ready for extraction | Most document flows | Available |
| Field Validation | Check extracted field values against rules | Fields and validation rules → a pass/fail result per rule, used to branch or flag | Document validation flows | Available |
| Review | The Agent pauses and asks a person to review or approve the work item | The item and the fields to review → the reviewed, approved, or corrected result | Any flow with human-in-the-loop review | Available |
| HTTP | Call an external HTTP API | Request configuration (URL, method, headers, body) → the API response, available downstream | Custom integrations | Available |
| HTTP File Upload | Upload a file to an external HTTP endpoint | A file and the endpoint configuration → the upload response | Custom integrations | Available |
| Custom Code Blocks | Run a custom code snippet for logic the built-in nodes don't cover | Data from upstream nodes → the value the code returns | Custom transformations | Available |
Actions
Action nodes change the state of the work item itself. See Action nodes for setup and configuration.
| Node | What it does | Inputs → Outputs | Related use cases | Status |
|---|---|---|---|---|
| Complete | Mark the work item complete to signal that processing has finished | The current item → the item marked complete | The final step of most flows | Available |
Controls
Control nodes shape the path execution takes through a flow — branching and looping. See Control nodes for setup and configuration.
| Node | What it does | Inputs → Outputs | Related use cases | Status |
|---|---|---|---|---|
| If | Split the flow into two paths based on a single condition | A condition over flow data → execution continues down the true or false branch | Routing by document type or value | Available |
| Switch | Route the flow down one of several branches by matching conditions | A set of conditions → execution continues down the first matching branch | Routing by document type or value | Available |
| For Loop | Repeat a set of nodes once for each item in a collection | A collection → the loop body runs for each element | Processing multiple documents or line items | Available |
InsurGPT
InsurGPT nodes apply Bevaya's insurance-trained document intelligence — segmenting page streams, extracting structured data, and generating insights from documents. See InsurGPT nodes for setup and configuration.
| Node | What it does | Inputs → Outputs | Related use cases | Status |
|---|---|---|---|---|
| Split Documents | Segment a multi-document page stream into separate documents | A page stream → the individual documents it contains | Multi-document intake flows | Available |
| InsurGPT: Custom | Extract structured data (such as FNOL fields) from insurance documents and classify the document type | Documents and the fields or prompt to extract → the extracted fields and a document classification | Triage and Routing; document extraction flows | Available |
| Insights | Generate business insights or a summary from documents | Documents and a prompt → the generated insights | Claim File Summarization | Available |
Sticky notes
A Sticky Note is an annotation you place on the builder canvas to leave a comment or label for the people building the flow. It is not a processing step, does not run as part of the flow, and is added from the canvas rather than the Nodes library.
Where to go next
- Configure triggers — set up the trigger that starts your flow.
- App integration nodes — connect to Outlook, Guidewire, and other external systems.
- Utility nodes — prepare files, validate fields, call APIs, and route work to a person.
- Action nodes — change the state of the work item.
- Control nodes — branch and loop within a flow.
- InsurGPT nodes — segment, extract, and summarize documents.
- Create an AI Agent — assemble nodes into a working flow.
- Build AI Agents — the full build lifecycle.