Documentation

Get up and running fast.

Everything you need to hire your first Actium assistant, connect your integrations, and schedule recurring jobs that run reliably every time.

Quick start

The fastest path to a running assistant is three steps: connect an integration, pick a template from the library, and set a schedule. No code required.

  1. Sign up at platform.actium.app and confirm your email.
  2. Connect an integration: navigate to Settings → Integrations and authorise the first service (HubSpot, Slack, Gmail, or whichever applies). OAuth credentials are stored in the CloudSwarm vault and never touch your browser again after the grant.
  3. Choose a template: from the assistant library pick one that matches your use case. Templates are pre-wired with the right skills and a sensible default schedule.
  4. Set the schedule: cron expression or natural-language shorthand (every weekday at 9 am, every Monday at 6 pm). Click Activate.

Your assistant is now running on Heroa. The first run happens at the next scheduled tick. Every run produces a timestamped audit record you can review from the Jobs tab.

Core concepts

Assistants

An Actium assistant is a named, scheduled agent. It has a trigger (a cron schedule or an event), a skill bundle (the integrations it is allowed to call), a policy envelope (spend ceiling, approval gates), and an audit stream. Each assistant maps to one recurring job. You can run many assistants in one workspace.

Skills

Skills are sandboxed integration wrappers: HubSpot read/write, Slack post, Gmail draft, Salesforce upsert, and more. A skill can only call the API it declares and can only use the credential bound to it. Actium ships with a curated skill catalog; custom skills require the Team or Enterprise tier.

Schedules

Schedules are standard UTC cron expressions. The UI accepts natural language and converts it for you. An assistant runs at most once per minute and at least once per month on paid tiers. Free-tier assistants are limited to once per day.

Approvals

Promotion levels (L0 shadow, L1 notify, L2 approve, L3 autonomous, L4 trusted) control how much an assistant can do without human sign-off. Start at L1 to watch the first few runs, then promote once you trust the output. Demotion is always available and instant.

Audit log

Every run appends to an immutable audit log: run ID, assistant ID, skills called, credential names (not values), outcome (pass / partial / fail), and an Ed25519-signed receipt from the underlying R1 runtime. Logs are exportable as JSON or NDJSON and can be streamed to a webhook for external SIEM ingestion.

Integrations

Actium connects to over forty services out of the box. The most used are:

  • CRM: HubSpot, Salesforce, Pipedrive
  • Communication: Slack, Gmail, Outlook, Intercom
  • Productivity: Notion, Airtable, Google Sheets, Jira, Linear
  • E-commerce: Shopify, WooCommerce, Stripe
  • Websites: WordPress, Webflow

See the full integrations catalog for setup guides, OAuth scopes required, and rate-limit information per connector.

API access

The Actium API is a JSON REST API. Authenticated with a bearer token issued from Settings → API Keys. The base URL is https://api.actium.app/v1.

Key endpoints:

  • GET /assistants — list all assistants in the workspace
  • POST /assistants/{id}/run — trigger an immediate run
  • GET /assistants/{id}/jobs — paginated run history
  • POST /webhooks — register a webhook for run completions

Full OpenAPI spec available from your workspace at Settings → API → Download spec.

Actium CRM

Actium includes a lightweight CRM that stores the contacts your assistants touch. It is not a replacement for HubSpot or Salesforce; it is the shared inbox that every assistant writes to when a human handoff is needed. When an assistant flags a lead for follow-up, it lands in the Actium CRM inbox and stays there until a team member marks it handled. See the CRM overview.

Actium Tasks

Tasks are one-off jobs: run once, immediately, with a specified skill bundle. They are not scheduled. Use Tasks for ad-hoc operations you want fully audited but do not want to automate yet. See the Tasks overview.

Composing with CloudSwarm

Every Actium assistant can be called as a tool by a CloudSwarm agent. This is the composition path for open-ended reasoning that needs to delegate to deterministic recurring work. A CloudSwarm agent can initiate an Actium run, wait for its completion event, and resume with the result. Credentials are not shared; each product uses its own vault.

Support

For implementation questions: [email protected]. For security issues: [email protected]. Status page: status.actium.app.