Titan AI is in beta. Features and behavior may change, and some functionality is still in development. To share feedback or report an issue, complete the support form.
The workflow editor is where you build a workflow. You add blocks to a canvas, connect them in the order you want them to run, and configure each one as needed. To open the editor, go to Automations > Workflows and select a workflow, or select + New Workflow to start a new one.
Areas of the editor
The editor has the following areas.
| Area | What it does |
| Toolbar (top) | Shows when the workflow was last saved, and holds undo and redo, Auto-layout, the Editor and Viewer toggle, Dry run, and Save. Select Viewer to open the workflow as read-only, so you can review it without changing it. Select Editor to return to editing. |
| Blocks panel (left) | Lists every block you can add, grouped by type with a count for each group. Search for a block by name, or scroll the list. Drag a block onto the canvas to add it. |
| Canvas (middle) | Place blocks and connect them here. A connection sets the order the blocks run in. Zoom in and out, fit the workflow to the view, and lock the canvas from the controls in the lower left. The zoom level and the number of selected blocks appear in the lower right. |
| Configuration panel (right) | Configure the selected block, including the values it accepts as input. When nothing is selected, it prompts you to select a block. |
| Status bar (bottom) | Shows counts of errors, warnings, and run logs for the workflow you're editing. You must fix an error before you can save; a warning doesn't block saving. See Workflow errors and warnings for what raises each one, and Test and save a workflow below for what appears in the logs. |
Arrange the canvas
Select Auto-layout to arrange every block on the canvas into a top-to-bottom flowchart. You do not have to position blocks by hand.
Auto-layout changes only where blocks sit on the canvas. It does not add, remove, or reconnect blocks, nor does it change the order in which they run. Because it does not change the workflow, it does not mark the workflow as unsaved, and undo and redo do not reverse it. Select Auto-layout again to rearrange.
Block positions are not saved with the workflow. When you open a saved workflow, the canvas is automatically arranged for you, so an arrangement you set by hand does not carry over to your next session.
Available blocks
The following blocks are available today. Titan adds blocks over time, so check the Blocks panel for the current set.
| Group | Block | What it does |
| Trigger | Event Listener | Starts the workflow when a platform event occurs. Choose an event object — Questionnaire, Vendor Intake, Vendor Relationship, or Security Event (Vendor Outreach) — and an action, such as "Sent to vendor," "Vendor intake submitted," "Risk Level changed," or "Confirmed breach on monitored vendor," plus an optional filter. |
| Trigger | Manual | Starts the workflow on demand when you select Run. It can prompt you for input values at launch. |
| Trigger | Schedule | Starts the workflow on a recurring schedule you configure, hourly, daily, every weekday, weekly, monthly, or a custom cron expression, with a timezone and time of day. |
| Control flow | End | Ends an execution path and records an outcome and a message. Every path finishes with an End block. |
| Control flow | Decision Switch | Routes the workflow down a branch based on a condition. It evaluates branch conditions in order, and the first match wins. If nothing matches and there's no catch-all branch, the run fails. |
| Custom | Call Another Workflow | Runs another published workflow, optionally waiting for it to finish. When you wait, the called workflow's outcome and returned data become available to later blocks; when you don't, it runs independently and continues after this workflow ends. |
| Data | Get Data | Extracts values from a JSON source, such as a prior block's result, into named variables that later blocks use. |
| Monitoring | Get Findings | Retrieves a vendor's findings that match one of your organization's saved filters from Open Findings, scoped to that vendor and capped at a result limit you set. |
| Monitoring | Get Security Event | Retrieves the following breach details for a confirmed security event on a monitored vendor: a summary, what data was leaked, the breach type, and its tier. Pairs with an Event Listener trigger set to Security Event (Vendor Outreach) > Confirmed breach on monitored vendor. |
| Notifications | Send Email | Sends an email to one recipient using the subject and body you define. |
| Questionnaires | Get Questionnaire Template | Loads a due diligence questionnaire template from your organization's template library, for use by a Create Questionnaire block. |
| Questionnaires | Create Questionnaire | Creates a questionnaire for a vendor from a template, without sending it. Creating and sending are separate blocks, allowing a workflow to create a questionnaire, check a condition, and then send it. |
| Questionnaires | Send Questionnaire | Invites recipients to a questionnaire by email, then pauses the workflow for up to 3 days waiting for the vendor to complete it. If it isn't completed in that time, the block times out; wire both outcomes to continue the workflow either way. |
| Questionnaires | Get Questionnaire Status | Reads a questionnaire's current response and due diligence status, and its due date. It does not return the vendor's answers. |
| Questionnaires | Get Questionnaire Results | Reads a questionnaire's questions and the answers submitted for them, with counts of total and answered questions. |
| Vendor | Add Vendor | Creates a vendor record from a domain name, with optional risk level, business impact, and contacts. Lifecycle status starts as New; use Update vendor to change it. |
| Vendor | Get Vendor Details | Retrieves a vendor relationship's attributes. |
| Vendor | List Vendors | Retrieves your organization's vendor relationships, optionally filtered by domain, lifecycle status, risk level, business impact, or monitoring status. Returns up to 500 vendors at a time; compare the total count in the result to see if your portfolio is larger. |
| Vendor | Update vendor | Updates an existing vendor's lifecycle status (for example, from New to Onboarded or Offboarded) and other details such as risk level, business impact, contract dates, and contacts. |
| Vendor | Get Vendor Contacts | Retrieves the contacts on file for a vendor relationship. |
| Vendor Intake | Evaluate Vendor Intake | Reads a submitted vendor intake form: its status, the questions and answers, and the risk level your rule set calculated. Using this block automatically creates five branches already wired to that risk level (Low, Medium, High, Critical, and Otherwise), so you don't need a separate Decision Switch. Typically follows an Event Listener trigger set to Vendor Intake > Vendor intake submitted. |
Test and save a workflow
Select Dry run to preview a workflow before you run it against live vendor data. Dry run walks the workflow's blocks in order without calling any real system; it doesn't create or update records or send email. The walk result, including where it stopped if it hit a problem, appears in the status bar's logs pane.
Select Save to save your changes. The toolbar shows when you last saved the workflow. Use Undo and Redo to step back through your recent edits while the workflow stays open; reopening it clears that history.
Errors and warnings
Titan checks a workflow as you build it and reports what it finds in the status bar. An error means the workflow cannot run as built, and you cannot save until you fix it. A warning means the workflow is valid and you can save it, but something is worth a second look before you run it.
For what raises each one and how to resolve it, see Workflow errors and warnings.