AutoBridge

Automation Builder


The Automation Builder is a visual, no-code workflow tool that lets you create event-driven processes across GovAssist. Automations run automatically when conditions are met — no developer involvement required.

Overview

FeatureDescription
Visual Flow EditorDrag-and-drop automation design
Trigger Types10+ event types to start workflows
Action LibraryRecord operations, email, AI, and more
Conditional BranchingIF/ELSE logic with nested conditions
Loop SupportRepeat actions for batch processing
Run HistoryExecution logs with success/failure tracking
Folder OrganizationGroup automations by category

Before You Start

Ensure the following are in place before building automations:

  • User has Automation Builder module permissions
  • Source entities exist for record-based triggers
  • Forms are created if using form submission triggers
  • Email templates are configured if using send-email actions

How Automations Work

Every automation follows this structure:

[Trigger] → [Action 1] → [Action 2] → ... → [End]
                 |
          [Branch Logic]
             /    \
         [Yes]    [No]

Initial Nodes

When you create a new automation, the canvas starts with three nodes:

NodePurpose
Trigger NodeThe event that starts the workflow
Action NodeThe first operation to perform
End NodeMarks workflow completion

Run History Statuses

StatusDescription
AllShow all runs
SuccessCompleted without errors
FailedEncountered an error during execution

Trigger Types

Navigate to Automation Builder → New Automation → Select Trigger to choose how your automation starts.

TriggerDescription
Form SubmittedWhen a user submits a specific form
Record CreatedWhen a new record is added to an entity
Record UpdatedWhen an existing record is modified
Record DeletedWhen a record is removed
Record Matches ConditionWhen a record meets defined rules
Process Evaluation CompletesWhen an AI evaluation finishes
Scheduled EventOn a time-based schedule
Webhook ReceivedWhen an external webhook is received
SharePoint EventWhen a SharePoint event occurs
Incoming CallWhen a phone call is received

Schedule Trigger Configuration

For time-based automations, configure the following:

FieldDescription
Interval TypeFrequency: Minutes, Hours, Days, Weeks, Months, or One-Time
Interval ValueHow often to repeat
Week DaysSpecific days (for weekly schedules)
Month DaysSpecific dates (for monthly schedules)
Start DateWhen to begin
Execution TimeTime of day to run
Time ZoneTimezone for scheduling

Action Types

Navigate to Automation Flow → Add Action → Select Action to add steps to your workflow.

ActionDescription
Create RecordCreate a new record in an entity
Update RecordModify an existing record
Delete RecordRemove a record
Find RecordsSearch for records matching criteria
Send EmailSend an email notification
Autofill with AIUse AI to populate fields automatically
AI-Driven ActionAI content generation with custom prompts
Extract from DocumentPull data from uploaded documents
Extract from WebsiteScrape data from web pages
FormulaCalculate values using field references
IF/ELSE ConditionBranch the workflow based on logic
RepeatLoop through a set of actions
WaitPause until a condition is met

AI-Driven Action Configuration

FieldDescription
EntityEntity for context
ModelAI model: GPT-4o, GPT-4.1, GPT-4o mini, o3
AI Action Typeai_criteria_action (evaluate) or custom (prompt-based)
Target FieldField to write AI output into
PromptInstructions for the AI
TemperatureRandomness 0-1 (default: 0.2)

Condition Builder

Conditions control when branches fire and when triggers activate.

Operators

OperatorDescription
is / is notExact match or exclusion
greater than / less thanNumeric comparisons
in / not inValue within a list
containsString contains (case-sensitive)
contains (case-insensitive)String contains, ignoring case
betweenValue falls in a range
is null / is not nullField is empty or populated
min length / max lengthString length constraints

Conjunctions

ConjunctionBehavior
AndAll conditions must be true
OrAny condition must be true

Branch Logic

Branches route workflow execution based on conditions.

Branch TypeDescription
IFPrimary condition branch
ELSE IFAdditional condition branches
ELSEFallback when no conditions match

Branch Limits

Each automation supports up to 10 branches. At least one IF branch is required. ELSE branches act as the default fallback path.


Dynamic Fields

Fields that support dynamic value insertion (via the + button):

Field TypeSupports Dynamic Values
TextYes
Text AreaYes
Rich TextYes
NumberYes
EmailYes
URLYes
FileYes

Formula Syntax

Formulas use {FieldName} syntax to reference record values.

Trigger character: { (open brace)

Example: {Amount} * {Quantity} * 0.1


Permitting Workflow Examples

Application Submission

Trigger: Form Submitted Use case: When an applicant submits a permit application

[Form Submitted]
  → [Create Record: Permit Entity]
  → [Update Status: "Submitted"]
  → [Send Email: Applicant — Application Received]
  → [Send Email: Reviewer — New Application]
  → [End]
StepActionConfiguration
1TriggerForm: Permit Application
2Create RecordEntity: Permits, map form fields
3Update RecordStatus = "Submitted"
4Send EmailTemplate: Application Received
5Send EmailTemplate: New Application, to Reviewer

Multi-Department Review Routing

Trigger: Record Created Use case: Route new permit to appropriate review departments

[Record Created: Permit]
  → [AI Action: Determine Required Reviews]
  → [IF Zoning Required] → [Update: Zoning Status = "Pending"]
  → [IF Building Required] → [Update: Building Status = "Pending"]
  → [IF Health Required] → [Update: Health Status = "Pending"]
  → [Send Email: Assignment Notifications]
  → [End]

Expiration Warning (Scheduled)

Trigger: Scheduled Event Use case: Daily check for permits expiring in 30 days

[Schedule Trigger: Daily at 8:00 AM]
  → [Find Records: Permits expiring in 30 days]
  → [Repeat for each record]
      → [Send Email: Expiration Warning]
      → [Update Record: Warning Sent = true]
  → [End]

Schedule settings:

FieldValue
Interval TypeDays
Interval Value1
Execution Time08:00
Time ZoneAmerica/New_York

AI-Powered Determination

Trigger: Process Evaluation Completes Use case: After AI evaluates a permit application

[Process Evaluation Completes]
  → [AI Action: Evaluate Compliance]
  → [IF Determination = "Approved"]
      → [Update Status: "AI Approved"]
      → [Create Record in Approvals Entity]
  → [ELSE IF Determination = "Denied"]
      → [Update Status: "AI Denied"]
      → [Send Email: Denial Notification]
  → [ELSE]
      → [Update Status: "Manual Review Required"]
      → [Send Email to Reviewer]
  → [End]

Testing and Publishing

1

Build Your Automation

Configure the trigger, add actions, and set up any branches or conditions.

2

Test the Automation

Click Test in the automation editor. Provide sample trigger data and review step-by-step execution.

3

Publish

When testing passes, publish the automation to make it live. Unpublished automations will not fire.

4

Monitor Run History

Go to Automation → Run History to view execution logs filtered by All, Success, or Failed.


Troubleshooting

Trigger Not Firing

Common Cause

The automation must be published to fire. Draft automations are inactive.

Check the following:

  1. Automation is published (not draft)
  2. Trigger conditions are correctly configured
  3. Entity or Form IDs are valid
  4. User has permissions on the source entity

Action Fails with "Record Not Found"

  1. Verify the Record ID reference is valid
  2. Confirm the record exists in the entity
  3. Check that you're using the correct field for record identification

Email Not Sending

  1. Confirm the email template exists
  2. Verify the recipient field is populated
  3. Ensure the email service is configured
  4. Check that recipient addresses are valid

Branch Conditions Not Evaluating

  1. Field names must match exactly (case-sensitive)
  2. Use operators appropriate for the field type
  3. Verify values are in the correct format
  4. Double-check AND/OR logic

Next Steps