EIGENN.
docsguidesapichangelogpricingsign in
EIGENN.

Configure Assistant Operations

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

This guide sets up the operational layers around Assistant. Start with team-wide automation defaults. Then add business context, goals, watchers, and scheduled work. Turn on Autopilot only after the approvals process works.

Prerequisites

  • You can sign in to an Eigenn team workspace.
  • The necessary bank, accounting, invoice, payment, or communication apps have a current connection.
  • Your team chose an approvals owner.
  • You know which outward actions, if any, can run before Assistant asks you.

1. Record Team Automation Preferences

Open Settings → Automation.

Webhook Configuration

  1. Choose Retry Attempts: No retries, 3 retries, or 5 retries.
  2. Choose Timeout: 10 seconds, 30 seconds, or 60 seconds.
  3. Choose Save in this section.

Three retries and a 30-second timeout are the saved defaults.

Data Sync

  1. Turn Enable Auto Sync on or off.
  2. Choose Sync Frequency, from Every 3 hours through Every 24 hours in three-hour steps.
  3. Choose Save in this section.

Automatic sync every three hours is the saved default.

Workflow Limits

  1. Set Max Concurrent Workflows to 2 workflows, 4 workflows, or 6 workflows.
  2. Set Workflow Timeout to 15 minutes, 30 minutes, or 60 minutes.
  3. Choose Save in this section.

Two concurrent workflows and a 30-minute timeout are the saved defaults.

Slack Notifications

  1. Paste a valid inbound webhook URL into Slack Webhook URL.
  2. Turn on Enable Slack Notifications.
  3. Choose Save in this section.

This is the team-wide automation notification setting. It does not make the Slack choice on an individual watcher deliver watcher crossings. Current watcher crossings appear in Workspace → Approvals.

At this time, these settings record team preferences. They do not yet change webhook delivery, integration sync, workflow execution, or Slack notification behavior. Check the feature that owns the behavior. A successful Save confirms storage, not enforcement or delivery.

2. Add Business Context

Open What I know about your business in the Assistant operation pages.

  1. Enter Industry.
  2. Choose the month under Fiscal year starts.
  3. Enter Base currency.
  4. Describe Primary goals and Focus areas.
  5. Add permanent context under Notes.
  6. Choose Save.
  7. Wait for Business profile saved.

Use facts that are stable across many conversations. Keep one-off scenario assumptions in the prompt or forecast instead of the business profile.

3. Create the First Goal

Open Goals.

  1. Choose New goal.
  2. Enter a label such as “Keep runway above 6 months.”
  3. Enter the metric name, for example runway.
  4. Choose the direction and target.
  5. Add a due date when the goal has a deadline.
  6. Choose Create goal.

Use the status selector to mark the goal Active, Met, Missed, or Archived as it resolves. At this time, the visible progress bar shows status. It does not show a metric percentage that Eigenn calculates continuously.

4. Create a Supported Watcher

Open Watchers.

  1. Choose New watcher.
  2. Describe what the alert means for the business.
  3. Enter a supported metric such as runway, runway_projected, cash_projected, breach_probability, overdue_ar, promises_at_risk, or dso.
  4. Choose is below, is at or below, is above, is at or above, or equals.
  5. Enter a numeric threshold.
  6. Choose Daily, Weekly, or Monthly.
  7. Keep In-app as the operational channel for current delivery.
  8. Choose Create watcher.

Use Pause when the rule is temporarily irrelevant. Use Delete when the rule must no longer exist.

You can also create a daily Runway watcher from the eye icon on Overview. That control pre-fills the current value. It appears only for supported metrics.

5. Create a Scheduled Prompt Carefully

Open Scheduled runs.

  1. Choose New scheduled run.
  2. Give the run a clear name.
  3. Write a self-contained prompt with its time range and the output that you want.
  4. Leave Agent (optional) blank unless you know the supported agent identifier.
  5. Choose Hourly, Daily, Weekly, or Monthly.
  6. Choose the requested delivery channel.
  7. Choose Create scheduled run.

Use Pause, Enable, and Delete to control the saved run.

Current scheduled prompts record a queued request for the period. They do not yet produce a completed background Assistant response. Slack or email result delivery is not available from this path. Use the row's last status and Workspace → Approvals to distinguish a recorded request from completed work.

6. Establish the Human Approval Loop

Open Workspace → Approvals before you turn on Autopilot.

  1. Filter to Open.
  2. Select a proposal.
  3. Read its plain-language action, amount, source context, and cash impact.
  4. Choose Claim to take ownership.
  5. Choose Approve or Reject.
  6. Confirm that approved work reaches Done or Failed.
  7. Test Undo on a reversible, non-production example while its undo window is open.

Assign a person to check Approved items that did not advance. Approval records intent. A separate process runs the action.

7. Examine Action Bundles

Open Action Bundles when a projected cash-floor watcher creates grouped work.

  1. Read the total cash impact and runway preview.
  2. Examine every line independently.
  3. Use Approve all only when every line is acceptable.
  4. Otherwise use Approve or Drop on individual lines.
  5. Return to Workspace → Approvals to follow execution status.

The runway preview can be absent when the burn history is not enough, or when the business is net positive. Never infer a zero impact from a missing preview.

8. Set Up Autopilot Last

Open Autopilot.

  1. Leave Enable autopilot off while you draft the policy.
  2. Enter exact, comma-separated action identifiers under Allowed actions (comma-separated action ids).
  3. Set Max amount.
  4. Keep a cap unless a reviewed reason exists to remove it.
  5. Set a positive whole-number Undo window (minutes).
  6. Turn on Enable autopilot.
  7. Choose Save.

Start with one reversible action. Autopilot examines an action only when the policy is on. The identifier must be an exact match. Eigenn must know the estimated amount. That amount must be within the cap. The action must not be irreversible.

An empty Max amount means no monetary cap. It does not weaken the exact allowlist or the irreversible-action block.

9. Confirm the Audit Trail

Open Autopilot audit after the first autonomous action.

Confirm that the entry includes:

  • a clear summary,
  • the action identifier,
  • the reason,
  • any failure state, and
  • whether the undo deadline remains open.

Use Workspace → Approvals for the real Undo control. The audit page is read-only.

10. Run a Controlled Acceptance Check

Before you decide that the configuration is complete:

  1. Ask Assistant a read-only question that uses connected data.
  2. Create one supported watcher with a threshold that you can safely observe.
  3. Confirm that a crossing appears in Workspace → Approvals at most one time for its period.
  4. Approve or reject a harmless proposal.
  5. Confirm that the status reaches a terminal state.
  6. Confirm one allowlisted reversible action and its audit entry when Autopilot is on.
  7. Check that an unlisted or over-cap action still waits for human review.

What Success Looks Like

The setup of Assistant operations is complete when:

  • all four Settings → Automation sections show the preferences that you set, and the team knows that they are not yet enforcement controls,
  • you saved stable business context,
  • goals and watchers use recognized metrics,
  • the approvals queue has a named operator,
  • the team understands that scheduled prompts record queued requests, not completed work,
  • Autopilot is narrow, capped, reversible, and tested, and
  • the team confirms terminal status and audit evidence, and does not assume completion.

Troubleshoot

A section in Settings did not retain my changes

Each section saves independently. Return to that section. Check the values. Choose the Save button of that section.

Auto Sync is on but Assistant data is stale

The saved preference does not yet enforce the integration sync schedule. Confirm that Marketplace shows the integration as connected. Run the supported refresh or sync workflow of the feature that owns it. Examine the detailed product page.

A metric name saves but never evaluates

The Watchers form accepts text. Proactive checks can evaluate only supported metrics. Replace the name with a canonical metric that this guide lists.

A watcher selected Slack or Email but only appears in Approvals

That is the current behavior. Slack and email watcher delivery is not available yet.

A scheduled run has no completed answer

At this time, scheduled prompt runs record queued requests. Read Workspace → Approvals. Do not treat the saved schedule or the queued status as delivered output.

Autopilot stays inactive after a save

Confirm that Enable autopilot is on. Confirm that at least one exact action identifier is present. Confirm that the amount is within the cap. Confirm that the action is reversible. Ask support to confirm that the workspace has proactive processing turned on.

Undo does not appear

Undo appears only for Done or Executing actions with an unexpired undo deadline. You cannot undo an action without a window, an expired action, or a non-executed proposal.

An approval is stuck

Check Approved, Executing, and Failed. Execution is separate from approval. Contact support when an approved item does not advance and proactive processing must be active.

Related Docs

  • Assistant Automation
  • Assistant Command Center
  • Run Your First Command Center Review
  • Overview
  • Webhook Delivery
  • Integrations

Build Your First Workflow

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

Configure Notifications and Branding

Set personal alert channels, confirm a custom sender domain, and test which brand settings reach customer output.

On this page

Prerequisites1. Record Team Automation PreferencesWebhook ConfigurationData SyncWorkflow LimitsSlack Notifications2. Add Business Context3. Create the First Goal4. Create a Supported Watcher5. Create a Scheduled Prompt Carefully6. Establish the Human Approval Loop7. Examine Action Bundles8. Set Up Autopilot Last9. Confirm the Audit Trail10. Run a Controlled Acceptance CheckWhat Success Looks LikeTroubleshootA section in Settings did not retain my changesAuto Sync is on but Assistant data is staleA metric name saves but never evaluatesA watcher selected Slack or Email but only appears in ApprovalsA scheduled run has no completed answerAutopilot stays inactive after a saveUndo does not appearAn approval is stuckRelated Docs

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