EIGENN.
docsguidesapichangelogpricingsign in
EIGENN.

Build Your First Workflow

Create a safe manual workflow, connect and validate its blocks, deploy it, run it one time, and confirm the execution.

This guide builds a minimal workflow that has no side effect. After that path completes, extend it with finance actions. Use the same validation and verification loop.

Before You Start

  • Use a Starter or higher workspace.
  • Sign in as a workspace owner.
  • Confirm that workflow creation is within the current entitlement of the workspace. The price configuration lists 3 workflows on Starter and unlimited workflows on Pro and Enterprise.
  • Use a test workspace or a non-production record before you add email, SMS, late-fee, escalation, or integration actions.

1. Create the Definition

  1. Select Workflows in the primary sidebar.
  2. Select Create Workflow.
  3. Enter a clear Name, such as Manual workflow smoke test.
  4. Select the namespace that owns the operation:
    • Payment Follow-up,
    • Promise to Pay, or
    • Settlement.
  5. Enter an optional Description that gives the owner and the expected outcome.
  6. Select Create workflow.

The workflow opens as an inactive version-1 draft with one Trigger block. The normal update flow cannot change the namespace later.

2. Configure a Safe Trigger

  1. Select the Trigger block on the canvas.
  2. Open Editor in the right panel.
  3. Set Trigger to Manual.
  4. Leave Policy and Trigger Filters empty for this first test.

New workflows set the trigger to Invoice Overdue by default. You must change this field before you use the definition as a manual smoke test.

3. Add an End Block

  1. Open Library.
  2. Search for End under Blocks, or locate it there.
  3. Select End to put it near the current view, or drag it to a position on the canvas.
  4. Connect the Trigger source handle to the End target handle.
  5. Select End and confirm that its terminal outcome is correct for a successful test.

The minimal path is now:

Trigger → End

This tests persistence, validation, activation, the queue, execution state, and replay. It does not send a message or change a financial record.

4. Save and Examine the Draft

The editor autosaves 1.5 seconds after a change. Wait for Saved in the header, or use Command+S on macOS or Control+S on Windows and Linux.

If the header shows Save failed, keep the page open and restore connectivity before you continue. A run or a deployment also requests an immediate save. Do not use that request in place of a fix for a visible save error.

5. Validate and Deploy

  1. Select Deploy.
  2. Expand Validation.
  3. Confirm that no check failed.
  4. Select Deploy in the sheet.
  5. Confirm that the editor badge changes from Draft to Published.

Eigenn can block deployment for a missing trigger, an orphaned block, a cycle, an invalid edge, an unmapped decision branch, or an invalid block configuration. A warning alone does not block deployment. Read the warning before you continue.

Activation is the current deployment operation. It makes the saved definition active. It does not create a separate artifact for each environment.

6. Run One Time

  1. Select Run one time.
  2. Confirm that the console opens.
  3. Watch the canvas overlay and the console events.
  4. Do not select Run again when Eigenn queues the first request.

The editor sends a manual trigger with empty trigger data and no idempotency key. Each selection can create a separate execution.

When the editor tracks an active run, Run becomes Stop. Select Stop only when you want to cancel that run.

7. Confirm the Execution

  1. Open Workflows → Executions.
  2. Select Refresh if the run is not visible yet.
  3. Find the execution by workflow, trigger, and start time.
  4. Open Execution Details.
  5. Confirm that the state reaches Completed.
  6. Review Execution Graph and Execution Replay.
  7. Confirm that the Trigger and End steps are present.
  8. Confirm that no failure card appears.

If Eigenn turns off live updates, reload the page and use the persisted steps.

8. Extend the Workflow Carefully

After the minimal run succeeds:

  1. Examine Executions for any run still Waiting or Running.
  2. Deactivate the workflow from its actions menu before a major structural edit.
  3. Add one block at a time from Library.
  4. Select each block in Editor.
  5. Complete the necessary settings for the block.
  6. Reconnect the path.
  7. Delete the orphaned blocks.
  8. Wait for Saved.
  9. Open Deploy.
  10. Examine the validation.
  11. Deploy the workflow again.
  12. Run the workflow with a test record.
  13. Confirm the side effect in the system that owns the record.

Useful visible blocks include Send Email, Send SMS, Notify Team, Apply Late Fee, Escalate, Decision, Router, Loop, Parallel, Subflow, Wait, and Pause.

Select Wait or Pause with care

  • Use Wait for a time-based delay.
  • Use Pause when a person must review and act.

Read Workflow Pauses before you use a human checkpoint. The current web resume action changes the checkpoint record. It does not prove that Eigenn queued the execution continuation.

Useful Editor Shortcuts

  • Command+Z or Control+Z: undo
  • Command+Shift+Z or Control+Shift+Z: redo
  • Command+Shift+D or Control+Shift+D: duplicate one selected block
  • Delete or Backspace: delete the selection
  • Shift+L: auto-layout
  • Command+Shift+F or Control+Shift+F: fit to view
  • Command+Enter or Control+Enter: run or stop

Troubleshoot

Create workflow is unavailable

Confirm Starter or higher, the workspace-owner role, current billing write access, and the configured workflow entitlement of the workspace.

Deploy reports an orphan

Connect every block into the path. Eigenn treats a block that has no input edge or output edge as orphaned. A single Trigger by itself is also orphaned.

Run is not available

The definition is not active. Resolve the validation and deploy it first.

The workflow completed but no business action happened

The minimal Trigger-to-End test has no side effect by design. Add one action, configure it, deploy it again, and confirm it with a test record.

The version remains v1

Autosave and activation in the current generic Workflow Studio do not increase the version that Eigenn shows.

An AI proposal changed too much

The wand applies a successful proposal immediately. Copilot waits until you accept the proposal. Both apply as one document change that you can undo. Use Command+Z or Control+Z before more edits, then examine the full graph.

Next Steps

  • Workflows
  • Workflow Executions
  • Workflow Pauses
  • Monitor and Recover Workflows

Build and Review a Forecast

Establish the cash baseline, add explicit assumptions, and interpret uncertainty without a mix-up of forecast and actuals.

Configure Assistant Operations

Set team automation defaults, give Assistant business context, create proactive controls, and keep a person in control of consequential actions.

On this page

Before You Start1. Create the Definition2. Configure a Safe Trigger3. Add an End Block4. Save and Examine the Draft5. Validate and Deploy6. Run One Time7. Confirm the Execution8. Extend the Workflow CarefullySelect Wait or Pause with careUseful Editor ShortcutsTroubleshootCreate workflow is unavailableDeploy reports an orphanRun is not availableThe workflow completed but no business action happenedThe version remains v1An AI proposal changed too muchNext Steps

Eigenn docs

current product

Overview
Overview
OverviewAccount PreferencesAssistant AutomationAssistant Command CenterBank ConnectionsBilling and UsageBudgets and ForecastCommand CenterCustomer LifecycleCustomer RecordsCustomersDeveloper PlatformDocument Processing and ExtractionDocument VaultFinancial Analytics and ReportsFinancial OverviewInvoice InsightsInvoice ProductsInvoicesMarketplace IntegrationsNotifications and BrandingOnboarding and SupportOverviewReceivablesReceivables AnalyticsReceivables ControlsSecurity and AccessSettings OverviewStress TestsTeams and OrganizationsTone Profiles and ExperimentsTransaction Categories and RulesTransactionsWeekly Finance RitualWorkflow ExecutionsWorkflow PausesWorkflowsWorkspace Inbox and Approvals
OverviewBuild and Review a ForecastBuild Your First WorkflowConfigure Assistant OperationsConfigure Notifications and BrandingConfigure Receivables ControlsConnect Transaction RecordsCreate and Manage CustomersCreate and Send InvoicesDeveloper API SetupFirst Cash ReviewInvoice Collection WorkflowMaintain Transaction RulesManage Security and BillingManage Team AccessManage the Invoice LifecycleMCP WorkflowsMonitor and Recover WorkflowsOrganize and Share DocumentsProcess Inbox ItemsReconcile and Categorize TransactionsReview a Customer Finance RecordRun a Finance Operating ReviewRun a Receivables Tone ExperimentRun a Runway Stress TestRun Your First Command Center ReviewSet Up a WorkspaceTroubleshoot Account AccessWebhook DeliveryWeekly CFO Review
OverviewIntegrationsMCPSDKsWebhooks
OverviewAuthenticationBank Accounts APICustomers APIErrorsForecasts and Stress Tests APIInvoice Payments APIInvoices APIPaginationRate LimitsRemote Tracker API StatusTracker Categories APITracker Entries and Timers APITracker Projects APITransactions APIWebhooks API StatusWorkflows API Status
Overview
Overview