Node catalog reference
This is the compact, definitive list of every node visible in the released builder, grouped by the categories the Nodes library uses: Triggers, Apps, Utilities, Actions, Controls, and InsurGPT. Each entry gives the node's purpose, a short input-to-output summary, and its availability.
For setup, configuration fields, and examples, use the detailed Build pages linked under each category. Only Available nodes have setup guidance; Coming Soon nodes are visible in the library but disabled and cannot be added or configured yet.
Triggers
Every flow starts with exactly one trigger. See Configure triggers and the compact Trigger reference.
| Node | Purpose | Inputs → Outputs | Status |
|---|---|---|---|
| Manual File Upload | Start a flow by uploading files by hand | Uploaded files → the files and a count | Available |
| Outlook Trigger | Start a flow when a matching email arrives | A filtered inbound email → the message and attachments | Available |
| API Trigger | Start a flow from another system via the Bevaya API | — | 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.
| Node | Purpose | Inputs → Outputs | Status |
|---|---|---|---|
| Outlook: Auth | Authorize the connection to an Outlook mailbox | Connection settings → an authorized session used by other Outlook nodes | Available |
| Download Outlook Email | Retrieve an email's contents and attachments | A message reference → the email body and its attachments | Available |
| Send Outlook Email | Send an email from the connected mailbox | Recipients, subject, body → a send confirmation | Available |
| Mark Outlook Email as Read | Mark a message as read | A message reference → confirmation | Available |
| Move Outlook Email | Move a message to another folder | A message reference and destination → confirmation | Available |
| Move Outlook Email to Folder | Move a message to a named folder | A message reference and folder name → confirmation | Available |
| Search for a Guidewire Claim | Look up an existing claim in Guidewire | Search criteria → matching claim record(s) | Available |
| Create a Guidewire Claim | Create a claim record in Guidewire | Claim field values → the created claim and its identifier | Available |
| Update a Guidewire Claim | Update an existing claim in Guidewire | A claim identifier and field values → the updated claim | Available |
Utilities
General-purpose tools for common tasks. See Utility nodes.
| Node | Purpose | Inputs → Outputs | Status |
|---|---|---|---|
| Read Files | Prepare ingested files for later processing | The ingested files → normalized documents | Available |
| Field Validation | Check extracted values against rules | Fields and rules → a pass/fail result per rule | Available |
| Review | The Agent pauses and asks a person to review the item | The item and fields to review → the reviewed/approved/corrected result | Available |
| HTTP | Call an external HTTP API | Request configuration (URL, method, headers, body) → the API response | Available |
| HTTP File Upload | Upload a file to an external HTTP endpoint | A file and endpoint configuration → the upload response | Available |
| Custom Code Blocks | Run a custom code snippet for logic built-in nodes don't cover | Data from upstream nodes → the value the code returns | Available |
Actions
Action nodes change the state of the work item. See Action nodes.
| Node | Purpose | Inputs → Outputs | Status |
|---|---|---|---|
| Complete | Mark the work item complete to signal processing has finished | The current item → the item marked complete | Available |
Controls
Control nodes shape the path execution takes. See Control nodes.
| Node | Purpose | Inputs → Outputs | Status |
|---|---|---|---|
| If | Split the flow into two paths on a single condition | A condition over flow data → the true or false branch | Available |
| Switch | Route the flow down one of several branches | A set of conditions → the first matching branch | Available |
| For Loop | Repeat a set of nodes for each item in a collection | A collection → the loop body runs per element | Available |
InsurGPT
InsurGPT nodes apply Bevaya's insurance-trained document intelligence. AI intelligence is an Admin capability. See InsurGPT nodes.
| Node | Purpose | Inputs → Outputs | Status |
|---|---|---|---|
| Split Documents | Segment a multi-document page stream into separate documents | A page stream → the individual documents | Available |
| InsurGPT: Custom | Classify a document and extract structured fields | Documents and the fields or prompt → extracted fields and a classification | Available |
| Insights | Generate business insights or a summary from documents | Documents and a prompt → the generated insights | Available |
Sticky notes
A Sticky Note is an annotation placed on the builder canvas to leave a comment or label. 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 and Trigger reference — the trigger that starts a flow.
- App integration nodes — connect to Outlook and Guidewire.
- Utility nodes, Action nodes, Control nodes, InsurGPT nodes — detailed configuration by category.
- Create an AI Agent — assemble nodes into a working flow.