Toolhub — Apps & Integrations

Install/uninstall apps, OAuth & scopes, triggers, featured apps, and ReachStream.

Toolhub — Apps & Integrations

The Toolhub is where you install and manage the apps your AI worker can use. Each app unlocks new tools, triggers, and integrations — turning the worker from a chat-only assistant into something connected to the rest of your work.

What is the Toolhub?

The Toolhub is a catalog of integrations that the worker can use to act in the real world. Apps are connected via OAuth and the worker can call them as tools.

Installing an App

  1. Click an app card's Install button.
  2. The Installation Wizard opens — a multi-step dialog.
  3. Each step varies by app, but typically:
    • Step 1: Overview of what the app does and what permissions it needs.
    • Step 2: OAuth or API key entry (e.g. "Sign in with Google" or "Paste your API key").
    • Step 3: Permission scopes (read calendar, send mail, etc.).
    • Step 4: Confirmation and the test call.
  4. Click Finish. The app moves to the Installed state.

Managing Installed Apps

Click Open on an installed app card. An installation wizard opens showing:

  • Installed Info — when installed, who connected it, last test status.
  • Permissions — what the app can do.
  • Test Connection — re-verify the OAuth/API key is still valid.
  • Uninstall — remove the app and revoke its access.

How Apps Work With the Worker

Once installed, an app's tools become available to the worker in chat. For example, after installing Google Calendar:

  • In chat: "Add a meeting with John tomorrow at 2pm" — the worker uses the gcal.createEvent tool.
  • Background: A new event arriving in Google Calendar can trigger a webhook that wakes the worker.

The app's tools are listed in the Tools catalog (a sub-page of the Toolhub). The worker picks the right tool for the user's intent.

Triggers

Some apps have triggers — events that wake the worker. For example:

  • Stripe trigger: when a new subscription is created, ask the worker to send a welcome email.
  • GitHub trigger: when a new issue is opened, ask the worker to triage it.
  • Slack trigger: when a DM is received, ask the worker to draft a reply.

Triggers are configured in the Triggers sub-page. Each trigger has:

  • App / event source (e.g. "Stripe → invoice.payment_failed")
  • Filter (optional conditions)
  • Action (what the worker should do)

ReachStream B2B Contacts — Special Case

The ReachStream integration is configured separately from the regular apps, in Settings → Integrations. This is because:

  • It powers the Find Leads feature and is more deeply integrated.
  • It uses an API key (not OAuth).
  • It's a paid service on Allorc's side, not your own subscription.

The settings screen has three states:

State What you see
Disconnected An API key input + Connect button.
Connected A "Connected as <account>" label + Disconnect + Test buttons.
Error Red banner explaining the issue (e.g. invalid key) + retry.

What Happens When You Uninstall

Uninstalling an app:

  1. Revokes the OAuth tokens or API key.
  2. Removes the app's tools from the worker's available tools.
  3. Disables any triggers sourced from this app.
  4. Preserves any data the app already pulled (e.g. a contact synced from HubSpot remains in the project).

The app card returns to the Not installed state.

Permissions & Security

When you install an app, you grant a specific set of scopes. The platform uses OAuth 2.0 with per-app, per-scope tokens — the worker can only do what the scopes allow. Scopes are visible in the app's detail view.

The worker cannot escalate. Even if the worker is asked to do something outside its scope, the platform denies the API call.

App States Reference

State Meaning UI
Not installed App is available but not connected. Install button.
Setup required App is partially installed (e.g. you closed the wizard mid-flow). Resume setup button.
Installed App is fully connected and working. Open button + green badge.
Error App was connected but lost the connection (e.g. token expired). Reconnect button + red badge.

What If the App Provider is Down?

If an installed app's provider (e.g. Google) has an outage, the app card shows the Error state with a brief reason. The worker can still try to call the tool but will receive an error from the provider. The error surfaces in chat with a clear message.

Frequently Asked Questions

Q: Do apps cost extra? A: Apps are included in your Starter plan. ReachStream is the only one that uses an API key, but no extra charge is passed to you.

Q: Can I install an app to just one project? A: No — apps are account-scoped. Once installed, the worker can use them in any project.

Q: What happens to triggers if I uninstall the source app? A: Triggers are auto-disabled. The trigger list entry stays but its action is paused. Reinstall the app to re-enable.

Q: Can the worker install apps on its own? A: No. App installation requires explicit user action and OAuth consent.

Q: Where do my OAuth tokens live? A: Encrypted at rest and scoped per user and per app.

Q: Can I share an installed app with a teammate? A: Not in the current model. Each user installs the app against their own account. Workspace-shared apps are on the roadmap.

Q: Does installing an app give the worker access to my data? A: Only the data the app's scopes allow. You see and approve the scopes during install.

Q: How do I report a broken app? A: Click the Help link in the app's detail view, or contact support with the app name and the error you saw.