Skip to content

Automation, Hooks, and Connections

Open Automation & Extensions → Automation or Settings → Automation on desktop. The dashboard separates Overview, automatic actions (hooks), Execution, and Imports. A project is required for sections that edit project configuration.

Choose the right mechanism

A hook is “when this event occurs, run this action.” It is not a schedule. Use AlphaBase Workflows for persistent, multi-stage or scheduled work supported by your host.

An assistant turn ending is not proof that an entire task or project completed. Check the task outcome and produced files independently.

Create an automatic action

  1. Open Automatic actions (hooks).
  2. Choose Project or User · all projects scope.
  3. Add a rule and optional name.
  4. Choose Before a tool runs, After a tool runs, When a prompt is submitted, or When an assistant turn ends.
  5. Optionally match specific tools; choose Run a command, Call a service (HTTP), or Run an AI check.
  6. Review its inputs, timeout, and scope, then save. Inspect Coverage for the selected runtime.

User hooks run before project hooks in that environment. Only supported synchronous before-action hooks can block the original action. After-action and asynchronous hooks cannot.

Commands can modify files, callbacks can transmit data, and AI checks can use paid model capacity. Hooks do not replace permission controls. If saving conflicts with updated configuration, inspect the current version and retained draft before retrying.

Import configuration

Use Imports to inspect compatible external configuration. Review the preview, scope, compatibility, and duplicate/conflict choices before applying it. Importing does not automatically grant permission or prove a rule is supported by every runtime.

Reuse connections

Open Integrations. Use Browse connections to find a service and My connections to manage saved connections. Select a service, review its capabilities, complete the offered authorization, and check readiness in the selected environment.

Supported partner credentials are shared across projects on the same host and account; users should not need to reconnect for every local folder. Separate accounts or environments can have distinct authorization. Custom sources retain their configured source scope.

Saving credentials is different from successful tool discovery or service health. Read attention messages before retrying. Disconnecting an account-wide service can affect other projects using that connection.

For persistent work, see tasks and workflows.