Assistant Automation

Configure business context, goals, watchers, scheduled work, approvals, and a deny-by-default Autopilot policy for your team.

Assistant automation turns recurring business questions into team-scoped operating controls. The current model is supervised: Eigenn can monitor thresholds, queue proposed work, group related actions, and record what happened, while operators keep an approval gate around consequential actions.

Prerequisites

Sign in to a workspace with an active team.
Connect and sync the data sources needed by the metric or prompt.
Decide who owns Workspace → Approvals before creating proactive work.
For Slack-related team settings, obtain an incoming Slack webhook URL before enabling notifications.

The settings on these pages apply to the whole team unless the page says otherwise. Coordinate changes with the other operators in the workspace.

Where the Controls Live

Use Settings → Automation for webhook delivery, integration sync, workflow limits, and general Slack notifications.
Use Workspace → Approvals to review, claim, approve, reject, or undo proposed Assistant actions.
Use the Assistant operation pages headed What I know about your business, Goals, Watchers, Scheduled runs, Autopilot, Action Bundles, Decisions, and Autopilot audit for proactive Assistant behavior.

Some deployments do not yet expose every Assistant operation page in the primary navigation. If a named page is unavailable in your workspace, contact your workspace administrator or support rather than guessing a URL.

Team Automation Preferences

Settings → Automation has four independently saved preference sections.

Section	Controls
Webhook Configuration	0, 3, or 5 retry attempts and a 10, 30, or 60 second response timeout
Data Sync	automatic sync on or off, at intervals from every 3 hours to every 24 hours
Workflow Limits	2, 4, or 6 concurrent workflows and a 15, 30, or 60 minute workflow timeout
Slack Notifications	a team incoming-webhook URL and notification switch

New teams default to 3 webhook retries, a 30-second webhook timeout, automatic sync every 3 hours, 2 concurrent workflows, a 30-minute workflow timeout, and Slack notifications off.

Each section has its own Save button. Saving one section does not submit unsaved changes in another section.

Saving these values records the team's preferences. They do not yet change webhook delivery, integration sync, workflow execution, or Slack notification behavior. Verify behavior in the owning feature instead of treating a saved preference as proof that a timeout, interval, concurrency limit, or notification was applied.

Business Context

What I know about your business stores the team facts Assistant should keep in mind:

Industry
Fiscal year starts
Base currency
Primary goals
Focus areas
Notes

Choose Save after editing. Benchmark, insight, and runway analysis can use these facts. They do not replace the live finance records in the workspace, and not every answer will restate them.

Goals

Use Goals for a standing target that a metric should reach or maintain.

Choose New goal.
Enter a plain-language label.
Enter the Metric name.
Choose at or above, above, at or below, below, or equal to.
Enter a numeric Target and optional Due date.
Choose Create goal.

Goals can be marked Active, Met, Missed, or Archived, or deleted. The current Goals page displays the saved rule and lifecycle status. Its progress bar is status-based—full for Met, empty for other statuses—not a live percentage from the metric.

Watchers

Use Watchers for a standing threshold question.

Choose New watcher.
Describe what should be watched.
Enter a supported Metric name.
Choose the condition and numeric threshold.
Choose Daily, Weekly, or Monthly.
Choose In-app, Slack, or Email as the requested channel.
Choose Create watcher.

New watchers are enabled. Use Pause, Enable, or Delete to manage them.

The most useful canonical metric names are:

Metric name	Meaning
`runway`	trailing cash runway in months
`runway_projected`	projected runway low point over the forward horizon
`cash_projected`	projected cash low point
`breach_probability`	probability of a cash breach from a fresh canonical forecast
`overdue_ar`	overdue receivables total
`promises_at_risk`	open payment promises considered at risk when supporting promise data is available
`dso`	trailing days sales outstanding

An unrecognized metric name can be saved, but it cannot be evaluated and will not fire. Prefer the canonical names above or create the watcher from a supported Watch this number control, such as the eye icon beside Runway on Overview.

Threshold crossings are deduplicated by the selected period, so a retry does not create the same proposal twice in one daily, weekly, or monthly window.

Scheduled Runs

Use Scheduled runs to save a recurring Assistant prompt.

Choose New scheduled run.
Enter a name and the complete prompt to run.
Optionally enter an agent identifier; leave it blank for automatic routing.
Choose Hourly, Daily, Weekly, or Monthly.
Choose In-app, Slack, or Email.
Choose Create scheduled run.

Use Pause, Enable, or Delete to manage a run. The row shows its schedule, requested channel, optional agent, and last status when available.

Current scheduled prompt runs record a deduplicated queued request for review; they do not yet produce a completed background Assistant answer. The selected delivery channel is stored, but Slack and email result delivery are not available from this path yet. Treat queued as confirmation that the request was recorded, not as proof that the prompt ran or that a message was delivered.

Workspace Approvals

Watchers and other Assistant operations can create proposed actions in Workspace → Approvals.

Start with Open.
Select a proposal and review the action, amount, customer or invoice context, tone, cash impact, and tool identifier.
Choose Claim when you are taking ownership.
Choose Approve or Reject.
Follow the status through Approved, Executing, Done, Failed, Rejected, or Undone.
Use Undo only when a completed or executing action still has an open undo window.

Approval records the operator's decision. Execution happens separately, so an Approved status is not the same as Done. Confirm the terminal status before assuming a message, fee, escalation, or connected-app action happened.

Action Bundles

Action Bundles group proposed responses to a projected cash-floor breach. A bundle can contain collections work, drafted communication, and bill-timing decisions.

Choose Approve all to approve every still-proposed line.
Choose Approve on an individual line to keep the decision narrow.
Choose Drop to reject one line without changing its siblings.
Review the read-only runway impact before approving when it is available.

The runway preview is omitted when there is not enough burn history or when runway is unbounded. It is a planning projection, not an executed cash change.

Autopilot

Autopilot is off by default and denies by default.

To enable it:

Add exact, comma-separated values to Allowed actions (comma-separated action ids).
Set Max amount, or leave it blank only when you intentionally want no numeric cap.
Set a positive whole-number Undo window (minutes).
Turn on Enable autopilot.
Choose Save and confirm Autopilot policy saved.

An action is eligible only when all applicable safety checks pass:

the team policy is enabled,
the action identifier exactly matches the allow-list,
a configured amount cap is not exceeded,
an amount can be determined when a cap exists, and
the action is not classified as irreversible.

Unknown amounts under a configured cap fail closed. Delete, remove, destroy, purge, drop, wipe, terminate, and hard-delete style actions are never auto-approved even if entered in the allow-list. Everything outside the policy continues to wait for human review.

Autopilot also depends on scheduled processing being enabled for the workspace. A saved policy alone does not prove that background action processing is active.

Autopilot Audit

Autopilot audit is a read-only record of autonomous actions. Entries show the summary, action identifier, reason, failure state, and whether the action is still undoable.

The page does not provide the undo control. Use Workspace → Approvals while the action's undo window remains open.

Decisions

Use Save as decision on supported affordability, pricing, or hiring results to create a durable record in Decisions. The list preserves the chosen answer and frozen snapshot. When a decision links to a scenario, Re-run now evaluates that scenario against current data without changing the frozen original.

What Success Looks Like

Assistant operations are ready when:

team-wide sync, workflow, and notification settings have been saved intentionally,
Assistant has current business context,
every goal and watcher uses a known metric and clear threshold,
proposed actions have an owner in Workspace → Approvals,
Autopilot is either deliberately off or narrowly allow-listed with a cap and undo window, and
operators check Done, Failed, and Autopilot audit instead of treating Approved or queued as completion.

Limitations

Watchers currently surface threshold crossings through in-app approvals. The Slack and Email watcher choices are stored but do not deliver watcher alerts yet.
Watchers do not offer an exact time-of-day or timezone control.
Scheduled prompt runs queue requests and do not yet complete a background AI response.
Goals require the operator to manage lifecycle status on the current page; the visible progress bar is not live metric progress.
Autopilot's blank amount cap means no monetary cap. The allow-list and irreversible-action block still apply.
Approved proposals execute separately and can remain approved when action processing is unavailable.
Settings → Automation currently stores team preferences but does not yet change the corresponding product behavior.

Troubleshooting

A watcher never fires

Confirm that it is enabled, uses a supported metric name, has enough synced source data, and actually crosses the configured condition. If it has never been evaluated, ask support to confirm proactive Assistant processing is enabled for the workspace.

Slack or email receives no watcher result

Use Workspace → Approvals. Direct Slack and email delivery for watcher crossings is not available yet.

A scheduled run stays queued

Queued means the recurring request was recorded. It does not mean a background Assistant answer completed. Review Workspace → Approvals and contact support if scheduled processing should be active for your workspace.

Autopilot does not run an allowed action

Check for an exact identifier match, an amount above the cap, an unknown amount while a cap is set, or an irreversible action classification. Also confirm the workspace has proactive processing enabled.

An approved action did not happen

Filter Workspace → Approvals to Approved, Done, and Failed. Approval and execution are separate. Use Autopilot audit for autonomous-action details.

Slack Notifications will not save as expected

Enter a valid incoming Slack webhook URL before enabling the switch, then use the Save button in the Slack Notifications section.