Skip to main content

​
What actions are

Actions are tools wired to your connected integrations plus first-party action cards that ship with Halo. Skills give your agent built-in capabilities (web search, UI highlighting); actions give it the ability to do things in your other tools (HubSpot, Linear, Stripe, Slack) and run first-party flows (ticket escalation, Stripe billing). When you connect an integration like HubSpot, its actions show up on AI Agents > [Your Agent] > Actions as toggles. Turn one on and the AI can call it mid-conversation.

​
How actions work end-to-end

1

Connect the integration

Go to Integrations in the sidebar, pick HubSpot/Slack/Stripe/Linear, complete OAuth or API key setup.
2

Enable the action on the agent

Open the agent and find the action under Actions. Each integration’s actions are listed with a description of what they do and a destructive flag (red badge for things that mutate external systems).
3

Configure scope and defaults

Each action has its own config — for example, HubSpot’s update_contact lets you whitelist which contact properties the AI can change. Linear’s create_bug lets you pick the team, labels, and confidence threshold.
4

The AI calls it when relevant

Once enabled, the action becomes an AI tool. The agent decides when to call it based on conversation context and your instructions.

​
Action types

Halo groups actions into two categories on the Actions tab:
CategoryExamples
First-party action cardsTicket Escalation, Stripe Billing, Web Search and UI Highlighting (skill toggles), and the Lead Capture card on sales agents. These have first-class UI at the top of the Actions tab.
Per-integration blocksOne block per connected integration (HubSpot, Slack, Linear, etc.), each containing that integration’s actions as toggles.
The first-party cards get prominence because they’re high-leverage for support workflows. Integration blocks group their toggles together so it’s clear which actions belong to which connected service.

​
Built-in actions

​
Ticket Escalation

The most important one. Every customer-facing agent has a ticket escalation action that controls when and how the AI hands off to humans. See Escalation for the full reference.

​
Bug Detection (Linear)

When connected to Linear, the AI can file bug tickets automatically. Configure:
  • Default team — which Linear team to file bugs in.
  • Labels — labels added to every filed bug.
  • Confidence threshold — only file a bug when the AI is at least N% confident it’s actually a bug (vs user error).
  • Response mode — whether the Linear Agent replies to dev comments on the filed ticket: off, mention_only, or always.
See Linear Integration for the full setup.

​
Feature Requests (Linear)

Same as Bug Detection, but for feature requests, improvements, and integration asks. Filed as Linear issues with the appropriate classification.

​
Billing (Stripe)

When connected to Stripe, the AI can submit billing requests to a human approval queue:
  • Refund (full or partial)
  • Cancel at period end
  • Cancel immediately
  • Apply credit
  • Extend trial
The AI never executes billing actions directly — it submits requests with a reason and summary, and a teammate approves or denies in the inbox. Configure default approval settings under the Billing action. See Stripe Integration.

​
Per-integration actions

​
HubSpot

ActionWhat it does
Create dealOpen a new deal for the conversation’s contact. Use when the user expresses buying intent or asks for a quote.
Update contactPatch a single property on the contact (lifecycle stage, job title, phone). Whitelisted properties only.
Log activityCreate a follow-up task on the contact (e.g. “send pricing PDF tomorrow”).
Create noteAttach a free-form note to the contact for handoff context or AI summaries.

​
Slack

ActionWhat it does
Post messagePost to a Slack channel on behalf of the agent. Use for updates, alerts, or customer notes. Optionally restrict to specific channels.

​
Linear

Covered above under Built-in.

​
Stripe

Covered above under Built-in.

​
Destructive actions

Some actions mutate state in external systems — creating a HubSpot deal, posting a Slack message, requesting a refund. These are flagged destructive in the UI with a red badge. Be deliberate when enabling destructive actions. For Stripe billing in particular, the approval queue gives a human checkpoint between “AI requests a refund” and “refund actually happens.”

​
Per-action configuration

Each enabled action has its own settings dialog. Common config:
SettingAction types
Confidence thresholdLinear bug, feature request — only act when sure
Allowed properties / channels / teamsWhitelist what the action can touch
Default valuesE.g. default Linear team, default HubSpot pipeline
Response modeFor Linear (off / mention_only / always replies on dev comments)
Settings live on the action card in the Actions tab — click the gear icon.

​
Sharing actions across agents

Actions are scoped to the agent, not the org. If you want billing and Linear filing on multiple agents, enable them per agent. There’s also a fallback for support-style agents: if a customer-facing or Ask AI agent has no explicit action row, configuration set on the org’s default support agent flows through automatically. This makes it easy to configure actions once on your main support agent and have other support-style agents inherit them. Sales agents are excluded from this fallback. If you want a sales agent to have access to integration actions, configure them explicitly on the sales agent.

​
Where to go next

HubSpot

Connect HubSpot and configure the four agent actions.

Linear

File bugs and feature requests automatically.

Stripe

Set up the billing approval queue.

Slack

Let the AI post into Slack channels.