Glossary

Use this glossary to quickly understand the key terms and concepts you’ll encounter while working with Autohive.

Term	Definition
Agent	An AI-powered assistant capable of carrying out tasks or answering questions. Agents can be general-purpose or specialised (e.g., Bumble The Biz Strategist).
Attachment	A file uploaded directly into a chat message for reference by agents or teammates.
Billing owner	The member responsible for subscription payments and invoices. Usually also a workspace owner.
Buzz	The animated Autohive guide who welcomes new users during onboarding and demonstrates how to use the platform.
Chat	The real-time conversation interface where users and agents communicate. Supports direct, group, and DM conversations.
Content area	Central repository for all documents, media, and knowledge used by agents. Supports versioning, folders, search, and permissions.
Creator	A user who publishes agents or integrations to the Autohive Marketplace. Creators have a public profile and manage their listings from the My Marketplace section.
Cron expression	A string defining complex job schedules (e.g., `0 9 * * MON-FRI`).
Custom role	A set of granular permissions to tailor access beyond built-in roles.
Edge	A connection between two nodes in a workflow that defines the execution order. Edges can carry conditional logic to control which path runs.
Explore	Section of Autohive where users discover, preview, and activate new agents.
History (job)	The log of executions for a specific job, including status, duration, and outputs.
Integration	A connection between Autohive and an external service (e.g., Slack, Google Drive, Webhooks).
Job	A saved instruction that triggers an agent or workflow on a schedule or event.
Job run / execution	A single occurrence of a job performing its task.
Job scheduler	The subsystem that calculates and triggers job runs based on cron, intervals, or dates.
Knowledge base	A collection of documents and files linked to a specific agent to give it deeper, context-rich information about a topic or business.
Label	A colour-coded tag that can be applied to todos for categorisation and filtering. Labels are scoped to a workspace.
Listing	An agent or integration published to the Autohive Marketplace by a creator. Listings go through a review process before becoming publicly available.
List view	A paginated, sortable table view of todos showing title, status, assignee, labels, and priority.
MCP Server	A Model Context Protocol server that provides a standardised interface for agents to access external tools and capabilities. MCP servers can use anonymous or bearer token authentication.
Scheduled jobs	The subsystem that calculates and triggers job runs based on cron, intervals, or dates.
Member	A human user who has access to a workspace. Members can have different roles and permissions.
Mention	Using `@` in chat to reference an agent, member, or file, alerting them and providing context.
Node	A single step in a workflow, representing an agent or action to be executed. Nodes are connected by edges to form the workflow’s execution path.
Notification	An alert delivered via email, push, or in-app banner or label based on chat mentions, job outcomes, or admin rules.
Owner (workspace)	Top-level role with full control, including billing, and all admin functions.
Permission	A specific capability (e.g., `job:create`, `content:delete`) that can be granted via roles.
Role	A collection of permissions assigned to members. Built-in roles include Owner, Admin, Member, and Viewer.
Run after trigger	A job trigger type that starts a job after another job completes successfully.
Secret	Securely stored credential (API key, token) used by jobs or integrations.
Trigger (job)	The mechanism that determines when a job runs, such as cron, interval, specific date, manual, or event.
Trigger (workflow)	The starting condition for a workflow, such as a schedule, an incoming webhook, or an external event.
Workflow	An automated process that chains together multiple agents and actions in a visual editor. Workflows consist of nodes connected by edges and are activated by a trigger.
Workspace	A logical container for agents, content, jobs, and members, often representing a project or organisation.
Webhook	HTTP endpoint used for inbound (triggering agents/jobs) or outbound (sending data) integrations.