# Helios by WarpBuild > Helios gives agents real computers in one shared workspace. Each chat and each workflow run gets its own sandbox, the full API of every connected tool (Slack, GitHub, Notion, Stripe, and more), and shared files your team reviews before anything changes. Workflows run in chat, on a schedule, on a webhook, or on an integration event. Helios is built by WarpBuild. --- # Helios - Agents with real computers. One shared workspace. URL: https://www.heliosapp.com/ Description: Delegate support roundups, CRM cleanup, and recurring reports to agents with real cloud computers, connected tools, and shared team context. Agents with real computers # Your team has better things to do. Give Helios the support roundup, the CRM cleanup, or the report that eats your Monday. Agents get a cloud computer, your tools, and the context to get to work. [Get started free ↗](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits. Invite your whole team. Account briefing Complete Get me ready for my call with Acme. Pull together the latest emails, account details, and meeting notes. 1. ![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Read the account history 2. ![](/static/img/assets/gmail-light.svg)![](/static/img/assets/gmail-dark.svg)Catch up on recent conversations 3. Find the notes from last time Meeting brief ## Acme · ready for your call Renewal is next month. The team is expanding to two new regions and asked about SSO in the last call. 3 sources, one briefing Ready to review An example of a task, from ask to done.[Meet Helios ](/product/) Right at home with your tools. * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) * [GitHub](/integrations/github/) * [![](/static/img/assets/gmail-light.svg)![](/static/img/assets/gmail-dark.svg)Gmail](/integrations/gmail/) * [Notion](/integrations/notion/) * [![](/static/img/assets/google-sheets-light.svg)![](/static/img/assets/google-sheets-dark.svg)Sheets](/integrations/google-sheets/) * [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Attio](/integrations/attio/) [See all ↗](/integrations/) One less Monday chore ## The roundup’s ready. You haven’t opened a tab. Ask Helios to read the week’s support threads, find the recurring problems, and send your team a digest. Use the same prompt in a workflow to do it every Monday. [Explore workflows ](/product/#workflows) Example workflow Mon, 09:00 UTC Support · weekly digest ### 142 threads. Here’s what came up. 1. 31 Invoice confusion 4 enterprise accounts affected 2. 12 Slow CSV exports Most reports involve large files 3. 09 SSO login loop Reports point to Safari Digest posted to #support-leads GitHub issue #1187 opened for invoice confusion ## Every run gets its own machine. Helios can write a script, run it, and use the result. Each task starts in a fresh sandbox with its own shell and files. * Bun, Node, git, and jq are preinstalled. The agent writes a script, runs it, and reads the result. * It can search the web and read a page when the task needs facts that are not in your tools. [See how runs work →](/product/) support-digest environment v4 · Dockerfile CPU 2 vCPU Memory 4 GB Disk 10 GB files * \~/context * org/ project/ personal/ * \~/workspace * app/ threads.json themes.md * /tmp installed * bash * git * bun * node * python * jq 1. Created 09:00:02 UTC 2. Running 4m 12s 3. Stops at 30 min ## Your tools, without the copy-paste. Agents get the complete API of each connected tool. They find the right endpoint for the task and call it. * Helios indexes each tool's API. The agent finds the endpoint it needs and makes the request. * The egress proxy attaches your credential on the way out. The sandbox never holds the token. [See integrations →](/integrations/) GitHub integration · full API indexed find-relevant-apis “open an issue for the top support bug” POST`/repos/{owner}/{repo}/issues` | parameter | in | value | | --------- | ---- | --------------------------------------- | | owner | path | acme | | repo | path | app | | title | body | Invoice confusion: 31 threads this week | | labels | body | \["bug", "support"\] | 201 Createdissue #1187credential added by the egress proxy ## Shared knowledge. Reviewed changes. Agents write to a shared Library. A person reviews the diff and approves each file before it becomes the team's context. * Organization, project, and personal files mount at \~/context in every run. * Edits are staged for review. A person approves or discards each file. Agents cannot approve their own. [See the Library →](/product/#library) org/support/themes.md Proposed by run 8f3c · Modified · waiting for review DiscardApprove ## Recurring themes -1. Invoice confusion (24 threads)+1. Invoice confusion (31 threads, 4 enterprise accounts)+ Tracked in acme/app#1187 2. Slow CSV export (12 threads)+3. SSO login loop on Safari (9 threads) Getting started ## Start with the task you keep putting off. An engineer connects tools, environments, and access. After that, anyone on the team can hand work to an agent. 1. 01 ### Describe the task Write what you want done in plain words. Name the tools it should use and the output you want back. Start it in chat and watch each tool call. 2. 02 ### Attach a trigger Reuse the same prompt as a workflow. Run it by hand, on a schedule, from a signed webhook, or on a GitHub, Slack, or Plain event. 3. 03 ### Review the run Open the run. Every command, tool call, and result is in the transcript. Changes to shared files wait for a person to approve them. Integrations ## Keep the tools you like. Connect your team’s apps and give each workflow access to the ones it needs. * [![](/static/img/assets/mailchimp-light.svg)![](/static/img/assets/mailchimp-dark.svg)MailchimpEmail](/integrations/mailchimp/) * [![](/static/img/assets/brevo-light.svg)![](/static/img/assets/brevo-dark.svg)BrevoEmail](/integrations/brevo/) * [GitHubDeveloper tools](/integrations/github/) * [GitLabDeveloper tools](/integrations/gitlab/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)SlackCommunication](/integrations/slack/) * [![](/static/img/assets/gmail-light.svg)![](/static/img/assets/gmail-dark.svg)GmailGoogle Workspace](/integrations/gmail/) * [![](/static/img/assets/google-sheets-light.svg)![](/static/img/assets/google-sheets-dark.svg)Google SheetsGoogle Workspace](/integrations/google-sheets/) * [![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)Google DocsGoogle Workspace](/integrations/google-docs/) * [Google DriveGoogle Workspace](/integrations/google-drive/) * [Google CalendarGoogle Workspace](/integrations/google-calendar/) * [NotionDocs & knowledge](/integrations/notion/) * [BoxDocs & knowledge](/integrations/box/) * [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)AttioSales & CRM](/integrations/attio/) * [![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)ApolloSales & CRM](/integrations/apollo/) * [![](/static/img/assets/clay-light.svg)![](/static/img/assets/clay-dark.svg)ClaySales & CRM](/integrations/clay/) * [StripeBilling](/integrations/stripe/) * [![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)ResendEmail](/integrations/resend/) * [![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)PlainSupport](/integrations/plain/) * [LinearDeveloper tools](/integrations/linear/) * [DiscordCommunity](/integrations/discord/) * [RedditCommunity](/integrations/reddit/) * [![](/static/img/assets/typeform-light.svg)![](/static/img/assets/typeform-dark.svg)TypeformForms](/integrations/typeform/) * [![](/static/img/assets/apify.svg)ApifyWeb data](/integrations/apify/) * [![](/static/img/assets/warpbuild-light.svg)![](/static/img/assets/warpbuild-dark.svg)WarpBuildDeveloper tools](/integrations/warpbuild/) * [JiraDeveloper tools](/integrations/jira/) * [DatabasesData](/integrations/databases/) * [PagerDutyDeveloper tools](/integrations/pagerduty/) * [SentryDeveloper tools](/integrations/sentry/) * [![](/static/img/assets/zendesk-light.svg)![](/static/img/assets/zendesk-dark.svg)ZendeskSupport](/integrations/zendesk/) * [![](/static/img/assets/webflow-light.svg)![](/static/img/assets/webflow-dark.svg)WebflowWeb data](/integrations/webflow/) * [![](/static/img/assets/shopify-light.svg)![](/static/img/assets/shopify-dark.svg)ShopifyE-commerce](/integrations/shopify/) * [![](/static/img/assets/woocommerce-light.svg)![](/static/img/assets/woocommerce-dark.svg)WooCommerceE-commerce](/integrations/woocommerce/) * [![](/static/img/assets/granola-light.svg)![](/static/img/assets/granola-dark.svg)GranolaDocs & knowledge](/integrations/granola/) * [VercelDeveloper tools](/integrations/vercel/) * [BitbucketDeveloper tools](/integrations/bitbucket/) * [![](/static/img/assets/hunter-light.svg)![](/static/img/assets/hunter-dark.svg)HunterSales & CRM](/integrations/hunter/) * [![](/static/img/assets/pipedrive-light.svg)![](/static/img/assets/pipedrive-dark.svg)PipedriveSales & CRM](/integrations/pipedrive/) * [![](/static/img/assets/lusha-light.svg)![](/static/img/assets/lusha-dark.svg)LushaSales & CRM](/integrations/lusha/) * [![](/static/img/assets/docusign-light.svg)![](/static/img/assets/docusign-dark.svg)DocusignSales & CRM](/integrations/docusign/) * [Zoho CRMSales & CRM](/integrations/zoho-crm/) * [![](/static/img/assets/salesforce-light.svg)![](/static/img/assets/salesforce-dark.svg)SalesforceSales & CRM](/integrations/salesforce/) * [CalendlySales & CRM](/integrations/calendly/) * [AsanaProject management](/integrations/asana/) * [ZoomCommunication](/integrations/zoom/) * [![](/static/img/assets/cal-com-light.svg)![](/static/img/assets/cal-com-dark.svg)Cal.comSales & CRM](/integrations/cal-com/) * [ClickUpProject management](/integrations/clickup/) * [DropboxDocs & knowledge](/integrations/dropbox/) * [![](/static/img/assets/zoho-desk-light.svg)![](/static/img/assets/zoho-desk-dark.svg)Zoho DeskSupport](/integrations/zoho-desk/) * [![](/static/img/assets/help-scout-light.svg)![](/static/img/assets/help-scout-dark.svg)Help ScoutSupport](/integrations/help-scout/) * [![](/static/img/assets/workable-light.svg)![](/static/img/assets/workable-dark.svg)WorkableHR](/integrations/workable/) * [![](/static/img/assets/figma-light.svg)![](/static/img/assets/figma-dark.svg)FigmaDesign](/integrations/figma/) * [![](/static/img/assets/square-light.svg)![](/static/img/assets/square-dark.svg)SquareBilling](/integrations/square/) * [![](/static/img/assets/deel-light.svg)![](/static/img/assets/deel-dark.svg)DeelHR](/integrations/deel/) * [![](/static/img/assets/wise-light.svg)![](/static/img/assets/wise-dark.svg)WiseBilling](/integrations/wise/) * [CloudflareDeveloper tools](/integrations/cloudflare/) [All integrations →](/integrations/) ## Questions people ask ### Which model runs my workflow? ### How do I cap what this costs? ### What happens when a run fails? ### Where does my data go? ### Do you support SSO and SCIM? ### Can I stop a run that is going wrong? ## Hand over your first task. Connect a tool, start a chat, and read the transcript. 5,000 free credits to begin. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # About - Built by the WarpBuild team | Helios URL: https://www.heliosapp.com/about Description: We run CI for engineering teams. Helios is the same idea for agents. A real machine, the right access, and a bill you can read. About # Built by the WarpBuild team We build the cloud infrastructure behind WarpBuild. With Helios, we’re bringing that experience to the everyday work teams hand to agents. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) * 5,000 free credits * Usage pricing, no seats * Backed by Y Combinator What we build ## Agents with real computers Helios gives every agent a cloud computer and gives your team one shared workspace. An engineer connects the tools, environments, and access once. After that, anyone on the team can start a workflow in chat. The work that keeps a company running is recurring. Triaging support, chasing leads, reading pull requests, pulling the same report every Monday. We think that work deserves a real machine, the right access, and a bill you can read. You can inspect every command and tool call in a run’s transcript. Access is scoped to the tools you connect, and spending limits keep recurring work within budget. * ### A real computer per run Every chat and every workflow run gets its own sandbox with a shell, a filesystem, and code execution. * ### The full API of each tool Helios indexes the complete API of a connected tool. The agent finds the endpoint it needs. * ### Say it in chat. Run it on a trigger. Start in a chat. Then reuse the prompt as a workflow that runs on a schedule, a webhook, or a GitHub, Slack, or Plain event. * ### One permissions model, everywhere The same roles cover the dashboard, the CLI, and your scripts. Credentials are injected at the network layer, so the agent never holds a raw token. ## Built by the WarpBuild team We are the team behind [WarpBuild](https://warpbuild.com). WarpBuild runs CI for engineering teams. Thousands of engineers run their builds on infrastructure we built and operate. Running CI taught us what people trust automation with and what they will not. Helios is the same idea applied to agents. A real machine for every run, honest controls, and a product that does what it says. Helios uses the same login as WarpBuild, and the status page is shared. We are a team of engineers who have built together for years. We are backed by Y Combinator. [warpbuild.com →](https://warpbuild.com)Backed by![Y Combinator](/images/yc.svg?dpl=dpl_GeLX2heYCXxcpKMEYahLADvngBcT) How Helios is run ## Pay for runs * You pay for the runs your agents do. There is no seat price. Add the whole team at no extra cost. * Set a monthly spending limit. Triggers stop when credits run out. * Auto refill is optional. You choose the threshold. * Every run keeps its full transcript, so you can see where credits went. [See pricing →](/pricing/) Free credits 5,000 Included on every account Per credit $0.002 Usage pricing Seats 0 The whole team is included Contact ## Talk to the team Questions about the product, pricing, or a task you want to hand to an agent. We read every message. * [Emailsupport@heliosapp.com](mailto:support@heliosapp.com) * [Book a demoWalk through a real task with us](https://cal.com/suryao/helios) * [Statusstatus.warpbuild.com](https://status.warpbuild.com) * [DocsStart with the quickstart](/docs/quickstart) ## Put an agent on the task Start with 5,000 free credits. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Changelog - What Shipped in Helios | Helios URL: https://www.heliosapp.com/changelog Description: Dated product updates for Helios. New integrations, workflow triggers, the Library, the CLI, and access controls, with links to the docs. Changelog # What shipped in Helios Dated product updates, newest first. Each entry links to the docs page that explains it. [RSS feed](/changelog/rss.xml)[Read the docs →](/docs/) 1. September 4, 2026Library ## [Library and change review](#library-and-change-review) Agents now work from a shared Library. Every file an agent edits is staged as a proposed change. A person reviews the diff and approves or discards each file. * Three scopes. Organization, project, and personal files, plus a scratch area per agent session. * Files are mounted in the sandbox at \~/context. * Side-by-side diffs with Added, Modified, and Deleted labels. Approve per file or approve all. * Conflict detection. Approval is blocked when the live file changed after staging. * Agents cannot approve their own changes. * Share any folder with viewer or editor access. * A Files panel in chat shows what the running agent can see and has changed. * Uploading files from the browser is not available yet. Files enter the Library through agent sessions. [Library docs →](/docs/library/overview/) 2. September 3, 2026CLI ## [CLI terminal app and helios configure](#cli-terminal-app-and-configure) Running helios opens a full-screen terminal app with chat, workflows, projects, access, and Helios Code. helios configure walks a new user from an API key to a running agent. * Home screen with a new chat input and recent chats. Command palette on ctrl+p. * Trigger a workflow with t, share it with s, and pick the service account it runs as. * helios configure saves progress and resumes. Rerun one step with --redo . * Launch a Helios Code agent, watch the boot logs, then attach. A files tab shows the diff for each repository the agent edits. * helios integration connect and helios code iac scaffold, export, and apply work from scripts. * Every command prints JSON when piped. [Install the CLI →](/docs/cli/install/) 3. August 28, 2026Access ## [Act as me for service accounts and credential mode on shares](#act-as-service-accounts-and-credential-mode) A named service account can act as you in integrations that need a personal login. When you share an integration, you choose whether the grantee connects with their own account or with the Helios app. * Act as me is a switch on the service account page. You can only point a service account at yourself. * Applies to GitHub and Slack, the two integrations that require a personal authorization. * The Share dialog for an integration has a Connects as picker. The default stays Their own account. * Change the mode later from the access list without sharing again. * Workflows that run as a service account no longer stop with authorization required on GitHub or Slack. [Service accounts →](/docs/access/service-accounts/) 4. August 21, 2026CLI ## [Sharing, groups, and service accounts from the CLI](#access-commands-in-the-cli) The helios command line has the same access controls as the dashboard. Pick a project, share any resource, and manage groups and service accounts from a shell or a script. * helios project use , the HELIOS\_PROJECT variable, or --project set the active project. * helios share / --with --role with an optional --expires date. Principals are everyone, user, group, or service account. * helios access list shows your effective role and every grant, direct or inherited. helios shared list shows what was shared with you. * helios group and helios service-account commands for create, rename, disable, enable, delete, and member changes. * helios service-account assign makes a workflow run as that account. * Roles are viewer, operator, editor, and admin. You cannot grant above your own role. [Roles and permissions →](/docs/basics/roles-permissions/) 5. July 2026Integrations ## [Gmail, Google Drive, Google Docs, and Google Sheets](#google-workspace-integrations) Four Google Workspace integrations. Agents get the full API of each one, with the Helios app or your own Google app. * Read and send mail, organize files, write documents, and update sheets from a chat or a workflow. * Connect with the Helios Google app or bring your own OAuth app. * Event triggers from Google are not available yet. Use a schedule. [Integrations →](/docs/integrations/) 6. July 2026Integrations ## [Database connections](#database-connections) Connect Postgres, MySQL, or ClickHouse and let agents query it directly. * Connection strings are encrypted with KMS and never enter the agent context. * Optional SSH tunnel for databases inside a private network. * Share a connection with a person, a group, or the whole organization. [Databases →](/docs/integrations/databases/) 7. July 2026MCP ## [Remote MCP servers](#mcp-servers) Attach any remote HTTP MCP server and its tools appear in chats and workflows. * Bearer token or OAuth2 authentication. * Tool allowlist and timeouts per server. * Scope a server to the organization or to one project. * Helios itself is an MCP server. Call find\_relevant\_apis and call\_api from your own client. [MCP servers →](/docs/basics/mcp-servers/) 8. July 2026Environments ## [Environments built from a Dockerfile](#environments) Build an environment from a Dockerfile, then run agents on it with a terminal and Git panel in the browser. * Overview, Versions, and Dockerfile tabs with build logs. * An environment bundles the image, secrets, cloud-init, integrations, and the coding agent. * Claude Code is pre-signed in the environment through the Claude Account integration. [Sandboxes →](/docs/basics/sandboxes/) 9. July 2026Workflows ## [Signed webhook triggers](#signed-webhooks) Start a workflow from any system that can send an HTTP request. Every request is signed with HMAC-SHA256. * A five minute replay window rejects old requests. * Rotate the signing secret without changing the URL. * The request body is available to the agent as the run payload. [Triggers →](/docs/workflows/triggers/) ## Try the latest release. Start with 5,000 free credits. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Compare - Helios vs Other Agent Products | Helios URL: https://www.heliosapp.com/compare Description: How Helios compares with Claude Cowork, OpenAI agents, Dust, Lindy, Grok Bot, and PromptQL. Facts from public pages, dated, with sources. Compare # Helios next to the others. Six honest comparisons. Each one says where the other product is strong, where Helios is different, and what each one charges. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Comparisons ## Pick a product Every page follows the same eight sections, so you can read two side by side. [AnthropicHelios vs Claude CoworkCowork and Routines run work for one person inside a Claude seat. Helios runs workflows for a team on triggers, with one meter for the organization.](/compare/claude-cowork/)[OpenAIHelios vs OpenAI AgentsOpenAI spreads agent work across scheduled tasks, Codex cloud, and Workspace Agents. Helios runs every workflow on one surface with the same triggers and one meter.](/compare/openai-agents/)[DustHelios vs DustDust builds chat agents grounded in company data. Helios runs agents on their own computer, on a trigger, with the full API of each tool.](/compare/dust/)[LindyHelios vs LindyLindy sells per-user plans with credit bundles and a large connector library. Helios gives every run its own computer and meters usage for the whole organization.](/compare/lindy/)[xAIHelios vs Grok BotGrok Bot gives one person a team of always-on Bots in a desktop app. Helios gives a whole team agents that run in isolated sandboxes on triggers.](/compare/grok-bot/)[HasuraHelios vs PromptQLPromptQL answers questions over governed data with shared threads. Helios runs tasks that act on your tools. Many teams need both.](/compare/promptql/)[MetaHelios vs Meta MuseMuse runs errands for one person on a Meta virtual machine with a consumer subscription. Helios runs workflows for a team on triggers, with one meter for the organization.](/compare/meta-muse/)[Spear Street TechnologyHelios vs InstinctInstinct is an invite-only personal agent you reach by text or phone. It acts on a cloud computer with your accounts. Helios runs team workflows on triggers with roles and one spend meter.](/compare/instinct/) How we compare * Read each product's public pages, docs, and pricing on a stated date. * Quote the vendor's own words for limits and prices, and link the source. * List where the other product is strong before we say where Helios differs. * Describe the mechanic. For example, one sandbox per run. What we do not claim * Guess at a vendor's roadmap or reasons for a change. * Cite review scores or star ratings. * Invent numbers. Every figure links to a dated public page. * Claim a Helios feature that is not shipped. Each page shows the date its facts were checked. We refresh them every quarter, and sooner when a vendor tells us something changed. ## Run your first task. 5,000 free credits. Set an organization spending limit before your first workflow runs. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Helios vs Claude Cowork - Different layers of the same stack. | Helios URL: https://www.heliosapp.com/compare/claude-cowork Description: Cowork and Routines run work for one person inside a Claude seat. Helios runs workflows for a team on triggers, with one meter for the organization. [← All comparisons](/compare/) Helios vs Claude Cowork # Different layers of the same stack. Cowork and Routines run work for one person inside a Claude seat. Helios runs workflows for a team on triggers, with one meter for the organization. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Claude Cowork is Anthropic's desktop work surface for knowledge workers. Claude Code Routines run scheduled or GitHub-triggered jobs on Anthropic's infrastructure for engineers. Both draw on the Claude plan you already pay for. Helios is a team runner. Each run gets its own sandbox, reaches the full API of each connected tool, and starts from a schedule, a webhook, or an integration event. Helios uses Anthropic models, so the question is which layer fits the work. At a glance ## Side by side Short facts for each product. The Claude Cowork column comes from public pages on the date shown at the bottom of this page. | Topic | Helios | Claude Cowork | | ----------------- | ------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | Sandbox per run | Yes. Each run and chat gets its own sandbox with shell, files, and code execution. | Cowork works on your desktop, with an optional 'Run Cowork in the cloud' setting for Team and Enterprise. Routines run on Claude Code's web infrastructure. | | Tools and APIs | The full API of each connected tool. The agent searches the API surface and calls the endpoint it needs. | Connectors and MCP servers. Admins can decide whether users may choose 'Always allow' for connector tools. | | Triggers | Manual, cron schedule, signed webhook, and integration events from GitHub, Slack, and Plain. | Cowork: scheduled recurring tasks. Routines: schedule, API endpoint, and GitHub PR and release events. | | Human review | Library changes are proposed by the agent and approved per file by a person. No approval step inside a run. | Cowork asks for permission on actions. Connector tool approvals can be set to 'Always allow' if the admin permits it. | | Permissions | Resource roles viewer, operator, editor, and admin. Share with a person, a group, or the whole organization, with expiry. | Organization on/off switches for Cowork, cloud runs, and the browser. Group roles and Compliance API on Enterprise. | | CLI | The Helios CLI runs, shares, and triggers workflows with the same permissions as the dashboard. JSON output when piped. | Claude Code is a CLI. Routines are created from Claude Code and run on the web. | | Pricing model | Credits. 5,000 free to start, then $0.002 per credit. No seats. | Included in the Claude plan seat. Routine runs are capped per day by plan, with paid overage.Seat prices per morphllm.com, Sep 2026 | | Org spend limits | Yes. A monthly spending limit for the organization. Triggers stop when credits run out. | Usage is a per-seat allowance. Cowork tasks share the five-hour rolling window with chat and Claude Code. | | Memory or context | Shared Library files mounted into the sandbox at \~/context. Edits are staged for review. | Files on your Mac and connected sources. Claude memory features depend on the plan. | | Availability | Web dashboard and CLI on any operating system. Available to teams now. | Cowork's product page offers a macOS download. Routines are in Claude Code on Pro, Max, Team, and Enterprise. | Where Claude Cowork is strong ## What Claude Cowork does well * A frontier model is included in the plan. There is no separate model bill. * Enterprise plumbing is mature. Events go to a SIEM, there is a Compliance API, and admins can turn Cowork and its browser on or off per organization. * Cowork has a built-in browser and works on the files already on your Mac. * Routines run on Claude Code's web infrastructure, so nothing depends on your laptop being open, and they react to GitHub PR and release events. * Distribution. Many teams already have a Claude seat, so there is nothing new to buy. Where Helios is different ## How Helios works instead * Every run and every chat gets its own sandbox with a shell, a filesystem, and code execution. The sandbox is discarded when the run ends. * Workflows start on a cron schedule, a signed webhook, or an integration event from GitHub, Slack, or Plain, for any task. Cowork tasks run on a schedule. Routines react to a schedule, an API call, or GitHub events. * Spend is credits on one organization meter with a spending limit. It is not a per-person seat allowance shared with chat. * Agents edit shared Library files through a review step. A person approves or discards each file change before it lands. Cowork outputs stay on one person's machine. * One permissions model. The roles you set in the dashboard apply in the CLI too, so \`helios share\` and the share dialog do the same thing. Pricing ## What each one charges Public list prices, checked on 7 September 2026\. Prices change, so confirm on each vendor's page before you decide. Helios 5,000 free credits to start. $0.002 per credit after that. No seats. Set an organization spending limit and optional auto refill. [Helios pricing →](/pricing/) Claude Cowork No separate price. Cowork and Routines draw from the Claude seat. Team standard seats are listed at about $20 to $25 per person per month, and premium seats at $100 to $125 with Cowork included. Routines are capped per day: Pro 5, Max 15, Team and Enterprise 25, then paid overage. [Claude Cowork pricing page →](https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork) Checked on 7 September 2026 Using both ## Helios and Claude Cowork together Most teams keep both. Cowork is good for one person's documents, spreadsheets, and memos on their own machine. Helios is for work that must run when nobody is at a keyboard, for a team, on a trigger, against the full API of a tool. Helios uses Anthropic models, so you can move a task from Cowork to a Helios workflow without changing how you write the prompt. FAQ ## Helios and Claude Cowork, common questions ### Does Helios use Claude? ### Can I set a spend cap? ### Can Helios react to GitHub events like Routines? ### Do I need a Claude subscription to use Helios? ### Is Cowork available on Linux or in a browser? ## Run your first task. 5,000 free credits. Set an organization spending limit before your first workflow runs. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) Claude Cowork information is from public pages on 7 September 2026\. Marks belong to their owners. Helios is not affiliated with Claude Cowork. Tell us if something is out of date at [support@heliosapp.com](mailto:support@heliosapp.com?subject=Correction%20for%20the%20Helios%20vs%20Claude%20Cowork%20page). Sources * [Claude Cowork product page](https://claude.com/product/cowork) * [Introducing Routines in Claude Code](https://claude.com/blog/introducing-routines-in-claude-code) * [Schedule recurring tasks in Claude Cowork (help center)](https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork) * [Use Claude Cowork on Team and Enterprise plans (help center)](https://support.claude.com/en/articles/13455879-use-claude-cowork-on-team-and-enterprise-plans) * [Claude Code team pricing summary (morphllm.com)](https://www.morphllm.com/claude-code-team-pricing) --- # Helios vs Dust - Helios vs Dust | Helios URL: https://www.heliosapp.com/compare/dust Description: Dust builds chat agents grounded in company data. Helios runs agents on their own computer, on a trigger, with the full API of each tool. [← All comparisons](/compare/) Helios vs Dust # Helios vs Dust Dust builds chat agents grounded in company data. Helios runs agents on their own computer, on a trigger, with the full API of each tool. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Dust describes itself as multiplayer AI for human and agent collaboration. Its agents answer questions in chat and call tools, grounded in data indexed from sources like Notion, Drive, Slack, GitHub, and Salesforce. Helios is built for work that has to run without a person in the chat. Each run gets its own sandbox, starts on a schedule, a webhook, or an event, and can call the full API of every connected tool. Both products are used by teams that want agents shared across a company. They solve different parts of that problem. At a glance ## Side by side Short facts for each product. The Dust column comes from public pages on the date shown at the bottom of this page. | Topic | Helios | Dust | | ------------------------- | ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | | Computer per run | Yes. Every run and chat starts an isolated sandbox with shell, filesystem, and code execution. | Agents run in conversation and call tools. Dust's public pages do not describe a per-run computer. | | Tools and APIs | The full OpenAPI or GraphQL surface of each connected service, plus remote MCP servers. | Tools and data connectors configured per agent, with 100 or more indexed data sources. | | Triggers | Manual, cron schedule, signed webhook, and events from GitHub, Slack, and Plain. | Chat in Dust or Slack. Event triggers are not described on the public pages we checked. | | Human review | Agents propose edits to shared Library files. A person approves or discards each file. | A person reads the agent's answer in chat before acting on it.Requires the Library release. | | Permissions | Four resource roles. Share with a person, a group, a service account, or the whole organization, with optional expiry. | Managed per workspace and seat. Check Dust's documentation for the current role list. | | CLI | A terminal app and CLI with the same roles as the dashboard. JSON output when piped. | A public API, metered at $0.01 per credit.Requires the CLI release. | | Pricing model | Usage credits. 5,000 free credits, then $0.002 per credit. No seats. | Per seat, with a credit bundle per plan. Free, Pro at $30 per seat per month, Max at $150 per seat per month. | | Organization spend limits | A monthly spending limit for the organization. Triggers stop when credits run out. Optional auto refill. | Credits reset monthly with no rollover. Enterprise plans pool credits across seats. | | Memory or context | Shared Library files mount into every run. Changes go through review before they are saved. | A company data index that agents retrieve from at answer time.Requires the Library release. | Where Dust is strong ## What Dust does well * Company knowledge indexing. Dust connects to 100 or more data sources and grounds every answer in that index. * Model choice per agent. Dust lets a builder pick from Claude, GPT, Gemini, and Mistral models for each agent. * Chat where people already are. Dust agents live inside Slack, and non-technical builders can create them without code. * EU data residency and SOC 2 Type II, with customers such as Doctolib, Clay, Datadog, and 1Password named on its public pages. Where Helios is different ## How Helios works instead * Every run gets its own computer. A Helios run starts a fresh sandbox with a shell, a filesystem, and code execution. Dust agents answer in conversation and call tools. * The full API of each tool. Helios indexes the complete OpenAPI or GraphQL surface of every connected service. The agent finds the endpoint it needs and calls it. There is no fixed action list per agent. * Runs start on a trigger. A Helios workflow runs on a cron schedule, a signed webhook, or an event from GitHub, Slack, or Plain. Dust's public pages describe conversation and retrieval. We did not find event-driven execution described there. * Usage is metered at the organization level. Helios charges credits with a monthly spending limit for the whole organization. There are no seats. Dust bundles credits per seat. * Agents propose file changes and people approve them. Library edits show as a side-by-side diff with per-file approve or discard. Requires the Library release. Pricing ## What each one charges Public list prices, checked on 7 September 2026\. Prices change, so confirm on each vendor's page before you decide. Helios 5,000 free credits to start. Then $0.002 per credit. No seats. Monthly spending limit per organization. Enterprise pricing on request. [Helios pricing →](/pricing/) Dust Free seat with 500 lifetime credits. Pro at $30 per seat per month, or $24 billed annually, with 8,000 credits. Max at $150 per seat per month, or $120 billed annually, with 40,000 credits. Enterprise is custom with pooled credits. Public list prices as of September 2026. [Dust pricing page →](https://www.usagepricing.com/blueprint/dust) Checked on 7 September 2026 Using both ## Helios and Dust together Moving a Dust agent to Helios means copying its instructions into a workflow prompt, connecting the same tools, and adding a trigger. There is no importer. Many teams keep Dust for questions over company documents and use Helios for work that has to run on a schedule or on an event. FAQ ## Helios and Dust, common questions ### Does Helios use Claude? ### Can I set a spend cap? ### Do I pay per seat? ### Can Helios search my company documents like Dust does? ### Can I import my Dust agents? ## Run your first task. 5,000 free credits. Set an organization spending limit before your first workflow runs. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) Dust information is from public pages on 7 September 2026\. Marks belong to their owners. Helios is not affiliated with Dust. Tell us if something is out of date at [support@heliosapp.com](mailto:support@heliosapp.com?subject=Correction%20for%20the%20Helios%20vs%20Dust%20page). Sources * [Dust home page](https://dust.tt/home) * [Dust pricing summary (Usage Pricing)](https://www.usagepricing.com/blueprint/dust) * [Dust pricing summary (Costbench)](https://costbench.com/software/ai-search-enterprise/dust-tt/) * [Dust Series B announcement (Tech.eu, May 2026)](https://tech.eu/2026/05/18/dust-raises-40m-series-b-to-build-the-multiplayer-operating-system-for-enterprise-ai/) --- # Helios vs Grok Bot - Helios vs Grok Bot | Helios URL: https://www.heliosapp.com/compare/grok-bot Description: Grok Bot gives one person a team of always-on Bots in a desktop app. Helios gives a whole team agents that run in isolated sandboxes on triggers. [← All comparisons](/compare/) Helios vs Grok Bot # Helios vs Grok Bot Grok Bot gives one person a team of always-on Bots in a desktop app. Helios gives a whole team agents that run in isolated sandboxes on triggers. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Grok Bot launched in beta on August 11, 2026 at x.ai/bot. It is a desktop and iOS app where named Bots work on a persistent cloud computer. It is not the @grok reply account on X, and it is not Grok Build, the open source coding CLI. Helios is a web product where each run gets its own sandbox, tools are reached through their full APIs, and spend is capped for the organization. At a glance ## Side by side Short facts for each product. The Grok Bot column comes from public pages on the date shown at the bottom of this page. | Topic | Helios | Grok Bot | | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | Computer per run | A fresh cloud sandbox for every run and chat, with shell, filesystem, and code execution. | One persistent cloud computer shared by all of an account's Bots. | | Tools and APIs | 21 integrations. The agent searches each service's full OpenAPI or GraphQL surface and calls any endpoint. Remote MCP servers can be attached. | MCP plus 1,000+ connectors, and a browser the Bot drives like a person. | | Triggers | Manual, schedule, signed webhook, and integration events from GitHub, Slack, and Plain. | Routines recorded by demonstration, run on a schedule or an event. | | Human review | Agents propose edits to shared Library files. A person approves or discards each file, with conflict detection. | Per-action prompts with Allow once, Deny, and Always allow. Human takeover for logins and payments.Library review depends on PRs 600 to 603. | | Permissions | Cedar roles on every resource, viewer to admin. Share with a person, group, service account, or the whole organization, with expiry. | Personal account. Enterprise controls are on a waitlist. | | CLI | helios CLI and terminal app with the same roles and sharing as the dashboard, JSON output when piped. | No CLI for Grok Bot. Grok Build is a separate coding CLI.CLI depends on PRs 619 and 624. | | Pricing model | Credits. 5,000 free, then $0.002 per credit. No seats. | Bundled in SuperGrok ($30), Plus ($100), Heavy ($300) and Cursor plans, with a weekly allowance and overflow billed at model cost. | | Organization spend limits | Monthly spending limit per organization. Triggers are blocked when credits run out. | "No Grok Bot-specific spend cap yet." | | Memory and context | Shared Library files mounted into the sandbox. Changes are reviewed before they merge. | Files and state persist on the Bot's computer between tasks.Library depends on PRs 600 to 603. | | Platforms | Web dashboard, Linux sandboxes, and a CLI. | Desktop app and iOS. Beta, and details may change.CLI depends on PRs 619 and 624. | Where Grok Bot is strong ## What Grok Bot does well * Routines by demonstration. You record up to ten minutes of work and the Bot repeats it on a schedule or event. * A persistent computer with a browser, files, and a shell. A person can take over for passwords, two-factor codes, CAPTCHAs, and payments. * Group chats of two to six Bots, a native iOS app, and a bundle inside existing SuperGrok and Cursor subscriptions. Where Helios is different ## How Helios works instead * Every Helios run and chat starts in its own cloud sandbox. xAI's docs say "All of your Bots use the same persistent cloud computer" and "Do not use separate Bots as a security boundary." * Helios has organization spending limits. Triggers stop when credits run out. xAI's pricing guidance says there is "no Grok Bot-specific spend cap yet" and overflow is billed from model and token cost. * Helios is available to teams today with resource roles, groups, service accounts, and share expiry. Grok Bot enterprise access is a waitlist. Pricing ## What each one charges Public list prices, checked on 7 September 2026\. Prices change, so confirm on each vendor's page before you decide. Helios 5,000 free credits, then $0.002 per credit. Usage based, no seats, with an organization spending limit and optional auto refill. [Helios pricing →](/pricing/) Grok Bot No standalone price as of September 7, 2026\. Included with SuperGrok $30, Plus $100, and Heavy $300 per month, and with Cursor Pro, Pro+, Ultra, and Teams plans. Weekly allowance, then overflow billed from model and token cost. Seven day trial credit. Enterprise is a waitlist. [Grok Bot pricing page →](https://www.aibuilderclub.com/blog/grok-bot-pricing) Checked on 7 September 2026 Using both ## Helios and Grok Bot together Some teams keep a Grok Bot for personal desktop work that needs a browser or a phone, and run team workflows on Helios where each run is isolated and spend has a cap. If you are moving a routine to Helios, write it as a plain language workflow, attach the integrations it needs, and set a schedule or webhook trigger. FAQ ## Helios and Grok Bot, common questions ### Is Grok Bot the same as @grok on X? ### Does Helios use Grok models? ### Can I set a spend cap in Helios? ### Does Helios have a browser tool? ### Do Helios agents share a computer? ## Run your first task. 5,000 free credits. Set an organization spending limit before your first workflow runs. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) Grok Bot information is from public pages on 7 September 2026\. Marks belong to their owners. Helios is not affiliated with Grok Bot. Tell us if something is out of date at [support@heliosapp.com](mailto:support@heliosapp.com?subject=Correction%20for%20the%20Helios%20vs%20Grok%20Bot%20page). Sources * [xAI, Introducing Grok Bot](https://x.ai/news/introducing-grok-bot) * [xAI, Grok Bot product page](https://x.ai/bot) * [xAI, Grok Build 0.1](https://x.ai/news/grok-build-0-1) * [xAI, Designing Grok Bot](https://x.ai/news/designing-grok-bot) * [Composio, Guide to Grok Bot](https://composio.dev/content/guide-to-frok-bot) * [AI Builder Club, Grok Bot pricing](https://www.aibuilderclub.com/blog/grok-bot-pricing) --- # Helios vs Instinct - An assistant you text. A runner for your team. | Helios URL: https://www.heliosapp.com/compare/instinct Description: Instinct is an invite-only personal agent you reach by text or phone. It acts on a cloud computer with your accounts. Helios runs team workflows on triggers with roles and one spend meter. [← All comparisons](/compare/) Helios vs Instinct # An assistant you text. A runner for your team. Instinct is an invite-only personal agent you reach by text or phone. It acts on a cloud computer with your accounts. Helios runs team workflows on triggers with roles and one spend meter. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Instinct is a personal AI assistant from Spear Street Technology, a San Francisco company led by Noah Shinn, a former research scientist at Sierra. There is no app. You text it on iMessage or WhatsApp, or call it, and it works on a persistent cloud computer with a browser and your connected accounts. Early users have booked restaurants, negotiated bills, bought groceries and concert tickets, and cancelled subscriptions. As of September 2026 it is in an invite-only beta, it is free while in beta, and the company has raised $350 million at a $2.5 billion valuation. Helios is aimed at engineers and operators. Each run gets its own sandbox, workflows start on schedules and events, and spend is one meter for the organization. Both products give an agent a real computer. They differ on who it is for, how work is triggered, and how it is shared and reviewed. At a glance ## Side by side Short facts for each product. The Instinct column comes from public pages on the date shown at the bottom of this page. | Topic | Helios | Instinct | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Computer per run | Yes, on every plan. Each run starts an isolated sandbox with shell, filesystem, and code execution. The sandbox is discarded when the run ends. | One persistent cloud computer per user with a browser and stored credentials. | | Tools and APIs | The full OpenAPI or GraphQL surface of each connected service, plus remote MCP servers. | Connected accounts such as Gmail, messaging apps, calendar, Resy, and travel sites, plus a browser. Its privacy notice also lists screen captures, keyboard input, audio, and location. | | Triggers | Manual, cron schedule, signed webhook, and events from GitHub, Slack, and Plain. | Text messages and phone calls, plus proactive follow-ups. No schedule or webhook trigger is described on the public pages we checked. | | Human review | Agents propose edits to shared Library files. A person approves or discards each file. No approval step inside a run. | Not described on the public pages we checked. Its terms allow it to enter into agreements and transactions on the user's behalf.Requires the Library release. | | Permissions | Four resource roles, groups, service accounts, and share expiry for every organization. | Per-account connections chosen by the user. No team or organization features are described on the public pages we checked. | | CLI | A terminal app and CLI with the same roles as the dashboard. JSON output when piped. | No CLI or developer API is described on the public pages we checked.Requires the CLI release. | | Pricing model | Usage credits. 5,000 free credits, then $0.002 per credit. No seats. | Free during the invite-only beta. No public pricing as of September 2026. | | Organization spend limits | A monthly spending limit for the organization. Triggers stop when credits run out. Optional auto refill. | Not described on the public pages we checked. | | Memory or context | Shared Library files mount into every run. Changes go through review before they are saved. | One continuous conversation per user. It indexes connected email and messages. Testers reported that indexed emails stayed after a source was disconnected.Requires the Library release. | | Availability | Web dashboard and CLI on any operating system. Available to teams now. | Invite-only beta by waitlist at instinct.co or an invite from a member. Reached by text or phone. | Where Instinct is strong ## What Instinct does well * No app to learn. You text or call Instinct like a person, on iMessage, WhatsApp, or the phone. * A persistent cloud computer with a browser and stored credentials, so it can use websites and services that have no API. * Proactive follow-up. It picks up dropped threads and reaches out without being asked. * Broad reach into a person's life. It connects to email, messages, calendar, and reservation and travel services. * Well funded. $350 million raised, so the product is likely to keep developing. Where Helios is different ## How Helios works instead * Built for teams. Helios workflows are shared with people, groups, or the whole organization with four resource roles and share expiry. Instinct is one assistant per person. * Triggers. Helios workflows start on a cron schedule, a signed webhook, or events from GitHub, Slack, and Plain. Instinct is driven by messages and its own follow-ups. * The full API of each tool. Helios indexes the complete OpenAPI or GraphQL surface of a connected service, plus remote MCP servers. Instinct works through connected accounts and a browser. * Credentials stay out of the agent. Helios injects credentials at the network layer, so the agent never holds a token. Instinct stores credentials on its cloud computer. * Reviewed shared memory. Agents propose edits to Library files and a person approves each one. Requires the Library release. Pricing ## What each one charges Public list prices, checked on 14 September 2026\. Prices change, so confirm on each vendor's page before you decide. Helios 5,000 free credits to start. Then $0.002 per credit. No seats. Monthly spending limit per organization. Enterprise pricing on request. [Helios pricing →](/pricing/) Instinct Free during the invite-only beta. Spear Street Technology has not published pricing as of September 2026\. Third-party guides speculate about subscription tiers, so check the live site. [Instinct pricing page →](https://www.vellum.ai/blog/official-instinct-breakdown) Checked on 14 September 2026 Using both ## Helios and Instinct together The two products rarely overlap. Instinct is for one person's bookings, purchases, and inbox. Helios is for work that must run for a team, on a trigger, against the full API of a tool, with roles and a shared spend limit. There is no importer between them. A task you would text to Instinct becomes a Helios workflow by writing the steps as a prompt, connecting the same tools, and picking a trigger. FAQ ## Helios and Instinct, common questions ### Does Helios give every run a computer like Instinct does? ### Can Helios browse websites like Instinct? ### Can I text a Helios workflow? ### Does the Helios agent hold my credentials? ### Is Instinct available for teams? ## Run your first task. 5,000 free credits. Set an organization spending limit before your first workflow runs. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) Instinct information is from public pages on 14 September 2026\. Marks belong to their owners. Helios is not affiliated with Instinct. Tell us if something is out of date at [support@heliosapp.com](mailto:support@heliosapp.com?subject=Correction%20for%20the%20Helios%20vs%20Instinct%20page). Sources * [Instinct's powerful AI assistant is raising privacy and security concerns (TechCrunch)](https://techcrunch.com/2026/08/24/instincts-powerful-ai-assistant-is-raising-privacy-and-security-concerns/) * [Viral AI startup Instinct has raised $350M at a $2.5B valuation (TechCrunch)](https://techcrunch.com/2026/08/26/viral-ai-startup-instinct-has-raised-350-million-at-a-2-5-billion-valuation/) * [Official Instinct breakdown (Vellum)](https://www.vellum.ai/blog/official-instinct-breakdown) * [AI assistant Instinct hits $2.5 billion valuation (Forbes)](https://www.forbes.com/sites/iainmartin/2026/08/26/vcs-are-so-obsessed-with-this-ai-assistant-that-its-valuation-jumped-fivefold-in-weeks/) --- # Helios vs Lindy - Helios vs Lindy | Helios URL: https://www.heliosapp.com/compare/lindy Description: Lindy sells per-user plans with credit bundles and a large connector library. Helios gives every run its own computer and meters usage for the whole organization. [← All comparisons](/compare/) Helios vs Lindy # Helios vs Lindy Lindy sells per-user plans with credit bundles and a large connector library. Helios gives every run its own computer and meters usage for the whole organization. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Lindy's home page says it connects to all your tools, knows everything about your company, and does real work for the whole team. It is aimed at operations, sales, and support teams at small and mid-sized companies, with templates and a quick first setup. Helios is aimed at engineers first and operators second. Each run gets a full computer on every plan, spending limits apply to the organization before a run starts, and roles and sharing are part of the product for every team. The two products overlap on scheduled and event-driven work. They differ on what an agent gets to work with and on how spend is controlled. At a glance ## Side by side Short facts for each product. The Lindy column comes from public pages on the date shown at the bottom of this page. | Topic | Helios | Lindy | | ------------------------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | | Computer per run | Yes, on every plan. Each run starts an isolated sandbox with shell, filesystem, and code execution. | Computer use is listed on the Pro plan and above. | | Tools and APIs | The full OpenAPI or GraphQL surface of each connected service, plus remote MCP servers. | More than 1,000 connectors with ready-made actions. | | Triggers | Manual, cron schedule, signed webhook, and events from GitHub, Slack, and Plain. | Triggers from connected apps such as email and calendar, plus schedules. | | Human review | Agents propose edits to shared Library files. A person approves or discards each file. | Not described on the pricing page we checked. See Lindy's documentation.Requires the Library release. | | Permissions | Four resource roles, groups, service accounts, and share expiry for every organization. | Per-user plans. Audit logs and HIPAA are listed on the Enterprise plan. | | CLI | A terminal app and CLI with the same roles as the dashboard. JSON output when piped. | No CLI is listed on the public pages we checked.Requires the CLI release. | | Pricing model | Usage credits. 5,000 free credits, then $0.002 per credit. No seats. | Per user per month, with a credit bundle per plan. Plus at $29.99, Pro at $99.99, Max at $199.99. | | Organization spend limits | A monthly spending limit for the organization. Triggers stop when credits run out. Optional auto refill. | Credits do not roll over. Service pauses when a plan's credits reach zero. | | Memory or context | Shared Library files mount into every run. Changes go through review before they are saved. | Lindy's home page says its agents know everything about your company.Requires the Library release. | Where Lindy is strong ## What Lindy does well * More than 1,000 connectors, so most SaaS tools have a ready-made action. * Interfaces where operators already are. Lindy agents can be reached over iMessage and Slack, and Lindy includes a meeting recorder. * A large template library and an easy first setup for people who do not write code. * A seven-day trial and month-to-month billing on the self-serve plans. Where Helios is different ## How Helios works instead * A full computer on every plan. Each Helios run starts its own sandbox with a shell, a filesystem, and code execution. Lindy lists computer use on its Pro plan and above. * Spending limits before a run. Each Helios organization sets a monthly spending limit. When credits run out, triggers stop. Usage is one meter for the whole organization. * Roles and sharing for every team. Helios has four resource roles, groups, service accounts, and share expiry. None of these are gated to a plan. * The full API of each tool. Helios indexes the complete OpenAPI or GraphQL surface of a connected service, so an agent is not limited to a curated action list. * The same permissions in the terminal. The Helios CLI reads the same roles as the dashboard and prints JSON when piped. Requires the CLI release. Pricing ## What each one charges Public list prices, checked on 7 September 2026\. Prices change, so confirm on each vendor's page before you decide. Helios 5,000 free credits to start. Then $0.002 per credit. No seats. Monthly spending limit per organization. Enterprise pricing on request. [Helios pricing →](/pricing/) Lindy Plus at $29.99 per user per month with 3,000 credits. Pro at $99.99 with 15,000 credits. Max at $199.99 with 35,000 credits. Enterprise is custom. Seven-day trial, month to month, no rollover. Prices from lindy.ai/pricing as of September 2026\. Third-party guides list other prices, so check the live page. [Lindy pricing page →](https://www.lindy.ai/pricing) Checked on 7 September 2026 Using both ## Helios and Lindy together Moving a Lindy agent to Helios means writing its steps as a workflow prompt, connecting the same tools, and choosing a trigger. There is no importer. Helios has fewer connectors than Lindy, so check the integrations page first. For a tool Helios does not connect to, a remote MCP server or a direct API call from the sandbox often covers it. FAQ ## Helios and Lindy, common questions ### Can I set a spend cap? ### Do I pay per seat? ### Does every plan get a computer? ### Does Helios have as many integrations as Lindy? ### Does Helios use Claude? ## Run your first task. 5,000 free credits. Set an organization spending limit before your first workflow runs. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) Lindy information is from public pages on 7 September 2026\. Marks belong to their owners. Helios is not affiliated with Lindy. Tell us if something is out of date at [support@heliosapp.com](mailto:support@heliosapp.com?subject=Correction%20for%20the%20Helios%20vs%20Lindy%20page). Sources * [Lindy home page](https://www.lindy.ai) * [Lindy pricing](https://www.lindy.ai/pricing) * [Lindy pricing guide (CloudTalk)](https://www.cloudtalk.io/blog/lindy-ai-pricing/) --- # Helios vs Meta Muse - A personal agent and a team runner. | Helios URL: https://www.heliosapp.com/compare/meta-muse Description: Muse runs errands for one person on a Meta virtual machine with a consumer subscription. Helios runs workflows for a team on triggers, with one meter for the organization. [← All comparisons](/compare/) Helios vs Meta Muse # A personal agent and a team runner. Muse runs errands for one person on a Meta virtual machine with a consumer subscription. Helios runs workflows for a team on triggers, with one meter for the organization. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Meta announced Muse on September 8, 2026\. Meta calls it a secure, private personal AI agent that helps with people's goals and suggests ideas. Each user gets a dedicated virtual machine in Meta's cloud with its own browser, and a separate Sentinel agent checks everything Muse sends to the internet. Muse sends emails, books travel, fills forms, negotiates bills, and pays with one-time card numbers through Link by Stripe. It is aimed at consumers in the United States, on iOS, Android, WhatsApp, and muse.ai. Helios is aimed at engineers and operators. Each run gets its own sandbox with a shell and code execution, workflows start on schedules and events, and spend is one meter for the whole organization. The two products both give an agent a real computer. They differ on who the computer is for and how the work is triggered and shared. At a glance ## Side by side Short facts for each product. The Meta Muse column comes from public pages on the date shown at the bottom of this page. | Topic | Helios | Meta Muse | | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Computer per run | Yes, on every plan. Each run starts an isolated sandbox with shell, filesystem, and code execution. The sandbox is discarded when the run ends. | A dedicated virtual machine per user, called Muse Secure VM, with its own browser. It keeps working after the app is closed. | | Tools and APIs | The full OpenAPI or GraphQL surface of each connected service, plus remote MCP servers. | Connected consumer apps for email, calendar, payments, health, shopping, and smart home, plus a browser for the open web. Users pick which apps to connect and can revoke access. | | Triggers | Manual, cron schedule, signed webhook, and events from GitHub, Slack, and Plain. | Chat messages and Muse's own proactive suggestions. It comes back when something changes. No schedule or webhook trigger is described on the public pages we checked. | | Human review | Agents propose edits to shared Library files. A person approves or discards each file. No approval step inside a run. | Approval gates before sensitive actions and a complete audit trail of past and planned actions.Requires the Library release. | | Permissions | Four resource roles, groups, service accounts, and share expiry for every organization. | Per-app permissions chosen by the user. No team or organization features are described on the public pages we checked. | | CLI | A terminal app and CLI with the same roles as the dashboard. JSON output when piped. | No CLI or developer API is described on the public pages we checked.Requires the CLI release. | | Pricing model | Usage credits. 5,000 free credits, then $0.002 per credit. No seats. | Free tier with a usage meter. Paid plans at $20 and $100 per month for more capacity. | | Organization spend limits | A monthly spending limit for the organization. Triggers stop when credits run out. Optional auto refill. | One subscription per person. The free tier shows a meter of remaining usage. | | Memory or context | Shared Library files mount into every run. Changes go through review before they are saved. | Muse remembers preferences and details per user and makes unprompted suggestions. Users can tell it to forget specific things.Requires the Library release. | | Availability | Web dashboard and CLI on any operating system. Available to teams now. | United States only, on iOS, Android, WhatsApp, and muse.ai. Meta AI glasses are coming soon. | Where Meta Muse is strong ## What Meta Muse does well * A dedicated virtual machine per user with a visible browser, so the agent can use websites that have no API. * Built-in payments. Checkout through Link by Stripe with one-time card numbers and purchase protection. Shop Pay and 1Password support are announced as coming. * Approval gates before sensitive actions, a full audit trail of what the agent has done and plans to do, and a Sentinel agent that must approve any network access. * Reach on consumer surfaces. Muse is available in the Muse app, on WhatsApp, at muse.ai, and is coming to Meta's AI glasses. * A free tier that Meta says covers most of what people need, with Muse Spark, Meta's own model, included. Where Helios is different ## How Helios works instead * Built for teams. Helios workflows are shared with people, groups, or the whole organization with four resource roles and share expiry. Muse is one agent per person. * Triggers. Helios workflows start on a cron schedule, a signed webhook, or events from GitHub, Slack, and Plain. Muse is driven by chat and by Muse's own proactive suggestions. * The full API of each tool. Helios indexes the complete OpenAPI or GraphQL surface of a connected service, plus remote MCP servers. Muse connects to consumer apps and drives them through its browser. * Code execution. Each Helios run starts a sandbox with a shell, a filesystem, Bun, Node, and git. Helios does not include browser automation. * Organization spend. Helios bills credits on one meter with a monthly spending limit. Muse is a per-person subscription. Pricing ## What each one charges Public list prices, checked on 14 September 2026\. Prices change, so confirm on each vendor's page before you decide. Helios 5,000 free credits to start. Then $0.002 per credit. No seats. Monthly spending limit per organization. Enterprise pricing on request. [Helios pricing →](/pricing/) Meta Muse A free tier that Meta says covers most of what people need. Two paid plans at $20 per month and $100 per month with more capacity. Meta has not published a per-tier feature list. United States only as of September 2026. [Meta Muse pricing page →](https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/) Checked on 14 September 2026 Using both ## Helios and Meta Muse together Most teams would use both for different work. Muse is for one person's errands, purchases, and bookings, and it can use websites that have no API. Helios is for work that must run for a team, on a trigger, against the full API of a tool, with roles and a shared spend limit. There is no importer between them. A task that runs in Muse becomes a Helios workflow by writing the steps as a prompt, connecting the same tools, and picking a trigger. FAQ ## Helios and Meta Muse, common questions ### Does Helios give every run a computer like Muse does? ### Can Helios browse websites like Muse? ### Can I set a spend cap? ### Is Muse available for teams? ### Does Helios use Meta's models? ## Run your first task. 5,000 free credits. Set an organization spending limit before your first workflow runs. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) Meta Muse information is from public pages on 14 September 2026\. Marks belong to their owners. Helios is not affiliated with Meta Muse. Tell us if something is out of date at [support@heliosapp.com](mailto:support@heliosapp.com?subject=Correction%20for%20the%20Helios%20vs%20Meta%20Muse%20page). Sources * [Introducing Muse (Meta newsroom)](https://about.fb.com/news/2026/09/introducing-muse-personal-ai-agent/) * [Meta debuts its Muse AI agent (TechCrunch)](https://techcrunch.com/2026/09/08/meta-debuts-its-muse-ai-agent-will-consumers-trust-it/) * [Meta's Muse arrives with three pricing tiers (Yahoo Finance)](https://finance.yahoo.com/technology/ai/articles/metas-muse-arrives-three-pricing-183437528.html) * [Meta debuts Muse, its long-planned personal AI agent (Axios)](https://www.axios.com/2026/09/08/meta-debuts-muse-personal-ai-agent) --- # Helios vs OpenAI Agents - Files persist. Triggers on every plan. | Helios URL: https://www.heliosapp.com/compare/openai-agents Description: OpenAI spreads agent work across scheduled tasks, Codex cloud, and Workspace Agents. Helios runs every workflow on one surface with the same triggers and one meter. [← All comparisons](/compare/) Helios vs OpenAI Agents # Files persist. Triggers on every plan. OpenAI spreads agent work across scheduled tasks, Codex cloud, and Workspace Agents. Helios runs every workflow on one surface with the same triggers and one meter. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. OpenAI offers agent work in several places. ChatGPT scheduled tasks run on a timer and, on Plus and above, on Gmail, Slack, and GitHub events. Codex cloud runs coding tasks in a disposable container. Workspace Agents are in preview for Business, Enterprise, and Edu, metered in credits. Helios is one product. Each run gets a sandbox, files come from a shared Library, and the same triggers work on every account. This page lists the facts, with dates, and lets you decide. At a glance ## Side by side Short facts for each product. The OpenAI Agents column comes from public pages on the date shown at the bottom of this page. | Topic | Helios | OpenAI Agents | | ----------------- | ------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Sandbox per run | Yes. Each run and chat gets its own sandbox with shell, files, and code execution. 30 minute limit per workflow run. | Codex cloud: a disposable container per task, cached for at most 12 hours, internet off by default. No published CPU, RAM, or timeout. Scheduled tasks: web or desktop, no sandbox. | | Tools and APIs | The full API of each connected tool. The agent searches the API surface and calls the endpoint it needs. | Connectors through the Connector Registry, and the Agents SDK for developers. ChatKit remains after the Agent Builder shutdown. | | Triggers | Manual, cron schedule, signed webhook, and integration events from GitHub, Slack, and Plain. Same on every account. | Scheduled tasks: timer on any plan. Gmail, Slack, and GitHub events on Plus and above since August 25 2026, web only. Desktop tasks need the computer on. | | Human review | Library changes are proposed by the agent and approved per file by a person. No approval step inside a run. | Codex opens pull requests for a person to review. Admins can allow or block event-triggered scheduled tasks. | | Permissions | Resource roles viewer, operator, editor, and admin. Share with a person, a group, or the whole organization, with expiry. | Workspace admin settings, including 'Allow event-triggered scheduled tasks'. Workspace Agents activity in the admin console. | | CLI | The Helios CLI runs, shares, and triggers workflows with the same permissions as the dashboard. JSON output when piped. | Codex CLI for local coding tasks. Scheduled tasks and Workspace Agents are web and app surfaces. | | Pricing model | Credits. 5,000 free to start, then $0.002 per credit. No seats. | Seats. Plus $20, Pro $200, Business $20 to $25 per user with a two-user minimum, Enterprise custom. Codex, Work, and Workspace Agents share one agentic credit pool.Per eesel.ai and openai.com, Sep 2026 | | Org spend limits | Yes. A monthly spending limit for the organization. Triggers stop when credits run out. | Workspace Agents are credit metered since July 6 2026, typical run 5 to 25 credits. Limits are set at the seat and pool level. | | Memory or context | Shared Library files mounted into the sandbox at \~/context. Edits are staged for review. | ChatGPT memory for chat. Web scheduled tasks keep no folder between runs. Codex containers are rebuilt after 12 hours. | | Availability | Web dashboard and CLI on any operating system. Available to teams now. | Scheduled tasks on every plan. Codex cloud on Plus and above. Workspace Agents in preview on Business, Enterprise, and Edu. | Where OpenAI Agents is strong ## What OpenAI Agents does well * Distribution and price anchor. ChatGPT Plus is $20 per month and most people already have an account. * Model quality. OpenAI models are among the best available, and they are in the plan. * Event triggers in a consumer product. Since August 25 2026, scheduled tasks on Plus and above can start on Gmail, Slack, and GitHub events. * Codex cloud integrates with GitHub and gives each task a fresh container with internet off by default. * Workspace Agents show activity in the admin console, and Slack-triggered runs were free on the date checked. Where Helios is different ## How Helios works instead * Files persist between runs. Shared Library files mount into the sandbox at \~/context, and edits are staged for review. Codex containers are 'cached for at most 12 hours, then rebuilt', and web scheduled tasks keep no folder between runs. * Triggers are the same on every account and surface. Manual, cron schedule, signed webhook, and integration events from GitHub, Slack, and Plain. OpenAI event triggers are web only and gated by plan. * One surface. OpenAI retired Operator in 2025, removed ChatGPT agent mode in August 2026, and will shut down Agent Builder, Evals, and reusable Prompts on November 30 2026\. Helios has not retired an agent surface. * One permissions model in the dashboard and the CLI. Roles, groups, and service accounts behave the same in both. * One meter. Credits with an organization spending limit cover model and sandbox usage for every workflow and chat. Pricing ## What each one charges Public list prices, checked on 7 September 2026\. Prices change, so confirm on each vendor's page before you decide. Helios 5,000 free credits to start. $0.002 per credit after that. No seats. Set an organization spending limit and optional auto refill. [Helios pricing →](/pricing/) OpenAI Agents ChatGPT Plus $20 per month, Pro $200, Business $20 to $25 per user per month with a two-user minimum, Enterprise custom. Codex, ChatGPT Work, and Workspace Agents share one agentic credit pool. Workspace Agents are credit metered since July 6 2026, with a typical run at 5 to 25 credits. [OpenAI Agents pricing page →](https://www.eesel.ai/blog/chatgpt-work-pricing) Checked on 7 September 2026 Using both ## Helios and OpenAI Agents together Most teams keep both. ChatGPT stays for chat and quick research, and Codex stays for pull requests in a repo. Helios takes the work that must run on a trigger for a team, with the full API of each tool and files that carry from one run to the next. If you built on Agent Builder, note the November 30 2026 shutdown and move those flows to a Helios workflow or to the Agents SDK before then. FAQ ## Helios and OpenAI Agents, common questions ### Is ChatGPT agent mode still available? ### What happens to Agent Builder on November 30 2026? ### Do files persist between Helios runs? ### Can I set a spend cap? ### Do Helios triggers depend on my plan? ## Run your first task. 5,000 free credits. Set an organization spending limit before your first workflow runs. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) OpenAI Agents information is from public pages on 7 September 2026\. Marks belong to their owners. Helios is not affiliated with OpenAI Agents. Tell us if something is out of date at [support@heliosapp.com](mailto:support@heliosapp.com?subject=Correction%20for%20the%20Helios%20vs%20OpenAI%20Agents%20page). Sources * [ChatGPT agent mode removal notice (usecarly.com)](https://www.usecarly.com/blog/chatgpt-agent-mode/) * [Agent Builder deprecation (OpenAI developer docs)](https://developers.openai.com/api/docs/guides/agent-builder) * [AgentKit and Agent Builder timeline (montanalabs.ai)](https://montanalabs.ai/news/openai-s-agentkit-and-the-eight-month-lifespan-of-agent-builder/) * [ChatGPT scheduled tasks and automations (learn.chatgpt.com)](https://learn.chatgpt.com/docs/automations) * [Codex cloud containers (agent37.com)](https://www.agent37.com/blog/codex-cloud) * [Introducing Workspace Agents in ChatGPT (openai.com)](https://openai.com/index/introducing-workspace-agents-in-chatgpt/) * [Workspace Agents pricing and credits (useauteur.com)](https://useauteur.com/blog/chatgpt-workspace-agents-pricing-credits-2026) * [ChatGPT Work pricing (eesel.ai)](https://www.eesel.ai/blog/chatgpt-work-pricing) --- # Helios vs PromptQL - When to use Helios or PromptQL | Helios URL: https://www.heliosapp.com/compare/promptql Description: PromptQL answers questions over governed data with shared threads. Helios runs tasks that act on your tools. Many teams need both. [← All comparisons](/compare/) Helios vs PromptQL # When to use Helios or PromptQL PromptQL answers questions over governed data with shared threads. Helios runs tasks that act on your tools. Many teams need both. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. PromptQL is Hasura's multiplayer AI agent. Its own site says it has "shared threads and a shared brain". It plans in a DSL, compiles the plan to Python and SQL, and runs it outside the model, so answers over data are repeatable and cited. Helios is a different category. Each run gets a computer, reaches tools through their full APIs, and starts on a schedule, a webhook, or an event. This page explains where each one fits. At a glance ## Side by side Short facts for each product. The PromptQL column comes from public pages on the date shown at the bottom of this page. | Topic | Helios | PromptQL | | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | Computer per run | A fresh cloud sandbox for every run and chat, with shell, filesystem, and code execution. | Generated Python and SQL run in PromptQL's runtime outside the model. | | Tools and APIs | 21 integrations reached through their full OpenAPI or GraphQL surface, plus Postgres, MySQL, and ClickHouse connections with an SSH tunnel option. Remote MCP servers can be attached. | Data sources and apps modeled in Hasura DDN. Cross-source joins and scoped access. | | Triggers | Manual, schedule, signed webhook, and integration events from GitHub, Slack, and Plain. | Chat threads first. Automations are exposed as HTTP APIs. | | Human review | Agents propose edits to shared Library files. A person approves or discards each file, with conflict detection and history. | Every answer carries citations and an audit trail. Answers are reviewed in shared threads.Library review depends on PRs 600 to 603. | | Permissions | Cedar roles on every resource, viewer to admin. Share with a person, group, service account, or the whole organization, with expiry. | Scoped access on data sources, SSO on the enterprise plan. | | CLI | helios CLI and terminal app with the same roles and sharing as the dashboard, JSON output when piped. | Hasura DDN CLI for metadata and project setup.CLI depends on PRs 619 and 624. | | Pricing model | Credits. 5,000 free, then $0.002 per credit. No seats. | Per OLU. Starter $0.14 introductory, $0.20 standard. Pay as you go. Enterprise is custom. | | Organization spend limits | Monthly spending limit per organization. Triggers are blocked when credits run out. | Free credit per project and per teammate. Pay as you go beyond that. | | Memory and context | Shared Library files mounted into the sandbox. Changes are reviewed before they merge. | A self-seeding wiki built from connected sources, shared across threads.Library depends on PRs 600 to 603. | | Best fit | Teams that want agents to do work on a trigger without a data engineering step first. | Data and analytics teams with engineering capacity for Hasura DDN metadata. | Where PromptQL is strong ## What PromptQL does well * Deterministic plan then execute. The query plan compiles to Python and SQL and runs outside the model, so the same question gives the same answer with citations. * Cross-database joins through Hasura DDN, with scoped access and a self-seeding team wiki built from Slack, Docs, Snowflake, PostHog, and Salesforce. * Bring your own model, plus VPC and BYOC deployment on the enterprise plan. Where Helios is different ## How Helios works instead * Helios runs any task, including questions over data. An agent can read a Stripe dispute, open a GitHub issue, and post to Slack in one run because it has a shell and the full API of each tool. * Helios needs no metadata modeling to start. Connect an integration or paste a database connection string and describe the task. PromptQL's docs walk through DDN metadata setup first. * Helios prices in credits with an organization spending limit. PromptQL prices per OLU, and the rate depends on the model used. Pricing ## What each one charges Public list prices, checked on 7 September 2026\. Prices change, so confirm on each vendor's page before you decide. Helios 5,000 free credits, then $0.002 per credit. Usage based, no seats, with an organization spending limit and optional auto refill. [Helios pricing →](/pricing/) PromptQL As of September 7, 2026\. Starter is $0.14 per OLU introductory, $0.20 standard, with up to $100 free credit per project plus $70 per teammate. Pay as you go. Enterprise is custom with VPC, BYOC, SSO, and bring your own LLM. [PromptQL pricing page →](https://promptql.io/pricing) Checked on 7 September 2026 Using both ## Helios and PromptQL together Use PromptQL when the question is about governed data and the answer must be repeatable and cited. Use Helios when the work is a task that touches several tools or needs a computer. The two fit together. A Helios workflow can call a PromptQL automation over its HTTP API as one step, then act on the result. FAQ ## Helios and PromptQL, common questions ### Is Helios a replacement for PromptQL? ### Can Helios query my database? ### Do I need a data engineer to start with Helios? ### Can I set a spend cap in Helios? ### Which models does each product use? ## Run your first task. 5,000 free credits. Set an organization spending limit before your first workflow runs. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) PromptQL information is from public pages on 7 September 2026\. Marks belong to their owners. Helios is not affiliated with PromptQL. Tell us if something is out of date at [support@heliosapp.com](mailto:support@heliosapp.com?subject=Correction%20for%20the%20Helios%20vs%20PromptQL%20page). Sources * [PromptQL homepage](https://promptql.io) * [PromptQL pricing](https://promptql.io/pricing) * [Hasura, PromptQL billing terms](https://hasura.io/promptql-billing-terms-1) * [eesel, PromptQL review](https://www.eesel.ai/blog/promptql-review) --- # Guides | Helios URL: https://www.heliosapp.com/guides Description: Step lists for Helios. Run your first workflow, put it on a schedule, react to GitHub events, connect a database, attach an MCP server, share with your team, install the CLI, review Library changes, and move from Relay.app. Guides # Get your first workflow running. Short step lists in the order you meet them. Run a workflow, put it on a trigger, give it tools and context, share it with your team, then move to the CLI and the Library. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) 5,000 free credits to start. 1. [01Run your first workflowDescribe a task in plain words, give the agent one tool, and read the run. Ten minutes from an empty workspace to a transcript you can read end to end.10 min](/guides/run-your-first-agent/) 2. [02Put a workflow on a scheduleTurn a working prompt into a standing task. Describe the cadence the way you would say it out loud. Helios writes the cron expression.8 min](/guides/put-an-agent-on-a-schedule/) 3. [03React to GitHub eventsStart a run the moment a pull request opens, a build finishes, or a tag lands. Filter down to exactly the events you want.12 min](/guides/react-to-github-events/) 4. [04Connect a databaseGive a workflow Postgres, MySQL, or ClickHouse. It reads the schema, writes real SQL, and checks the results in its own sandbox.10 min](/guides/connect-a-database/) 5. [05Attach an MCP serverPoint Helios at a remote MCP server, choose which of its tools workflows may call, and use Helios itself over MCP from other clients.10 min](/guides/attach-an-mcp-server/) 6. [06Pin repositories as contextPin a GitHub repository to a workflow or a chat. The agent starts every run with it.7 min](/guides/pin-context-resources/) 7. [07Use secrets and variablesKeep the values a task needs out of the prompt. Variables hold configuration. Secrets hold credentials. The agent never sees a secret in plain text.8 min](/guides/use-secrets-and-variables/) 8. [08Share with your teamHand a workflow to the people who need it. Four roles decide who may view, run, or edit. Every run leaves a transcript of what happened.9 min](/guides/share-with-your-team/) 9. [09Move from Relay.app to HeliosRelay.app shut down on 16 July 2026\. Paid accounts are deleted on 14 September 2026\. Here is how each Relay concept maps to Helios, and what to export first.15 min](/guides/move-from-relay-app/) 10. [10Install and configure the Helios CLIInstall one binary, run \`helios configure\`, and go from an API key to a running workflow in your terminal. Every command prints JSON when piped.10 min](/guides/install-the-helios-cli/) 11. [11Review agent changes in the LibraryAgents propose edits to shared files. A person reviews the diff and approves or discards each one. Nothing reaches the team's files without approval.8 min](/guides/review-agent-changes-in-the-library/) ## Start with the first guide. Ten minutes from an empty workspace to a run transcript you can read end to end. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Attach an MCP server | Helios URL: https://www.heliosapp.com/guides/attach-an-mcp-server Description: Point Helios at a remote MCP server, choose which of its tools workflows may call, and use Helios itself over MCP from other clients. [← All guides](/guides/) 10 min # Attach an MCP server Point Helios at a remote MCP server, choose which of its tools workflows may call, and use Helios itself over MCP from other clients. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/basics/mcp-servers) 5,000 free credits to start. 1. 01 ### Add the server URL From Settings, then MCP Servers, add a remote server by its HTTP endpoint. Choose whether it belongs to the organization or to one project. 2. 02 ### Choose how it authenticates Servers connect with a bearer token or an OAuth flow. Tokens are stored encrypted and attached at call time, the same way integration credentials are. Set a timeout for slow servers. 3. 03 ### Review the tools it exposes Helios lists every tool the server advertises, with its description and input schema. Read the list before you attach it to anything. This is the surface you hand your workflows. 4. 04 ### Allow only the tools you want The tool allowlist narrows the server to a named subset. A server with forty tools can contribute the three that matter to a task. 5. 05 ### Attach it to a workflow and run it Enable the server on a workflow, name the tools in the prompt, and run it by hand. The transcript shows each MCP tool call next to the integration calls. 6. 06 ### Point another agent at Helios Helios is also an MCP server. A client such as Claude Code can call \`find\_relevant\_apis\` and \`call\_api\` to reach any connected integration through Helios. The same roles apply from that side. Keep going ## Next guides [10 minRun your first workflowDescribe a task in plain words, give the agent one tool, and read the run. Ten minutes from an empty workspace to a transcript you can read end to end.](/guides/run-your-first-agent/)[8 minUse secrets and variablesKeep the values a task needs out of the prompt. Variables hold configuration. Secrets hold credentials. The agent never sees a secret in plain text.](/guides/use-secrets-and-variables/)[7 minPin repositories as contextPin a GitHub repository to a workflow or a chat. The agent starts every run with it.](/guides/pin-context-resources/) Templates ## Put it to work Templates that use what this guide covers. [EngineeringPull request reviewerReviews every pull request against your conventions and leaves inline comments only where it found something concrete.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/pr-review-digest/)[EngineeringIncident postmortem drafterRebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/incident-postmortem-drafter/)[OperationsNightly data quality checksRuns your invariants against production every night and emails the on-call analyst which rows broke and since when.Nightly at 3:00am![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/templates/database-health-check/) ## Try it in your workspace. Start free, connect a tool, and write the first prompt in plain words. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/basics/mcp-servers) --- # Connect a database | Helios URL: https://www.heliosapp.com/guides/connect-a-database Description: Give a workflow Postgres, MySQL, or ClickHouse. It reads the schema, writes real SQL, and checks the results in its own sandbox. [← All guides](/guides/) 10 min # Connect a database Give a workflow Postgres, MySQL, or ClickHouse. It reads the schema, writes real SQL, and checks the results in its own sandbox. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/integrations/databases) 5,000 free credits to start. 1. 01 ### Create a read-only role first Before you touch Helios, create a database role that can read the schemas a task needs and nothing else. Your database enforces the rule, which is where that decision belongs. 2. 02 ### Add the connection From Settings, then Integrations, add a Postgres, MySQL, or ClickHouse connection with a host, port, database, and credentials. The connection string is encrypted and decrypted only when a run needs it. 3. 03 ### Reach a private database through an SSH tunnel When the database sits on a private network, add an SSH tunnel on the connection. Runs connect through the bastion you name. Nothing is exposed to the public internet. 4. 04 ### Ask a question you already know the answer to Start a chat, attach the database, and ask something you can check. The agent reads tables, columns, types, and keys, writes the SQL, runs it, and explains the result. Compare it with the answer you knew. 5. 05 ### Read the SQL it wrote Every run records the queries the agent ran and the rows they returned. When a number looks wrong, the query that produced it is in the transcript. 6. 06 ### Reuse the prompt as a workflow Create a workflow with the same prompt and add a schedule. Put stable facts about the schema in the prompt so every run starts with them. Keep going ## Next guides [7 minPin repositories as contextPin a GitHub repository to a workflow or a chat. The agent starts every run with it.](/guides/pin-context-resources/)[8 minPut a workflow on a scheduleTurn a working prompt into a standing task. Describe the cadence the way you would say it out loud. Helios writes the cron expression.](/guides/put-an-agent-on-a-schedule/)[8 minUse secrets and variablesKeep the values a task needs out of the prompt. Variables hold configuration. Secrets hold credentials. The agent never sees a secret in plain text.](/guides/use-secrets-and-variables/) Templates ## Put it to work Templates that use what this guide covers. [OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out.Mondays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/weekly-metrics-report/)[OperationsNightly data quality checksRuns your invariants against production every night and emails the on-call analyst which rows broke and since when.Nightly at 3:00am![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/templates/database-health-check/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to find the accounts drifting toward the exit.Mondays at 7:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/churn-risk-watchlist/) ## Try it in your workspace. Start free, connect a tool, and write the first prompt in plain words. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/integrations/databases) --- # Install and configure the Helios CLI | Helios URL: https://www.heliosapp.com/guides/install-the-helios-cli Description: Install one binary, run `helios configure`, and go from an API key to a running workflow in your terminal. Every command prints JSON when piped. [← All guides](/guides/) 10 min # Install and configure the Helios CLI Install one binary, run \`helios configure\`, and go from an API key to a running workflow in your terminal. Every command prints JSON when piped. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/cli/install) 5,000 free credits to start. 1. 01 ### Install the binary The CLI ships as a single binary for macOS and Linux. Run the install script from the CLI docs, then check it with \`helios version\`. \`helios doctor\` checks that your machine is ready. 2. 02 ### Create an API key in the dashboard The CLI signs in with an API key. Create one in the Helios dashboard first. Browser login from the terminal is not available yet. 3. 03 ### Run helios configure \`helios configure\` asks for the API key, then a project. Progress is saved to \`\~/.helios/onboarding.json\`, so you can stop and resume. \`helios configure --redo \` repeats one step. 4. 04 ### Set the active project Every command is scoped to a project. Switch with \`helios project use\`, set \`HELIOS\_PROJECT\`, or pass \`--project\` on one command. \`helios auth whoami\` shows the project and your role. 5. 05 ### Open the terminal app Run \`helios\` with no arguments for the full-screen app. The home screen shows recent chats and a new chat input. \`^p\` opens the command palette. Workflows can be searched, triggered with \`t\`, and shared with \`s\`. 6. 06 ### Connect integrations from the terminal \`helios integration connect\` starts an OAuth or Claude account connection and \`helios integration wait\` polls until it is ready. Integrations that use a pasted key, such as Stripe or Resend, still connect from the dashboard. 7. 07 ### Script it Every command prints JSON when its output is piped. \`helios share\`, \`helios group\`, and \`helios service-account\` manage access from scripts. \`helios code iac scaffold\`, \`export\`, and \`apply\` manage environments as YAML. Keep going ## Next guides [9 minShare with your teamHand a workflow to the people who need it. Four roles decide who may view, run, or edit. Every run leaves a transcript of what happened.](/guides/share-with-your-team/)[10 minRun your first workflowDescribe a task in plain words, give the agent one tool, and read the run. Ten minutes from an empty workspace to a transcript you can read end to end.](/guides/run-your-first-agent/)[8 minReview agent changes in the LibraryAgents propose edits to shared files. A person reviews the diff and approves or discards each one. Nothing reaches the team's files without approval.](/guides/review-agent-changes-in-the-library/) Templates ## Put it to work Templates that use what this guide covers. [EngineeringPull request reviewerReviews every pull request against your conventions and leaves inline comments only where it found something concrete.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/pr-review-digest/)[EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup to Slack every weekday morning.Weekdays at 9:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/daily-standup-digest/)[EngineeringIncident postmortem drafterRebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/incident-postmortem-drafter/) ## Try it in your workspace. Start free, connect a tool, and write the first prompt in plain words. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/cli/install) --- # Move from Relay.app to Helios | Helios URL: https://www.heliosapp.com/guides/move-from-relay-app Description: Relay.app shut down on 16 July 2026. Paid accounts are deleted on 14 September 2026. Here is how each Relay concept maps to Helios, and what to export first. [← All guides](/guides/) 15 min # Move from Relay.app to Helios Relay.app shut down on 16 July 2026\. Paid accounts are deleted on 14 September 2026\. Here is how each Relay concept maps to Helios, and what to export first. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/workflows) 5,000 free credits to start. 1. 01 ### Export your Relay data before 14 September Relay.app deleted free accounts on 15 August 2026 and deletes paid accounts on 14 September 2026\. Sign in while you still can. Copy each playbook's steps, prompts, and connected apps into a document. Screenshots are fine. The prompts are what you will reuse. 2. 02 ### A Relay playbook becomes a Helios workflow A playbook was a trigger plus a chain of steps. A Helios workflow is a prompt, a model, a trigger, and the integrations it may use. Write the steps of the playbook as sentences in the prompt. The agent decides the order at run time and shows every call in the transcript. 3. 03 ### Map each Relay trigger A Relay schedule becomes a Helios schedule. Describe it in plain words and Helios writes the cron expression. A Relay webhook becomes a signed Helios webhook. A Relay app event becomes a GitHub, Slack, or Plain event in Helios. Events from other apps are not available yet. Use a schedule that checks the app every few minutes instead. Relay form and email triggers have no Helios equivalent today. Point the form's webhook at Helios instead. 4. 04 ### Map each Relay step to an integration Relay offered a fixed list of actions per app. Helios gives the agent the full API of each connected integration. Connect the same apps from Settings, then Integrations. If you used a Relay action that did not exist for an app, it will most likely be reachable now. 5. 05 ### Replace human in the loop steps Relay let a person approve a step inside a run. Helios has no approval step inside a run today. For messages and records, have the workflow draft and post to a Slack channel or leave the draft unsent, then let a person send it. For shared files, the Library stages every agent change for a person to approve. 6. 06 ### Replace Relay AI steps with the model choice Relay charged AI credits per step. In Helios the whole run is one agent with a model you pick per workflow. Prompts that were split across several AI steps in Relay usually merge into one paragraph. 7. 07 ### Run each workflow by hand first Start each migrated workflow by hand and read the transcript before you add the trigger. Then turn on the trigger and watch the first few runs. You start with 5,000 free credits. Keep going ## Next guides [10 minRun your first workflowDescribe a task in plain words, give the agent one tool, and read the run. Ten minutes from an empty workspace to a transcript you can read end to end.](/guides/run-your-first-agent/)[8 minPut a workflow on a scheduleTurn a working prompt into a standing task. Describe the cadence the way you would say it out loud. Helios writes the cron expression.](/guides/put-an-agent-on-a-schedule/)[8 minReview agent changes in the LibraryAgents propose edits to shared files. A person reviews the diff and approves or discards each one. Nothing reaches the team's files without approval.](/guides/review-agent-changes-in-the-library/) Templates ## Put it to work Templates that use what this guide covers. [SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.slack · message.channel![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/templates/slack-support-triage/)[Sales & RevOpsInbound lead enrichmentEnriches every new signup, scores it against your ICP by reading the company's own website, and routes the strong fits.Signup webhook![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/apollo-lead-enrichment/)[Sales & RevOpsFailed payment recoveryFinds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/stripe-failed-payment-recovery/) ## Try it in your workspace. Start free, connect a tool, and write the first prompt in plain words. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/workflows) --- # Pin repositories as context | Helios URL: https://www.heliosapp.com/guides/pin-context-resources Description: Pin a GitHub repository to a workflow or a chat. The agent starts every run with it. [← All guides](/guides/) 7 min # Pin repositories as context Pin a GitHub repository to a workflow or a chat. The agent starts every run with it. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/basics/integration-resources) 5,000 free credits to start. 1. 01 ### Find the repository the agent keeps looking up Read a few runs and notice which codebase the agent reaches for every time. The service it reviews, the repository whose conventions it checks. That is the one worth pinning. 2. 02 ### Pin it as an integration resource A pinned resource scopes a connection to one repository. The pin carries the connection with it, so credentials stay at the network layer. 3. 03 ### Attach it to the workflow or chat A pinned repository is available in the sandbox on every run. The agent clones it with the in-sandbox git credential helper and starts from the code. 4. 04 ### Use pinning to narrow reach A workflow pinned to one repository has a smaller surface than one that can read the whole organization. Its prompt gets shorter as well. 5. 05 ### Put stable facts in the prompt Each run starts fresh. Escalation rules, naming conventions, and schema notes belong in the prompt so every run has them from the first step. Keep going ## Next guides [10 minRun your first workflowDescribe a task in plain words, give the agent one tool, and read the run. Ten minutes from an empty workspace to a transcript you can read end to end.](/guides/run-your-first-agent/)[12 minReact to GitHub eventsStart a run the moment a pull request opens, a build finishes, or a tag lands. Filter down to exactly the events you want.](/guides/react-to-github-events/)[9 minShare with your teamHand a workflow to the people who need it. Four roles decide who may view, run, or edit. Every run leaves a transcript of what happened.](/guides/share-with-your-team/) Templates ## Put it to work Templates that use what this guide covers. [EngineeringPull request reviewerReviews every pull request against your conventions and leaves inline comments only where it found something concrete.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/pr-review-digest/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes a draft release on GitHub, and files a changelog entry in Notion.github · tag.created![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/github-release-notes/)[EngineeringIncident postmortem drafterRebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/incident-postmortem-drafter/) ## Try it in your workspace. Start free, connect a tool, and write the first prompt in plain words. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/basics/integration-resources) --- # Put a workflow on a schedule | Helios URL: https://www.heliosapp.com/guides/put-an-agent-on-a-schedule Description: Turn a working prompt into a standing task. Describe the cadence the way you would say it out loud. Helios writes the cron expression. [← All guides](/guides/) 8 min # Put a workflow on a schedule Turn a working prompt into a standing task. Describe the cadence the way you would say it out loud. Helios writes the cron expression. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/workflows/triggers) 5,000 free credits to start. 1. 01 ### Start from a prompt that already works Run the workflow by hand until the output is what you want. A schedule repeats whatever the prompt does. A task that is 80% right becomes 80% right every morning. 2. 02 ### Add a schedule trigger Open the workflow's triggers and add a schedule. Describe the cadence in plain words. \`Every weekday at 7am\`, \`the first of every month\`, \`every four hours\`. Helios turns it into a cron expression you can inspect and edit. 3. 03 ### Schedules run in UTC Convert your local time before you save. A standup digest meant for 9am in California is 16:00 UTC in winter and 17:00 UTC in summer. 4. 04 ### Give each run a window Tell the agent what period it covers. \`The last 24 hours\`, \`the last hour\`, \`since Monday\`. Each run starts fresh, so the window in the prompt is what keeps runs from overlapping. 5. 05 ### Say what to skip Runs should not send the same email twice or post an empty report. Put the rule in the prompt. \`When nothing changed, post one line saying so.\` 6. 06 ### Watch the first few scheduled runs Open the run history after the first two or three runs. Read what the agent did on a quiet day and on a busy one. Each run has a 30 minute limit, and there are no failure alerts yet, so check the history in the first week. Keep going ## Next guides [10 minRun your first workflowDescribe a task in plain words, give the agent one tool, and read the run. Ten minutes from an empty workspace to a transcript you can read end to end.](/guides/run-your-first-agent/)[12 minReact to GitHub eventsStart a run the moment a pull request opens, a build finishes, or a tag lands. Filter down to exactly the events you want.](/guides/react-to-github-events/)[10 minConnect a databaseGive a workflow Postgres, MySQL, or ClickHouse. It reads the schema, writes real SQL, and checks the results in its own sandbox.](/guides/connect-a-database/) Templates ## Put it to work Templates that use what this guide covers. [EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup to Slack every weekday morning.Weekdays at 9:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/daily-standup-digest/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out.Mondays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/weekly-metrics-report/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing company fields, and flags deals that have gone quiet. Every night.Nightly at 2:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/attio-crm-hygiene/) ## Try it in your workspace. Start free, connect a tool, and write the first prompt in plain words. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/workflows/triggers) --- # React to GitHub events | Helios URL: https://www.heliosapp.com/guides/react-to-github-events Description: Start a run the moment a pull request opens, a build finishes, or a tag lands. Filter down to exactly the events you want. [← All guides](/guides/) 12 min # React to GitHub events Start a run the moment a pull request opens, a build finishes, or a tag lands. Filter down to exactly the events you want. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/workflows/triggers) 5,000 free credits to start. 1. 01 ### Connect GitHub and choose the repositories Connect GitHub from Settings, then Integrations, and select which repositories the connection covers. That selection is the limit of what a workflow can reach. Start with one repository. 2. 02 ### Pick the event that matches the task A reviewer runs on \`pull\_request.opened\` and \`pull\_request.synchronize\`. A build explainer runs on \`workflow\_run.completed\`. A release notes writer runs on \`tag.created\`. An issue triager runs on \`issues.opened\`. GitHub exposes twelve events. 3. 03 ### Filter the trigger down Filters combine with AND or OR and accept globs. Filter by base branch so the workflow ignores long-lived feature branches. Filter by label so a pull request opts in one at a time. 4. 04 ### Write the prompt against the event payload The run receives the event that started it, so the prompt can refer to the pull request, the workflow run, or the tag directly. Tell it what to read first. The diff, the contributing guide, the last twenty merged reviews. 5. 05 ### Start with a label filter and a comment Have the agent post a comment instead of an approving review, and gate it behind a label. Add the label to a few of your own pull requests, read what it wrote, then widen the filter. 6. 06 ### Decide who can change it A workflow that comments on pull requests is one your team will read closely. Editors and admins change the prompt. Operators run it. Viewers read the runs. Share it with the team that owns the repository. Keep going ## Next guides [10 minRun your first workflowDescribe a task in plain words, give the agent one tool, and read the run. Ten minutes from an empty workspace to a transcript you can read end to end.](/guides/run-your-first-agent/)[8 minPut a workflow on a scheduleTurn a working prompt into a standing task. Describe the cadence the way you would say it out loud. Helios writes the cron expression.](/guides/put-an-agent-on-a-schedule/)[9 minShare with your teamHand a workflow to the people who need it. Four roles decide who may view, run, or edit. Every run leaves a transcript of what happened.](/guides/share-with-your-team/) Templates ## Put it to work Templates that use what this guide covers. [EngineeringPull request reviewerReviews every pull request against your conventions and leaves inline comments only where it found something concrete.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/pr-review-digest/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes a draft release on GitHub, and files a changelog entry in Notion.github · tag.created![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/github-release-notes/)[EngineeringIncident postmortem drafterRebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/incident-postmortem-drafter/) ## Try it in your workspace. Start free, connect a tool, and write the first prompt in plain words. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/workflows/triggers) --- # Review agent changes in the Library | Helios URL: https://www.heliosapp.com/guides/review-agent-changes-in-the-library Description: Agents propose edits to shared files. A person reviews the diff and approves or discards each one. Nothing reaches the team's files without approval. [← All guides](/guides/) 8 min # Review agent changes in the Library Agents propose edits to shared files. A person reviews the diff and approves or discards each one. Nothing reaches the team's files without approval. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/library/reviewing-changes) 5,000 free credits to start. 1. 01 ### Know the three scopes The Library has organization files, project files, and personal files. Each is mounted in the sandbox under \`\~/context\`. Open the Library from the sidebar, or press \`h\` then \`l\`. 2. 02 ### Let an agent edit a file Files enter the Library through agent sessions. In a chat or a run, ask the agent to update a document under \`\~/context\`. The edit is staged for review before it reaches the shared file. 3. 03 ### Open the Changes inbox Go to Library, then Changes. The Open tab lists every pending proposal with the session, the file count, and the time. The History tab lists every merged change with who approved it and when. 4. 04 ### Read the diff Each proposal shows every staged file side by side with Added, Modified, or Deleted labels. A file you edited yourself is marked as such. 5. 05 ### Approve or discard each file Approve one file, discard one file, or use Approve all. Agents cannot approve their own changes. A run token is rejected on every approval route. 6. 06 ### Handle a conflict If the live file changed after the agent staged its edit, the entry shows a Conflict badge and the current content. Approval is blocked until the agent stages again from the new version. 7. 07 ### Share a folder Share any folder prefix with a person, a group, or the organization as viewer or editor. In a chat, the Files panel shows what the running agent can see and what it changed. Keep going ## Next guides [9 minShare with your teamHand a workflow to the people who need it. Four roles decide who may view, run, or edit. Every run leaves a transcript of what happened.](/guides/share-with-your-team/)[10 minRun your first workflowDescribe a task in plain words, give the agent one tool, and read the run. Ten minutes from an empty workspace to a transcript you can read end to end.](/guides/run-your-first-agent/)[10 minInstall and configure the Helios CLIInstall one binary, run \`helios configure\`, and go from an API key to a running workflow in your terminal. Every command prints JSON when piped.](/guides/install-the-helios-cli/) Templates ## Put it to work Templates that use what this guide covers. [MarketingResearch brief writerResearches a topic across the live web and returns a sourced draft in your voice, with the open questions flagged.Run on demand![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)![](/static/img/assets/apify.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/google-docs-brief-writer/)[SupportDocumentation freshness auditChecks your written docs against the codebase every month and comments on the pages that have gone stale.Monthly on the 1st![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/notion-docs-freshness-audit/)[EngineeringIncident postmortem drafterRebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/incident-postmortem-drafter/) ## Try it in your workspace. Start free, connect a tool, and write the first prompt in plain words. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/library/reviewing-changes) --- # Run your first workflow | Helios URL: https://www.heliosapp.com/guides/run-your-first-agent Description: Describe a task in plain words, give the agent one tool, and read the run. Ten minutes from an empty workspace to a transcript you can read end to end. [← All guides](/guides/) 10 min # Run your first workflow Describe a task in plain words, give the agent one tool, and read the run. Ten minutes from an empty workspace to a transcript you can read end to end. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/quickstart) 5,000 free credits to start. 1. 01 ### Connect one integration Open Settings, then Integrations, and connect a single service. Slack and GitHub are the easiest first connections. Helios stores the credential encrypted and injects it at the network layer. The agent never sees the token. 2. 02 ### Create a workflow A workflow is a prompt, a model, a trigger, and the tools it may use. Give it a name that says what it does. \`Daily standup digest\` beats \`Workflow 1\` when you have twenty of them. 3. 03 ### Write the prompt in plain words Say what the agent should do, which sources it should read, and what a good result looks like. Say what to skip, when to escalate, and what to do when it is unsure. The prompt is the whole configuration. 4. 04 ### Pick a model and attach context Choose the model for this workflow. If the task lives in a codebase, pin the GitHub repository. If it needs a threshold or an API key, store it as a variable or a secret. 5. 05 ### Run it by hand and read the transcript Start the first run yourself. The run page shows every tool call, the arguments, and what came back. This is where you learn whether the prompt said what you meant. 6. 06 ### Fix the prompt, then add a trigger Change the sentence that produced the wrong behavior and run again. Once two or three manual runs look right, add a schedule, a webhook, or an event trigger. Keep going ## Next guides [8 minPut a workflow on a scheduleTurn a working prompt into a standing task. Describe the cadence the way you would say it out loud. Helios writes the cron expression.](/guides/put-an-agent-on-a-schedule/)[7 minPin repositories as contextPin a GitHub repository to a workflow or a chat. The agent starts every run with it.](/guides/pin-context-resources/)[9 minShare with your teamHand a workflow to the people who need it. Four roles decide who may view, run, or edit. Every run leaves a transcript of what happened.](/guides/share-with-your-team/) Templates ## Put it to work Templates that use what this guide covers. [EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup to Slack every weekday morning.Weekdays at 9:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/daily-standup-digest/)[SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.slack · message.channel![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/templates/slack-support-triage/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out.Mondays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/weekly-metrics-report/) ## Try it in your workspace. Start free, connect a tool, and write the first prompt in plain words. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/quickstart) --- # Share with your team | Helios URL: https://www.heliosapp.com/guides/share-with-your-team Description: Hand a workflow to the people who need it. Four roles decide who may view, run, or edit. Every run leaves a transcript of what happened. [← All guides](/guides/) 9 min # Share with your team Hand a workflow to the people who need it. Four roles decide who may view, run, or edit. Every run leaves a transcript of what happened. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/basics/projects-and-sharing) 5,000 free credits to start. 1. 01 ### Understand the four roles A viewer reads the workflow and its runs. An operator can also start runs. An editor changes the prompt, model, and triggers. An admin manages sharing. Most teams end up with a few editors and everyone else as an operator. 2. 02 ### Share with a person, a group, or everyone Open Share on the workflow and pick a person, a group, a service account, or the whole organization. You can never grant a role above your own. 3. 03 ### Set an expiry when it fits A share can last forever, one day, one week, or a custom period. A contractor's access ends on its own. A trial run for another team cleans itself up. 4. 04 ### Use groups and service accounts Groups hold people and service accounts, so one share covers a team. A service account is a named identity a workflow runs as. It can be disabled without touching anyone's login. 5. 05 ### Point everyone at the run history Every run records the tool calls, the arguments, and the results. When someone asks why a workflow wrote that field or sent that message, the answer is a link. 6. 06 ### Share a chat, and let people fork it A chat can be shared by link up to a message you choose. Anyone with the link can fork it and continue from that point with their own copy. The original is untouched. Keep going ## Next guides [10 minRun your first workflowDescribe a task in plain words, give the agent one tool, and read the run. Ten minutes from an empty workspace to a transcript you can read end to end.](/guides/run-your-first-agent/)[8 minUse secrets and variablesKeep the values a task needs out of the prompt. Variables hold configuration. Secrets hold credentials. The agent never sees a secret in plain text.](/guides/use-secrets-and-variables/)[10 minInstall and configure the Helios CLIInstall one binary, run \`helios configure\`, and go from an API key to a running workflow in your terminal. Every command prints JSON when piped.](/guides/install-the-helios-cli/) Templates ## Put it to work Templates that use what this guide covers. [EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup to Slack every weekday morning.Weekdays at 9:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/daily-standup-digest/)[SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.slack · message.channel![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/templates/slack-support-triage/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out.Mondays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/weekly-metrics-report/) ## Try it in your workspace. Start free, connect a tool, and write the first prompt in plain words. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/basics/projects-and-sharing) --- # Use secrets and variables | Helios URL: https://www.heliosapp.com/guides/use-secrets-and-variables Description: Keep the values a task needs out of the prompt. Variables hold configuration. Secrets hold credentials. The agent never sees a secret in plain text. [← All guides](/guides/) 8 min # Use secrets and variables Keep the values a task needs out of the prompt. Variables hold configuration. Secrets hold credentials. The agent never sees a secret in plain text. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/basics/variables-and-secrets) 5,000 free credits to start. 1. 01 ### Know which one you need A variable holds a value you are happy to read in a run transcript. A channel name, a threshold, a sending address. A secret holds anything you are not. An API token, a signing key, a password. 2. 02 ### Store it at the right level Put a value the whole organization shares at the organization level. Put a one-off token on the workflow that needs it. The narrowest level that works is the right one. 3. 03 ### Reference it from the prompt Name the variable in the prompt and the run resolves it. A secret is injected where it is needed and never lands in the prompt text, so it stays out of the transcript your team reads. 4. 04 ### Rotate without touching a prompt The value lives beside the workflow. Rotating a token is one edit in one place. Every workflow that references it picks up the new value on its next run. 5. 05 ### Prefer integrations for credentials Connected integrations already inject their credentials at the network layer. The token for Slack or Stripe belongs in the integration. Keep going ## Next guides [10 minConnect a databaseGive a workflow Postgres, MySQL, or ClickHouse. It reads the schema, writes real SQL, and checks the results in its own sandbox.](/guides/connect-a-database/)[10 minAttach an MCP serverPoint Helios at a remote MCP server, choose which of its tools workflows may call, and use Helios itself over MCP from other clients.](/guides/attach-an-mcp-server/)[9 minShare with your teamHand a workflow to the people who need it. Four roles decide who may view, run, or edit. Every run leaves a transcript of what happened.](/guides/share-with-your-team/) Templates ## Put it to work Templates that use what this guide covers. [Sales & RevOpsFailed payment recoveryFinds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/stripe-failed-payment-recovery/)[OperationsNightly data quality checksRuns your invariants against production every night and emails the on-call analyst which rows broke and since when.Nightly at 3:00am![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/templates/database-health-check/)[Sales & RevOpsInbound lead enrichmentEnriches every new signup, scores it against your ICP by reading the company's own website, and routes the strong fits.Signup webhook![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/apollo-lead-enrichment/) ## Try it in your workspace. Start free, connect a tool, and write the first prompt in plain words. [Get started free](https://app.heliosapp.com/)[Open the docs](/docs/basics/variables-and-secrets) --- # Integrations - Connect a Tool Once. Agents Get All of It. | Helios URL: https://www.heliosapp.com/integrations Description: Helios indexes the full API of each connected service. Helios OAuth app, your own app, or an API key. Event triggers from GitHub, Slack, and Plain. Databases and remote MCP servers. Integrations # Your tools are already here. Helios indexes the full API of each service. Bring the Helios app, your own app, or an API key. 54 services today, plus your databases and any remote MCP server. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Services 54 Full API of each one Event triggers 41 Mailchimp, Brevo, GitHub, GitLab, Slack, Google Drive, Google Calendar, Box, Clay, Plain, Linear, Jira, PagerDuty, Sentry, Zendesk, Webflow, Shopify, WooCommerce, Granola, Vercel, Bitbucket, Hunter, Pipedrive, Lusha, Docusign, Zoho CRM, Salesforce, Calendly, Asana, Zoom, Cal.com, ClickUp, Dropbox, Zoho Desk, Help Scout, Workable, Figma, Square, Deel, Wise, Cloudflare Databases 3 Postgres, MySQL, ClickHouse MCP servers Any Remote, over HTTPS How it works ## The full API of each tool. Helios gives an agent the whole API of a connected tool and a way to search it. 1. 01 ### Helios indexes the API spec When you connect a service, its full OpenAPI or GraphQL spec goes into a vector index. Every endpoint, parameter, and description is searchable. 2. 02 ### The agent finds the endpoint The agent calls find-relevant-apis with a plain description of what it needs. It gets back the closest endpoints and their schemas. 3. 03 ### The agent calls it The agent calls call-api with the method, path, and body. The egress proxy adds the credential on the way out. The sandbox never holds a token. agent transcript $find-relevant-apis "add a label to a pull request"POST /repos/{owner}/{repo}/issues/{issue_number}/labels 0.91GET /repos/{owner}/{repo}/labels 0.84$call-api github POST /repos/acme/api/issues/482/labels {"labels":["needs-review"]}200 OK · credential added by the egress proxy The two tools run inside the sandbox. The credential does not. Helios attaches it at the network layer, so a prompt injection has nothing to read. Auth modes ## Three ways to connect a service. Every credential is envelope-encrypted at rest and attached to requests outside the sandbox. Sharing an integration never exposes its credential. ### Helios OAuth app Click connect and approve the Helios app on the provider's consent screen. Helios refreshes the tokens. ### Your own OAuth app Register your own OAuth app or bot with the provider. Pick your own scopes and show your own name on the consent screen. ### API key Paste a key from the provider's dashboard. A read-only key keeps a reporting agent from writing anything. | Service | Helios OAuth app | Your own OAuth app | API key | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | ------------------ | ------- | | MailchimpConnect with an API key or authorize your own Mailchimp OAuth app. | – | ● | ● | | BrevoConnect with an API key or a private OAuth app from your Brevo organization. | – | ● | ● | | GitHubOrganization installs also ask each person to authorize once, so the agent acts as that person. | ● | ● | ● | | GitLabConnect with an access token that has the api scope, or with your own GitLab OAuth app that has the api and mcp scopes. Helios adds the webhook for trigger events to projects where the token has the Maintainer role, and to a group you name where it has the Owner role. GitLab Self-Managed works too, and its triggers need GitLab 19.0 or later. | – | ● | ● | | SlackEach person authorizes once after the workspace installs the app. | ● | ● | – | | Gmail | ● | ● | – | | Google Sheets | ● | ● | – | | Google Docs | ● | ● | – | | Google Drive | ● | ● | – | | Google CalendarYour own OAuth app is a Web application client in your Google Cloud project, with the Google Calendar API turned on. Publish an External app, because Google expires refresh tokens after 7 days in Testing. | ● | ● | – | | Notion | ● | ● | ● | | BoxPaste the client ID and secret of a Box Server app that uses Client Credentials Grant, which acts as its service account or a managed user. Or sign in through your own Box User app with OAuth 2.0. | – | ● | ● | | Attio | ● | ● | – | | Apollo | ● | ● | ● | | ClayCreate an API key with the Public API scope on Clay's API and CLI page. For triggers, add an HTTP API column to a Clay table that sends rows to Helios, or create a Clay webhook with the Clay CLI. HTTP API columns need a Growth or Enterprise plan. | – | – | ● | | Stripe | – | – | ● | | Resend | – | – | ● | | PlainPaste the webhook signing secret from Plain to receive thread events. | – | – | ● | | LinearGive the API key the Admin permission, or turn on Admin access for an OAuth app, so Helios can register the webhook for Linear events. | – | ● | ● | | DiscordCreate a bot in the Discord developer portal and paste its token. | – | ● | – | | Reddit | ● | ● | – | | Typeform | ● | ● | ● | | Apify | – | – | ● | | WarpBuild | – | – | ● | | JiraConnect with an Atlassian API token and your site URL, or with your own Atlassian OAuth app with every scope in the docs turned on. Helios registers the webhooks for triggers. The API token's account needs the Administer Jira global permission for that, and an OAuth app receives issue, comment, issue property, sprint, and version events only. | – | ● | ● | | PagerDutyUse a general access key with full access and the email of a PagerDuty user, or your own Scoped OAuth app with the scopes for your workflows, authorized by a user who can create webhook subscriptions. Helios creates the webhook subscription for triggers. | – | ● | ● | | SentryUse the token of a Sentry internal integration, or your own public integration through OAuth. For triggers, point the same integration's webhook at Helios. | – | ● | ● | | ZendeskEnter your Zendesk account URL. Your own OAuth client must belong to that account unless Zendesk has approved it as a global client. | – | ● | ● | | WebflowConnect a site API token or authorize your own Webflow Data Client app. | – | ● | ● | | ShopifyConnect one store with a custom app Admin API token and API secret key, or authorize your own Shopify app. | – | ● | ● | | WooCommerceConnect your HTTPS store with a Read/Write consumer key and secret. | – | – | ● | | GranolaUse a personal or workspace API key on a Business or Enterprise plan. | – | – | ● | | VercelUse an access token or your own Vercel integration through OAuth. Triggers with a token need a Pro or Enterprise team. With your own integration, you point its webhook at Helios. | – | ● | ● | | BitbucketUse an Atlassian API token, a Bitbucket access token, or your own Bitbucket OAuth consumer. Helios registers the webhook for trigger events when you save the connection. | – | ● | ● | | HunterHelios uses the API key to register email webhooks. | – | – | ● | | PipedriveAn API token also needs your company domain, such as acme in acme.pipedrive.com. API calls and triggers follow the connected user's permissions. OAuth calls also require the app's scopes. | – | ● | ● | | LushaHelios creates the Lusha webhook subscriptions for the contacts and companies you list on the connection, and the account's opt-out subscription. | – | – | ● | | DocusignUse an app from your Docusign account, with either a JWT grant or a sign-in. Add a Connect HMAC key for Connect events. | – | ● | – | | Zoho CRMRegister a server-based client in the Zoho API Console. Check Admin access to let agents change settings and manage users. Outside the US data center, set the connection's base URL to your data center's API domain. | – | ● | – | | SalesforceCreate an External Client App in your org. Connect as its run-as user with the client credentials flow, or sign in through it as yourself. | – | ● | – | | CalendlyTriggers need a paid Calendly plan. Connect as an organization owner or admin so triggers cover every member's meetings. | – | ● | ● | | AsanaSet the project and the workspace to watch on the connection, and Helios registers the webhooks for task, comment, project, goal, and membership events. | – | ● | ● | | ZoomUse a Server-to-Server OAuth app for the whole account, or a user-managed General app for one user. Helios sets up event subscriptions and shows events that Zoom does not accept as unavailable. | – | ● | – | | Cal.comHelios registers the webhook for Cal.com events with your key or OAuth app. With Admin access, an organization admin's connection also gets an organization webhook. | – | ● | ● | | ClickUpSet the workspace ID on the connection if the token can see more than one ClickUp workspace. Helios registers the webhook for trigger events there. | – | ● | ● | | DropboxCreate a scoped app in the Dropbox App Console, or a team app that a team admin approves for the whole team. For triggers, add the Helios webhook URL to the app. | – | ● | – | | Zoho DeskUse your OAuth app or existing OAuth tokens, with the matching data centre and organization ID. | – | ● | – | | Help ScoutConnect your Help Scout OAuth app. App-only tokens are not supported. | – | ● | – | | WorkableAccount API tokens are the default. OAuth requires Workable partner approval and remains untested. | – | ● | ● | | FigmaUse a personal access token or your own OAuth app. Team webhooks require Professional or higher and team admin access. | – | ● | ● | | SquareUse a personal access token for your own account or your Square OAuth app for sellers. OAuth triggers also require the application's personal access token. | – | ● | ● | | DeelConnect an API token or your own Deel OAuth app, then select production or sandbox. | – | ● | ● | | WisePersonal API tokens are the default. Partner OAuth requires Wise onboarding and mTLS. | – | ● | ● | | CloudflareUse an API token, or your own OAuth app with the scopes Helios requests. Give it Notifications Edit so Helios can register the alerts for triggers. | – | ● | ● | | DatabasesPaste a database connection string. Add an SSH tunnel for a database on a private network. | Connection string | | | Triggers ## Which services can start a run. Every workflow can run by hand, on a schedule, or from a signed webhook. Mailchimp, Brevo, GitHub, GitLab, Slack, Google Drive, Google Calendar, Box, Clay, Plain, Linear, Jira, PagerDuty, Sentry, Zendesk, Webflow, Shopify, WooCommerce, Granola, Vercel, Bitbucket, Hunter, Pipedrive, Lusha, Docusign, Zoho CRM, Salesforce, Calendly, Asana, Zoom, Cal.com, ClickUp, Dropbox, Zoho Desk, Help Scout, Workable, Figma, Square, Deel, Wise, Cloudflare can also start a run from their own events. | Service | Manual | Schedule | Signed webhook | Service events | | -------------------------------------------------------------------------------------------------------------------------------------------------------- | ------ | -------- | -------------- | -------------- | | [Mailchimp](/integrations/mailchimp/)11 events | ● | ● | ● | ● | | [Brevo](/integrations/brevo/)4 events | ● | ● | ● | ● | | [GitHub](/integrations/github/)12 events | ● | ● | ● | ● | | [GitLab](/integrations/gitlab/)5 events | ● | ● | ● | ● | | [Slack](/integrations/slack/)2 events | ● | ● | ● | ● | | [Google Drive](/integrations/google-drive/)8 events | ● | ● | ● | ● | | [Google Calendar](/integrations/google-calendar/)6 events | ● | ● | ● | ● | | [Box](/integrations/box/)6 events | ● | ● | ● | ● | | [Clay](/integrations/clay/)2 events | ● | ● | ● | ● | | [Plain](/integrations/plain/)2 events | ● | ● | ● | ● | | [Linear](/integrations/linear/)5 events | ● | ● | ● | ● | | [Jira](/integrations/jira/)5 events | ● | ● | ● | ● | | [PagerDuty](/integrations/pagerduty/)8 events | ● | ● | ● | ● | | [Sentry](/integrations/sentry/)6 events | ● | ● | ● | ● | | [Zendesk](/integrations/zendesk/)5 events | ● | ● | ● | ● | | [Webflow](/integrations/webflow/)17 events | ● | ● | ● | ● | | [Shopify](/integrations/shopify/)3 events | ● | ● | ● | ● | | [WooCommerce](/integrations/woocommerce/)16 events | ● | ● | ● | ● | | [Granola](/integrations/granola/)3 events | ● | ● | ● | ● | | [Vercel](/integrations/vercel/)9 events | ● | ● | ● | ● | | [Bitbucket](/integrations/bitbucket/)6 events | ● | ● | ● | ● | | [Hunter](/integrations/hunter/)4 events | ● | ● | ● | ● | | [Pipedrive](/integrations/pipedrive/)5 events | ● | ● | ● | ● | | [Lusha](/integrations/lusha/)5 events | ● | ● | ● | ● | | [Docusign](/integrations/docusign/)5 events | ● | ● | ● | ● | | [Zoho CRM](/integrations/zoho-crm/)4 events | ● | ● | ● | ● | | [Salesforce](/integrations/salesforce/)1 events | ● | ● | ● | ● | | [Calendly](/integrations/calendly/)7 events | ● | ● | ● | ● | | [Asana](/integrations/asana/)5 events | ● | ● | ● | ● | | [Zoom](/integrations/zoom/)6 events | ● | ● | ● | ● | | [Cal.com](/integrations/cal-com/)9 events | ● | ● | ● | ● | | [ClickUp](/integrations/clickup/)4 events | ● | ● | ● | ● | | [Dropbox](/integrations/dropbox/)5 events | ● | ● | ● | ● | | [Zoho Desk](/integrations/zoho-desk/)3 events | ● | ● | ● | ● | | [Help Scout](/integrations/help-scout/)6 events | ● | ● | ● | ● | | [Workable](/integrations/workable/)10 events | ● | ● | ● | ● | | [Figma](/integrations/figma/)6 events | ● | ● | ● | ● | | [Square](/integrations/square/)4 events | ● | ● | ● | ● | | [Deel](/integrations/deel/)4 events | ● | ● | ● | ● | | [Wise](/integrations/wise/)34 events | ● | ● | ● | ● | | [Cloudflare](/integrations/cloudflare/)5 events | ● | ● | ● | ● | | Every other service (14)Gmail, Google Sheets, Google Docs, Notion, Attio, Apollo, Stripe, Resend, Discord, Reddit, Typeform, Apify, WarpBuild, Databases | ● | ● | ● | Not yet | Webhook triggers are signed with HMAC-SHA256 and reject requests older than five minutes. Schedules take a cron expression or a plain sentence. [Trigger docs](/docs/workflows/triggers/) ## Developer tools 10 [GitHubGitHub REST APIEvent triggers · 12](/integrations/github/)[GitLabGitLab REST APIEvent triggers · 5](/integrations/gitlab/)[LinearLinear GraphQL APIEvent triggers · 5](/integrations/linear/)[![](/static/img/assets/warpbuild-light.svg)![](/static/img/assets/warpbuild-dark.svg)WarpBuildWarpBuild API v1Schedule and webhook](/integrations/warpbuild/)[JiraJira Cloud platform REST API v3, Jira Software REST API, Jira Service Management REST API, Assets REST API, Forms REST API, and Jira Service Management operations and incident REST APIsEvent triggers · 5](/integrations/jira/)[PagerDutyPagerDuty REST API and incident and service webhooksEvent triggers · 8](/integrations/pagerduty/)[SentrySentry REST APIEvent triggers · 6](/integrations/sentry/)[VercelVercel REST APIEvent triggers · 9](/integrations/vercel/)[BitbucketBitbucket Cloud REST APIEvent triggers · 6](/integrations/bitbucket/)[CloudflareCloudflare API v4Event triggers · 5](/integrations/cloudflare/) ## Communication 02 [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)SlackSlack Web APIEvent triggers · 2](/integrations/slack/)[ZoomZoom REST APIs for Meetings, Users, Team Chat, Phone, Contact Center, Rooms, and Zoom's other productsEvent triggers · 6](/integrations/zoom/) ## Google Workspace 05 [![](/static/img/assets/gmail-light.svg)![](/static/img/assets/gmail-dark.svg)GmailGmail API v1Schedule and webhook](/integrations/gmail/)[![](/static/img/assets/google-sheets-light.svg)![](/static/img/assets/google-sheets-dark.svg)Google SheetsGoogle Sheets API v4Schedule and webhook](/integrations/google-sheets/)[![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)Google DocsGoogle Docs API v1Schedule and webhook](/integrations/google-docs/)[Google DriveGoogle Drive API v3Event triggers · 8](/integrations/google-drive/)[Google CalendarGoogle Calendar API v3Event triggers · 6](/integrations/google-calendar/) ## Docs & knowledge 04 [NotionNotion APISchedule and webhook](/integrations/notion/)[BoxBox API 2.0Event triggers · 6](/integrations/box/)[![](/static/img/assets/granola-light.svg)![](/static/img/assets/granola-dark.svg)GranolaGranola v1 APIEvent triggers · 3](/integrations/granola/)[DropboxDropbox API v2 and Content Processing APIEvent triggers · 5](/integrations/dropbox/) ## Design 01 [![](/static/img/assets/figma-light.svg)![](/static/img/assets/figma-dark.svg)FigmaFigma REST APIEvent triggers · 6](/integrations/figma/) ## Sales & CRM 11 [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)AttioAttio API v2Schedule and webhook](/integrations/attio/)[![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)ApolloApollo API v1Schedule and webhook](/integrations/apollo/)[![](/static/img/assets/clay-light.svg)![](/static/img/assets/clay-dark.svg)ClayClay Public APIEvent triggers · 2](/integrations/clay/)[![](/static/img/assets/hunter-light.svg)![](/static/img/assets/hunter-dark.svg)HunterHunter API v2Event triggers · 4](/integrations/hunter/)[![](/static/img/assets/pipedrive-light.svg)![](/static/img/assets/pipedrive-dark.svg)PipedrivePipedrive API v1 and v2Event triggers · 5](/integrations/pipedrive/)[![](/static/img/assets/lusha-light.svg)![](/static/img/assets/lusha-dark.svg)LushaLusha API v3 and v2Event triggers · 5](/integrations/lusha/)[![](/static/img/assets/docusign-light.svg)![](/static/img/assets/docusign-dark.svg)DocusignDocusign eSignature, Click, Admin, Rooms, Workspaces, Web Forms, Workflow Builder, Agreement Manager, Connected Fields, and Monitor APIsEvent triggers · 5](/integrations/docusign/)[Zoho CRMZoho CRM REST API v8Event triggers · 4](/integrations/zoho-crm/)[![](/static/img/assets/salesforce-light.svg)![](/static/img/assets/salesforce-dark.svg)SalesforceSalesforce REST, Bulk, GraphQL, Connect, Reports, and CRM Analytics APIsEvent triggers · 1](/integrations/salesforce/)[CalendlyCalendly API v2Event triggers · 7](/integrations/calendly/)[![](/static/img/assets/cal-com-light.svg)![](/static/img/assets/cal-com-dark.svg)Cal.comCal.com API v2Event triggers · 9](/integrations/cal-com/) ## Project management 02 [AsanaAsana REST APIEvent triggers · 5](/integrations/asana/)[ClickUpClickUp API v2 and v3Event triggers · 4](/integrations/clickup/) ## Billing 03 [StripeStripe APISchedule and webhook](/integrations/stripe/)[![](/static/img/assets/square-light.svg)![](/static/img/assets/square-dark.svg)SquareSquare REST API, version 2026-09-16Event triggers · 4](/integrations/square/)[![](/static/img/assets/wise-light.svg)![](/static/img/assets/wise-dark.svg)WiseWise Platform API, 2026Q4 and legacyEvent triggers · 34](/integrations/wise/) ## E-commerce 02 [![](/static/img/assets/shopify-light.svg)![](/static/img/assets/shopify-dark.svg)ShopifyShopify GraphQL Admin API 2026-10Event triggers · 3](/integrations/shopify/)[![](/static/img/assets/woocommerce-light.svg)![](/static/img/assets/woocommerce-dark.svg)WooCommerceWooCommerce REST API v3Event triggers · 16](/integrations/woocommerce/) ## HR 02 [![](/static/img/assets/workable-light.svg)![](/static/img/assets/workable-dark.svg)WorkableWorkable REST API v3Event triggers · 10](/integrations/workable/)[![](/static/img/assets/deel-light.svg)![](/static/img/assets/deel-dark.svg)DeelDeel REST and SCIM APIsEvent triggers · 4](/integrations/deel/) ## Email 03 [![](/static/img/assets/mailchimp-light.svg)![](/static/img/assets/mailchimp-dark.svg)MailchimpMailchimp Marketing API v3Event triggers · 11](/integrations/mailchimp/)[![](/static/img/assets/brevo-light.svg)![](/static/img/assets/brevo-dark.svg)BrevoBrevo v3 APIEvent triggers · 4](/integrations/brevo/)[![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)ResendResend API v1Schedule and webhook](/integrations/resend/) ## Support 04 [![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)PlainPlain GraphQL APIEvent triggers · 2](/integrations/plain/)[![](/static/img/assets/zendesk-light.svg)![](/static/img/assets/zendesk-dark.svg)ZendeskZendesk Support, Help Center, and Talk APIsEvent triggers · 5](/integrations/zendesk/)[![](/static/img/assets/zoho-desk-light.svg)![](/static/img/assets/zoho-desk-dark.svg)Zoho DeskZoho Desk REST APIEvent triggers · 3](/integrations/zoho-desk/)[![](/static/img/assets/help-scout-light.svg)![](/static/img/assets/help-scout-dark.svg)Help ScoutHelp Scout Inbox APIEvent triggers · 6](/integrations/help-scout/) ## Community 02 [DiscordDiscord API v10Schedule and webhook](/integrations/discord/)[RedditReddit API v1Schedule and webhook](/integrations/reddit/) ## Forms 01 [![](/static/img/assets/typeform-light.svg)![](/static/img/assets/typeform-dark.svg)TypeformTypeform API v1Schedule and webhook](/integrations/typeform/) ## Web data 02 [![](/static/img/assets/apify.svg)ApifyApify API v2Schedule and webhook](/integrations/apify/)[![](/static/img/assets/webflow-light.svg)![](/static/img/assets/webflow-dark.svg)WebflowWebflow Data API v2 and betaEvent triggers · 17](/integrations/webflow/) ## Data 01 [DatabasesPostgres, MySQL, and ClickHouse over SQLSchedule and webhook](/integrations/databases/) Beyond the catalogue ## Your own tools and data. Some tools have no integration. These three cover the rest. [MCP serversAttach any remote MCP serverPoint Helios at an HTTPS MCP server with a bearer token or OAuth 2.0\. Allowlist the tools an agent may call. Each server gets its own sub-agent.How MCP works →](/product/#mcp)[DatabasesPostgres, MySQL, and ClickHouseAgents list connections, introspect the schema, and run read-only SQL. Reach a private database through an SSH tunnel.Connect a database →](/integrations/databases/)[The webSearch and read pages without a connectionEvery agent can search the web and read a page as markdown. No integration needed.Read the docs →](/docs/integrations/) ## Connect your first tool. Authorize a service, describe the task in chat, and read the transcript of every call the agent makes. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Apify Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/apify Description: Agents run Apify actors to collect structured data from the web at scale, then analyze the results in their own sandbox. Pair it with built-in web search and scraping for research that goes wide and deep. [← All integrations](/integrations/) Web data ![](/static/img/assets/apify.svg) # Give your agents full access to Apify. Agents run Apify actors to collect structured data from the web at scale, then analyze the results in their own sandbox. Pair it with built-in web search and scraping for research that goes wide and deep. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Apify API v2 The full surface, searched at run time. Connect with * API key Event triggers Not yet Manual, schedule, and signed webhook are available. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/apify/) What the agent can do ## What agents do with Apify Helios searches the Apify API v2 at run time. The agent finds the endpoint the task needs and calls it. * Search Apify's entire API surface at run time and call any endpoint your token allows. * Start actor runs with custom input and wait for them to finish. * Read datasets, key-value stores, and run logs from completed runs. * Analyze scraped datasets as code in the agent's sandbox. * Combine actor output with built-in web search and page scraping. * Write results into a sheet, a database, or a document. Examples ## Tasks you can hand to a Apify agent ### Track competitor pricing A weekly agent scrapes competitor pricing pages, diffs them against last week, and reports only what changed. Mondays at 6:00am Weekly, scrape competitor pricing pages and report what changed. 1. apify·run the web scraper on 9 pricing pages 2. apify·read the resulting dataset 3. code·diff against last week's snapshot 4. slack·post changes to #competitive ✓2 pricing changes detected * Competitor A raised its team tier to $29/seat * Competitor B added a usage-based plan * 7 pages unchanged ### Collect a dataset for research Point the agent at a source. It runs the right actor, cleans the output, and writes a dataset you can actually use. Collect job postings for platform engineers at Series B devtools companies. 1. apify·run the job board actor across 3 sources 2. code·dedupe and normalize 1,240 postings 3. google-sheets·write \`Hiring Signals\` ✓1,240 postings collected * 418 remain after dedupe and filtering * 64 companies hiring for the target role * Sorted by posting recency ### Monitor a page for changes The agent watches the pages you care about - docs, changelogs, status pages - and tells you the moment something moves. Daily at 8:00am Daily, check competitor changelogs and summarize anything new. 1. apify·scrape 5 changelog pages 2. code·diff against yesterday's snapshot 3. notion·append new entries to \`Competitive Intel\` ✓3 new entries * Competitor A shipped SAML SSO * Competitor C deprecated its v1 API ### Enrich a list with public web data Take a list of companies and let the agent read each site, pull what you asked for, and write it back in a column. For each company in the sheet, read its site and classify its category. 1. google-sheets·read 300 company URLs 2. apify·scrape homepages and about pages 3. code·classify by category and stage 4. google-sheets·write the classification columns ✓300 companies classified * 287 classified with high confidence * 13 flagged for a human to check Triggers ## How a Apify workflow starts Apify does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook. ### Manual Run it from the app with an optional JSON payload. Every workflow supports this. ### Schedule A cron expression or a plain sentence such as every weekday at 9am. Times are UTC. ### Signed webhook A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes. Works with ## Apify works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [Apify + RedditGive your agents full access to Reddit.](/integrations/reddit/)[![](/static/img/assets/google-sheets-light.svg)![](/static/img/assets/google-sheets-dark.svg)Apify + Google SheetsGive your agents full access to Google Sheets.](/integrations/google-sheets/)[![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)Apify + Google DocsGive your agents full access to Google Docs.](/integrations/google-docs/) Templates ## Ready-to-run Apify workflows Copy the prompt, connect your tools, and start a run. [MarketingResearch brief writerResearches a topic across the live web and returns a sourced draft in your voice, with the open questions flagged.Run on demand![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)![](/static/img/assets/apify.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/google-docs-brief-writer/) Use cases ## Where Apify agents fit [MarketingResearch briefsA workflow searches the web, reads what it finds, and writes a draft with every claim linked to its source. Give it your prior work and the draft matches your voice.Run on demand![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)![](/static/img/assets/apify.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/content-pipeline/) FAQ ## Questions, answered ### How do I connect Apify? ### What can an agent reach in Apify? ### Can an Apify run trigger a Helios agent? ### Do I need Apify for web research? ### Does Apify usage cost extra? ## Put an agent on Apify. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Apollo Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/apollo Description: Agents search Apollo's contact and company graph, enrich the records you already have, and build target lists that match a definition you write in plain words. [← All integrations](/integrations/) Sales & CRM ![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg) # Give your agents full access to Apollo. Agents search Apollo's contact and company graph, enrich the records you already have, and build target lists that match a definition you write in plain words. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Apollo API v1 The full surface, searched at run time. Connect with * Helios OAuth app * Your own OAuth app * API key Event triggers Not yet Manual, schedule, and signed webhook are available. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/apollo/) What the agent can do ## What agents do with Apollo Helios searches the Apollo API v1 at run time. The agent finds the endpoint the task needs and calls it. * Search Apollo's entire API surface at run time and call any endpoint your key allows. * Enrich people and companies with firmographics, titles, and contact data. * Search for contacts matching a persona across an account list. * Build target account lists from criteria described in plain English. * Write enriched results straight into your CRM or a spreadsheet. * Combine with web research so each record carries a reason to reach out. Examples ## Tasks you can hand to a Apollo agent ### Enrich inbound leads within the minute A signup arrives. The agent enriches the person and their company, scores fit, and routes the ones worth a conversation. Signup webhook For each new signup, enrich and score fit, then route the good ones. 1. apollo·enrich person and company by email 2. code·score fit against our ICP definition 3. attio·create record with fit score 4. slack·post strong fits to #inbound ✓Lead scored 87/100 * Series B fintech · 240 employees * Signup is Head of Platform * Routed to @dana with a suggested opener ### Build a target list from a description Describe the accounts you want in a sentence. The agent searches, filters, verifies against the web, and hands back a list. Find Series A–B devtools companies in North America with 50–300 employees. 1. apollo·search companies matching the criteria 2. web·verify positioning on 120 company sites 3. apollo·find 2 contacts per qualified account 4. google-sheets·write \`Q2 Target List\` ✓94 accounts qualified * 188 contacts with verified titles * 26 accounts dropped after reading their site * Each row has a one-line reason to reach out ### Fill the gaps in your CRM The agent walks your existing records, finds the empty fields, and fills them from Apollo without touching what you already know. Weekly on Sunday Fill missing headcount, industry, and funding on CRM companies. 1. attio·list companies with empty firmographics 2. apollo·enrich 214 companies 3. attio·update only the empty fields ✓214 companies enriched * 181 matched with high confidence * 33 left empty for a human to check * Existing values preserved ### Research an account before outreach For a named account, the agent gathers the org chart, recent news, and product signals, then drafts an opener grounded in all of it. Research Northwind and draft an opener for their Head of Engineering. 1. apollo·pull org structure and contact details 2. web·read recent news and their engineering blog 3. attio·check prior touches with this account 4. google-docs·write research note and draft opener ✓Research note ready * They shipped a migration to Postgres last month * No prior contact with this account * Opener references their scaling post Triggers ## How a Apollo workflow starts Apollo does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook. ### Manual Run it from the app with an optional JSON payload. Every workflow supports this. ### Schedule A cron expression or a plain sentence such as every weekday at 9am. Times are UTC. ### Signed webhook A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes. Works with ## Apollo works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Apollo + AttioGive your agents full access to Attio.](/integrations/attio/)[![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)Apollo + ResendGive your agents full access to Resend.](/integrations/resend/)[![](/static/img/assets/typeform-light.svg)![](/static/img/assets/typeform-dark.svg)Apollo + TypeformGive your agents full access to Typeform.](/integrations/typeform/) Templates ## Ready-to-run Apollo workflows Copy the prompt, connect your tools, and start a run. [Sales & RevOpsInbound lead enrichmentEnriches every new signup, scores it against your ICP by reading the company's own website, and routes the strong fits.Signup webhook![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/apollo-lead-enrichment/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing company fields, and flags deals that have gone quiet. Every night.Nightly at 2:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/attio-crm-hygiene/) Use cases ## Where Apollo agents fit [Sales & RevOpsLead enrichmentA signup or form response fires a webhook. The workflow enriches the person and company, scores fit against your definition, creates the CRM record, and tells the right rep.Signup webhook![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/typeform-light.svg)![](/static/img/assets/typeform-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/lead-enrichment/)[Sales & RevOpsCRM data syncA workflow computes usage from your database, joins it with billing state and support volume, and writes the result onto each account record every night.Nightly at 1:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)](/use-cases/crm-data-sync/) FAQ ## Questions, answered ### How do I connect Apollo? ### What can an agent reach in Apollo? ### Can an Apollo event trigger an agent? ### Do Apollo credits get consumed by agent runs? ### How is my API key protected? ## Put an agent on Apollo. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Asana Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/asana Description: Agents turn requests into tasks, keep assignees and due dates current, answer questions in comments, and report on a project's status. Asana trigger events start an agent when a task is added, changes, or gets a comment, and when projects, portfolios, goals, or memberships change. [← All integrations](/integrations/) Project management # Let your agents work with Asana tasks and projects. Agents turn requests into tasks, keep assignees and due dates current, answer questions in comments, and report on a project's status. Asana trigger events start an agent when a task is added, changes, or gets a comment, and when projects, portfolios, goals, or memberships change. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Asana REST API The full surface, searched at run time. Connect with * API key * Your own OAuth app Set the project and the workspace to watch on the connection, and Helios registers the webhooks for task, comment, project, goal, and membership events. Event triggers Yes · 5 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/asana/) What the agent can do ## What agents do with Asana Helios searches the Asana REST API at run time. The agent finds the endpoint the task needs and calls it. * Call Asana API endpoints with the connected user's permissions. * Create tasks with an assignee, a due date, a project, and a description. * Change assignees and due dates, and mark tasks complete. * Comment on tasks, reply to the people who ask the agent a question, and attach files. * List a project's open tasks to report on progress and blockers. * Start a run when a task is added, changes, or gets a comment, or when a project, portfolio, goal, or membership changes. Examples ## Tasks you can hand to a Asana agent ### Triage every new task The agent reads each new task, fills in the description, sets a due date, and assigns an owner. asana · task.added On each new task in the Launch project: add the missing details, set a due date, and assign an owner. 1. asana·read the task and its project 2. slack·find the thread the request came from 3. asana·update the description, due date, and assignee ✓Task triaged * Description filled in from the Slack thread * Due Friday · assigned to the design lead ### Follow up when a task is done When a task is completed, the agent tells the people waiting on it and starts the next step. asana · task.changed When a task in the Launch project is completed, post an update and comment on the tasks it was blocking. 1. asana·read the task and the tasks that depend on it 2. asana·comment on each blocked task 3. slack·post the update to #launch ✓Follow-up sent * Comments added to two dependent tasks * Update posted to #launch ### Answer questions in task comments When someone asks a question in a comment, the agent looks it up and replies on the same task. asana · comment.added When a comment asks the agent a question, answer it on the same task. 1. asana·read the comment and the task 2. notion·find the spec it refers to 3. asana·reply on the task ✓Replied on the task * Linked the spec section on rollout dates * Confirmed the launch date is unchanged ### Report on a project every week A scheduled agent reads the project's open tasks and tells the team what is late, what is next, and what is blocked. Mondays at 9:00am Every Monday, summarize the Launch project's open tasks and post it to Slack. 1. asana·list the project's incomplete tasks 2. code·group by due date and assignee 3. slack·post the summary to #launch ✓Launch project summary * 12 open tasks, 3 overdue * 2 blocked on legal review Event triggers ## Start a run on Asana events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ------------- | --------------------------------------------------------------------------------------------------- | | task.added | A task is added to the project or one of its sections. | | task.changed | A task changes. Filter on the field that changed, such as the assignee, the due date, or completed. | | comment.added | Someone comments on a task, so an agent can answer or pick up the follow-up. | | project.added | A project is created in the workspace, so an agent can set it up from a template. | | goal.changed | A goal changes, so an agent can tell the people who own the work behind it. | Works with ## Asana works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Asana + SlackGive your agents full access to Slack.](/integrations/slack/)[Asana + NotionGive your agents full access to Notion.](/integrations/notion/) FAQ ## Questions, answered ### How do I connect Asana? ### What can an agent reach in Asana? ### Which Asana events can trigger an agent? ### Can one connection watch several projects? ## Put an agent on Asana. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Attio Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/attio Description: Agents read and write records, keep lists current, log activity, and turn a CRM into something that maintains itself. Combine Attio with enrichment and billing data and every record carries the context a rep needs. [← All integrations](/integrations/) Sales & CRM ![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg) # Give your agents full access to Attio. Agents read and write records, keep lists current, log activity, and turn a CRM into something that maintains itself. Combine Attio with enrichment and billing data and every record carries the context a rep needs. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Attio API v2 The full surface, searched at run time. Connect with * Helios OAuth app * Your own OAuth app Event triggers Not yet Manual, schedule, and signed webhook are available. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/attio/) What the agent can do ## What agents do with Attio Helios searches the Attio API v2 at run time. The agent finds the endpoint the task needs and calls it. * Search Attio's entire API surface at run time and call any endpoint your key allows. * Query, create, and update records across people, companies, deals, and custom objects. * Read and write list entries, including stage and status attributes. * Append notes and activity so every agent action leaves a trail on the record. * Reconcile records against enrichment, billing, and product data. * Run on a schedule so hygiene work happens without anyone remembering it. Examples ## Tasks you can hand to a Attio agent ### Keep the CRM clean on a schedule The agent finds duplicates, fills missing fields, corrects stage drift, and writes a note explaining every change it made. Nightly at 2:00am Nightly, dedupe companies, fill missing firmographics, and flag stale deals. 1. attio·list companies updated in 30 days 2. apollo·enrich 61 records missing headcount 3. attio·merge 9 duplicate companies 4. attio·note stale deals with no activity in 21 days ✓CRM hygiene pass complete * 61 records enriched * 9 duplicates merged * 14 deals flagged stale for their owners ### Enrich every new record as it lands A new company appears and the agent fills in size, industry, funding, and the people worth knowing before a rep opens it. Hourly Every hour, enrich new companies with firmographics and key contacts. 1. attio·list companies created in the last hour 2. apollo·enrich firmographics and find 3 contacts each 3. web·read each company's site for positioning 4. attio·update records and add a research note ✓12 companies enriched * Headcount, industry, and funding filled * 36 contacts added with titles * A two-line positioning summary per account ### Give reps a briefing before the call The agent assembles everything known about an account - usage, billing, support history, recent news - into one note on the record. Weekdays at 7:00am Each morning, write a briefing note on accounts with a call today. 1. attio·list accounts with a scheduled next step 2. postgres·pull product usage per account 3. stripe·check plan, MRR, and payment health 4. attio·write briefing note on each record ✓7 briefings written * Usage trend and top features per account * 2 accounts flagged with a failed payment * Recent support threads summarized ### Sync product signals into the CRM Usage from your database becomes fields on the account, so the CRM reflects what customers actually do. Nightly at 1:00am Nightly, sync product usage and health scores into Attio. 1. postgres·compute 30-day usage per workspace 2. code·score health from usage and support volume 3. attio·update \`health\` and \`last\_active\` on 480 accounts ✓480 accounts updated * 31 accounts moved into \`at risk\` * 18 accounts flagged as expansion candidates Triggers ## How a Attio workflow starts Attio does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook. ### Manual Run it from the app with an optional JSON payload. Every workflow supports this. ### Schedule A cron expression or a plain sentence such as every weekday at 9am. Times are UTC. ### Signed webhook A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes. Works with ## Attio works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)Attio + ApolloGive your agents full access to Apollo.](/integrations/apollo/)[Attio + StripeGive your agents full access to Stripe.](/integrations/stripe/)[![](/static/img/assets/typeform-light.svg)![](/static/img/assets/typeform-dark.svg)Attio + TypeformGive your agents full access to Typeform.](/integrations/typeform/) Templates ## Ready-to-run Attio workflows Copy the prompt, connect your tools, and start a run. [SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.slack · message.channel![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/templates/slack-support-triage/)[Sales & RevOpsFailed payment recoveryFinds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/stripe-failed-payment-recovery/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to find the accounts drifting toward the exit.Mondays at 7:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/churn-risk-watchlist/)[Sales & RevOpsInbound lead enrichmentEnriches every new signup, scores it against your ICP by reading the company's own website, and routes the strong fits.Signup webhook![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/apollo-lead-enrichment/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing company fields, and flags deals that have gone quiet. Every night.Nightly at 2:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/attio-crm-hygiene/) Use cases ## Where Attio agents fit [SupportSupport triageA workflow reads each new thread as it arrives. It finds the customer, checks the plan and billing state, sets labels and priority, and drafts a reply from your docs.plain · thread.thread\_created![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/use-cases/support-triage/)[Sales & RevOpsLead enrichmentA signup or form response fires a webhook. The workflow enriches the person and company, scores fit against your definition, creates the CRM record, and tells the right rep.Signup webhook![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/typeform-light.svg)![](/static/img/assets/typeform-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/lead-enrichment/)[OperationsBilling operationsA workflow watches Stripe for failed charges and starts recovery. A second one reconciles what you billed against what your own database recorded after the books close.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/billing-ops/)[Sales & RevOpsCRM data syncA workflow computes usage from your database, joins it with billing state and support volume, and writes the result onto each account record every night.Nightly at 1:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)](/use-cases/crm-data-sync/) FAQ ## Questions, answered ### How do I connect Attio? ### What can an agent reach in Attio? ### Can an Attio change trigger an agent? ### How do I keep an agent from writing bad data? ### Does Attio access cost extra? ## Put an agent on Attio. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Bitbucket Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/bitbucket Description: Agents can use the Bitbucket Cloud REST API to read repositories, manage pull requests, and inspect builds. Workflows can start on supported webhook events, subject to the connection's permissions and filters. [← All integrations](/integrations/) Developer tools # Connect agents to Bitbucket Cloud. Agents can use the Bitbucket Cloud REST API to read repositories, manage pull requests, and inspect builds. Workflows can start on supported webhook events, subject to the connection's permissions and filters. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Bitbucket Cloud REST API The full surface, searched at run time. Connect with * API key * Your own OAuth app Use an Atlassian API token, a Bitbucket access token, or your own Bitbucket OAuth consumer. Helios registers the webhook for trigger events when you save the connection. Event triggers Yes · 6 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/bitbucket/) What the agent can do ## What agents do with Bitbucket Helios searches the Bitbucket Cloud REST API at run time. The agent finds the endpoint the task needs and calls it. * Call Bitbucket Cloud REST API endpoints with your connection's permissions. * Open, comment on, approve, decline, and merge pull requests. * Read diffs, commits, branches, and files at any ref. * Read build statuses and Bitbucket Pipelines runs, steps, and logs. * Create branches and tags, report build statuses, and run pipelines. * Start runs on supported pull request, comment, push, build status, and Pipelines trace events. Examples ## Tasks you can hand to a Bitbucket agent ### Review every pull request as it opens The agent reads the diff and the files around it, then leaves a review comment with the risks it found. bitbucket · pull\_request.created On each new pull request into main: review the diff and comment with the review. 1. bitbucket·read the pull request and its diff 2. bitbucket·read the changed files at the source branch 3. code·check the change against the tests 4. bitbucket·comment with the review ✓Reviewed pull request #318 * The retry loop has no upper bound * One new function has no test * The migration matches the model change ### Explain a failed build When a build fails, the agent reads the Pipelines logs and tells the author what broke on the pull request. bitbucket · build\_status.updated When a build fails on a pull request branch, explain the failure on the pull request. 1. bitbucket·read the failed pipeline and its steps 2. bitbucket·download the step log 3. bitbucket·find the open pull request for the branch 4. bitbucket·comment with the cause ✓Explained the failure on pull request #322 * \`test\_invoice\_totals\` fails after the rounding change * The fix is a one-line change in \`totals.py\` ### Answer questions in pull request comments When someone asks a question in a comment, the agent looks it up and replies on the same pull request. bitbucket · pull\_request\_comment.created When a pull request comment asks the agent a question, answer it. 1. bitbucket·read the comment and the pull request 2. bitbucket·search the code it mentions 3. bitbucket·reply on the pull request ✓Replied on pull request #330 * The config flag is read in \`settings.py\` * It defaults to off in production ### Write release notes after a merge When a pull request merges into main, the agent adds it to the draft release notes and tells the team. bitbucket · pull\_request.merged When a pull request merges into main, add it to the release notes and post to Slack. 1. bitbucket·read the merged pull request 2. notion·append to the release notes draft 3. slack·post a summary to #releases ✓Release notes updated * Added pull request #335 under Fixes * Posted to #releases Event triggers ## Start a run on Bitbucket events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ------------------------------ | ------------------------------------------------------------------------------------------------------ | | pull\_request.created | A pull request is opened. Filter by repository or destination branch. | | pull\_request.approved | Someone approves a pull request, so the agent can check it is ready to merge. | | pull\_request.merged | A pull request is merged, so the agent can follow up on shipped work. | | pull\_request\_comment.created | Someone comments on a pull request, so an agent can answer or pick up the follow-up. | | repository.pushed | Commits or tags are pushed. Filter by branch so only \`main\` wakes the agent, or by tag for releases. | | build\_status.updated | A build status changes, such as a Bitbucket Pipelines run. Filter by build state to catch failures. | Works with ## Bitbucket works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [Bitbucket + GitHubGive your agents full access to GitHub.](/integrations/github/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Bitbucket + SlackGive your agents full access to Slack.](/integrations/slack/) FAQ ## Questions, answered ### How do I connect Bitbucket? ### Do app passwords still work? ### Which Bitbucket events can trigger an agent? ### What permission does Helios need for triggers? ## Put an agent on Bitbucket. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Box Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/box Description: Agents search your Box content, read and upload files, comment on files, share them, send them for signature, and keep folders organized. Box webhook events in a folder you choose start an agent when files and folders change, someone comments or gets access, a shared link appears, metadata changes, a task is assigned, or a Box Sign request moves forward. [← All integrations](/integrations/) Docs & knowledge # Give your agents access to your Box files. Agents search your Box content, read and upload files, comment on files, share them, send them for signature, and keep folders organized. Box webhook events in a folder you choose start an agent when files and folders change, someone comments or gets access, a shared link appears, metadata changes, a task is assigned, or a Box Sign request moves forward. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Box API 2.0 The full surface, searched at run time. Connect with * API key * Your own OAuth app Paste the client ID and secret of a Box Server app that uses Client Credentials Grant, which acts as its service account or a managed user. Or sign in through your own Box User app with OAuth 2.0. Event triggers Yes · 6 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/box/) What the agent can do ## What agents do with Box Helios searches the Box API 2.0 at run time. The agent finds the endpoint the task needs and calls it. * Call Box API 2.0 operations allowed by the connected account and app scopes. * Search files and folders by name and content. * Read and download files, and upload new files and versions. * Comment on files and reply to comments. * Create shared links and manage collaborators. * Create folders, and rename, copy, and move files and folders. * Send Box Sign requests and ask Box AI about files. * Start a run on file, folder, comment, collaboration, shared link, metadata, task, and Box Sign events in a folder you choose. Examples ## Tasks you can hand to a Box agent ### Route every file that lands in an intake folder When a file is uploaded, the agent reads it, moves it to the right folder, and tells the owner. box · file.uploaded When a file lands in \`Intake\`, file it by type and tell the owner in Slack. 1. box·read \`Acme renewal notice.txt\` 2. box·move it to \`Customers/Acme\` 3. slack·message the account owner ✓Renewal notice filed * Moved to \`Customers/Acme\` * Renewal date and price change sent to the owner ### Answer questions in file comments When someone asks a question in a comment, the agent reads the file and replies in the same thread. box · comment.created When a comment asks the agent a question, answer it on the same file. 1. box·read the comment and the file 2. box·reply to the comment ✓Replied on \`Q3 plan.md\` * The launch moved to the second week of November * Quoted the section that says so ### Share files on request Ask in plain words for a file, and the agent finds it, creates a shared link, and sends it where you need it. Find the latest security questionnaire and send a view-only link to #sales. 1. box·search for \`security questionnaire\` 2. box·create a shared link 3. slack·post the link to #sales ✓Link shared * Found the newest of three versions * Link posted to #sales Event triggers ## Start a run on Box events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ----------------------- | ------------------------------------------------------------------------------------- | | file.uploaded | A file lands in the watched folder - the moment to read it, file it, or tell someone. | | folder.created | A new folder appears, such as one for each customer or project, ready to be set up. | | comment.created | Someone comments on a file, so an agent can answer or follow up. | | collaboration.created | Someone is invited to a folder. Filter by folder name or role. | | shared\_link.created | A file or folder gets a shared link. Filter by link access to catch open links. | | sign\_request.completed | Every signer has signed, so an agent can file the document and tell the team. | Works with ## Box works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Box + SlackGive your agents full access to Slack.](/integrations/slack/)[Box + NotionGive your agents full access to Notion.](/integrations/notion/)[Box + Google DriveGive your agents access to Google Drive.](/integrations/google-drive/) FAQ ## Questions, answered ### How do I connect Box? ### What can an agent reach in Box? ### Which Box events can trigger an agent? ## Put an agent on Box. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Brevo Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/brevo Description: Agents search the Brevo API to manage contacts, send messages, inspect campaigns and update CRM records. Email and contact webhooks can start workflows. [← All integrations](/integrations/) Email ![](/static/img/assets/brevo-light.svg)![](/static/img/assets/brevo-dark.svg) # Manage contacts, campaigns and transactional email with your agents. Agents search the Brevo API to manage contacts, send messages, inspect campaigns and update CRM records. Email and contact webhooks can start workflows. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Brevo v3 API The full surface, searched at run time. Connect with * API key * Your own OAuth app Connect with an API key or a private OAuth app from your Brevo organization. Event triggers Yes · 4 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/brevo/) What the agent can do ## What agents do with Brevo Helios searches the Brevo v3 API at run time. The agent finds the endpoint the task needs and calls it. * Create and update contacts and lists. * Send transactional messages and manage marketing campaigns. * Read delivery reports and campaign statistics. * Manage CRM companies, deals and tasks. Examples ## Tasks you can hand to a Brevo agent Event triggers ## Start a run on Brevo events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ----------------------- | ------------------------------------------------------------ | | email.delivered | An email reaches its recipient. | | email.hard\_bounced | An email permanently fails delivery. | | contact.added\_to\_list | A contact joins a list. | | email.received | An inbound email is parsed on a configured receiving domain. | Works with ## Brevo works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)Brevo + ResendGive your agents full access to Resend.](/integrations/resend/)[![](/static/img/assets/gmail-light.svg)![](/static/img/assets/gmail-dark.svg)Brevo + GmailGive your agents full access to Gmail.](/integrations/gmail/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Brevo + SlackGive your agents full access to Slack.](/integrations/slack/) FAQ ## Questions, answered ### How do I connect Brevo? ### Do I need to create webhooks? ## Put an agent on Brevo. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Cal.com Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/cal-com Description: Agents check availability, create bookings, and reschedule or cancel meetings using your Cal.com permissions. Cal.com trigger events start an agent when a booking changes, a meeting starts or ends, a recording is ready, or a routing form is submitted. [← All integrations](/integrations/) Sales & CRM ![](/static/img/assets/cal-com-light.svg)![](/static/img/assets/cal-com-dark.svg) # Check availability and manage Cal.com bookings. Agents check availability, create bookings, and reschedule or cancel meetings using your Cal.com permissions. Cal.com trigger events start an agent when a booking changes, a meeting starts or ends, a recording is ready, or a routing form is submitted. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Cal.com API v2 The full surface, searched at run time. Connect with * API key * Your own OAuth app Helios registers the webhook for Cal.com events with your key or OAuth app. With Admin access, an organization admin's connection also gets an organization webhook. Event triggers Yes · 9 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/cal-com/) What the agent can do ## What agents do with Cal.com Helios searches the Cal.com API v2 at run time. The agent finds the endpoint the task needs and calls it. * Call Cal.com API v2 endpoints allowed by your API key or OAuth token. * Find open slots for an event type and book one for an attendee. * Reschedule or cancel bookings, and confirm or decline booking requests. * Read bookings with their attendees and the answers to booking questions. * Create and change event types, availability schedules, and out-of-office entries. * Start a run on bookings, meetings, Cal Video recordings, routing forms, and out-of-office entries. Examples ## Tasks you can hand to a Cal.com agent ### Prepare a meeting brief Use a booking trigger with Apollo, Attio, and Slack to research the attendee and send a brief to the host. cal.com · booking.created When someone books a demo, research them and post a brief to the host in Slack. 1. cal.com·read the booking and the attendee's answers 2. apollo·enrich the attendee and their company 3. attio·check for an existing deal 4. slack·post the brief to the host ✓Brief posted for the 2pm demo * VP Operations at a 300-person logistics company * Open deal in Attio, last touched three weeks ago * Asked about SSO in the booking form ### Qualify booking requests For event types that need confirmation, the agent checks each request against your criteria and confirms or declines it. cal.com · booking.requested Confirm enterprise demo requests from companies over 100 people, and decline the rest with a link to the self-serve tour. 1. cal.com·read the request 2. apollo·look up the company's size 3. cal.com·confirm the booking ✓Request confirmed * Company has 850 employees * Booking confirmed for Thursday at 10am ### Follow up when the meeting ends Use the scheduled meeting end trigger with Gmail and Attio to draft a follow-up and log the booking. cal.com · meeting.ended After each sales call, draft a follow-up email and log the call in Attio. 1. cal.com·read the booking and attendees 2. attio·log the call on the deal 3. gmail·draft the follow-up email ✓Follow-up drafted * Draft in Gmail with next steps and the pricing page * Call logged on the deal in Attio ### Offer new times after a cancellation When a booking is cancelled, the agent finds new open times and emails the attendee to rebook. cal.com · booking.cancelled When a demo is cancelled, email the attendee three new times from my calendar. 1. cal.com·read the cancellation reason 2. cal.com·find open slots this week 3. gmail·email the attendee new times ✓Rebooking email sent * Offered Tuesday 11am, Wednesday 3pm, and Friday 9am Event triggers ## Start a run on Cal.com events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ----------------------- | -------------------------------------------------------- | | booking.created | A booking is created and confirmed. | | booking.requested | Someone requests a booking that needs your confirmation. | | booking.rescheduled | A booking moves to a new time. | | booking.cancelled | A booking is cancelled. | | booking.updated | A booking's location or no-show status changes. | | meeting.started | A booking reaches its scheduled start time. | | meeting.ended | A booking reaches its scheduled end time. | | recording.transcribed | A Cal Video transcript is ready. | | routing\_form.submitted | Someone submits a routing form. | Works with ## Cal.com works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/gmail-light.svg)![](/static/img/assets/gmail-dark.svg)Cal.com + GmailGive your agents full access to Gmail.](/integrations/gmail/)[![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Cal.com + AttioGive your agents full access to Attio.](/integrations/attio/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Cal.com + SlackGive your agents full access to Slack.](/integrations/slack/) FAQ ## Questions, answered ### How do I connect Cal.com? ### What can an agent reach in Cal.com? ### Which Cal.com events can trigger an agent? ### Can I connect with OAuth? ## Put an agent on Cal.com. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Calendly Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/calendly Description: Agents find open times, share booking links, book and cancel meetings, prepare hosts for upcoming meetings, and follow up on meeting recaps. Calendly trigger events start an agent when someone books, cancels, misses a meeting, or submits a routing form, when an event type or contact changes, and when a meeting recap is ready. [← All integrations](/integrations/) Sales & CRM # Manage Calendly meetings with your agents. Agents find open times, share booking links, book and cancel meetings, prepare hosts for upcoming meetings, and follow up on meeting recaps. Calendly trigger events start an agent when someone books, cancels, misses a meeting, or submits a routing form, when an event type or contact changes, and when a meeting recap is ready. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Calendly API v2 The full surface, searched at run time. Connect with * API key * Your own OAuth app Triggers need a paid Calendly plan. Connect as an organization owner or admin so triggers cover every member's meetings. Event triggers Yes · 7 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/calendly/) What the agent can do ## What agents do with Calendly Helios searches the Calendly API v2 at run time. The agent finds the endpoint the task needs and calls it. * Find event types and share booking links, or create single-use links. * List upcoming meetings with their invitees and booking answers. * Find open times and book meetings at them through the Scheduling API, on Standard plans and above. * Cancel meetings with a reason, and mark no-shows. * Create and update event types and their availability. * Read and update contacts, and read meeting recaps and transcripts from Calendly Notetaker. * Read routing form submissions and the meetings they led to. * Start a run on bookings, cancellations, no-shows, routing form submissions, event type and contact changes, and meeting recaps. Examples ## Tasks you can hand to a Calendly agent ### Brief the host before each new meeting When someone books a demo, the agent researches the invitee and their company and sends the host a short brief. calendly · invitee.created When a demo is booked, research the invitee and DM the host a brief. 1. calendly·read the booking and the invitee's answers 2. apollo·enrich the invitee and their company 3. web·read recent news about the company 4. slack·DM the brief to the host ✓Brief sent for Thursday's demo * Head of RevOps at a 300-person logistics company * Asked about Salesforce sync in the booking form * Suggested agenda attached ### Qualify routing form leads When someone submits a routing form, the agent scores the lead, creates the CRM record, and alerts the owner. calendly · routing\_form\_submission.created Qualify each routing form submission and route good leads to sales. 1. calendly·read the submission and its answers 2. apollo·enrich the company 3. attio·create the person and company 4. slack·notify the owner in #inbound ✓Lead qualified * Fits the ideal customer profile, 120 seats * Record created in Attio and assigned to Dana ### Follow up on cancellations When an invitee cancels, the agent drafts a short note with the booking link so they can pick a new time. Reschedules are skipped. calendly · invitee.canceled When a meeting is canceled, not rescheduled, draft a follow-up with my booking link. 1. calendly·read the canceled meeting and the reason 2. calendly·find the event type's booking link 3. gmail·draft the follow-up ✓Follow-up drafted * Reason given: a conflict with a board meeting * Draft offers next week with the booking link ### Daily meeting prep Every morning, the agent lists the day's meetings and posts what the team should know about each invitee. Weekdays at 8:00am Every weekday at 8:00am, post a prep note for today's meetings. 1. calendly·list today's meetings and invitees 2. attio·look up each invitee's record 3. slack·post the prep note to #sales ✓Prep note for 5 meetings * 2 renewals, 2 first calls, 1 partner sync * One invitee has an open support ticket Event triggers ## Start a run on Calendly events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | --------------------------------- | ----------------------------------------------------------------------------------------------------------------- | | invitee.created | Someone books a meeting, so an agent can research the invitee and brief the host. Filter on the event type. | | invitee.canceled | A meeting is canceled. Filter out reschedules to follow up only on real cancellations. | | invitee\_no\_show.created | A host marks an invitee as a no-show, so an agent can send a link to book again. | | routing\_form\_submission.created | Someone submits a routing form, whether or not they book. Needs a connection from an organization owner or admin. | | meeting\_recap.created | Calendly Notetaker finishes a recap of one of your meetings, so an agent can file the action items. | | contact.created | A contact is added by a booking, by hand or through the API, so an agent can enrich it or sync it to a CRM. | | event\_type.updated | An event type changes. Filter on the event type to watch the ones that matter. | Works with ## Calendly works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Calendly + AttioGive your agents full access to Attio.](/integrations/attio/)[![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)Calendly + ApolloGive your agents full access to Apollo.](/integrations/apollo/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Calendly + SlackGive your agents full access to Slack.](/integrations/slack/) FAQ ## Questions, answered ### How do I connect Calendly? ### What can an agent reach in Calendly? ### Can an agent book meetings? ### Which Calendly events can trigger an agent? ### Why do no Calendly events reach Helios? ## Put an agent on Calendly. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Clay Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/clay Description: Agents search Clay's database of companies and people and run your Clay functions on the records they find. An HTTP API column in a Clay table can start a workflow when it sends a row. A Clay webhook can start one when a function or Workflow run started with its webhook ID finishes. [← All integrations](/integrations/) Sales & CRM ![](/static/img/assets/clay-light.svg)![](/static/img/assets/clay-dark.svg) # Give your agents access to Clay. Agents search Clay's database of companies and people and run your Clay functions on the records they find. An HTTP API column in a Clay table can start a workflow when it sends a row. A Clay webhook can start one when a function or Workflow run started with its webhook ID finishes. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Clay Public API The full surface, searched at run time. Connect with * API key Create an API key with the Public API scope on Clay's API and CLI page. For triggers, add an HTTP API column to a Clay table that sends rows to Helios, or create a Clay webhook with the Clay CLI. HTTP API columns need a Growth or Enterprise plan. Event triggers Yes · 2 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/clay/) What the agent can do ## What agents do with Clay Helios searches the Clay Public API at run time. The agent finds the endpoint the task needs and calls it. * Search the Clay Public API at run time and call any endpoint your key allows. * Find people at target accounts by job title and company size. * Look up companies and their firmographics by domain. * Run Clay-managed and custom functions on up to 100 records and read the results. * Query known Clay tables with filters on Enterprise plans. * Start a run when an HTTP API column in a Clay table sends a row. * Start a run when a Clay function run that names your Clay webhook finishes. Examples ## Tasks you can hand to a Clay agent ### Act on leads sent by a Clay table When an HTTP API column sends a lead, the agent can qualify it and create a CRM contact. clay · row.sent For each row from the Inbound leads table, score the lead and create the contact in the CRM. 1. clay·look up the company's size and industry 2. attio·create the person and company 3. slack·post the lead to #sales ✓Lead routed * Head of RevOps at a 400-person software company * Matches the mid-market profile * Created in Attio and posted to #sales ### Build a prospect list The agent searches Clay for people who match a persona at a set of accounts and returns a clean list. Run now Find heads of sales at software companies with 200 to 1,000 employees. 1. clay·read the search query reference 2. clay·create and run a people search 3. code·drop duplicates and sort ✓42 prospects found * Name, title, company, and location for each * Grouped by company size ### Enrich a list with a Clay function The agent runs a Clay function on a list of domains, waits for the results, and reports what came back. Run now Find the work email for each person in this list with our Clay function. 1. clay·start a function run on 25 items 2. clay·read the run's results 3. code·match results to the input rows ✓Function run complete * 21 emails found * 4 items failed with no match Event triggers ## Start a run on Clay events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | --------------------- | ----------------------------------------------------------------------------------------- | | row.sent | A Clay table sends a row through an HTTP API column. Filter on the table name in the row. | | routine\_run.finished | A Clay function or Workflow run that was started with your Clay webhook's ID finishes. | Works with ## Clay works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Clay + AttioGive your agents full access to Attio.](/integrations/attio/)[![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)Clay + ApolloGive your agents full access to Apollo.](/integrations/apollo/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Clay + SlackGive your agents full access to Slack.](/integrations/slack/) FAQ ## Questions, answered ### How do I connect Clay? ### Can an agent add rows to a Clay table? ### How do Clay rows trigger an agent? ### Can an agent react when a Clay function run finishes? ### Do agent runs use Clay credits? ## Put an agent on Clay. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # ClickUp Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/clickup Description: Agents create tasks from requests, move work between statuses, log time, and report on lists. ClickUp trigger events start an agent when a task, comment, list, folder, space, or goal changes. [← All integrations](/integrations/) Project management # Manage ClickUp tasks, comments, and time entries with agents. Agents create tasks from requests, move work between statuses, log time, and report on lists. ClickUp trigger events start an agent when a task, comment, list, folder, space, or goal changes. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach ClickUp API v2 and v3 The full surface, searched at run time. Connect with * API key * Your own OAuth app Set the workspace ID on the connection if the token can see more than one ClickUp workspace. Helios registers the webhook for trigger events there. Event triggers Yes · 4 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/clickup/) What the agent can do ## What agents do with ClickUp Helios searches the ClickUp API v2 and v3 at run time. The agent finds the endpoint the task needs and calls it. * Call ClickUp API v2 and v3 with your connected user's permissions. * Create tasks with a list, priority, assignee, due date, and tags. * Move tasks between statuses and update their fields. * Log time on tasks in Spaces with time tracking turned on, and read time entries. * Comment on tasks and reply to the people who ask the agent. * Attach files to tasks and read the files attached to them. * Start a run when a task is created, updated, moved, or deleted, when a comment is added or edited, or when a list, folder, space, or goal changes. Examples ## Tasks you can hand to a ClickUp agent ### Triage every new task The agent reads the new task, checks for duplicates in the list, then sets priority and an assignee. clickup · task.created On each new task in the Support list: set priority, add tags, and assign an owner. 1. clickup·read the task and its list 2. clickup·search open tasks for duplicates 3. clickup·set priority, tags, and assignee ✓Task triaged * Priority High · tagged \`billing\` * Linked to an open task with the same error * Assigned to the billing on-call engineer ### Hand off work when a task moves to review When a task moves to In Review, the agent checks the linked pull request and posts a summary for the reviewer. clickup · task.updated When a task moves to In Review, summarize the linked pull request in a comment. 1. clickup·read the task and its description 2. github·read the linked pull request 3. clickup·comment with a review summary ✓Summary posted for review * Four files changed in the invoice export * Tests added for the empty-invoice case * One open question about the date format ### Report on a list every week A scheduled agent reads a list, groups its tasks by status and owner, and posts what moved and what is stuck. Fridays at 4:00pm Every Friday, report on the Roadmap list and post it to Slack. 1. clickup·list tasks and their statuses 2. code·group by status and owner 3. slack·post the report to #product ✓Roadmap weekly report * 9 tasks complete, 6 in progress * 3 overdue, all waiting on design * 21 hours logged this week Event triggers ## Start a run on ClickUp events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | --------------- | ---------------------------------------------------------------------------------- | | task.created | A task is created in a list. | | task.updated | A task changes. Filter on the status it moved to, such as in progress or complete. | | task.moved | A task moves to another list, such as from triage to a team's backlog. | | comment.created | Someone comments on a task, so an agent can answer or pick up the follow-up. | Works with ## ClickUp works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [ClickUp + GitHubGive your agents full access to GitHub.](/integrations/github/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)ClickUp + SlackGive your agents full access to Slack.](/integrations/slack/) FAQ ## Questions, answered ### How do I connect ClickUp? ### What can an agent reach in ClickUp? ### Which ClickUp events can trigger an agent? ### What if I belong to more than one workspace? ## Put an agent on ClickUp. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Cloudflare Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/cloudflare Description: Agents manage DNS records and zone settings, look into failing Workers, and work with KV, R2, D1, WAF rules, and Zero Trust. Supported alerts can start workflows for health check changes, DDoS attacks, Pages deployments, and SSL certificate changes. Availability depends on your account and permissions. [← All integrations](/integrations/) Developer tools # Give your agents access to Cloudflare. Agents manage DNS records and zone settings, look into failing Workers, and work with KV, R2, D1, WAF rules, and Zero Trust. Supported alerts can start workflows for health check changes, DDoS attacks, Pages deployments, and SSL certificate changes. Availability depends on your account and permissions. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Cloudflare API v4 The full surface, searched at run time. Connect with * API key * Your own OAuth app Use an API token, or your own OAuth app with the scopes Helios requests. Give it Notifications Edit so Helios can register the alerts for triggers. Event triggers Yes · 5 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/cloudflare/) What the agent can do ## What agents do with Cloudflare Helios searches the Cloudflare API v4 at run time. The agent finds the endpoint the task needs and calls it. * Look up REST endpoints in a pinned Cloudflare API specification and call them with your connection credentials. * Create, update, and delete DNS records, and change zone settings such as the security level. * Purge cached files after a deploy. * Inspect Workers, their versions and deployments, query their logs, and set secrets. * Read and write Workers KV, manage R2 buckets, and query D1 databases. * Start a run on supported Cloudflare alerts, with optional zone filters for alerts about a zone. Examples ## Tasks you can hand to a Cloudflare agent ### Fail over when a health check goes down When a health check reports an unhealthy origin, the agent points the DNS record at the backup origin and tells the team. cloudflare · health\_check\_status\_notification.sent When the api.example.com health check goes unhealthy, point its DNS record at the backup origin. 1. cloudflare·read the health check alert 2. cloudflare·find the A record for the failing origin 3. cloudflare·point the record at the backup origin 4. slack·post the change to #incidents ✓api.example.com moved to the backup origin * The primary origin failed its health check in 3 regions * The A record now points at the backup origin * Posted in #incidents with the health check details ### Respond to a DDoS attack When Cloudflare reports an HTTP DDoS attack, the agent turns on Under Attack mode for the zone and writes up what it saw. cloudflare · dos\_attack\_l7.sent On an HTTP DDoS alert, turn on Under Attack mode for the zone and summarize the attack. 1. cloudflare·read the DDoS alert 2. cloudflare·set the zone's security level to Under Attack 3. slack·post a summary to #security ✓Under Attack mode on for example.com * Attack on shop.example.com peaked at 48,000 requests a second * Cloudflare mitigated it with the HTTP DDoS managed ruleset * Posted in #security with the attack details ### Debug a failing Worker A scheduled agent reads a Worker's recent errors and opens an issue with the stack trace and the last deploy. Every hour Every hour, find new errors in the checkout Worker's logs and open an issue. 1. cloudflare·query the Worker's logs for the last hour 2. cloudflare·list the Worker's recent deployments 3. github·find the commit behind the last deploy 4. github·open an issue with the stack trace ✓Issue opened for checkout-worker * TypeError in the cart handler since the 14:02 deploy * 1,240 failed requests in the last hour * Linked to the commit that changed the cart schema ### Audit DNS records every week A scheduled agent lists DNS records across your zones and flags records that point at retired origins or are missing a proxy. Mondays at 9:00am Every Monday, list DNS records that point at retired origins and post them to Slack. 1. cloudflare·list the account's zones 2. cloudflare·list DNS records in each zone 3. code·compare them with the origin list 4. slack·post the list to #platform ✓DNS audit for 6 zones * 3 records point at decommissioned servers * 2 records are DNS-only and expose the origin IP Event triggers ## Start a run on Cloudflare events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ---------------------------------------- | ----------------------------------------------------------------------------------------------------- | | health\_check\_status\_notification.sent | A health check's origin becomes healthy or unhealthy, so an agent can fail over or bring it back. | | dos\_attack\_l7.sent | Cloudflare mitigates an HTTP DDoS attack on a zone, so an agent can tighten security and write it up. | | pages\_event\_alert.sent | A Pages deployment starts, fails, or succeeds, so an agent can look into a failed build. | | universal\_ssl\_event\_type.sent | A Universal SSL certificate is validated, issued, renewed, or about to expire. | | tunnel\_health\_event.sent | A Cloudflare Tunnel's health changes, so an agent can check the connector behind it. | Works with ## Cloudflare works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [Cloudflare + GitHubGive your agents full access to GitHub.](/integrations/github/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Cloudflare + SlackGive your agents full access to Slack.](/integrations/slack/) FAQ ## Questions, answered ### How do I connect Cloudflare? ### What can an agent reach in Cloudflare? ### Which Cloudflare events can trigger an agent? ### Why don't Cloudflare notifications reach Helios? ## Put an agent on Cloudflare. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Databases Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/databases Description: Connect Postgres, MySQL, or ClickHouse and agents introspect the schema, write real SQL, and reason over the results in their own sandbox. Reach private databases through an SSH tunnel without opening anything to the internet. [← All integrations](/integrations/) Data # Give your agents full access to your databases. Connect Postgres, MySQL, or ClickHouse and agents introspect the schema, write real SQL, and reason over the results in their own sandbox. Reach private databases through an SSH tunnel without opening anything to the internet. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Postgres, MySQL, and ClickHouse over SQL The full surface, searched at run time. Connect with * Connection string Add an SSH tunnel with a password or private key for databases on a private network. Event triggers Not yet Manual, schedule, and signed webhook are available. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/databases/) What the agent can do ## What agents do with Databases Agents introspect the schema, write SQL, and work over the results in their own sandbox. Credentials stay outside the sandbox. * Connect Postgres, MySQL, and ClickHouse with credentials stored envelope-encrypted. * Introspect schemas - tables, columns, types, keys, and indexes - before writing a query. * Write and run SQL against your data, then analyze results in the sandbox with code. * Reach private databases through an SSH tunnel, so nothing needs public exposure. * Grant read-only credentials so a reporting agent can never write. * Queries run read-only with a 60 second timeout and a 100 row default limit. Examples ## Tasks you can hand to a database agent ### Ask your database a question in English The agent reads the schema, writes the SQL, runs it, and explains the answer - including the caveats in the data. Which accounts grew usage more than 50% last month, and what do they have in common? 1. postgres·introspect schema for usage tables 2. postgres·query month-over-month usage by account 3. code·cluster the growing accounts by attributes ✓23 accounts grew over 50% * 18 connected a second integration last month * Median team size 12, up from 7 * Query and assumptions included in the run ### Publish a metrics report on a schedule Every morning the agent runs the queries, computes the derived metrics, and posts a report your team reads. Weekdays at 7:00am Each morning, post yesterday's metrics with anything unusual called out. 1. clickhouse·query events for the last 24h 2. postgres·join account metadata 3. code·compute trends and flag anomalies 4. slack·post report to #metrics ✓Metrics · Mar 6 * Runs 41.2k · up 6% day over day * Signups 128 · in line with the trend * Error rate up 0.4pp, concentrated in one region ### Run data quality checks every night The agent checks the invariants you care about, and when one breaks it says which rows, since when, and what changed upstream. Nightly at 3:00am Nightly, run our data quality checks and alert on failures. 1. postgres·run 14 invariant checks 2. postgres·isolate failing rows and first occurrence 3. resend·email the on-call analyst ✓2 checks failed * \`orders.currency\` null on 41 rows since 02:10 * \`accounts.plan\` has 3 values outside the enum * 12 checks passed ### Move data where it needs to be Query results become CRM fields, spreadsheet rows, or an email. The agent handles the shape change in code. Nightly at 1:00am Nightly, sync product usage into the CRM as account health fields. 1. postgres·compute 30-day usage per account 2. code·map usage into health tiers 3. attio·update 480 account records ✓480 accounts synced * 31 moved into \`at risk\` * 18 flagged as expansion candidates Triggers ## How a database workflow starts Databases does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook. ### Manual Run it from the app with an optional JSON payload. Every workflow supports this. ### Schedule A cron expression or a plain sentence such as every weekday at 9am. Times are UTC. ### Signed webhook A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes. Works with ## Your databases work with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/google-sheets-light.svg)![](/static/img/assets/google-sheets-dark.svg)Databases + Google SheetsGive your agents full access to Google Sheets.](/integrations/google-sheets/)[Databases + StripeGive your agents full access to Stripe.](/integrations/stripe/)[![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Databases + AttioGive your agents full access to Attio.](/integrations/attio/) Templates ## Ready-to-run database workflows Copy the prompt, connect your tools, and start a run. [Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to find the accounts drifting toward the exit.Mondays at 7:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/churn-risk-watchlist/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out.Mondays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/weekly-metrics-report/)[OperationsNightly data quality checksRuns your invariants against production every night and emails the on-call analyst which rows broke and since when.Nightly at 3:00am![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/templates/database-health-check/) Use cases ## Where database agents fit [OperationsDatabase reportingA workflow reads your schema, writes the SQL, runs it, checks the results in its sandbox, and posts a report to the channel your team reads.Weekdays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/database-reporting/)[OperationsBilling operationsA workflow watches Stripe for failed charges and starts recovery. A second one reconciles what you billed against what your own database recorded after the books close.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/billing-ops/)[Sales & RevOpsCRM data syncA workflow computes usage from your database, joins it with billing state and support volume, and writes the result onto each account record every night.Nightly at 1:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)](/use-cases/crm-data-sync/) FAQ ## Questions, answered ### Which databases can I connect? ### How does an agent reach a database on a private network? ### Can a database change trigger an agent? ### How do I stop an agent from writing to production? ### Does the agent see my whole schema? ## Put an agent on your databases. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Deel Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/deel Description: Agents search Deel's API to manage contracts, workers, payroll and HR records. Webhooks can start workflows when those records change. [← All integrations](/integrations/) HR ![](/static/img/assets/deel-light.svg)![](/static/img/assets/deel-dark.svg) # Manage workforce operations with your agents. Agents search Deel's API to manage contracts, workers, payroll and HR records. Webhooks can start workflows when those records change. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Deel REST and SCIM APIs The full surface, searched at run time. Connect with * API key * Your own OAuth app Connect an API token or your own Deel OAuth app, then select production or sandbox. Event triggers Yes · 4 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/deel/) What the agent can do ## What agents do with Deel Helios searches the Deel REST and SCIM APIs at run time. The agent finds the endpoint the task needs and calls it. * Create and update contracts and worker records. * Read payroll, payslip and invoice information. * Manage time off, timesheets and invoice adjustments. * Work with recruiting, immigration and IT asset records. Examples ## Tasks you can hand to a Deel agent Event triggers ## Start a run on Deel events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | --------------------------- | ----------------------------------------- | | contract.created | A contract is created. | | worker.updated | A worker record changes. | | gp\_payslip.made\_available | Global Payroll payslips become available. | | time\_off.reviewed | A time off request is reviewed. | Works with ## Deel works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Deel + SlackGive your agents full access to Slack.](/integrations/slack/)[![](/static/img/assets/google-sheets-light.svg)![](/static/img/assets/google-sheets-dark.svg)Deel + Google SheetsGive your agents full access to Google Sheets.](/integrations/google-sheets/) FAQ ## Questions, answered ### How do I connect Deel? ### Which events can start workflows? ### Do I need to configure a webhook? ## Put an agent on Deel. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Discord Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/discord Description: Agents read channels, follow threads, post updates, and keep an eye on the community while your team sleeps. Give one a schedule and every question, bug report, and feature request gets captured. [← All integrations](/integrations/) Community # Give your agents full access to Discord. Agents read channels, follow threads, post updates, and keep an eye on the community while your team sleeps. Give one a schedule and every question, bug report, and feature request gets captured. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Discord API v10 The full surface, searched at run time. Connect with * Your own OAuth app Create a bot in the Discord developer portal and paste its token. Event triggers Not yet Manual, schedule, and signed webhook are available. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/discord/) What the agent can do ## What agents do with Discord Helios searches the Discord API v10 at run time. The agent finds the endpoint the task needs and calls it. * Search Discord's entire API surface at run time and call any endpoint your bot's permissions allow. * Read channel messages and threads across the servers your bot has joined. * Post messages, embeds, and thread replies. * Manage roles, reactions, and channel membership within the bot's permissions. * Cluster community conversation into themes worth acting on. * Route bug reports and feature requests into GitHub or Notion. Examples ## Tasks you can hand to a Discord agent ### Digest the community every day The agent reads every channel, separates questions from noise, and posts a digest with the threads that still need an answer. Daily at 7:00pm Every evening, summarize community activity and list unanswered questions. 1. discord·read 6 channels from the last 24h 2. code·cluster topics and find unanswered threads 3. slack·post digest to #community ✓Community · Mar 6 * 142 messages · 4 themes * 7 questions still unanswered, oldest 9h * 2 bug reports worth filing ### Capture bug reports as issues When someone describes a real bug, the agent files it in GitHub with the reproduction steps and links back to the thread. Every 2 hours File clear bug reports from #help as GitHub issues. 1. discord·read new #help threads 2. github·search for an existing issue 3. github·open issue with repro steps 4. discord·reply with the issue link ✓2 issues filed * #1194 export fails on large workspaces * #1195 dark mode contrast on the runs table * Both linked back to their Discord threads ### Answer the common questions The agent watches for questions it has documentation for, answers them in thread, and leaves the rest for the team. Every 15 minutes Answer questions in #help that our docs already cover. 1. discord·read unanswered #help messages 2. notion·search docs for a match 3. discord·reply in thread with the answer ✓4 questions answered * Each reply links the relevant doc section * 3 questions left for the team as no doc exists ### Announce what shipped When a release publishes, the agent writes the community-facing version of the notes and posts it to the announcements channel. github · release.published On each release, post community-friendly notes to #announcements. 1. github·read release notes for v2.8.0 2. discord·post embed to #announcements ✓v2.8.0 announced * Rewrote three internal terms into plain language * Called out the one breaking change up front Triggers ## How a Discord workflow starts Discord does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook. ### Manual Run it from the app with an optional JSON payload. Every workflow supports this. ### Schedule A cron expression or a plain sentence such as every weekday at 9am. Times are UTC. ### Signed webhook A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes. Works with ## Discord works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [Discord + RedditGive your agents full access to Reddit.](/integrations/reddit/)[Discord + GitHubGive your agents full access to GitHub.](/integrations/github/)[Discord + NotionGive your agents full access to Notion.](/integrations/notion/) Use cases ## Where Discord agents fit [MarketingCommunity monitoringA workflow sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space. It picks the threads worth a reply and brings them to your team.Every 4 hours![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/community-monitoring/) FAQ ## Questions, answered ### How do I connect Discord? ### What can an agent reach in Discord? ### Can a Discord message trigger an agent? ### Can I limit which channels the agent sees? ### Does Discord access cost extra? ## Put an agent on Discord. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Docusign Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/docusign Description: Agents can send documents and templates for signature, check unsigned envelopes, and download completed agreements. With Docusign triggers, an agent starts when an envelope or recipient changes, a template is saved, an elastic template is accepted, or a workflow finishes. [← All integrations](/integrations/) Sales & CRM ![](/static/img/assets/docusign-light.svg)![](/static/img/assets/docusign-dark.svg) # Send documents for signature and respond to Docusign events. Agents can send documents and templates for signature, check unsigned envelopes, and download completed agreements. With Docusign triggers, an agent starts when an envelope or recipient changes, a template is saved, an elastic template is accepted, or a workflow finishes. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Docusign eSignature, Click, Admin, Rooms, Workspaces, Web Forms, Workflow Builder, Agreement Manager, Connected Fields, and Monitor APIs The full surface, searched at run time. Connect with * Your own OAuth app Use an app from your Docusign account, with either a JWT grant or a sign-in. Add a Connect HMAC key for Connect events. Event triggers Yes · 5 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/docusign/) What the agent can do ## What agents do with Docusign Helios searches the Docusign eSignature, Click, Admin, Rooms, Workspaces, Web Forms, Workflow Builder, Agreement Manager, Connected Fields, and Monitor APIs at run time. The agent finds the endpoint the task needs and calls it. * Call Docusign APIs with the connected user's permissions and the products enabled on the account. * Send documents and templates for signature, with recipients, routing order, and custom fields. * Check envelope status, see which recipients still have to sign, and download the signed documents. * Resend envelopes, correct recipients, and void envelopes that went out by mistake. * Manage templates, elastic templates, rooms, workspaces, and web forms, and start Workflow Builder workflows. * With Admin access, manage the users, groups, and permission profiles of your Docusign organization. * Start a run on supported Docusign Connect events, such as an envelope being sent or completed, a recipient signing, or a template changing. Examples ## Tasks you can hand to a Docusign agent ### Record every signed contract When an envelope completes, the agent marks the deal won and tells the team who signed. docusign · envelope.completed When an order form is fully signed, mark the deal won and tell #sales. 1. docusign·read the envelope, recipients, and custom fields 2. attio·find the deal by its record ID 3. attio·set the stage to Won 4. slack·post the signers and signing date to #sales ✓Acme order form recorded * Deal moved to Won with the signing date * Signed by the customer and countersigned by finance ### Chase unsigned envelopes A scheduled agent finds envelopes that have waited too long, resends them, and reports who is holding them up. Weekdays at 9:00am Every morning, resend envelopes that have waited more than three days and list them in Slack. 1. docusign·list envelopes sent more than three days ago 2. docusign·resend the ones still waiting for a signer 3. slack·post the list to #deal-desk ✓4 envelopes resent * 2 waiting on the customer's legal team * 1 waiting on our countersign * 1 sent to an address that bounced ### Send an agreement on request Ask for an NDA or order form in plain words, and the agent fills the template's roles and sends it. Run on demand Send our mutual NDA to jane@acme.com and copy legal. 1. docusign·find the Mutual NDA template 2. docusign·fill the signer and copy roles and send ✓NDA sent to Jane Doe * Signer: jane@acme.com * Copy: legal@example.com ### Follow up on a declined envelope When a recipient declines, the agent reads the reason and tells the owner what to fix. docusign · envelope.declined When a contract is declined, send the reason to the owner in Slack. 1. docusign·read the envelope and the decline reason 2. slack·message the sender ✓Owner told about the decline * Reason: the payment terms should be net 45 Event triggers ## Start a run on Docusign events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ------------------- | --------------------------------------------------------------------------------------- | | envelope.completed | Every recipient has signed, so an agent can record the agreement and update the deal. | | envelope.declined | A recipient declined to sign, so an agent can tell the owner and capture the reason. | | envelope.voided | The sender voided an envelope. Filter on the subject to watch one kind of agreement. | | recipient.completed | One recipient finished their part, such as the customer signing before the countersign. | | envelope.sent | An envelope went out, so an agent can log it against the right record. | Works with ## Docusign works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Docusign + AttioGive your agents full access to Attio.](/integrations/attio/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Docusign + SlackGive your agents full access to Slack.](/integrations/slack/)[![](/static/img/assets/gmail-light.svg)![](/static/img/assets/gmail-dark.svg)Docusign + GmailGive your agents full access to Gmail.](/integrations/gmail/) FAQ ## Questions, answered ### How do I connect Docusign? ### Which Docusign events can trigger an agent? ### What do triggers need? ### Does it work with a production account? ### Does Docusign cost extra? ## Put an agent on Docusign. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Dropbox Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/dropbox Description: Agents find, read, and upload files, organize folders, share files and file requests, and manage a Dropbox team. Dropbox trigger events start an agent when a file lands in a folder or changes. [← All integrations](/integrations/) Docs & knowledge # Give your agents access to your Dropbox files. Agents find, read, and upload files, organize folders, share files and file requests, and manage a Dropbox team. Dropbox trigger events start an agent when a file lands in a folder or changes. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Dropbox API v2 and Content Processing API The full surface, searched at run time. Connect with * Your own OAuth app Create a scoped app in the Dropbox App Console, or a team app that a team admin approves for the whole team. For triggers, add the Helios webhook URL to the app. Event triggers Yes · 5 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/dropbox/) What the agent can do ## What agents do with Dropbox Helios searches the Dropbox API v2 and Content Processing API at run time. The agent finds the endpoint the task needs and calls it. * Call Dropbox endpoints allowed by your app's scopes, including uploads and downloads. * Search files and folders, and read their versions, tags, and properties. * Download files to read, parse, and summarize them, and upload the results. * Create folders, and move, copy, rename, tag, lock, and delete files and folders. * Create shared links, share folders, and create file requests for the files a task touches. * With a team app, manage members, groups, and team folders, and read the team's activity log. Examples ## Tasks you can hand to a Dropbox agent ### Process files added to a folder When a file arrives in a watched folder, the agent reads it, pulls out what matters, and records it where the team works. dropbox · file.created When an invoice lands in /Invoices, extract the vendor, amount, and due date and add a row to the tracker. 1. dropbox·download the new invoice 2. code·extract the vendor, amount, and due date 3. google-sheets·append a row to the invoice tracker ✓Invoice from Northwind recorded * $4,820.00 due on November 14 * Added to the invoice tracker ### Summarize a folder of documents The agent reads documents in a folder and posts a summary where the team works. Summarize the contracts in /Legal/2026 and post the summary to #legal. 1. dropbox·list 12 files in /Legal/2026 2. dropbox·download each contract 3. code·summarize terms and renewal dates 4. slack·post the summary to #legal ✓Summary posted * 3 contracts renew in the next 60 days * 2 have no termination clause ### Set up new client folders When someone creates a client folder, the agent adds the standard subfolders and a file request for the client's documents. dropbox · folder.created When a folder is created under /Clients, add the standard subfolders and a file request for onboarding documents. 1. dropbox·create Contracts and Invoices 2. dropbox·create a file request 3. slack·post the request link ✓Acme folder ready * Two subfolders created * File request link posted to #onboarding Event triggers ## Start a run on Dropbox events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | -------------------- | --------------------------------------------------------------------------- | | file.created | A file is added. Filter by path, such as every PDF in an Invoices folder. | | file.updated | A new version of a file is saved, so an agent can review what changed. | | folder.created | A folder is created, so an agent can set it up for a new client or project. | | item.deleted | A file or folder is deleted or moved away. | | team\_member.changed | A team member is invited, joins, is removed, or changes. Team apps only. | Works with ## Dropbox works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/google-sheets-light.svg)![](/static/img/assets/google-sheets-dark.svg)Dropbox + Google SheetsGive your agents full access to Google Sheets.](/integrations/google-sheets/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Dropbox + SlackGive your agents full access to Slack.](/integrations/slack/)[Dropbox + NotionGive your agents full access to Notion.](/integrations/notion/) FAQ ## Questions, answered ### How do I connect Dropbox? ### What can an agent reach in Dropbox? ### Can an agent upload files to Dropbox? ### Which Dropbox events can trigger an agent? ## Put an agent on Dropbox. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Figma Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/figma Description: Agents read file content, inspect libraries, manage comments and follow design changes through the Figma REST API. [← All integrations](/integrations/) Design ![](/static/img/assets/figma-light.svg)![](/static/img/assets/figma-dark.svg) # Connect designs and comments to your workflows. Agents read file content, inspect libraries, manage comments and follow design changes through the Figma REST API. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Figma REST API The full surface, searched at run time. Connect with * API key * Your own OAuth app Use a personal access token or your own OAuth app. Team webhooks require Professional or higher and team admin access. Event triggers Yes · 6 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/figma/) What the agent can do ## What agents do with Figma Helios searches the Figma REST API at run time. The agent finds the endpoint the task needs and calls it. * Read file content and version history. * Post comments and manage dev resources. * Inspect published components, styles and variables. * Request rendered image URLs and download the images. Examples ## Tasks you can hand to a Figma agent Event triggers ## Start a run on Figma events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ------------------------- | ----------------------------------- | | file.updated | A file changes after editing stops. | | file.deleted | A file is deleted. | | file\_version.created | A named version is created. | | library.published | Library assets are published. | | comment.created | A file receives a comment. | | dev\_mode\_status.updated | A node's Dev Mode status changes. | Works with ## Figma works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Figma + SlackGive your agents full access to Slack.](/integrations/slack/)[Figma + GitHubGive your agents full access to GitHub.](/integrations/github/) FAQ ## Questions, answered ### Can I use a Starter plan? ## Put an agent on Figma. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # GitHub Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/github Description: Agents read repositories, review pull requests, triage issues, ship releases, and watch CI - using the whole GitHub REST API. Pair it with GitHub trigger events and an agent picks up work the moment a PR opens or a workflow finishes. [← All integrations](/integrations/) Developer tools # Give your agents full access to GitHub. Agents read repositories, review pull requests, triage issues, ship releases, and watch CI - using the whole GitHub REST API. Pair it with GitHub trigger events and an agent picks up work the moment a PR opens or a workflow finishes. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach GitHub REST API The full surface, searched at run time. Connect with * Helios OAuth app * Your own OAuth app * API key Organization installs also ask each person to authorize once, so the agent acts as that person. Event triggers Yes · 12 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/github/) What the agent can do ## What agents do with GitHub Helios searches the GitHub REST API at run time. The agent finds the endpoint the task needs and calls it. * Search the entire GitHub OpenAPI surface at run time and call any endpoint the task requires. * Read and write pull requests: diffs, files changed, reviews, review comments, merges, labels. * Manage issues end to end - open, comment, label, assign, close, and cross-link. * Inspect repository contents, branches, tags, commits, and blame at any ref. * Read Actions workflow runs, jobs, and logs to explain a failure in plain English. * Cut releases and tags, and compose release notes from merged commits. Examples ## Tasks you can hand to a GitHub agent ### Review every pull request as it opens An agent reads the diff, checks it against your conventions, and leaves a review with concrete suggestions before a human opens the tab. github · pull\_request.opened Review new pull requests against our engineering conventions and leave inline comments. 1. github·fetch diff for PR #2841 2. github·read CONTRIBUTING.md and recent reviews 3. code·run analysis over changed files 4. github·post review with 3 inline comments ✓Review posted on PR #2841 * Flagged an unhandled error path in \`sync.ts:142\` * Suggested reusing \`parseCursor\` instead of a second parser * Confirmed migration is backward compatible ### Explain a failing CI run When a workflow run finishes red, the agent pulls the logs, finds the first real failure, and posts a plain-English explanation with the likely fix. github · workflow\_run.completed When CI fails on main, explain the failure and suggest a fix. 1. github·fetch failed jobs for run 91422 2. github·download step logs 3. code·isolate first failing assertion 4. slack·post summary to #eng-alerts ✓CI failure explained * \`billing.spec.ts\` timed out waiting on a Stripe mock * Introduced by #2833, which changed the fixture loader * Suggested fix: await \`seedFixtures()\` before the test body ### Triage and route new issues Every incoming issue gets read, labeled, deduplicated against existing issues, and routed to the team that owns the area. github · issues.opened Triage new issues: label them, find duplicates, and assign an owner. 1. github·read issue #1180 body and attachments 2. github·search open issues for duplicates 3. github·apply labels: \`area/auth\`, \`bug\` 4. github·assign to @auth-team and comment ✓Issue #1180 triaged * Labeled \`area/auth\` · \`bug\` · \`needs-repro\` * Linked to #1042 as a likely duplicate * Assigned to the auth team ### Draft release notes from merged work On every tag, the agent walks the commits since the last release, groups them by theme, and writes notes your users can read. github · tag.created When a tag is created, draft release notes grouped by theme. 1. github·compare v2.7.0...v2.8.0 2. github·read merged PR titles and bodies 3. github·publish draft release v2.8.0 ✓Draft release v2.8.0 * Features - 6 entries, led by scheduled exports * Fixes - 11 entries, grouped by area * Breaking - 1 entry, with a migration snippet ### Answer questions about the codebase Point an agent at a repository as a pinned resource and hand it questions. It reads real files at the ref you name. Where do we validate webhook signatures, and which routes skip it? 1. github·search repo for signature verification 2. github·read \`middleware/verify.ts\` at \`main\` 3. code·trace route registrations ✓Answer with citations * Verification lives in \`middleware/verify.ts:31\` * Applied to every \`/hooks/\*\` route * \`/hooks/health\` opts out via \`skipVerify\` ### Keep a weekly engineering digest A scheduled agent summarizes merged work, open review load, and CI health, then posts it where the team already reads. Fridays at 4:00pm Every Friday, summarize merged PRs, review backlog, and CI health. 1. github·list PRs merged in the last 7 days 2. github·list open PRs awaiting review 3. github·aggregate Actions run outcomes 4. slack·post digest to #engineering ✓Week of Mar 3 * 38 PRs merged · median review time 6h * 5 PRs waiting more than 3 days * CI pass rate 94%, down from 97% Event triggers ## Start a run on GitHub events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ------------------------- | ------------------------------------------------------------------------------------ | | pull\_request.opened | A pull request is opened. Filter by base branch, author, or labels. | | pull\_request.closed | A pull request is closed or merged, so agents can follow up on shipped work. | | pull\_request.synchronize | New commits land on an open pull request and the review needs a refresh. | | pull\_request.labeled | A label lands on a pull request - the usual way to opt a PR into an agent. | | issues.opened | A new issue arrives, ready for triage, labeling, and routing. | | issues.closed | An issue closes, so the agent can update a changelog or notify the reporter. | | issues.labeled | A label lands on an issue. Filter on the label name to scope the agent. | | push | Commits land on a branch. Filter by branch so only \`main\` wakes the agent. | | tag.created | A tag is created - the signal to draft release notes or start a rollout check. | | release.published | A release goes out, and the agent announces it to the channels you name. | | workflow\_run.completed | A GitHub Actions run finishes. Filter on conclusion to catch only failures. | | issue\_comment.created | Someone comments on an issue or pull request, including \`@mentions\` of your agent. | Works with ## GitHub works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)GitHub + SlackGive your agents full access to Slack.](/integrations/slack/)[GitHub + NotionGive your agents full access to Notion.](/integrations/notion/)[![](/static/img/assets/warpbuild-light.svg)![](/static/img/assets/warpbuild-dark.svg)GitHub + WarpBuildGive your agents full access to WarpBuild.](/integrations/warpbuild/) Templates ## Ready-to-run GitHub workflows Copy the prompt, connect your tools, and start a run. [EngineeringPull request reviewerReviews every pull request against your conventions and leaves inline comments only where it found something concrete.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/pr-review-digest/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes a draft release on GitHub, and files a changelog entry in Notion.github · tag.created![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/github-release-notes/)[EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup to Slack every weekday morning.Weekdays at 9:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/daily-standup-digest/)[EngineeringIncident postmortem drafterRebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/incident-postmortem-drafter/)[SupportDocumentation freshness auditChecks your written docs against the codebase every month and comments on the pages that have gone stale.Monthly on the 1st![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/notion-docs-freshness-audit/) Use cases ## Where GitHub agents fit [EngineeringPull request reviewA workflow reads each diff against your conventions and leaves a real review. A second workflow on a schedule posts the week's merged work, review backlog, and CI health.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/pr-review-digest/)[EngineeringIncident summariesA workflow rebuilds the timeline from your incident channel and the deploys around it. It names the likely change and drafts the write-up with the facts in place.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/incident-summaries/)[MarketingCommunity monitoringA workflow sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space. It picks the threads worth a reply and brings them to your team.Every 4 hours![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/community-monitoring/) FAQ ## Questions, answered ### How do I connect GitHub? ### What can an agent actually reach in GitHub? ### Which GitHub events can trigger an agent? ### Where do the credentials live? ### Does the GitHub integration cost extra? ## Put an agent on GitHub. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # GitLab Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/gitlab Description: Agents review merge requests, triage issues, and explain failed pipelines from their job logs, using the GitLab REST API on GitLab.com or your own instance. GitLab trigger events start an agent on pushes, merge requests, issues, comments, pipelines, jobs, deployments, releases, and other GitLab events. [← All integrations](/integrations/) Developer tools # Connect agents to GitLab projects and events. Agents review merge requests, triage issues, and explain failed pipelines from their job logs, using the GitLab REST API on GitLab.com or your own instance. GitLab trigger events start an agent on pushes, merge requests, issues, comments, pipelines, jobs, deployments, releases, and other GitLab events. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach GitLab REST API The full surface, searched at run time. Connect with * API key * Your own OAuth app Connect with an access token that has the api scope, or with your own GitLab OAuth app that has the api and mcp scopes. Helios adds the webhook for trigger events to projects where the token has the Maintainer role, and to a group you name where it has the Owner role. GitLab Self-Managed works too, and its triggers need GitLab 19.0 or later. Event triggers Yes · 5 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/gitlab/) What the agent can do ## What agents do with GitLab Helios searches the GitLab REST API at run time. The agent finds the endpoint the task needs and calls it. * Call GitLab REST API endpoints with your connection's permissions. * Open merge requests, read their diffs, and leave review comments. * Create, label, and close issues, and reply in their threads. * Read pipeline and job status, fetch a failed job's log, and retry jobs. * Read files, branches, tags, and commits at any ref, and download job artifacts. * Start a run on pushes and tags, merge request and issue changes, comments, pipeline and job status, deployments, releases, and group membership changes. Examples ## Tasks you can hand to a GitLab agent ### Review every new merge request The agent reads the diff, checks it against the project's conventions, and leaves a review comment for a person to review. gitlab · merge\_request.opened On each new merge request into main: review the diff and comment with findings. 1. gitlab·read the merge request and diff 2. gitlab·read CONTRIBUTING.md and related files 3. code·check the changed functions 4. gitlab·post a review comment ✓Reviewed !318 * One missing null check in the invoice parser * New endpoint has no test * Naming matches the project's conventions ### Explain a failed pipeline When a pipeline on main fails, the agent reads the failed job's log, compares recent changes, and files an issue with its findings. gitlab · pipeline.updated When a pipeline on main fails, find the cause and open an issue. 1. gitlab·list the pipeline's failed jobs 2. gitlab·read the job log 3. gitlab·compare with the last passing commit 4. gitlab·open an issue with the cause ✓Issue #904 opened * test:unit failed on a timezone assertion * Introduced by the commit that changed the date helper * Assigned to that commit's author ### Answer questions in comments When someone asks the agent a question on a merge request or issue, it looks up the answer and replies in the thread. gitlab · comment.created When a comment mentions the agent, answer on the same merge request or issue. 1. gitlab·read the comment and the thread 2. gitlab·search the code it asks about 3. gitlab·reply in the thread ✓Replied on !322 * The retry limit is set in config/jobs.yml * It applies to every queue except billing ### Weekly merge request digest A scheduled agent lists what merged and what is waiting for review, and posts the summary to the team. Mondays at 9:00am Every Monday, summarize last week's merge requests and post them to Slack. 1. gitlab·list merged and open merge requests 2. code·group by project and author 3. slack·post the digest to #engineering ✓Week 40 digest * 27 merge requests merged across 4 projects * 6 waiting for review for more than 2 days Event triggers ## Start a run on GitLab events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | --------------------- | ------------------------------------------------------------------------------------------------------------- | | merge\_request.opened | A merge request is opened. Filter by project, target branch, or labels. | | merge\_request.merged | A merge request is merged - the moment to update docs, changelogs, or tickets. | | issue.opened | A new issue is opened. Filter by project or labels to triage it. | | pipeline.updated | A pipeline's status changes. Filter on the failed status and a branch to watch only main or release branches. | | comment.created | Someone comments on a merge request, issue, commit, or snippet. | Works with ## GitLab works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [GitLab + GitHubGive your agents full access to GitHub.](/integrations/github/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)GitLab + SlackGive your agents full access to Slack.](/integrations/slack/) FAQ ## Questions, answered ### How do I connect GitLab? ### What can an agent reach in GitLab? ### Which GitLab events can trigger an agent? ### Why does the token need the Maintainer role? ### Does GitLab cost extra? ## Put an agent on GitLab. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Gmail Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/gmail Description: Agents read the inbox, follow threads, draft replies in your voice, apply labels, and send when you tell them to. Put one on a schedule and the inbox is triaged before you open it. [← All integrations](/integrations/) Google Workspace ![](/static/img/assets/gmail-light.svg)![](/static/img/assets/gmail-dark.svg) # Give your agents full access to Gmail. Agents read the inbox, follow threads, draft replies in your voice, apply labels, and send when you tell them to. Put one on a schedule and the inbox is triaged before you open it. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Gmail API v1 The full surface, searched at run time. Connect with * Helios OAuth app * Your own OAuth app Event triggers Not yet Manual, schedule, and signed webhook are available. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/google-gmail/) What the agent can do ## What agents do with Gmail Helios searches the Gmail API v1 at run time. The agent finds the endpoint the task needs and calls it. * Search Gmail's entire API surface at run time and call any endpoint your scopes allow. * Search and read messages and threads with Gmail's full query syntax. * Compose drafts, reply in thread, and send when the task calls for it. * Apply and manage labels, archive, and mark read to shape the inbox. * Read attachments into the sandbox and analyze them with code. * Combine with a CRM so every reply carries account context. Examples ## Tasks you can hand to a Gmail agent ### Triage the inbox before you open it A morning agent reads what arrived overnight, labels it, drafts replies to the easy ones, and hands you a short list of what needs a human. Weekdays at 7:30am Every morning, triage overnight mail: label it, draft the easy replies, list what needs me. 1. gmail·search \`newer\_than:1d -in:chats\` 2. gmail·apply labels by topic 3. gmail·create 4 draft replies 4. slack·DM me the needs-a-human list ✓31 messages triaged * 4 drafts ready to review and send * 22 labeled and archived * 5 flagged for you, ranked by urgency ### Turn inbound interest into CRM records When a prospect writes in, the agent enriches the sender, creates or updates the CRM record, and files the thread against it. Every 30 minutes For inbound sales mail, enrich the sender and create the CRM record. 1. gmail·search label:inbound-sales is:unread 2. apollo·enrich sender by email domain 3. attio·upsert person and company records 4. gmail·label thread \`crm-synced\` ✓6 inbound leads captured * 6 companies enriched with size, industry, and funding * 2 matched existing accounts and were merged * Owners assigned by territory ### Chase the threads that went quiet The agent finds conversations that stalled after your last message and drafts a follow-up that references what was actually discussed. Tuesdays at 9:00am Find threads where I sent the last message 5+ days ago and draft a follow-up. 1. gmail·search sent threads with no reply 2. gmail·read each thread for context 3. gmail·draft 7 follow-ups in thread ✓7 follow-ups drafted * Each references the last concrete next step * 3 include the pricing page they asked for * All waiting in Drafts for your review ### Extract data from attachments Invoices, reports, and spreadsheets land in the inbox. The agent opens them in its sandbox, pulls the numbers, and writes them where you keep them. Weekly on Monday Pull totals from vendor invoices in my inbox into the finance sheet. 1. gmail·fetch attachments from label:invoices 2. code·parse 9 PDFs and extract totals 3. google-sheets·append rows to Vendor Spend ✓9 invoices processed * $41,208 total added for March * 1 invoice flagged: amount differs from the PO Triggers ## How a Gmail workflow starts Gmail does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook. ### Manual Run it from the app with an optional JSON payload. Every workflow supports this. ### Schedule A cron expression or a plain sentence such as every weekday at 9am. Times are UTC. ### Signed webhook A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes. Works with ## Gmail works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/google-sheets-light.svg)![](/static/img/assets/google-sheets-dark.svg)Gmail + Google SheetsGive your agents full access to Google Sheets.](/integrations/google-sheets/)[![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Gmail + AttioGive your agents full access to Attio.](/integrations/attio/)[![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)Gmail + ResendGive your agents full access to Resend.](/integrations/resend/) FAQ ## Questions, answered ### How do I connect Gmail? ### What can an agent reach in Gmail? ### Can new mail trigger an agent? ### Will an agent send mail on its own? ### Is my mail used to train models? ## Put an agent on Gmail. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Google Calendar Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/google-calendar Description: Agents schedule meetings, read the agenda, find free time, move or cancel events, and manage and share calendars. Calendar triggers start an agent when events or sharing change on the calendars you choose, or when your calendar list or settings change. [← All integrations](/integrations/) Google Workspace # Give your agents access to your Google Calendar. Agents schedule meetings, read the agenda, find free time, move or cancel events, and manage and share calendars. Calendar triggers start an agent when events or sharing change on the calendars you choose, or when your calendar list or settings change. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Google Calendar API v3 The full surface, searched at run time. Connect with * Helios OAuth app * Your own OAuth app Your own OAuth app is a Web application client in your Google Cloud project, with the Google Calendar API turned on. Publish an External app, because Google expires refresh tokens after 7 days in Testing. Event triggers Yes · 6 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/google-calendar/) What the agent can do ## What agents do with Google Calendar Helios searches the Google Calendar API v3 at run time. The agent finds the endpoint the task needs and calls it. * Call the Google Calendar API with the access granted by your connected account. * Create events with guests, a description, and a Google Meet link. * List the agenda for a day or a week across your calendars. * Check availability with the free/busy API before booking a slot. * Reschedule or cancel events, and choose whether guests are notified. * Create calendars, share them, and change who can see or edit them. * Start a run when an event, a calendar's sharing, your calendar list, or a setting changes. Examples ## Tasks you can hand to a Google Calendar agent ### Check meeting availability Ask an agent to check free/busy information for calendars your account can access before creating an event. Check whether my team calendar is free tomorrow at 10am. 1. google-calendar·query free/busy for the team calendar ✓Availability checked * The team calendar is free at 10am. ### Read the day's agenda Ask an agent to list today's events across your calendars. Show me today's agenda. 1. google-calendar·list today's events ✓Today's agenda * 10am: Team meeting * 2pm: Design review Event triggers ## Start a run on Google Calendar events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | --------------------------- | --------------------------------------------------------------------------------------------------- | | event.created | An event is created on a watched calendar. | | event.updated | An event changes. Filter on the title, the organizer, or your own response. | | event.cancelled | An event on a watched calendar is cancelled or deleted. | | acl\_rule.created | A watched calendar is shared with someone. Filter on who it is shared with and the access it gives. | | calendar\_list\_entry.added | A calendar is added to your calendar list, such as a team calendar you subscribe to. | | setting.updated | One of your Google Calendar settings changes, such as your time zone. | Works with ## Google Calendar works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/gmail-light.svg)![](/static/img/assets/gmail-dark.svg)Google Calendar + GmailGive your agents full access to Gmail.](/integrations/gmail/)[![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)Google Calendar + Google DocsGive your agents full access to Google Docs.](/integrations/google-docs/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Google Calendar + SlackGive your agents full access to Slack.](/integrations/slack/) FAQ ## Questions, answered ### How do I connect Google Calendar? ### Which calendars can trigger an agent? ### Which events can trigger an agent? ### Can agents send event invitations? ## Put an agent on Google Calendar. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Google Docs Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/google-docs Description: Agents draft, edit, and read documents where your team writes. Hand an agent a research task and it comes back with a real doc - sourced, structured, and shared with the people who need it. [← All integrations](/integrations/) Google Workspace ![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg) # Give your agents full access to Google Docs. Agents draft, edit, and read documents where your team writes. Hand an agent a research task and it comes back with a real doc - sourced, structured, and shared with the people who need it. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Google Docs API v1 The full surface, searched at run time. Connect with * Helios OAuth app * Your own OAuth app Event triggers Not yet Manual, schedule, and signed webhook are available. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/google-docs/) What the agent can do ## What agents do with Google Docs Helios searches the Google Docs API v1 at run time. The agent finds the endpoint the task needs and calls it. * Search the Docs API surface at run time and call any endpoint your scopes allow. * Create documents and write structured content with headings, lists, and tables. * Read existing documents as context for research, drafts, and summaries. * Apply batch edits: insert, replace, and restructure sections. * Combine with web search and scraping to draft from live sources. * Save drafts to a Drive folder and share them with the right people. Examples ## Tasks you can hand to a Google Docs agent ### Draft a research brief from live sources Give the agent a topic. It searches the web, reads what it finds, and writes a sourced brief into a new document. Research the SOC 2 audit process for a Series A startup and write me a brief. 1. web·search and read 14 sources 2. code·outline and cluster findings 3. google-docs·create \`SOC 2 Brief\` with citations 4. google-drive·share with the ops folder ✓\`SOC 2 Brief\` created * 1,900 words across 5 sections * Every claim linked to a source * Timeline and cost table included ### Turn a rough outline into a first draft The agent reads your bullet points and your existing docs for voice, then writes a draft that already sounds like you. Expand the outline in \`Q2 Launch Plan\` into a full draft in our voice. 1. google-docs·read outline and 3 prior plans 2. google-docs·write expanded draft in place ✓Draft expanded * 6 sections written from 22 bullets * Matched the structure of prior launch plans * Open questions left as inline comments ### Summarize a long document for the team The agent reads a dense doc, writes a one-page summary with the decisions and owners, and posts it where people will see it. Summarize the architecture RFC into one page and post it to Slack. 1. google-docs·read \`Storage RFC\` (11k words) 2. google-docs·create one-page summary doc 3. slack·post summary to #engineering ✓RFC summarized * 3 proposals compared on cost and latency * Recommendation and its two risks * 4 open questions with owners ### Keep a living document current A scheduled agent refreshes the sections that go stale - metrics, roadmap status, open risks - and leaves the prose alone. Mondays at 7:00am Every Monday, refresh the metrics and status sections of the board update. 1. postgres·query current metrics 2. github·read roadmap milestone progress 3. google-docs·replace metrics and status sections ✓Board update refreshed * Metrics table rebuilt from the warehouse * Roadmap status pulled from 4 milestones * Narrative sections left untouched Triggers ## How a Google Docs workflow starts Google Docs does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook. ### Manual Run it from the app with an optional JSON payload. Every workflow supports this. ### Schedule A cron expression or a plain sentence such as every weekday at 9am. Times are UTC. ### Signed webhook A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes. Works with ## Google Docs works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [Google Docs + Google DriveGive your agents access to Google Drive.](/integrations/google-drive/)[Google Docs + NotionGive your agents full access to Notion.](/integrations/notion/)[![](/static/img/assets/apify.svg)Google Docs + ApifyGive your agents full access to Apify.](/integrations/apify/) Templates ## Ready-to-run Google Docs workflows Copy the prompt, connect your tools, and start a run. [MarketingResearch brief writerResearches a topic across the live web and returns a sourced draft in your voice, with the open questions flagged.Run on demand![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)![](/static/img/assets/apify.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/google-docs-brief-writer/) Use cases ## Where Google Docs agents fit [MarketingResearch briefsA workflow searches the web, reads what it finds, and writes a draft with every claim linked to its source. Give it your prior work and the draft matches your voice.Run on demand![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)![](/static/img/assets/apify.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/content-pipeline/) FAQ ## Questions, answered ### How do I connect Google Docs? ### What can an agent reach in Docs? ### Can a document edit trigger an agent? ### Will the agent overwrite my writing? ### Does this integration cost extra? ## Put an agent on Google Docs. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Google Drive Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/google-drive Description: Agents find files, read text files and exported Docs, Sheets and Slides, organize folders, and audit sharing. They write text results, such as a report or a CSV export, back to Drive. Drive triggers start an agent when files, folders or shared drives change. [← All integrations](/integrations/) Google Workspace # Give your agents access to Google Drive. Agents find files, read text files and exported Docs, Sheets and Slides, organize folders, and audit sharing. They write text results, such as a report or a CSV export, back to Drive. Drive triggers start an agent when files, folders or shared drives change. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Google Drive API v3 The full surface, searched at run time. Connect with * Helios OAuth app * Your own OAuth app Event triggers Yes · 8 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/google-drive/) What the agent can do ## What agents do with Google Drive Helios searches the Google Drive API v3 at run time. The agent finds the endpoint the task needs and calls it. * Use Drive API operations within the permissions you grant. * Search files and folders with Drive's full query syntax. * Read text files, and export Docs, Sheets and Slides as text or CSV to analyze with code. * Create folders, move files, rename, and organize by content. * Upload text results, such as reports and CSV exports, back to Drive. * Read sharing permissions, and change them on files the agent created. * Start a run when a file or folder is created, changed, trashed, restored or removed, or when a shared drive changes. Examples ## Tasks you can hand to a Google Drive agent ### Organize a folder that got out of hand The agent reads file names, types and the text of documents, proposes a folder structure, and files everything where it belongs. Organize the \`Shared Uploads\` folder by content and tell me what you did. 1. google-drive·list 340 files in \`Shared Uploads\` 2. code·classify by content and date 3. google-drive·create folders and move files 4. slack·post the summary to #ops ✓340 files organized * 7 folders created by document type * 22 near-duplicates grouped for review * Nothing deleted ### Audit who has access to what A scheduled agent sweeps a folder for files shared beyond your domain and reports each one with its sharing settings. Sundays at 8:00pm Weekly, flag any file in \`Finance\` shared outside the company. 1. google-drive·list files and permissions in \`Finance\` 2. code·filter external and link-shared files 3. slack·DM the finance lead ✓3 files shared externally * 1 open to anyone with the link * 2 shared with a former contractor * Suggested revocations listed ### Extract data from a pile of documents Point the agent at a folder of contracts or reports in Google Docs. It exports each one as text, pulls the fields you name, and writes a table. Read every contract in \`Vendor Agreements\` and build a renewal table. 1. google-drive·export 28 Google Docs as text 2. code·extract term, renewal date, and value 3. google-sheets·write \`Vendor Renewals\` ✓28 contracts parsed * 4 renew within 60 days * $310k total annual commitment * 2 contracts missing a stated term ### Deliver reports where people look for them Whatever an agent produces - a cleaned export, a monthly report, a scraped dataset - lands in the right Drive folder automatically. Monthly on the 1st On the 1st, generate the monthly report and file it in Drive. 1. clickhouse·query last month's usage 2. code·render the report as CSV 3. google-drive·upload to \`Reports/2025\` ✓March report filed * Uploaded to \`Reports/2025/March.csv\` * Shared with the leadership group Event triggers ## Start a run on Google Drive events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | --------------------- | ------------------------------------------------------------------------------------------------------------------- | | file.created | A file or folder is created, uploaded or copied. Filter on the name, the MIME type, the folder or the shared drive. | | file.updated | A file or folder changes, such as its content, its name, its folder or its sharing. | | file.trashed | A file or folder is moved to the trash. | | file.untrashed | A file or folder is restored from the trash. | | file.removed | A file or folder is deleted permanently, or the account loses access to it. | | shared\_drive.added | You're added to a shared drive, or you create one. | | shared\_drive.updated | A shared drive changes, such as its name or its settings. | | shared\_drive.removed | A shared drive is deleted, or you're removed from it. | Works with ## Google Drive works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)Google Drive + Google DocsGive your agents full access to Google Docs.](/integrations/google-docs/)[![](/static/img/assets/google-sheets-light.svg)![](/static/img/assets/google-sheets-dark.svg)Google Drive + Google SheetsGive your agents full access to Google Sheets.](/integrations/google-sheets/)[![](/static/img/assets/gmail-light.svg)![](/static/img/assets/gmail-dark.svg)Google Drive + GmailGive your agents full access to Gmail.](/integrations/gmail/) Templates ## Ready-to-run Google Drive workflows Copy the prompt, connect your tools, and start a run. [MarketingResearch brief writerResearches a topic across the live web and returns a sourced draft in your voice, with the open questions flagged.Run on demand![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)![](/static/img/assets/apify.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/google-docs-brief-writer/) FAQ ## Questions, answered ### How do I connect Google Drive? ### What can an agent reach in Drive? ### Can a new file in Drive trigger an agent? ### What happens to files the agent downloads? ### Does Drive access cost extra? ## Put an agent on Google Drive. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Google Sheets Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/google-sheets Description: Agents read ranges, write rows, reshape tabs, and turn a spreadsheet into the place your numbers land. Because each agent has a real computer, it can pull from a database, run the analysis in code, and write the finished table. [← All integrations](/integrations/) Google Workspace ![](/static/img/assets/google-sheets-light.svg)![](/static/img/assets/google-sheets-dark.svg) # Give your agents full access to Google Sheets. Agents read ranges, write rows, reshape tabs, and turn a spreadsheet into the place your numbers land. Because each agent has a real computer, it can pull from a database, run the analysis in code, and write the finished table. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Google Sheets API v4 The full surface, searched at run time. Connect with * Helios OAuth app * Your own OAuth app Event triggers Not yet Manual, schedule, and signed webhook are available. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/google-sheets/) What the agent can do ## What agents do with Google Sheets Helios searches the Google Sheets API v4 at run time. The agent finds the endpoint the task needs and calls it. * Search the Sheets API surface at run time and call any endpoint your scopes allow. * Read ranges and whole sheets, with formulas or evaluated values. * Append rows, update ranges, and create or rename tabs. * Apply formatting, freeze headers, and add conditional formatting rules. * Combine with database access to move query results straight into a sheet. * Run analysis as code in the sandbox before writing results. Examples ## Tasks you can hand to a Google Sheets agent ### Keep a KPI sheet current Every morning the agent queries your warehouse, computes the metrics your team argues about, and writes them into the sheet leadership already opens. Daily at 6:00am Each morning, refresh the KPI tab from the warehouse. 1. postgres·query signups, activation, revenue 2. code·compute 7-day and 28-day trends 3. google-sheets·write KPI tab and refresh charts ✓KPI sheet updated * Signups 1,204 · up 8% week over week * Activation 41% · flat * Net revenue retention 112% ### Clean a messy import Point the agent at a tab of raw rows. It normalizes formats, deduplicates, flags what looks wrong, and writes a clean sheet next to it. Clean the \`Raw Leads\` tab: normalize names, dedupe, and flag bad emails. 1. google-sheets·read \`Raw Leads\` (2,140 rows) 2. code·normalize, dedupe, validate emails 3. google-sheets·write \`Clean Leads\` tab ✓2,140 rows in, 1,876 out * 211 duplicates merged * 53 invalid emails moved to a review tab * Company names title-cased and trimmed ### Turn a sheet into a work queue The agent reads rows marked ready, does the work each row describes, and writes the outcome back into the row it came from. Hourly For each row marked \`ready\`, enrich the company and write the result back. 1. google-sheets·read rows where status = ready 2. apollo·enrich 24 companies 3. google-sheets·write results and set status = done ✓24 rows processed * Headcount, industry, and funding filled in * 3 rows marked \`no-match\` for a human ### Reconcile two sources of truth The agent pulls both sides, diffs them, and writes a reconciliation tab that shows exactly where the numbers disagree. Monthly on the 1st Reconcile Stripe revenue against the finance sheet and show me the gaps. 1. stripe·list charges for last month 2. google-sheets·read \`Finance · March\` 3. code·diff by invoice id 4. google-sheets·write \`Reconciliation\` tab ✓4 discrepancies found * $1,240 in refunds missing from the sheet * 2 invoices recorded twice * Everything else matches to the cent Triggers ## How a Google Sheets workflow starts Google Sheets does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook. ### Manual Run it from the app with an optional JSON payload. Every workflow supports this. ### Schedule A cron expression or a plain sentence such as every weekday at 9am. Times are UTC. ### Signed webhook A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes. Works with ## Google Sheets works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [Google Sheets + DatabasesGive your agents full access to your databases.](/integrations/databases/)[Google Sheets + Google DriveGive your agents access to Google Drive.](/integrations/google-drive/)[Google Sheets + StripeGive your agents full access to Stripe.](/integrations/stripe/) FAQ ## Questions, answered ### How do I connect Google Sheets? ### What can an agent reach in Sheets? ### Can a sheet edit trigger an agent? ### How large a sheet can an agent handle? ### Who can see the data the agent reads? ## Put an agent on Google Sheets. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Granola Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/granola Description: Agents read Granola notes, summaries and transcripts. Note events can start workflows that extract action items or prepare follow-ups. [← All integrations](/integrations/) Docs & knowledge ![](/static/img/assets/granola-light.svg)![](/static/img/assets/granola-dark.svg) # Read meeting notes and act on new summaries. Agents read Granola notes, summaries and transcripts. Note events can start workflows that extract action items or prepare follow-ups. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Granola v1 API The full surface, searched at run time. Connect with * API key Use a personal or workspace API key on a Business or Enterprise plan. Event triggers Yes · 3 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/granola/) What the agent can do ## What agents do with Granola Helios searches the Granola v1 API at run time. The agent finds the endpoint the task needs and calls it. * Read notes, AI summaries and transcripts. * List folders and spaces. * Manage webhook endpoints. Examples ## Tasks you can hand to a Granola agent Event triggers ## Start a run on Granola events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | -------------------- | ---------------------------------------------- | | note.generated | A note's first AI summary is generated. | | note.edited | A summary is edited or regenerated. | | note.access\_granted | A note is shared directly or through a folder. | Works with ## Granola works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [Granola + NotionGive your agents full access to Notion.](/integrations/notion/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Granola + SlackGive your agents full access to Slack.](/integrations/slack/)[![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Granola + AttioGive your agents full access to Attio.](/integrations/attio/) FAQ ## Questions, answered ### Which notes can agents read? ### Can agents edit Granola notes? ## Put an agent on Granola. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Help Scout Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/help-scout Description: Agents search the Inbox API to read conversations, write replies and notes, manage customers, and retrieve reports. Webhook events can start support workflows. [← All integrations](/integrations/) Support ![](/static/img/assets/help-scout-light.svg)![](/static/img/assets/help-scout-dark.svg) # Act on customer conversations in Help Scout. Agents search the Inbox API to read conversations, write replies and notes, manage customers, and retrieve reports. Webhook events can start support workflows. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Help Scout Inbox API The full surface, searched at run time. Connect with * Your own OAuth app Connect your Help Scout OAuth app. App-only tokens are not supported. Event triggers Yes · 6 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/help-scout/) What the agent can do ## What agents do with Help Scout Helios searches the Help Scout Inbox API at run time. The agent finds the endpoint the task needs and calls it. * Read conversations and add replies or internal notes. * Manage customers, organizations, tags, and assignments. * Retrieve inbox and team reports. * Start workflows from conversation, customer, chat, rating, survey, organization, tag, and user status events. Examples ## Tasks you can hand to a Help Scout agent ### Triage new conversations Read the customer's message, find related context, and add a note for the support team. Help Scout conversation created Summarize new billing conversations for the support team. 1. help-scout·read the conversation and customer history 2. help-scout·add an internal note with the issue and next steps ✓Triage note added * Billing question summarized * Customer history linked for the support team Event triggers ## Start a run on Help Scout events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ---------------------------- | -------------------------------------------------------------------- | | convo.created | A conversation arrives. Filter by inbox, subject, tags, or customer. | | convo.assigned | A conversation is assigned. | | convo.status | A conversation changes status. | | convo.customer.reply.created | A customer replies to a conversation. | | satisfaction.ratings | A customer submits a satisfaction rating. | | beacon.chat.created | A Beacon chat starts. | Works with ## Help Scout works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Help Scout + SlackGive your agents full access to Slack.](/integrations/slack/)[Help Scout + GitHubGive your agents full access to GitHub.](/integrations/github/)[![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)Help Scout + PlainGive your agents full access to Plain.](/integrations/plain/) FAQ ## Questions, answered ### How do I connect Help Scout? ### Which events are available? ### Does this include the Docs API? ## Put an agent on Help Scout. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Hunter Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/hunter Description: Agents find and verify work email addresses, keep lead lists clean, and follow up on outreach. With Hunter triggers, an agent starts when an email from Hunter is sent, opened, clicked, or answered. [← All integrations](/integrations/) Sales & CRM ![](/static/img/assets/hunter-light.svg)![](/static/img/assets/hunter-dark.svg) # Find email addresses and manage outreach with Hunter. Agents find and verify work email addresses, keep lead lists clean, and follow up on outreach. With Hunter triggers, an agent starts when an email from Hunter is sent, opened, clicked, or answered. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Hunter API v2 The full surface, searched at run time. Connect with * API key Helios uses the API key to register email webhooks. Event triggers Yes · 4 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/hunter/) What the agent can do ## What agents do with Hunter Helios searches the Hunter API v2 at run time. The agent finds the endpoint the task needs and calls it. * Find and call Hunter API endpoints with your connected API key. * Find the email addresses Hunter knows for a company domain. * Find one person's work email from their name and company. * Verify addresses before they go into a sequence. * Get a company's logo from its domain. * Save leads, move them between lists, and update their fields. * Send an email to a lead and read the replies. * Start a run when an email is sent, opened, clicked, or answered. Examples ## Tasks you can hand to a Hunter agent ### Route every reply When a lead replies to a sequence, the agent reads the reply, records it in the CRM, and tells the account owner. hunter · message.replied When a lead replies to the Q4 outreach sequence, log the reply and alert the owner. 1. hunter·read the lead and the email 2. attio·find the company record 3. attio·add a note with the reply 4. slack·message the account owner ✓Reply from Acme logged * Note added to the Acme record * Owner told in Slack that the lead asked for a demo ### Find contacts for new accounts A scheduled agent searches company domains for contacts, verifies their addresses, and saves them as leads. Mondays at 9:00am Every Monday, find and verify contacts at last week's new target accounts and save them as leads. 1. attio·list new target accounts 2. hunter·search each domain 3. hunter·verify the addresses found 4. hunter·save leads to the Q4 list ✓31 leads saved * 12 accounts searched * 31 valid addresses saved, 6 invalid ones skipped ### Clean a list before a send The agent verifies addresses in a lead list and moves those Hunter marks as invalid to another list. Run now Verify every lead in the Webinar list and move invalid ones to a separate list. 1. hunter·list leads in the Webinar list 2. hunter·verify each address 3. hunter·move invalid leads ✓Webinar list cleaned * 184 leads checked * 9 invalid leads moved out Event triggers ## Start a run on Hunter events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | --------------- | ---------------------------------------------------------------------- | | message.sent | An email from Hunter goes out, from a sequence or from a lead's page. | | message.read | A lead opens an email. Filter on the sequence it came from. | | message.clicked | A lead clicks a link in an email. | | message.replied | A lead replies, so an agent can log it in the CRM and alert the owner. | Works with ## Hunter works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)Hunter + ApolloGive your agents full access to Apollo.](/integrations/apollo/)[![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Hunter + AttioGive your agents full access to Attio.](/integrations/attio/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Hunter + SlackGive your agents full access to Slack.](/integrations/slack/) FAQ ## Questions, answered ### How do I connect Hunter? ### Which Hunter events can trigger an agent? ### Does using Hunter through Helios use my Hunter credits? ## Put an agent on Hunter. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Jira Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/jira Description: Agents file issues from alerts and bug reports, search with JQL, move work through your workflow, plan sprints, and answer service desk requests. Jira events can start an agent when an issue is created or changes status, someone comments, a sprint starts, or a version is released. [← All integrations](/integrations/) Developer tools # Give your agents access to Jira. Agents file issues from alerts and bug reports, search with JQL, move work through your workflow, plan sprints, and answer service desk requests. Jira events can start an agent when an issue is created or changes status, someone comments, a sprint starts, or a version is released. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Jira Cloud platform REST API v3, Jira Software REST API, Jira Service Management REST API, Assets REST API, Forms REST API, and Jira Service Management operations and incident REST APIs The full surface, searched at run time. Connect with * API key * Your own OAuth app Connect with an Atlassian API token and your site URL, or with your own Atlassian OAuth app with every scope in the docs turned on. Helios registers the webhooks for triggers. The API token's account needs the Administer Jira global permission for that, and an OAuth app receives issue, comment, issue property, sprint, and version events only. Event triggers Yes · 5 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/jira/) What the agent can do ## What agents do with Jira Helios searches the Jira Cloud platform REST API v3, Jira Software REST API, Jira Service Management REST API, Assets REST API, Forms REST API, and Jira Service Management operations and incident REST APIs at run time. The agent finds the endpoint the task needs and calls it. * Use the Jira platform, Jira Software, Jira Service Management, Assets, Forms, and Jira Service Management operations and incident APIs, subject to the connection's permissions. * Create issues with a project, issue type, labels, priority, and assignee. * Run JQL searches and summarize a sprint, a project, or a saved filter. * Transition issues through your workflow, assign them, log work, and attach files. * Read boards and backlogs, move issues into sprints, and start or close a sprint. * Answer service desk requests, add participants, and handle approvals. * Start a run on issue, comment, worklog, sprint, board, version, project, and other Jira events. Examples ## Tasks you can hand to a Jira agent ### Triage every new bug The agent reads the report, looks for duplicates with JQL, checks recent changes, then sets labels, priority, and an assignee. jira · issue.created On each new Bug in the PAY project: find duplicates, set priority, and assign an owner. 1. jira·read the issue and its fields 2. jira·search open bugs with JQL for duplicates 3. github·find recent commits in the affected code 4. jira·set labels, priority, and assignee ✓PAY-1182 triaged * Labeled \`checkout\` · priority High * Linked to PAY-1170, which reports the same error * Assigned to the author of the last change to the refund service ### File an issue when CI fails When a GitHub Actions run fails on main, the agent opens a Jira issue with the failing job and its error, unless one is already open. github · workflow\_run.completed When CI fails on main, open a Jira issue in OPS with the failing job, unless one is already open. 1. github·read the failed job and its log 2. jira·search OPS with JQL for an open issue on this job 3. jira·create a Bug with the error and a link to the run 4. slack·post the issue link to #oncall ✓OPS-311 opened * Bug · priority High * \`checkout.spec.ts\` fails on main since run 91422 * Posted to #oncall ### Brief the assignee when work starts When an issue moves to In Progress, the agent gathers the code, docs, and related issues the assignee needs and posts them as a comment. jira · issue.updated When an issue moves to In Progress, comment with the related code, issues, and docs. 1. jira·read the issue and its links 2. github·search the code it mentions 3. notion·find the design doc 4. jira·comment with a starting brief ✓Brief posted on PAY-1190 * Two files that handle refund retries * The design doc section on idempotency * PAY-1043, closed with the same root cause ### Summarize the sprint A scheduled agent reads the active sprint with JQL and tells the team what shipped, what slipped, and what is blocked. Fridays at 4:00pm Every Friday, summarize the active sprint and post it to Slack. 1. jira·search issues in the open sprint with JQL 2. code·group by status and assignee 3. slack·post the summary to #payments ✓Sprint 37 summary * 21 of 27 issues done * 4 carried over to the next sprint * 2 blocked on the ledger migration Event triggers ## Start a run on Jira events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ---------------- | -------------------------------------------------------------------------------- | | issue.created | An issue was created in a project. | | issue.updated | An issue changes. Filter on the status it moved to, such as In Progress or Done. | | comment.created | Someone comments on an issue, so an agent can answer or pick up the follow-up. | | sprint.started | A sprint starts on a board, so an agent can post the plan or check the scope. | | version.released | A version is released, so an agent can write the release notes from its issues. | Works with ## Jira works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [Jira + GitHubGive your agents full access to GitHub.](/integrations/github/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Jira + SlackGive your agents full access to Slack.](/integrations/slack/)[Jira + NotionGive your agents full access to Notion.](/integrations/notion/) FAQ ## Questions, answered ### How do I connect Jira? ### What can an agent reach in Jira? ### Which Jira events can trigger an agent? ### Why does the account need the Administer Jira permission? ## Put an agent on Jira. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Linear Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/linear Description: Agents file issues from bug reports and alerts, triage the backlog, move work between states, and answer questions in comments. Linear events can start workflows when issues, comments, project updates, cycles, documents, or customer requests change. [← All integrations](/integrations/) Developer tools # Create and update Linear issues with your agents. Agents file issues from bug reports and alerts, triage the backlog, move work between states, and answer questions in comments. Linear events can start workflows when issues, comments, project updates, cycles, documents, or customer requests change. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Linear GraphQL API The full surface, searched at run time. Connect with * API key * Your own OAuth app Give the API key the Admin permission, or turn on Admin access for an OAuth app, so Helios can register the webhook for Linear events. Event triggers Yes · 5 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/linear/) What the agent can do ## What agents do with Linear Helios searches the Linear GraphQL API at run time. The agent finds the endpoint the task needs and calls it. * Query and update Linear through its GraphQL API, within your connection's permissions. * Create issues with a team, labels, priority, assignee, and project. * Move issues between workflow states and update priority, estimate, or cycle. * Comment on issues, project updates, and documents, and reply to comments. * Read cycles, projects, and roadmaps to report on progress. * Start a run when an issue, comment, project, cycle, document, initiative, customer request, or release is created, updated, or removed, or when an issue's SLA is at risk or breached. Available events depend on your Linear plan and permissions. Examples ## Tasks you can hand to a Linear agent ### Triage every new issue The agent reads the report, finds related issues and recent changes, then sets labels, priority, and an owner. linear · issue.created On each new issue in the Platform team: label it, set priority, and assign an owner. 1. linear·read the issue and team labels 2. linear·search open issues for duplicates 3. github·find recent commits in the affected code 4. linear·set labels, priority, and assignee ✓PLAT-482 triaged * Labeled \`bug\` and \`billing\` · priority High * Linked to PLAT-455, which reports the same error * Assigned to the author of the last change to the invoice job ### Start work when an issue moves to In Progress When an issue moves to In Progress, the agent gathers the context an engineer needs and posts it as a comment. linear · issue.updated When an issue moves to In Progress, post the related code, issues, and docs as a comment. 1. linear·read the issue and its history 2. github·search the code it mentions 3. notion·find the design doc 4. linear·comment with a starting brief ✓Brief posted on PLAT-490 * Three files that handle webhook retries * The design doc section on idempotency keys * Two closed issues with the same root cause ### Answer questions in issue comments When someone asks a question in a comment, the agent looks it up and replies in the same thread. linear · comment.created When a comment asks the agent a question, answer it on the same issue. 1. linear·read the comment and the issue 2. github·check the related pull request 3. linear·reply in the thread ✓Replied on PLAT-501 * The fix is in the pull request that merged yesterday * It ships in the next release ### Summarize the cycle A scheduled agent reads the active cycle and tells the team what shipped, what slipped, and what is blocked. Fridays at 4:00pm Every Friday, summarize the active cycle and post it to Slack. 1. linear·list issues in the active cycle 2. code·group by state and owner 3. slack·post the summary to #platform ✓Cycle 42 summary * 18 of 24 issues done * 4 moved to the next cycle * 2 blocked on the billing migration Event triggers ## Start a run on Linear events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ----------------------- | ----------------------------------------------------------------------------------------------------------- | | issue.created | An issue is created in a team. | | issue.updated | An issue changes. Filter on the state it moved to, such as In Progress or Done. | | comment.created | Someone comments on an issue, project update, or document, so an agent can answer or pick up the follow-up. | | project\_update.created | A project lead posts an update, so an agent can check it against the issues in the project. | | issue\_sla.high\_risk | An issue is close to breaching its SLA, so an agent can escalate it before it does. | Works with ## Linear works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [Linear + GitHubGive your agents full access to GitHub.](/integrations/github/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Linear + SlackGive your agents full access to Slack.](/integrations/slack/)[Linear + NotionGive your agents full access to Notion.](/integrations/notion/) FAQ ## Questions, answered ### How do I connect Linear? ### What can an agent reach in Linear? ### Which Linear events can trigger an agent? ### Why do triggers need admin permission? ## Put an agent on Linear. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Lusha Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/lusha Description: Agents enrich people and companies, find contacts at target accounts, and act on buying signals. Lusha trigger events start an agent on a specific Lusha signal for a contact or company you watch, such as a job change, a hiring surge, or a funding story, and when a contact opts out. [← All integrations](/integrations/) Sales & CRM ![](/static/img/assets/lusha-light.svg)![](/static/img/assets/lusha-dark.svg) # Enrich contacts and companies with Lusha. Agents enrich people and companies, find contacts at target accounts, and act on buying signals. Lusha trigger events start an agent on a specific Lusha signal for a contact or company you watch, such as a job change, a hiring surge, or a funding story, and when a contact opts out. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Lusha API v3 and v2 The full surface, searched at run time. Connect with * API key Helios creates the Lusha webhook subscriptions for the contacts and companies you list on the connection, and the account's opt-out subscription. Event triggers Yes · 5 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/lusha/) What the agent can do ## What agents do with Lusha Helios searches the Lusha API v3 and v2 at run time. The agent finds the endpoint the task needs and calls it. * Find a person's work email or phone number from their name and company. * Enrich a company by domain with size, industry, revenue, and technologies. * Find contacts at an account with prospecting filters. * Start a run on a specific Lusha signal for a watched contact or company, or when a contact opts out. Examples ## Tasks you can hand to a Lusha agent ### Follow champions to new jobs When a contact from a closed deal moves to another company, the agent looks up the new account and asks the owner to reach out. lusha · contact.company\_changed When a watched champion changes companies, research the new company and tell the account owner. 1. lusha·read the job change 2. lusha·enrich the new company 3. attio·create the company record 4. slack·message the account owner ✓Champion moved to Northwind * Northwind added to Attio with 420 employees * Owner told in Slack with an intro draft ### Find contacts for new accounts A scheduled agent finds the decision makers at new target accounts and adds them to the CRM with their work emails. Mondays at 9:00am Every Monday, find sales leaders at last week's new target accounts and add them to Attio. 1. attio·list new target accounts 2. lusha·search each domain 3. lusha·reveal work emails 4. attio·create the people records ✓18 contacts added * 7 accounts searched * 18 sales leaders added with work emails ### Act on hiring surges When a watched company starts hiring fast, the agent checks which teams are growing and suggests the right contacts to the owner. lusha · company.hiring\_surged When a watched account has a hiring surge, find the growing teams and suggest contacts. 1. lusha·read the signal 2. lusha·find leaders in the growing teams 3. slack·post the suggestions ✓Acme is hiring in engineering * 3 engineering leaders found * Suggestions posted in #accounts Event triggers ## Start a run on Lusha events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ----------------------------------------- | ---------------------------------------------------------------------------------------------------- | | contact.company\_changed | A watched contact moves to another company. | | contact.promoted | A watched contact is promoted. Filter on the new job title. | | company.hiring\_surged | Open job postings at a watched company increase sharply. | | company.financial\_events\_news\_reported | A watched company is in the news for funding, investments, or an IPO. Filter on the news event type. | | contact.opted\_out | A contact your account revealed opts out of Lusha. | Works with ## Lusha works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)Lusha + ApolloGive your agents full access to Apollo.](/integrations/apollo/)[![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Lusha + AttioGive your agents full access to Attio.](/integrations/attio/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Lusha + SlackGive your agents full access to Slack.](/integrations/slack/) FAQ ## Questions, answered ### How do I connect Lusha? ### Which Lusha events can trigger an agent? ### What if another tool already watches a contact? ### Does using Lusha through Helios use my Lusha credits? ## Put an agent on Lusha. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Mailchimp Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/mailchimp Description: Agents search the Marketing API to manage contacts, campaigns, reports and ecommerce data. Audience changes and completed batch operations can start workflows. [← All integrations](/integrations/) Email ![](/static/img/assets/mailchimp-light.svg)![](/static/img/assets/mailchimp-dark.svg) # Manage audiences and campaigns with your agents. Agents search the Marketing API to manage contacts, campaigns, reports and ecommerce data. Audience changes and completed batch operations can start workflows. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Mailchimp Marketing API v3 The full surface, searched at run time. Connect with * API key * Your own OAuth app Connect with an API key or authorize your own Mailchimp OAuth app. Event triggers Yes · 11 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/mailchimp/) What the agent can do ## What agents do with Mailchimp Helios searches the Mailchimp Marketing API v3 at run time. The agent finds the endpoint the task needs and calls it. * Create and update audiences, contacts and segments. * Manage email campaigns and read campaign reports. * Manage ecommerce stores, products and orders. * Run batch operations and retrieve their results. Examples ## Tasks you can hand to a Mailchimp agent Event triggers ## Start a run on Mailchimp events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | --------------------------- | --------------------------------------------- | | contact.subscribed | A contact subscribes to email. | | contact.unsubscribed | A contact unsubscribes from email. | | contact.profile\_updated | A contact profile changes. | | contact.cleaned | An email address is cleaned from an audience. | | contact.email\_updated | A contact email address changes. | | campaign.finished | An email campaign is sent or cancelled. | | contact.sms\_subscribed | A contact subscribes to SMS (beta). | | contact.sms\_unsubscribed | A contact unsubscribes from SMS (beta). | | contact.sms\_phone\_updated | A contact SMS phone number changes (beta). | | sms\_campaign.sent | An SMS campaign is sent (beta). | | batch.completed | An API batch operation completes. | Works with ## Mailchimp works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/brevo-light.svg)![](/static/img/assets/brevo-dark.svg)Mailchimp + BrevoManage contacts, campaigns and transactional email with your agents.](/integrations/brevo/)[![](/static/img/assets/gmail-light.svg)![](/static/img/assets/gmail-dark.svg)Mailchimp + GmailGive your agents full access to Gmail.](/integrations/gmail/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Mailchimp + SlackGive your agents full access to Slack.](/integrations/slack/) FAQ ## Questions, answered ### How do I connect Mailchimp? ### Do I need to create webhooks? ## Put an agent on Mailchimp. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Notion Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/notion Description: Agents search your workspace, read pages and databases, write new entries, and keep knowledge current. Name a database in the prompt once and memory carries what the agent learns about it across runs. [← All integrations](/integrations/) Docs & knowledge # Give your agents full access to Notion. Agents search your workspace, read pages and databases, write new entries, and keep knowledge current. Name a database in the prompt once and memory carries what the agent learns about it across runs. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Notion API The full surface, searched at run time. Connect with * Helios OAuth app * Your own OAuth app * API key Event triggers Not yet Manual, schedule, and signed webhook are available. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/notion/) What the agent can do ## What agents do with Notion Helios searches the Notion API at run time. The agent finds the endpoint the task needs and calls it. * Search Notion's entire API surface at run time and call any endpoint your integration can reach. * Search and read pages, blocks, and database rows across the workspace. * Create pages, append blocks, and write structured content. * Query databases with filters and sorts; create and update rows with typed properties. * Keep a database current on a schedule - audit stale entries, fill gaps, fix formatting. * Use your workspace as the knowledge base an agent answers questions from. Examples ## Tasks you can hand to a Notion agent ### Answer questions from your workspace An agent searches Notion the way a colleague would, reads the pages that matter, and answers with links to the source. What is our current on-call escalation policy? 1. notion·search workspace for on-call policy 2. notion·read \`Engineering Handbook → On-call\` ✓Answer with sources * Primary pages within 5 minutes, secondary at 15 * Sev-1 pages the eng manager immediately * Source: Engineering Handbook, updated Feb 12 ### Find documentation that went stale A scheduled agent checks pages against the code and flags the ones that describe something that changed. Monthly on the 1st Monthly, find docs pages that contradict the current codebase. 1. notion·list pages in \`Engineering Docs\` 2. github·read referenced files at \`main\` 3. code·diff documented behavior vs code 4. notion·comment on 6 stale pages ✓6 stale pages flagged * \`Auth Setup\` references a removed env var * \`Deploy Runbook\` names an old cluster * Each page commented with the specific line ### File decisions where you keep them The agent turns a channel discussion into a structured Notion entry with decisions, owners, and next steps. Thursdays at 5:00pm After the weekly product discussion, file decisions into the Decisions database. 1. slack·read this week's #product threads 2. notion·create rows in \`Decisions\` ✓4 decisions recorded * Each row has an owner, date, and Slack link * 2 tagged \`needs-follow-up\` ### Publish release notes to your docs When a release ships, the agent writes the notes as a Notion page and links it from the changelog database. github · release.published On each published release, write a Notion changelog entry. 1. github·read release body and merged PRs 2. notion·create page in \`Changelog\` ✓Changelog entry published * v2.8.0 with features, fixes, and breaking changes * Linked to the GitHub release Triggers ## How a Notion workflow starts Notion does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook. ### Manual Run it from the app with an optional JSON payload. Every workflow supports this. ### Schedule A cron expression or a plain sentence such as every weekday at 9am. Times are UTC. ### Signed webhook A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes. Works with ## Notion works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Notion + SlackGive your agents full access to Slack.](/integrations/slack/)[Notion + GitHubGive your agents full access to GitHub.](/integrations/github/)[![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)Notion + Google DocsGive your agents full access to Google Docs.](/integrations/google-docs/) Templates ## Ready-to-run Notion workflows Copy the prompt, connect your tools, and start a run. [SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.slack · message.channel![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/templates/slack-support-triage/)[SupportPlain thread triageTriages every new Plain thread on arrival. Labels, priority, a draft reply, and an internal note with what it checked.plain · thread.thread\_created![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/plain-thread-summarizer/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes a draft release on GitHub, and files a changelog entry in Notion.github · tag.created![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/github-release-notes/)[EngineeringIncident postmortem drafterRebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/incident-postmortem-drafter/)[SupportDocumentation freshness auditChecks your written docs against the codebase every month and comments on the pages that have gone stale.Monthly on the 1st![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/notion-docs-freshness-audit/) Use cases ## Where Notion agents fit [SupportSupport triageA workflow reads each new thread as it arrives. It finds the customer, checks the plan and billing state, sets labels and priority, and drafts a reply from your docs.plain · thread.thread\_created![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/use-cases/support-triage/)[EngineeringPull request reviewA workflow reads each diff against your conventions and leaves a real review. A second workflow on a schedule posts the week's merged work, review backlog, and CI health.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/pr-review-digest/)[EngineeringIncident summariesA workflow rebuilds the timeline from your incident channel and the deploys around it. It names the likely change and drafts the write-up with the facts in place.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/incident-summaries/)[MarketingResearch briefsA workflow searches the web, reads what it finds, and writes a draft with every claim linked to its source. Give it your prior work and the draft matches your voice.Run on demand![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)![](/static/img/assets/apify.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/content-pipeline/) FAQ ## Questions, answered ### How do I connect Notion? ### What can an agent reach in Notion? ### Can a Notion change trigger an agent? ### How do I stop an agent from touching a private page? ### Does Notion access cost extra? ## Put an agent on Notion. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # PagerDuty Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/pagerduty Description: Agents can look up who is on call, manage incidents, and add notes for responders. Supported incident and service events can start workflows. Access depends on the connection's permissions and your PagerDuty account's features. [← All integrations](/integrations/) Developer tools # Give your agents access to PagerDuty. Agents can look up who is on call, manage incidents, and add notes for responders. Supported incident and service events can start workflows. Access depends on the connection's permissions and your PagerDuty account's features. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach PagerDuty REST API and incident and service webhooks The full surface, searched at run time. Connect with * API key * Your own OAuth app Use a general access key with full access and the email of a PagerDuty user, or your own Scoped OAuth app with the scopes for your workflows, authorized by a user who can create webhook subscriptions. Helios creates the webhook subscription for triggers. Event triggers Yes · 8 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/pagerduty/) What the agent can do ## What agents do with PagerDuty Helios searches the PagerDuty REST API and incident and service webhooks at run time. The agent finds the endpoint the task needs and calls it. * Look up and call PagerDuty REST API operations allowed by your connection's permissions. * Find who is on call for a service, schedule, or escalation policy. * Create incidents, and acknowledge, reassign, escalate, or resolve them. * Add notes and status updates to incidents and read their timelines. * List open incidents by service, team, urgency, or priority. * Start runs on supported incident and service events, including priority changes, responder requests, and service deletion. Examples ## Tasks you can hand to a PagerDuty agent ### Gather context when an incident triggers The agent reads the incident, checks recent deploys and errors for the service, and posts what it found as a note for the responder. pagerduty · incident.triggered When a high-urgency incident triggers on the Checkout service, post recent deploys and errors as a note. 1. pagerduty·read the incident and its service 2. github·list deploys to checkout in the last two hours 3. postgres·count failed orders by minute 4. pagerduty·add a note with the findings ✓Note added to incident #1482 * Deploy 3f2a91c went out 14 minutes before the alert * Failed orders rose from 0.2% to 6% after it * The same error opened incident #1391 last month ### Draft the write-up when an incident resolves When an incident resolves, the agent reads its timeline and notes and drafts a postmortem for the team to review. pagerduty · incident.resolved When a P1 incident resolves, draft a postmortem from its timeline and notes. 1. pagerduty·read the log entries and notes 2. github·find the fix that was merged 3. notion·create the postmortem draft 4. pagerduty·add a note linking the draft ✓Postmortem drafted for incident #1482 * Timeline from trigger to resolve: 38 minutes * Root cause: a config change in deploy 3f2a91c * Three follow-up actions for review ### Answer questions in incident notes Responders ask the agent a question in a note, and the agent looks it up and answers in another note. pagerduty · incident.annotated When a note mentions @helios, answer the question in a new note on the same incident. 1. pagerduty·read the note and the incident 2. postgres·check how many customers are affected 3. pagerduty·add a note with the answer ✓Answered on incident #1482 * 412 customers saw a failed checkout in the last hour ### Post who is on call A scheduled agent reads this week's on-call rotation and posts it to the team's channel. Mondays at 9:00am Every Monday, post who is on call for each service this week to Slack. 1. pagerduty·list on-calls for each escalation policy 2. code·group by service and level 3. slack·post the rotation to #on-call ✓On-call for this week * Checkout: Priya, then Sam * Payments: Alex, then Jordan Event triggers ## Start a run on PagerDuty events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | -------------------------- | -------------------------------------------------------------------------------------------------- | | incident.triggered | An incident is triggered. Filter by service, team, urgency, or priority. | | incident.acknowledged | A responder picks up an incident. Filter by service, team, urgency, or priority. | | incident.escalated | An incident escalates, so an agent can bring in the next team with context. | | incident.priority\_updated | An incident's priority changes. Filter by service, team, urgency, or priority. | | incident.resolved | An incident is resolved. Use its timeline and notes to draft a write-up. | | incident.annotated | Someone adds a note to an incident. Filter on the note's text to answer questions from responders. | | incident.responder.added | Someone is asked to join an incident, so an agent can brief them on what happened so far. | | service.updated | A service changes. Filter by service or team to review changes to critical services. | Works with ## PagerDuty works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [PagerDuty + GitHubGive your agents full access to GitHub.](/integrations/github/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)PagerDuty + SlackGive your agents full access to Slack.](/integrations/slack/) FAQ ## Questions, answered ### How do I connect PagerDuty? ### Why does Helios ask for an email? ### Which PagerDuty events can trigger an agent? ### Does it work with the EU service region? ## Put an agent on PagerDuty. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Pipedrive Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/pipedrive Description: Agents look up deals and people before a call, update the pipeline from meeting notes, log activities, and report on what is moving. Pipedrive trigger events start an agent when a deal, lead, person, organization, activity, product, project, or another record is created, updated, or deleted. [← All integrations](/integrations/) Sales & CRM ![](/static/img/assets/pipedrive-light.svg)![](/static/img/assets/pipedrive-dark.svg) # Read and update Pipedrive records with your agents. Agents look up deals and people before a call, update the pipeline from meeting notes, log activities, and report on what is moving. Pipedrive trigger events start an agent when a deal, lead, person, organization, activity, product, project, or another record is created, updated, or deleted. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Pipedrive API v1 and v2 The full surface, searched at run time. Connect with * API key * Your own OAuth app An API token also needs your company domain, such as acme in acme.pipedrive.com. API calls and triggers follow the connected user's permissions. OAuth calls also require the app's scopes. Event triggers Yes · 5 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/pipedrive/) What the agent can do ## What agents do with Pipedrive Helios searches the Pipedrive API v1 and v2 at run time. The agent finds the endpoint the task needs and calls it. * Call Pipedrive v1 and v2 API endpoints within your connected user's permissions and OAuth scopes. * Find deals, people, and organizations, and read their notes and activity history. * Create and update deals, people, and organizations from a request. * Move deals between stages and mark them won or lost. * Add notes and schedule calls, meetings, and other activities. * Start a run when a record is created, updated, or deleted, with filters for pipeline, owner, stage, status, activity type, and done. Examples ## Tasks you can hand to a Pipedrive agent ### Update the pipeline from call notes After a call, the agent reads the notes, moves the deal to the right stage, and schedules the next step. Run after calls Read the call notes on my deals, update each deal's stage, and schedule the follow-up. 1. pipedrive·read the call notes on the deals 2. pipedrive·find the matching deals 3. pipedrive·move deals and add the notes 4. pipedrive·schedule follow-up calls ✓3 deals updated * Acme moved to Proposal made * Globex follow-up call set for Thursday * Initech notes added, no stage change Event triggers ## Start a run on Pipedrive events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ---------------- | ------------------------------------------------------------------------------------------- | | deal.created | A new deal is created. Filter by pipeline or owner. | | deal.updated | A deal changes. Filter on the stage it moved to, or on a status change such as won or lost. | | person.created | A new person is added. Filter by owner. | | lead.created | A new lead is created. Filter by owner. | | activity.updated | An activity changes. Filter by owner, activity type, or a change in completion status. | Works with ## Pipedrive works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)Pipedrive + ApolloGive your agents full access to Apollo.](/integrations/apollo/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Pipedrive + SlackGive your agents full access to Slack.](/integrations/slack/) FAQ ## Questions, answered ### How do I connect Pipedrive? ### What can an agent reach in Pipedrive? ### Which Pipedrive events can trigger an agent? ### Why do some deals not start a run? ## Put an agent on Pipedrive. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Plain Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/plain Description: Agents read customer threads, draft replies grounded in your docs, label and prioritize, and hand the hard ones to a person. Plain trigger events mean an agent starts working the moment a customer writes in. [← All integrations](/integrations/) Support ![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg) # Give your agents full access to Plain. Agents read customer threads, draft replies grounded in your docs, label and prioritize, and hand the hard ones to a person. Plain trigger events mean an agent starts working the moment a customer writes in. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Plain GraphQL API The full surface, searched at run time. Connect with * API key Paste the webhook signing secret from Plain to receive thread events. Event triggers Yes · 2 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/plain/) What the agent can do ## What agents do with Plain Helios searches the Plain GraphQL API at run time. The agent finds the endpoint the task needs and calls it. * Search Plain's entire API surface at run time and call any endpoint your key allows. * Read threads, messages, and customer context including tenants and custom fields. * Draft and send replies, and add internal notes for the human who picks it up. * Apply labels, set priority, assign, snooze, and mark threads done. * Look up the customer in your CRM and database before answering. * Start a run the moment a thread is created or a chat arrives. Examples ## Tasks you can hand to a Plain agent ### Triage every thread the moment it arrives The agent reads the thread, identifies the customer, checks their plan and usage, labels it, sets priority, and drafts a reply for review. plain · thread.thread\_created On each new thread: identify the customer, label, prioritize, and draft a reply. 1. plain·read thread and customer record 2. stripe·check plan and payment health 3. notion·search help center for the answer 4. plain·label, set priority, and draft reply ✓Thread triaged in 22 seconds * Labeled \`billing\` · priority \`high\` (Enterprise plan) * Draft reply cites the invoice settings doc * Internal note names the failed charge from Tuesday ### Answer the questions you have answered before The agent searches past resolved threads and your docs, and sends a reply when it is confident, escalating when it is not. plain · chat.received Answer questions we have resolved before; escalate anything new. 1. plain·search resolved threads for the same question 2. notion·read the referenced doc 3. plain·send reply and mark thread done ✓Answered and closed * Matched 3 prior threads on SSO group mapping * Replied with steps and a doc link * Left an internal note with the sources used ### Summarize the support week A scheduled agent reads every thread, clusters them by theme, and tells the product team what customers kept asking about. Fridays at 3:00pm Every Friday, cluster the week's threads by theme and post to Slack. 1. plain·list threads from the last 7 days 2. code·cluster by topic and count 3. slack·post themes to #product ✓Support themes · week of Mar 3 * 41 threads · 3 clusters cover 68% * SSO setup confusion is the top theme (14) * 2 threads describe the same undocumented bug ### Escalate the accounts that matter When a high-value customer writes in unhappy, the agent pages the owner with the account context already assembled. plain · thread.thread\_created When an Enterprise customer opens an urgent thread, page the account owner. 1. plain·read thread and tenant tier 2. attio·look up the account owner 3. slack·DM the owner with a summary 4. plain·set priority urgent and assign ✓Escalated to @priya * Northwind · Enterprise · $4.2k MRR * Third thread this week on the same issue * Priority set to urgent Event triggers ## Start a run on Plain events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ---------------------- | ------------------------------------------------------------------------------- | | thread.thread\_created | A customer opens a new thread - the moment to triage, label, and draft a reply. | | thread.chat\_received | A live chat message arrives and an agent can answer or route it immediately. | Works with ## Plain works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Plain + SlackGive your agents full access to Slack.](/integrations/slack/)[Plain + NotionGive your agents full access to Notion.](/integrations/notion/)[Plain + StripeGive your agents full access to Stripe.](/integrations/stripe/) Templates ## Ready-to-run Plain workflows Copy the prompt, connect your tools, and start a run. [SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.slack · message.channel![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/templates/slack-support-triage/)[SupportPlain thread triageTriages every new Plain thread on arrival. Labels, priority, a draft reply, and an internal note with what it checked.plain · thread.thread\_created![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/plain-thread-summarizer/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to find the accounts drifting toward the exit.Mondays at 7:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/churn-risk-watchlist/) Use cases ## Where Plain agents fit [SupportSupport triageA workflow reads each new thread as it arrives. It finds the customer, checks the plan and billing state, sets labels and priority, and drafts a reply from your docs.plain · thread.thread\_created![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/use-cases/support-triage/)[Sales & RevOpsCRM data syncA workflow computes usage from your database, joins it with billing state and support volume, and writes the result onto each account record every night.Nightly at 1:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)](/use-cases/crm-data-sync/) FAQ ## Questions, answered ### How do I connect Plain? ### What can an agent reach in Plain? ### Which Plain events can trigger an agent? ### Will an agent reply to customers on its own? ### Does Plain cost extra? ## Put an agent on Plain. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Reddit Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/reddit Description: Agents watch subreddits, read threads and comments, and surface the conversations where your product, your competitors, or your problem space comes up. [← All integrations](/integrations/) Community # Give your agents full access to Reddit. Agents watch subreddits, read threads and comments, and surface the conversations where your product, your competitors, or your problem space comes up. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Reddit API v1 The full surface, searched at run time. Connect with * Helios OAuth app * Your own OAuth app Event triggers Not yet Manual, schedule, and signed webhook are available. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/reddit/) What the agent can do ## What agents do with Reddit Helios searches the Reddit API v1 at run time. The agent finds the endpoint the task needs and calls it. * Search Reddit's entire API surface at run time and call any endpoint your credential allows. * Search posts and comments across subreddits with full query control. * Read a thread and its comment tree for real context. * Track mentions of your brand, competitors, and category terms. * Judge sentiment and intent so the team sees the threads worth answering. * Route findings into Slack, Notion, or your CRM. Examples ## Tasks you can hand to a Reddit agent ### Watch for brand mentions The agent sweeps the subreddits that matter, reads the threads where you come up, and posts the ones worth a reply. Every 4 hours Every few hours, find mentions of us and flag the ones worth answering. 1. reddit·search 8 subreddits for brand terms 2. reddit·read comment trees on 6 threads 3. code·score sentiment and reply-worthiness 4. slack·post the shortlist to #community ✓3 threads worth a reply * One asks how we compare on pricing * One reports a real bug with a repro * One is a positive review worth thanking ### Track what people say about competitors A weekly agent reads competitor discussions, extracts the recurring complaints and praise, and hands product a summary. Mondays at 9:00am Weekly, summarize what people say about our competitors. 1. reddit·search competitor names across 12 subreddits 2. reddit·read the 20 most-discussed threads 3. notion·write to \`Competitive Intel\` ✓Competitive intel · week of Mar 3 * Pricing changes drove 40% of the discussion * Two recurring complaints about onboarding * One competitor announced a feature we already ship ### Find where your customers gather Describe your customer. The agent finds the subreddits where they talk, reads them, and tells you what they care about. Find the subreddits where platform engineers discuss CI costs. 1. reddit·search for the topic across Reddit 2. reddit·sample top threads in 15 candidate subreddits 3. google-docs·write a findings brief ✓6 subreddits identified * Ranked by relevance and activity * Top three recurring pain points listed * Sample threads linked for each ### Mine threads for product feedback The agent turns scattered complaints and wishes into structured feedback entries your product team can actually read. Monthly on the 1st Monthly, extract feature requests about us and file them in Notion. 1. reddit·collect a month of brand mentions 2. code·extract and dedupe requests 3. notion·create rows in \`Feedback\` ✓9 requests filed * Ranked by how often each came up * 3 match existing roadmap items and were linked Triggers ## How a Reddit workflow starts Reddit does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook. ### Manual Run it from the app with an optional JSON payload. Every workflow supports this. ### Schedule A cron expression or a plain sentence such as every weekday at 9am. Times are UTC. ### Signed webhook A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes. Works with ## Reddit works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [Reddit + DiscordGive your agents full access to Discord.](/integrations/discord/)[Reddit + NotionGive your agents full access to Notion.](/integrations/notion/)[![](/static/img/assets/apify.svg)Reddit + ApifyGive your agents full access to Apify.](/integrations/apify/) Templates ## Ready-to-run Reddit workflows Copy the prompt, connect your tools, and start a run. [MarketingReddit brand monitorSweeps the subreddits where your customers gather, judges which threads deserve a reply, and brings you a shortlist.Every 4 hours![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/reddit-brand-monitor/) Use cases ## Where Reddit agents fit [MarketingCommunity monitoringA workflow sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space. It picks the threads worth a reply and brings them to your team.Every 4 hours![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/community-monitoring/) FAQ ## Questions, answered ### How do I connect Reddit? ### What can an agent reach on Reddit? ### Can a Reddit post trigger an agent? ### Will the agent post to Reddit? ### Does Reddit access cost extra? ## Put an agent on Reddit. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Resend Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/resend Description: Agents compose and send transactional and lifecycle email from your own domain. Pair Resend with a database or CRM and an agent writes the message with the context each recipient deserves. [← All integrations](/integrations/) Email ![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg) # Give your agents full access to Resend. Agents compose and send transactional and lifecycle email from your own domain. Pair Resend with a database or CRM and an agent writes the message with the context each recipient deserves. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Resend API v1 The full surface, searched at run time. Connect with * API key Event triggers Not yet Manual, schedule, and signed webhook are available. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/resend/) What the agent can do ## What agents do with Resend Helios searches the Resend API v1 at run time. The agent finds the endpoint the task needs and calls it. * Search Resend's entire API surface at run time and call any endpoint your key allows. * Send individual and batch emails from your verified domain. * Compose HTML and plain-text bodies tailored per recipient. * Manage audiences and contacts for lifecycle sequences. * Read delivery events to confirm what landed and what bounced. * Combine with database queries so each message reflects real account state. Examples ## Tasks you can hand to a Resend agent ### Run an onboarding sequence that reads the account The agent checks what each new account has actually done and sends the message that helps next. Daily at 9:00am Daily, email new accounts based on what they have set up so far. 1. postgres·list accounts created in the last 14 days 2. code·determine each account's next milestone 3. resend·send 46 tailored emails ✓46 onboarding emails sent * 19 nudged to connect their first integration * 14 shown how to schedule a task * 13 invited to add a teammate ### Notify people when something needs them Any agent that finds a problem can also tell the right person about it, with the detail they need to act. Nightly at 3:00am When a nightly task finds a data issue, email the on-call analyst. 1. postgres·run data quality checks 2. code·summarize the 2 failing checks 3. resend·email the on-call analyst ✓Data quality alert sent * \`orders.currency\` null on 41 rows since 02:10 * Upstream job \`ingest\_orders\` last succeeded at 01:55 ### Send a weekly customer digest Each customer gets a summary of their own numbers, written from their own data. Mondays at 8:00am Every Monday, send each account a digest of last week's usage. 1. clickhouse·aggregate weekly usage per account 2. code·write per-account narrative 3. resend·batch send 312 digests ✓312 digests sent * Each names the account's top workflow by runs * 28 accounts told they are near a plan limit ### Follow up on failed payments When billing finds a problem, the agent writes a clear message with a working link and sends it from your domain. Hourly For each failed charge, email the billing contact with an update link. 1. stripe·list failed charges 2. stripe·create hosted payment update links 3. resend·send recovery emails ✓3 recovery emails sent * Sent from billing@yourdomain.com * Each links a hosted update page * Escalation scheduled if unpaid in 48h Triggers ## How a Resend workflow starts Resend does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook. ### Manual Run it from the app with an optional JSON payload. Every workflow supports this. ### Schedule A cron expression or a plain sentence such as every weekday at 9am. Times are UTC. ### Signed webhook A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes. Works with ## Resend works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [Resend + StripeGive your agents full access to Stripe.](/integrations/stripe/)[Resend + DatabasesGive your agents full access to your databases.](/integrations/databases/)[![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Resend + AttioGive your agents full access to Attio.](/integrations/attio/) Templates ## Ready-to-run Resend workflows Copy the prompt, connect your tools, and start a run. [Sales & RevOpsFailed payment recoveryFinds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/stripe-failed-payment-recovery/)[OperationsNightly data quality checksRuns your invariants against production every night and emails the on-call analyst which rows broke and since when.Nightly at 3:00am![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/templates/database-health-check/) Use cases ## Where Resend agents fit [Sales & RevOpsLead enrichmentA signup or form response fires a webhook. The workflow enriches the person and company, scores fit against your definition, creates the CRM record, and tells the right rep.Signup webhook![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/typeform-light.svg)![](/static/img/assets/typeform-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/lead-enrichment/)[OperationsDatabase reportingA workflow reads your schema, writes the SQL, runs it, checks the results in its sandbox, and posts a report to the channel your team reads.Weekdays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/database-reporting/)[OperationsBilling operationsA workflow watches Stripe for failed charges and starts recovery. A second one reconciles what you billed against what your own database recorded after the books close.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/billing-ops/) FAQ ## Questions, answered ### How do I connect Resend? ### What can an agent reach in Resend? ### Can a Resend event trigger an agent? ### How do I review email before it goes out? ### Does Resend cost extra? ## Put an agent on Resend. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Salesforce Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/salesforce Description: Agents find and update leads, contacts, accounts, and opportunities, log calls and tasks, post to Chatter, and report on the pipeline with SOQL. Salesforce flows can send records to Helios, so an agent starts when a lead arrives or a deal closes. [← All integrations](/integrations/) Sales & CRM ![](/static/img/assets/salesforce-light.svg)![](/static/img/assets/salesforce-dark.svg) # Query and update Salesforce records with your agents. Agents find and update leads, contacts, accounts, and opportunities, log calls and tasks, post to Chatter, and report on the pipeline with SOQL. Salesforce flows can send records to Helios, so an agent starts when a lead arrives or a deal closes. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Salesforce REST, Bulk, GraphQL, Connect, Reports, and CRM Analytics APIs The full surface, searched at run time. Connect with * Your own OAuth app Create an External Client App in your org. Connect as its run-as user with the client credentials flow, or sign in through it as yourself. Event triggers Yes · 1 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/salesforce/) What the agent can do ## What agents do with Salesforce Helios searches the Salesforce REST, Bulk, GraphQL, Connect, Reports, and CRM Analytics APIs at run time. The agent finds the endpoint the task needs and calls it. * Query objects the connected user can access with SOQL or SOSL, including custom objects and fields. * Create and update records one at a time, or many at once with Composite and the Bulk API. * Move opportunities between stages and record the next step from call notes. * Log calls, create follow-up tasks, and post Chatter updates. * Read object and field definitions, query metadata with the Tooling API, and call your own Apex REST services. * Run reports and dashboards, and query CRM Analytics datasets. * Start a run when a record-triggered flow sends a record through an outbound message. Examples ## Tasks you can hand to a Salesforce agent ### Research and route every new lead A flow sends each new lead to Helios. The agent looks up the company, fills in the missing fields, and adds a follow-up task for the owner. salesforce · record.changed · Lead On each new lead: research the company, complete the lead, and add a follow-up task. 1. salesforce·read the new lead 2. web·research the company 3. salesforce·update industry, size, and website 4. salesforce·create a follow-up task for the owner ✓Lead ready * Industry and employee count filled in * Follow-up task due tomorrow with three talking points ### Hand off won deals When an opportunity moves to Closed Won, the agent creates the kickoff task and tells the onboarding team. salesforce · record.changed · Opportunity When an opportunity is won, create a kickoff task and post the deal summary to Slack. 1. salesforce·read the opportunity and its account 2. salesforce·create a kickoff task on the opportunity 3. slack·post to #onboarding ✓Kickoff scheduled * Task assigned to the onboarding lead for Monday * Deal size, products, and contacts posted to #onboarding ### Review the pipeline every week A scheduled agent runs SOQL over the open opportunities and flags deals with a past close date or no recent activity. Mondays at 9:00am Every Monday, list open opportunities that need attention and post them to Slack. 1. salesforce·query open opportunities and their last activity 2. code·find stale and overdue deals 3. slack·post the list to #sales ✓Pipeline review * 5 opportunities past their close date * 3 with no activity in 30 days Event triggers ## Start a run on Salesforce events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | record.changed | A Salesforce flow sends a created or updated record, such as a new lead or an opportunity that moved to Closed Won. Filter on the object. | Works with ## Salesforce works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Salesforce + SlackGive your agents full access to Slack.](/integrations/slack/)[![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)Salesforce + ApolloGive your agents full access to Apollo.](/integrations/apollo/)[![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Salesforce + AttioGive your agents full access to Attio.](/integrations/attio/) FAQ ## Questions, answered ### How do I connect Salesforce? ### What can an agent reach in Salesforce? ### How do Salesforce events reach Helios? ### Which Salesforce editions work? ## Put an agent on Salesforce. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Sentry Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/sentry Description: Agents triage new issues, read stack traces and recent events, resolve or archive what is handled, and report on releases. Workflows can start from supported issue, alert, Seer, and comment webhooks. [← All integrations](/integrations/) Developer tools # Read and update Sentry issues from your workflows. Agents triage new issues, read stack traces and recent events, resolve or archive what is handled, and report on releases. Workflows can start from supported issue, alert, Seer, and comment webhooks. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Sentry REST API The full surface, searched at run time. Connect with * API key * Your own OAuth app Use the token of a Sentry internal integration, or your own public integration through OAuth. For triggers, point the same integration's webhook at Helios. Event triggers Yes · 6 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/sentry/) What the agent can do ## What agents do with Sentry Helios searches the Sentry REST API at run time. The agent finds the endpoint the task needs and calls it. * Call Sentry's REST API with the connected integration's permissions. * Find the newest or most frequent issues in a project, environment, or release. * Read an issue's events, stack trace, breadcrumbs, and tags. * Resolve, archive, assign, or delete issues, and change their priority. * Read an issue's comments and reply to them. * Create releases and deploys, and manage alerts and monitors. * Start a run when an issue changes, an error arrives, an alert fires, Seer reaches a stage of a fix, a mobile build is processed, or someone comments. Examples ## Tasks you can hand to a Sentry agent ### Investigate a metric monitor alert When error rates cross a threshold, the agent checks what shipped recently and posts what it found to the on-call channel. sentry · metric\_alert.triggered When a metric monitor's alert fires, compare it with recent deploys and post a summary to #oncall. 1. sentry·read the alert and its query 2. sentry·list releases deployed in the last hour 3. sentry·find the issues that grew the most 4. slack·post a summary to #oncall ✓Error spike traced to release 2026.10.1 * Errors rose from 40 to 900 a minute after the 14:05 deploy * Most come from one new issue in the payments service * Posted to #oncall with a link to the release ### Clean up stale issues A scheduled agent reviews unresolved issues that have not been seen in weeks and resolves or archives them. Mondays at 9:00am Every Monday, resolve issues not seen in 30 days and archive known noisy ones. 1. sentry·list unresolved issues last seen 30+ days ago 2. sentry·resolve the stale issues 3. sentry·archive known noisy issues until they escalate 4. slack·post what changed to #eng ✓Weekly Sentry cleanup * Resolved 37 issues not seen in 30 days * Archived 5 browser extension errors Event triggers ## Start a run on Sentry events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | --------------------------- | ----------------------------------------------------------------------------------------------------- | | issue.created | A new issue appears in a project - the moment to triage it and file a ticket. | | issue\_alert.triggered | An issue alert sends a notification to Helios. Filter on the project, environment, or alert name. | | issue.unresolved | A resolved issue regresses or an archived one escalates, so an agent can find what changed. | | activity\_alert.triggered | An alert fires when an issue resolves, regresses, or reaches a Seer stage, so an agent can follow up. | | seer.root\_cause\_completed | Seer finds the root cause of an issue, so an agent can file a ticket with it. | | comment.created | Someone comments on an issue, so an agent can pick up the request. | Works with ## Sentry works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [Sentry + GitHubGive your agents full access to GitHub.](/integrations/github/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Sentry + SlackGive your agents full access to Slack.](/integrations/slack/) FAQ ## Questions, answered ### How do I connect Sentry? ### What can an agent reach in Sentry? ### Which Sentry events can trigger an agent? ### Does it work with the EU region or self-hosted Sentry? ## Put an agent on Sentry. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Shopify Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/shopify Description: Agents can search the GraphQL Admin API, inspect orders and update products, customers and inventory within the app’s granted permissions. [← All integrations](/integrations/) E-commerce ![](/static/img/assets/shopify-light.svg)![](/static/img/assets/shopify-dark.svg) # Manage store operations with Shopify agents. Agents can search the GraphQL Admin API, inspect orders and update products, customers and inventory within the app’s granted permissions. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Shopify GraphQL Admin API 2026-10 The full surface, searched at run time. Connect with * API key * Your own OAuth app Connect one store with a custom app Admin API token and API secret key, or authorize your own Shopify app. Event triggers Yes · 3 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/shopify/) What the agent can do ## What agents do with Shopify Helios searches the Shopify GraphQL Admin API 2026-10 at run time. The agent finds the endpoint the task needs and calls it. * Read and update products and inventory. * Inspect orders, customers and fulfillment. * Work with discounts, returns and store content. * Start workflows from available Shopify webhook topics. Examples ## Tasks you can hand to a Shopify agent ### Review new orders Inspect incoming orders and prepare a fulfillment summary. Shopify order created Review the new order and summarize items that need fulfillment. 1. shopify·Read the order and fulfillment status ✓Order reviewed * Items and fulfillment status summarized. Event triggers ## Start a run on Shopify events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ------------------------ | -------------------------------- | | order.created | An order is created. | | product.updated | A product changes. | | inventory\_level.updated | Inventory changes at a location. | Works with ## Shopify works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Shopify + SlackGive your agents full access to Slack.](/integrations/slack/)[![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Shopify + AttioGive your agents full access to Attio.](/integrations/attio/)[Shopify + StripeGive your agents full access to Stripe.](/integrations/stripe/) FAQ ## Questions, answered ### Which credentials do I need? ### Are all webhook topics available to every store? ## Put an agent on Shopify. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Slack Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/slack Description: Agents read channels, follow threads, search history, and post where your team already works. Slack message events let an agent answer the moment a question lands, and channel filters on triggers keep each agent scoped to the conversations that matter. [← All integrations](/integrations/) Communication ![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg) # Give your agents full access to Slack. Agents read channels, follow threads, search history, and post where your team already works. Slack message events let an agent answer the moment a question lands, and channel filters on triggers keep each agent scoped to the conversations that matter. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Slack Web API The full surface, searched at run time. Connect with * Helios OAuth app * Your own OAuth app Each person authorizes once after the workspace installs the app. Event triggers Yes · 2 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/slack/) What the agent can do ## What agents do with Slack Helios searches the Slack Web API at run time. The agent finds the endpoint the task needs and calls it. * Search Slack's entire API surface at run time and call any endpoint within your scopes. * Read channel history and thread replies, including files and attachments. * Post messages, thread replies, and rich blocks; update or delete what the agent posted. * Search across the workspace to reconstruct what happened and who said it. * React with emoji, pin messages, and manage channel membership. * Trigger on new messages with a channel filter, so one agent watches one room. Examples ## Tasks you can hand to a Slack agent ### Answer support questions in channel An agent watches your support channel, searches your docs and past threads, and replies with a real answer plus a link. slack · new message in #support Watch #support. When someone asks a question, answer it from our docs and past threads. 1. slack·read the thread in #support 2. notion·search internal help center 3. slack·search prior threads for the same question 4. slack·reply in thread ✓Replied in thread * Answered the SSO group-mapping question * Linked to the SCIM setup doc * Tagged @ops because the customer is on Enterprise ### Summarize a busy channel A scheduled agent reads everything that happened, separates decisions from chatter, and posts a digest with open questions called out. Weekdays at 6:00pm Every evening, summarize #product: decisions made, open questions, who owns what. 1. slack·read 24h of #product history 2. slack·expand threads with 3+ replies 3. slack·post digest to #product-digest ✓#product · Mar 5 * 3 decisions, including shipping the export beta on Friday * 2 open questions awaiting @dana * 1 escalation moved to #incidents ### Route escalations to the right owner The agent recognizes an escalation, pulls the customer record, and pages the owner with everything they need in one message. slack · new message in #customer-issues When a message looks like an escalation, look up the account and page the owner. 1. slack·read message and thread context 2. attio·look up the account record 3. stripe·check plan and payment status 4. slack·DM the account owner with context ✓Escalation routed * Account: Northwind · Growth plan · $4.2k MRR * Owner @priya paged with the thread link * Follow-up task created in Attio ### Broadcast what shipped When a release publishes, the agent turns the notes into a message your whole company can read and posts it. github · release.published When we publish a release, announce it in #general in plain language. 1. github·read release v2.8.0 notes 2. slack·post announcement to #general ✓Announced v2.8.0 * Highlighted scheduled exports and the faster search * Linked the changelog and the upgrade note ### Run a standup without the meeting The agent reads yesterday's commits and merged work, drafts a standup per person, and posts it before the day starts. Weekdays at 9:00am Every weekday at 9am, post a standup from yesterday's GitHub activity. 1. github·list commits and merged PRs since yesterday 2. github·list PRs still awaiting review 3. slack·post standup to #standup ✓Standup · Mar 6 * 5 engineers shipped 12 PRs * @sam blocked on a review for #2841 * Nothing red in CI overnight Event triggers ## Start a run on Slack events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | --------------- | -------------------------------------------------------------------------------------------------- | | message.channel | A new message lands in a public channel. Filter by channel so one agent watches one room. | | message.group | A new message lands in a private channel the connection has joined, with the same channel filters. | Works with ## Slack works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [Slack + GitHubGive your agents full access to GitHub.](/integrations/github/)[![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)Slack + PlainGive your agents full access to Plain.](/integrations/plain/)[Slack + NotionGive your agents full access to Notion.](/integrations/notion/) Templates ## Ready-to-run Slack workflows Copy the prompt, connect your tools, and start a run. [SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.slack · message.channel![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/templates/slack-support-triage/)[SupportPlain thread triageTriages every new Plain thread on arrival. Labels, priority, a draft reply, and an internal note with what it checked.plain · thread.thread\_created![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/plain-thread-summarizer/)[EngineeringPull request reviewerReviews every pull request against your conventions and leaves inline comments only where it found something concrete.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/pr-review-digest/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes a draft release on GitHub, and files a changelog entry in Notion.github · tag.created![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/github-release-notes/)[EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup to Slack every weekday morning.Weekdays at 9:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/daily-standup-digest/)[EngineeringIncident postmortem drafterRebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/incident-postmortem-drafter/)[Sales & RevOpsFailed payment recoveryFinds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/stripe-failed-payment-recovery/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to find the accounts drifting toward the exit.Mondays at 7:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/churn-risk-watchlist/)[Sales & RevOpsInbound lead enrichmentEnriches every new signup, scores it against your ICP by reading the company's own website, and routes the strong fits.Signup webhook![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/apollo-lead-enrichment/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing company fields, and flags deals that have gone quiet. Every night.Nightly at 2:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/attio-crm-hygiene/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out.Mondays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/weekly-metrics-report/)[MarketingReddit brand monitorSweeps the subreddits where your customers gather, judges which threads deserve a reply, and brings you a shortlist.Every 4 hours![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/reddit-brand-monitor/)[MarketingResearch brief writerResearches a topic across the live web and returns a sourced draft in your voice, with the open questions flagged.Run on demand![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)![](/static/img/assets/apify.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/google-docs-brief-writer/)[SupportDocumentation freshness auditChecks your written docs against the codebase every month and comments on the pages that have gone stale.Monthly on the 1st![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/notion-docs-freshness-audit/) Use cases ## Where Slack agents fit [SupportSupport triageA workflow reads each new thread as it arrives. It finds the customer, checks the plan and billing state, sets labels and priority, and drafts a reply from your docs.plain · thread.thread\_created![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/use-cases/support-triage/)[Sales & RevOpsLead enrichmentA signup or form response fires a webhook. The workflow enriches the person and company, scores fit against your definition, creates the CRM record, and tells the right rep.Signup webhook![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/typeform-light.svg)![](/static/img/assets/typeform-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/lead-enrichment/)[EngineeringPull request reviewA workflow reads each diff against your conventions and leaves a real review. A second workflow on a schedule posts the week's merged work, review backlog, and CI health.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/pr-review-digest/)[EngineeringIncident summariesA workflow rebuilds the timeline from your incident channel and the deploys around it. It names the likely change and drafts the write-up with the facts in place.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/incident-summaries/)[OperationsDatabase reportingA workflow reads your schema, writes the SQL, runs it, checks the results in its sandbox, and posts a report to the channel your team reads.Weekdays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/database-reporting/)[MarketingResearch briefsA workflow searches the web, reads what it finds, and writes a draft with every claim linked to its source. Give it your prior work and the draft matches your voice.Run on demand![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)![](/static/img/assets/apify.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/content-pipeline/)[MarketingCommunity monitoringA workflow sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space. It picks the threads worth a reply and brings them to your team.Every 4 hours![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/community-monitoring/) FAQ ## Questions, answered ### How do I connect Slack? ### What can an agent reach in Slack? ### Can a Slack message trigger an agent? ### Can I keep an agent scoped to one channel? ### Does Slack cost extra? ## Put an agent on Slack. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Square Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/square Description: Agents use Square's REST API to work with payments, orders, customers, bookings and inventory. Square events can start workflows for the connected merchant. [← All integrations](/integrations/) Billing ![](/static/img/assets/square-light.svg)![](/static/img/assets/square-dark.svg) # Connect payments, orders and inventory to your workflows. Agents use Square's REST API to work with payments, orders, customers, bookings and inventory. Square events can start workflows for the connected merchant. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Square REST API, version 2026-09-16 The full surface, searched at run time. Connect with * API key * Your own OAuth app Use a personal access token for your own account or your Square OAuth app for sellers. OAuth triggers also require the application's personal access token. Event triggers Yes · 4 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/square/) What the agent can do ## What agents do with Square Helios searches the Square REST API, version 2026-09-16 at run time. The agent finds the endpoint the task needs and calls it. * Read payments, refunds and payouts. * Create and update orders, customers and catalog items. * Manage bookings, subscriptions and inventory with your account's permissions. * Connect production or Sandbox accounts. Examples ## Tasks you can hand to a Square agent ### Review payment activity Use a payment event to retrieve the related order and prepare an operations summary. Square payment.created Summarize this payment and its related order. 1. square·Retrieve the payment. 2. square·Read the related order. ✓Payment summary * Payment status, amount and order details are ready for review. Event triggers ## Start a run on Square events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ------------------------ | ------------------------ | | payment.created | A payment is created. | | order.updated | An order changes. | | inventory\_count.updated | Inventory counts change. | | booking.created | A booking is created. | Works with ## Square works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [Square + StripeGive your agents full access to Stripe.](/integrations/stripe/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Square + SlackGive your agents full access to Slack.](/integrations/slack/)[![](/static/img/assets/google-sheets-light.svg)![](/static/img/assets/google-sheets-dark.svg)Square + Google SheetsGive your agents full access to Google Sheets.](/integrations/google-sheets/) FAQ ## Questions, answered ### Can I use Sandbox? ### Which events can start workflows? ## Put an agent on Square. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Stripe Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/stripe Description: Agents read customers, subscriptions, invoices, and charges, and act on what they find. Billing operations that used to be a person with a spreadsheet become a task that runs every night. [← All integrations](/integrations/) Billing # Give your agents full access to Stripe. Agents read customers, subscriptions, invoices, and charges, and act on what they find. Billing operations that used to be a person with a spreadsheet become a task that runs every night. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Stripe API The full surface, searched at run time. Connect with * API key Event triggers Not yet Manual, schedule, and signed webhook are available. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/stripe/) What the agent can do ## What agents do with Stripe Helios searches the Stripe API at run time. The agent finds the endpoint the task needs and calls it. * Search Stripe's entire API surface at run time and call any endpoint your key allows. * Read customers, subscriptions, invoices, charges, disputes, and payouts. * Reconcile billing data against your own database and your CRM. * Act on failed payments: notify, retry, and escalate on your rules. * Compute revenue metrics in the sandbox and publish them where the team reads. * Use restricted keys so an agent reads without any ability to move money. Examples ## Tasks you can hand to a Stripe agent ### Recover failed payments When a charge fails, the agent checks the account, emails the right person with a working payment link, and tells the account owner. Hourly Every hour, find failed charges and start recovery. 1. stripe·list failed charges in the last hour 2. attio·look up account owner and contact 3. resend·send a payment update email 4. slack·notify owner in #revenue ✓3 failed payments handled * $2,340 at risk across 3 accounts * Emails sent with hosted update links * 1 enterprise account escalated to its owner ### Publish revenue metrics every morning The agent pulls charges and subscriptions, computes the metrics your team actually tracks, and posts them before standup. Weekdays at 8:00am Each morning, post MRR, new revenue, churn, and expansion to Slack. 1. stripe·list subscriptions and yesterday's charges 2. code·compute MRR, churn, expansion 3. slack·post to #revenue ✓Revenue · Mar 6 * MRR $412k · up 3.1% month to date * New $9.2k · Expansion $4.1k · Churn $2.3k * 2 accounts downgraded overnight ### Watch for churn risk The agent joins billing signals with product usage and support volume, and surfaces the accounts drifting toward the exit. Mondays at 7:00am Weekly, list accounts at risk of churn with the reason for each. 1. stripe·read subscriptions and payment history 2. postgres·pull 60-day usage per account 3. code·score risk and rank 4. attio·write risk score and note per account ✓11 accounts at risk * $38k ARR represented * 6 driven by usage decline, 3 by failed payments * Each has a suggested next action for its owner ### Reconcile billing against your database The agent compares what Stripe billed with what your own system says it should have billed, and reports every mismatch. Monthly on the 2nd Monthly, reconcile Stripe invoices against our usage records. 1. stripe·list last month's invoices 2. clickhouse·aggregate metered usage by account 3. code·diff billed vs recorded usage 4. google-sheets·write reconciliation tab ✓5 mismatches found * 2 accounts under-billed by $1,180 total * 3 accounts billed for a cancelled add-on * Everything else matches Triggers ## How a Stripe workflow starts Stripe does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook. ### Manual Run it from the app with an optional JSON payload. Every workflow supports this. ### Schedule A cron expression or a plain sentence such as every weekday at 9am. Times are UTC. ### Signed webhook A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes. Works with ## Stripe works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Stripe + AttioGive your agents full access to Attio.](/integrations/attio/)[![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)Stripe + ResendGive your agents full access to Resend.](/integrations/resend/)[Stripe + DatabasesGive your agents full access to your databases.](/integrations/databases/) Templates ## Ready-to-run Stripe workflows Copy the prompt, connect your tools, and start a run. [SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.slack · message.channel![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/templates/slack-support-triage/)[SupportPlain thread triageTriages every new Plain thread on arrival. Labels, priority, a draft reply, and an internal note with what it checked.plain · thread.thread\_created![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/plain-thread-summarizer/)[Sales & RevOpsFailed payment recoveryFinds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/stripe-failed-payment-recovery/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to find the accounts drifting toward the exit.Mondays at 7:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/churn-risk-watchlist/) Use cases ## Where Stripe agents fit [SupportSupport triageA workflow reads each new thread as it arrives. It finds the customer, checks the plan and billing state, sets labels and priority, and drafts a reply from your docs.plain · thread.thread\_created![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/use-cases/support-triage/)[OperationsBilling operationsA workflow watches Stripe for failed charges and starts recovery. A second one reconciles what you billed against what your own database recorded after the books close.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/billing-ops/)[Sales & RevOpsCRM data syncA workflow computes usage from your database, joins it with billing state and support volume, and writes the result onto each account record every night.Nightly at 1:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)](/use-cases/crm-data-sync/) FAQ ## Questions, answered ### How do I connect Stripe? ### What can an agent reach in Stripe? ### Can a Stripe event trigger an agent? ### Can an agent move money? ### Where is the Stripe key stored? ## Put an agent on Stripe. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Typeform Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/typeform Description: Agents read form definitions and every response that arrives, then act on what people told you - routing leads, filing requests, and answering the person who filled it in. [← All integrations](/integrations/) Forms ![](/static/img/assets/typeform-light.svg)![](/static/img/assets/typeform-dark.svg) # Give your agents full access to Typeform. Agents read form definitions and every response that arrives, then act on what people told you - routing leads, filing requests, and answering the person who filled it in. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Typeform API v1 The full surface, searched at run time. Connect with * Helios OAuth app * Your own OAuth app * API key Event triggers Not yet Manual, schedule, and signed webhook are available. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/typeform/) What the agent can do ## What agents do with Typeform Helios searches the Typeform API v1 at run time. The agent finds the endpoint the task needs and calls it. * Search Typeform's entire API surface at run time and call any endpoint your credential allows. * List forms and read their questions, logic, and fields. * Fetch responses with filters, including hidden fields and metadata. * Route each response by its content to the right owner or system. * Enrich the respondent before anyone sees the submission. * Start a run the instant a response arrives via a Typeform webhook. Examples ## Tasks you can hand to a Typeform agent ### Route demo requests to the right rep A response arrives, the agent enriches the company, decides who owns the territory, and creates the record with a summary already written. Typeform response webhook For each demo request, enrich, score, and route it to the right owner. 1. typeform·read the submitted response 2. apollo·enrich the company and person 3. attio·create the deal and assign an owner 4. slack·notify @dana in #inbound ✓Demo request routed * Northwind · 240 employees · Series B * Fit score 87 · assigned to @dana * Summary of their stated use case attached ### Turn survey responses into themes The agent reads every open-text answer, clusters them, and reports what people actually said. Fridays at 2:00pm Weekly, cluster open-text survey answers and summarize the themes. 1. typeform·fetch 214 responses from this week 2. code·cluster open-text answers 3. notion·write \`Survey Themes\` entry ✓214 responses · 5 themes * Setup friction is the top theme (61 mentions) * Pricing clarity second (38) * Verbatim quotes attached per theme ### File support requests from a form Requests submitted through a form become real support threads with the customer already identified and the priority set. Typeform response webhook Turn each support form response into a Plain thread with priority set. 1. typeform·read the response and hidden fields 2. plain·find or create the customer 3. plain·create thread with labels and priority ✓Thread created * Customer matched by email * Labeled \`billing\` · priority \`high\` * Full form response attached as a note ### Follow up while it is still warm The agent writes a reply that references what the person actually wrote, and sends it within minutes of the submission. Typeform response webhook Reply to each form submission within 5 minutes, referencing their answers. 1. typeform·read the response 2. apollo·enrich the respondent 3. resend·send a tailored reply ✓Reply sent in 3 minutes * Referenced their stated goal of consolidating tools * Included the two docs that match their stack Triggers ## How a Typeform workflow starts Typeform does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook. ### Manual Run it from the app with an optional JSON payload. Every workflow supports this. ### Schedule A cron expression or a plain sentence such as every weekday at 9am. Times are UTC. ### Signed webhook A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes. Works with ## Typeform works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Typeform + AttioGive your agents full access to Attio.](/integrations/attio/)[![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)Typeform + ApolloGive your agents full access to Apollo.](/integrations/apollo/)[![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)Typeform + PlainGive your agents full access to Plain.](/integrations/plain/) Use cases ## Where Typeform agents fit [Sales & RevOpsLead enrichmentA signup or form response fires a webhook. The workflow enriches the person and company, scores fit against your definition, creates the CRM record, and tells the right rep.Signup webhook![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/typeform-light.svg)![](/static/img/assets/typeform-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/lead-enrichment/) FAQ ## Questions, answered ### How do I connect Typeform? ### What can an agent reach in Typeform? ### Can a form response trigger an agent? ### How do I verify the webhook is really from Typeform? ### Does Typeform access cost extra? ## Put an agent on Typeform. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Vercel Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/vercel Description: Agents read build logs, explain failed deployments, redeploy, and manage environment variables, domains, and feature flags. A workflow can start when a deployment fails or is promoted, a certificate renewal fails, an environment variable changes, or Vercel raises an alert. [← All integrations](/integrations/) Developer tools # Connect your agents to Vercel. Agents read build logs, explain failed deployments, redeploy, and manage environment variables, domains, and feature flags. A workflow can start when a deployment fails or is promoted, a certificate renewal fails, an environment variable changes, or Vercel raises an alert. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Vercel REST API The full surface, searched at run time. Connect with * API key * Your own OAuth app Use an access token or your own Vercel integration through OAuth. Triggers with a token need a Pro or Enterprise team. With your own integration, you point its webhook at Helios. Event triggers Yes · 9 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/vercel/) What the agent can do ## What agents do with Vercel Helios searches the Vercel REST API at run time. The agent finds the endpoint the task needs and calls it. * Call Vercel REST API endpoints with your connection's permissions. * Read deployment build logs to investigate failures. * List projects and deployments and report their state. * Redeploy a deployment, promote one to production, or roll back. * Read, add, and update environment variables for each environment. * Start a run on deployment, rollback, domain, certificate, environment variable, rolling release, feature flag, alert, and firewall events. Examples ## Tasks you can hand to a Vercel agent ### Diagnose failed deployments When a build fails, the agent reads the logs, investigates the related changes, and opens an issue with the cause. vercel · deployment.failed When a production deployment fails, find the cause and file an issue. 1. vercel·read the build logs 2. github·compare the commit with the last good one 3. github·open an issue with the error and related changes ✓GitHub issue filed * \`Module not found: @/lib/flags\` in the build step * The import came from the last merged pull request * Assigned to the pull request's author ### Share preview links When a preview deployment is ready, the agent posts the link and what changed to the team's channel. vercel · deployment.succeeded When a preview deployment of the web project is ready, post the link to Slack. 1. vercel·read the deployment and its branch 2. github·summarize the pull request 3. slack·post to #web-reviews ✓Preview shared * Branch \`feature/checkout\` is ready to review * The pull request moves checkout to the new pricing table ### Write release notes on promotion When a deployment reaches production, the agent collects the changes since the last release and posts release notes. vercel · deployment.promoted When a deployment is promoted to production, post release notes. 1. vercel·find the previous production deployment 2. github·list the commits between the two 3. slack·post the notes to #releases ✓Release notes posted * 6 merged pull requests * New checkout flow and two bug fixes ### Audit environment variables A scheduled agent compares environment variables across projects and environments and reports gaps. Mondays at 9:00am Every Monday, check that each project has the same keys in Preview and Production. 1. vercel·list projects 2. vercel·read each project's environment variables 3. code·compare keys by environment 4. slack·post the gaps to #platform ✓2 projects with gaps * \`web\` is missing \`STRIPE\_WEBHOOK\_SECRET\` in Preview * \`docs\` has \`SEARCH\_API\_KEY\` only in Production Event triggers ## Start a run on Vercel events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | --------------------------- | ------------------------------------------------------------------------------------- | | deployment.failed | A build failed. Filter by project, environment, or branch, then diagnose it. | | deployment.succeeded | A deployment finished building, so an agent can check it or share the preview link. | | deployment.promoted | A deployment was promoted to production. | | deployment.created | A deployment started building. | | deployment.canceled | A deployment was canceled before it finished. | | deployment.rolled\_back | Vercel accepted a rollback request, so an agent can open an incident. | | env\_variable.updated | An environment variable changed in a project. | | certificate.renewal\_failed | A certificate didn't renew, so an agent can check the domain's DNS before it expires. | | alert.triggered | Vercel raised an alert about unusual traffic or errors in a project. | Works with ## Vercel works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [Vercel + GitHubGive your agents full access to GitHub.](/integrations/github/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Vercel + SlackGive your agents full access to Slack.](/integrations/slack/) FAQ ## Questions, answered ### How do I connect Vercel? ### What can an agent reach in Vercel? ### Which Vercel events can trigger an agent? ### Do triggers work on the Hobby plan? ## Put an agent on Vercel. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # WarpBuild Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/warpbuild Description: Agents read your CI runners, jobs, and spend, and turn build infrastructure into something you can ask questions about. Combine it with GitHub and an agent can explain a slow pipeline and what it costs you. [← All integrations](/integrations/) Developer tools ![](/static/img/assets/warpbuild-light.svg)![](/static/img/assets/warpbuild-dark.svg) # Give your agents full access to WarpBuild. Agents read your CI runners, jobs, and spend, and turn build infrastructure into something you can ask questions about. Combine it with GitHub and an agent can explain a slow pipeline and what it costs you. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach WarpBuild API v1 The full surface, searched at run time. Connect with * API key Event triggers Not yet Manual, schedule, and signed webhook are available. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/warpbuild/) What the agent can do ## What agents do with WarpBuild Helios searches the WarpBuild API v1 at run time. The agent finds the endpoint the task needs and calls it. * Search WarpBuild's entire API surface at run time and call any endpoint your token allows. * Read runner fleets, job history, queue times, and durations. * Pull spend data and attribute it to repositories and workflows. * Correlate CI runs with the GitHub pull requests that caused them. * Analyze trends in the sandbox and publish a report to Slack or a sheet. * Alert when queue times or spend cross the thresholds you name. Examples ## Tasks you can hand to a WarpBuild agent ### Report on CI spend every week The agent attributes build spend to the repositories and workflows driving it, and shows what changed since last week. Mondays at 7:00am Weekly, report CI spend by repo and workflow with week-over-week change. 1. warpbuild·pull last week's job and spend data 2. code·attribute spend by repo and workflow 3. slack·post report to #platform ✓CI spend · week of Mar 3 * $3,140 total · up 12% week over week * \`api\` integration tests drove 41% of spend * One workflow doubled after a matrix change ### Find the slow jobs The agent ranks jobs by duration and queue time, correlates them with recent changes, and names the ones worth fixing first. Find the slowest CI jobs and what made them slow. 1. warpbuild·list jobs by p95 duration 2. github·find the PRs that changed those workflows 3. code·correlate duration with change dates ✓3 jobs worth fixing * \`e2e\` p95 rose from 8m to 19m after #2790 * \`lint\` spends 60% of its time on install * \`build-matrix\` queues 4m before it starts ### Alert on a spend spike A daily agent checks yesterday's spend against the trend and speaks up only when something is genuinely off. Daily at 6:00am Daily, alert if CI spend exceeds the 14-day trend by more than 30%. 1. warpbuild·pull spend for the last 14 days 2. code·compare yesterday against the trend 3. slack·alert #platform with the top contributors ✓Spend spike detected * Yesterday $780 against a $520 trend * Driven by 61 reruns of \`e2e\` on one branch ### Explain CI health to the team The agent turns runner data into a readable picture of how CI is treating engineers: queue times, flakes, and where time goes. Fridays at 4:00pm Every Friday, summarize CI health for the engineering team. 1. warpbuild·aggregate queue times and outcomes 2. github·count reruns per workflow 3. slack·post to #engineering ✓CI health · week of Mar 3 * Median queue 22s · p95 3m 10s * Pass rate 94%, down from 97% * \`e2e\` accounts for most reruns Triggers ## How a WarpBuild workflow starts WarpBuild does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook. ### Manual Run it from the app with an optional JSON payload. Every workflow supports this. ### Schedule A cron expression or a plain sentence such as every weekday at 9am. Times are UTC. ### Signed webhook A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes. Works with ## WarpBuild works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [WarpBuild + GitHubGive your agents full access to GitHub.](/integrations/github/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)WarpBuild + SlackGive your agents full access to Slack.](/integrations/slack/)[WarpBuild + DatabasesGive your agents full access to your databases.](/integrations/databases/) FAQ ## Questions, answered ### How do I connect WarpBuild? ### What can an agent reach in WarpBuild? ### Can a WarpBuild event trigger an agent? ### Does this work alongside the GitHub integration? ### Does WarpBuild access cost extra? ## Put an agent on WarpBuild. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Webflow Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/webflow Description: Agents use the Webflow API to manage CMS content, pages, forms, assets and ecommerce. Webhooks can start workflows when content changes or customers submit forms and orders. [← All integrations](/integrations/) Web data ![](/static/img/assets/webflow-light.svg)![](/static/img/assets/webflow-dark.svg) # Manage website content and respond to Webflow events. Agents use the Webflow API to manage CMS content, pages, forms, assets and ecommerce. Webhooks can start workflows when content changes or customers submit forms and orders. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Webflow Data API v2 and beta The full surface, searched at run time. Connect with * API key * Your own OAuth app Connect a site API token or authorize your own Webflow Data Client app. Event triggers Yes · 17 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/webflow/) What the agent can do ## What agents do with Webflow Helios searches the Webflow Data API v2 and beta at run time. The agent finds the endpoint the task needs and calls it. * Create, update and publish CMS items. * Read form submissions and manage pages and assets. * Manage ecommerce orders and inventory. * Use Enterprise and beta endpoints when your account permits them. Examples ## Tasks you can hand to a Webflow agent ### Route form submissions Read a new submission and create a CRM record. Webflow form submitted Create an Attio lead from a Webflow form submission. 1. webflow·Read the form submission. 2. attio·Create a lead with the submitted details. ✓Lead created Event triggers ## Start a run on Webflow events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ---------------------------- | ------------------------------ | | form.submitted | A visitor submits a form. | | site.published | A site or page is published. | | page.created | A page is created. | | page.metadata\_updated | Page metadata changes. | | page.deleted | A page is deleted. | | collection\_item.created | A CMS item is created. | | collection\_item.updated | CMS content changes. | | collection\_item.deleted | A CMS item is deleted. | | collection\_item.published | A CMS item is published. | | collection\_item.unpublished | A CMS item is unpublished. | | order.created | An ecommerce order is created. | | order.updated | An ecommerce order changes. | | inventory.updated | Ecommerce inventory changes. | | comment.created | A comment or reply is created. | | branch.created | A page branch is created. | | branch.merged | A page branch is merged. | | branch.deleted | A page branch is deleted. | Works with ## Webflow works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Webflow + AttioGive your agents full access to Attio.](/integrations/attio/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Webflow + SlackGive your agents full access to Slack.](/integrations/slack/) FAQ ## Questions, answered ### How are Webflow triggers connected? ### Can I use a site API token? ## Put an agent on Webflow. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Wise Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/wise Description: Connect Wise so agents can look up transfers, manage recipients, reconcile multi-currency balances, and respond to supported profile events. [← All integrations](/integrations/) Billing ![](/static/img/assets/wise-light.svg)![](/static/img/assets/wise-dark.svg) # Track international transfers and reconcile balances Connect Wise so agents can look up transfers, manage recipients, reconcile multi-currency balances, and respond to supported profile events. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Wise Platform API, 2026Q4 and legacy The full surface, searched at run time. Connect with * API key * Your own OAuth app Personal API tokens are the default. Partner OAuth requires Wise onboarding and mTLS. Event triggers Yes · 34 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/wise/) What the agent can do ## What agents do with Wise Helios searches the Wise Platform API, 2026Q4 and legacy at run time. The agent finds the endpoint the task needs and calls it. * Look up transfers, fees, exchange rates and recipients through the indexed API. * Reconcile balances and investigate failed or refunded payments within your token's permissions. * Start workflows from supported profile webhooks with filters for profile, resource and status. Examples ## Tasks you can hand to a Wise agent ### Investigate a failed payout Use a payout failure event to inspect the transfer and summarize the reason for review. Wise payout failed Investigate this failed Wise payout 1. wise·Read the transfer and its payout failure details 2. wise·Look up the recipient and payment status ✓Payout investigation * Transfer status and failure reason prepared for review. Event triggers ## Start a run on Wise events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ------------------------------------------------ | --------------------------------------- | | transfer.active\_cases\_updated | Transfer active cases. | | transfer.refunded | Transfer refund. | | transfer.payout\_failed | Transfer payout failure. | | transfer.state\_changed | Transfer state change. | | account\_details\_order.state\_changed | Account details order state change. | | account\_details\_payment.state\_changed | Account details payment state change. | | allocation.state\_changed | Allocations state changed. | | card.status\_changed | Card status change. | | card.production\_status\_changed | Card production status change. | | card.3ds\_challenge\_requested | 3DS challenge. | | card\_order.status\_changed | Card order status change. | | card\_transaction.state\_changed | Card transaction state change. | | card.provisioning\_verification\_requested | Cards manual provisioning verification. | | hold\_limit\_breach.updated | Hold limit breach update. | | profile.additional\_verification\_state\_changed | Additional verification state change. | | profile.overdraft\_threshold\_reached | Overdraft limit threshold. | | profile.state\_changed | Profile state change. | | profile.verification\_state\_changed | Verification state change. | | kyc\_review.state\_changed | KYC review state change. | | user.state\_changed | User state change. | | balance.updated | Balance update. | | balance.state\_changed | Balance account state change. | | batch\_payment.state\_changed | Batch payment initiations state change. | | support\_case.changed | Partner support case changed. | | settlement.funds\_received | Settlement funds received. | | swift\_payment.credited | Swift receive credit. | | swift\_message.received | Swift message received. | | transaction\_dispute.updated | Transaction disputes update. | | bulk\_settlement.payment\_received | Bulk settlement payment received. | | incoming\_transfer.credited | Incoming transfer credited. | | recipient.state\_changed | Recipient state change. | | balance.credited | Balance credited. | | payment\_instrument.status\_changed | Payment instrument status changed. | | payin.status\_changed | Payin status changed. | Works with ## Wise works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [Wise + StripeGive your agents full access to Stripe.](/integrations/stripe/)[![](/static/img/assets/google-sheets-light.svg)![](/static/img/assets/google-sheets-dark.svg)Wise + Google SheetsGive your agents full access to Google Sheets.](/integrations/google-sheets/) FAQ ## Questions, answered ### Which Wise webhooks can start workflows? ### Can agents complete actions that require strong customer authentication? ## Put an agent on Wise. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # WooCommerce Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/woocommerce Description: Agents use your store's REST API to manage orders, products, customers and coupons. Core WooCommerce webhooks can start workflows. [← All integrations](/integrations/) E-commerce ![](/static/img/assets/woocommerce-light.svg)![](/static/img/assets/woocommerce-dark.svg) # Manage your store from orders to inventory. Agents use your store's REST API to manage orders, products, customers and coupons. Core WooCommerce webhooks can start workflows. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach WooCommerce REST API v3 The full surface, searched at run time. Connect with * API key Connect your HTTPS store with a Read/Write consumer key and secret. Event triggers Yes · 16 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/woocommerce/) What the agent can do ## What agents do with WooCommerce Helios searches the WooCommerce REST API v3 at run time. The agent finds the endpoint the task needs and calls it. * Read and update orders. Create and read order notes and refunds. * Manage products, variations, inventory and categories. * Create and update customers and coupons. * Inspect reports, shipping, taxes and store settings. Examples ## Tasks you can hand to a WooCommerce agent Event triggers ## Start a run on WooCommerce events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ----------------- | ----------------------- | | order.created | An order is created. | | order.updated | An order changes. | | order.deleted | An order is deleted. | | order.restored | An order is restored. | | product.created | A product is created. | | product.updated | A product changes. | | product.deleted | A product is deleted. | | product.restored | A product is restored. | | product.published | A product is published. | | customer.created | A customer is created. | | customer.updated | A customer changes. | | customer.deleted | A customer is deleted. | | coupon.created | A coupon is created. | | coupon.updated | A coupon changes. | | coupon.deleted | A coupon is deleted. | | coupon.restored | A coupon is restored. | Works with ## WooCommerce works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [WooCommerce + StripeGive your agents full access to Stripe.](/integrations/stripe/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)WooCommerce + SlackGive your agents full access to Slack.](/integrations/slack/)[![](/static/img/assets/google-sheets-light.svg)![](/static/img/assets/google-sheets-dark.svg)WooCommerce + Google SheetsGive your agents full access to Google Sheets.](/integrations/google-sheets/) FAQ ## Questions, answered ### How do I connect my store? ### Which events can start workflows? ## Put an agent on WooCommerce. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Workable Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/workable Description: Agents search Workable's API to work with jobs, candidates, employees, requisitions, offers, time off, time tracking, and review templates, within your token's permissions. [← All integrations](/integrations/) HR ![](/static/img/assets/workable-light.svg)![](/static/img/assets/workable-dark.svg) # Manage recruiting and employee workflows with Workable. Agents search Workable's API to work with jobs, candidates, employees, requisitions, offers, time off, time tracking, and review templates, within your token's permissions. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Workable REST API v3 The full surface, searched at run time. Connect with * API key * Your own OAuth app Account API tokens are the default. OAuth requires Workable partner approval and remains untested. Event triggers Yes · 10 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/workable/) What the agent can do ## What agents do with Workable Helios searches the Workable REST API v3 at run time. The agent finds the endpoint the task needs and calls it. * Find jobs and candidates, add comments, and move candidates between stages. * Read and update employee records and documents with the required permissions. * Work with requisitions, offers, time off, time tracking, and review templates where your token and plan allow it. Examples ## Tasks you can hand to a Workable agent ### Review candidates entering a stage Start a workflow when a candidate moves, then retrieve the candidate and job details for a review. Candidate moved Summarize the candidate who entered the interview stage. 1. workable·Read the candidate and job details ✓Candidate summary * Experience, job requirements, and interview notes ready for review. Event triggers ## Start a run on Workable events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | -------------------- | ----------------------------------- | | candidate.created | A candidate was created. | | candidate.deleted | A candidate was deleted. | | candidate.moved | A candidate moved to another stage. | | employee.created | An employee was created. | | employee.updated | Employee details changed. | | employee.published | An employee profile was published. | | job.deleted | A job was deleted. | | onboarding.completed | An employee completed onboarding. | | timeoff.approved | A time off request was approved. | | timeoff.reverted | A time off request was reverted. | Works with ## Workable works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Workable + SlackGive your agents full access to Slack.](/integrations/slack/)[![](/static/img/assets/gmail-light.svg)![](/static/img/assets/gmail-dark.svg)Workable + GmailGive your agents full access to Gmail.](/integrations/gmail/)[![](/static/img/assets/google-sheets-light.svg)![](/static/img/assets/google-sheets-dark.svg)Workable + Google SheetsGive your agents full access to Google Sheets.](/integrations/google-sheets/) FAQ ## Questions, answered ### How do I connect Workable? ### What happens when I rotate my account token? ## Put an agent on Workable. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Zendesk Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/zendesk Description: Agents can read and update tickets, work with users and organizations, and manage Help Center content through your Zendesk account. Native webhook events can start workflows when your account permits the subscription. [← All integrations](/integrations/) Support ![](/static/img/assets/zendesk-light.svg)![](/static/img/assets/zendesk-dark.svg) # Triage tickets and keep support content current. Agents can read and update tickets, work with users and organizations, and manage Help Center content through your Zendesk account. Native webhook events can start workflows when your account permits the subscription. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Zendesk Support, Help Center, and Talk APIs The full surface, searched at run time. Connect with * API key * Your own OAuth app Enter your Zendesk account URL. Your own OAuth client must belong to that account unless Zendesk has approved it as a global client. Event triggers Yes · 5 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/zendesk/) What the agent can do ## What agents do with Zendesk Helios searches the Zendesk Support, Help Center, and Talk APIs at run time. The agent finds the endpoint the task needs and calls it. * Read tickets, comments, customer details, and ticket history. * Assign tickets, set priorities, add tags, and post replies. * Manage Help Center articles, sections, and community content. * Filter ticket events by status, priority, group, brand, or tags. Examples ## Tasks you can hand to a Zendesk agent ### Triage new support tickets Read the customer's request and history, then assign a group and priority. ticket.created Triage this new Zendesk ticket using the support team's routing rules. 1. zendesk·Read the ticket and requester history 2. zendesk·Set the support group, priority, and tags ✓Ticket triaged * Assigned to the support group with priority and tags. Event triggers ## Start a run on Zendesk events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ---------------------- | ----------------------------------- | | ticket.created | A ticket is created. | | ticket.status\_changed | A ticket changes status. | | ticket.comment\_added | A comment is added to a ticket. | | user.created | A user is created. | | article.published | A Help Center article is published. | Works with ## Zendesk works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Zendesk + SlackGive your agents full access to Slack.](/integrations/slack/)[Zendesk + GitHubGive your agents full access to GitHub.](/integrations/github/)[![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)Zendesk + PlainGive your agents full access to Plain.](/integrations/plain/) FAQ ## Questions, answered ### Can I connect with my own OAuth app? ### Does Helios register webhooks? ## Put an agent on Zendesk. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Zoho CRM Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/zoho-crm Description: Agents turn emails into leads, keep contacts and deals current, move deals through the pipeline, and log notes and follow-up tasks. Zoho CRM trigger events start an agent when a lead, contact, deal, or other record is created, updated, or deleted, or when a deal reaches a stage. [← All integrations](/integrations/) Sales & CRM # Manage Zoho CRM records and respond to record changes. Agents turn emails into leads, keep contacts and deals current, move deals through the pipeline, and log notes and follow-up tasks. Zoho CRM trigger events start an agent when a lead, contact, deal, or other record is created, updated, or deleted, or when a deal reaches a stage. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Zoho CRM REST API v8 The full surface, searched at run time. Connect with * Your own OAuth app Register a server-based client in the Zoho API Console. Check Admin access to let agents change settings and manage users. Outside the US data center, set the connection's base URL to your data center's API domain. Event triggers Yes · 4 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/zoho-crm/) What the agent can do ## What agents do with Zoho CRM Helios searches the Zoho CRM REST API v8 at run time. The agent finds the endpoint the task needs and calls it. * Call Zoho CRM APIs with the connected user's permissions and granted scopes. * Create, update, and delete records in modules your Zoho account can access. * Find records with search and COQL queries, and read their related lists. * Convert leads, move deals between stages, change owners, and update or delete many records at once. * Work with notes, tasks, tags, attachments, and email through the Zoho CRM API. * Export and import records in bulk. With Admin access, change fields, layouts, workflow rules, and users. * Start a run when a record in a built-in module is created, updated, or deleted, or when a deal moves to a stage. Examples ## Tasks you can hand to a Zoho CRM agent ### Qualify every new lead When a lead is created, the agent researches the company, fills in the missing fields, and leaves a note for the owner. zoho-crm · lead.created On each new lead, research the company, fill in industry and size, and add a note. 1. zoho-crm·read the lead 2. apollo·enrich the company and contact 3. zoho-crm·update industry and employee count 4. zoho-crm·add a note with talking points ✓Lead qualified: Dana Kim, Northwind * Logistics, 420 employees * Recently opened a second warehouse * Note added for the lead owner ### Hand off deals that reach Closed Won When a deal moves to Closed Won, the agent creates the onboarding task and tells the team, with the deal's context attached. zoho-crm · deal.updated When a deal moves to Closed Won, create the onboarding task and post the handoff to Slack. 1. zoho-crm·read the deal, account, and contacts 2. zoho-crm·create an onboarding task on the deal 3. slack·post the handoff to #customer-success ✓Northwind handed off * Onboarding task assigned to the CSM * Handoff posted with contract value and contacts ### Turn emails into leads The agent reads inbound emails, creates a lead for each new sender, and skips people who are already in the CRM. Every hour Every hour, create a lead for each new sender in the sales inbox. 1. gmail·read new emails in the sales inbox 2. zoho-crm·search leads and contacts by email 3. zoho-crm·create leads for the new senders ✓3 leads created * 2 senders were already contacts * Each new lead has the email attached as a note Event triggers ## Start a run on Zoho CRM events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | --------------- | ------------------------------------------------------------------------------- | | lead.created | A new lead arrives, so an agent can enrich it and route it. | | deal.updated | A deal changes. Filter on the fields that changed, or on the stage it moved to. | | meeting.created | A meeting is booked, so an agent can prepare a brief for it. | | contact.deleted | A contact is deleted, so an agent can clean up the systems that copied it. | Works with ## Zoho CRM works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/gmail-light.svg)![](/static/img/assets/gmail-dark.svg)Zoho CRM + GmailGive your agents full access to Gmail.](/integrations/gmail/)[![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Zoho CRM + SlackGive your agents full access to Slack.](/integrations/slack/)[![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)Zoho CRM + ApolloGive your agents full access to Apollo.](/integrations/apollo/) FAQ ## Questions, answered ### How do I connect Zoho CRM? ### My Zoho account is in Europe or India. Does that work? ### Which Zoho CRM events can trigger an agent? ## Put an agent on Zoho CRM. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Zoho Desk Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/zoho-desk Description: Agents can search tickets, update customers, maintain knowledge articles and respond to help desk events. [← All integrations](/integrations/) Support ![](/static/img/assets/zoho-desk-light.svg)![](/static/img/assets/zoho-desk-dark.svg) # Manage support work with Zoho Desk. Agents can search tickets, update customers, maintain knowledge articles and respond to help desk events. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Zoho Desk REST API The full surface, searched at run time. Connect with * Your own OAuth app Use your OAuth app or existing OAuth tokens, with the matching data centre and organization ID. Event triggers Yes · 3 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/zoho-desk/) What the agent can do ## What agents do with Zoho Desk Helios searches the Zoho Desk REST API at run time. The agent finds the endpoint the task needs and calls it. * Read and update support tickets and their threads. * Manage contacts, accounts and support activities. * Search and maintain knowledge articles. * Use supported administration and automation endpoints within the connected user's permissions. Examples ## Tasks you can hand to a Zoho Desk agent ### Triage new tickets Use ticket details to assign an owner and priority. ticket.created Review a new support ticket and route it to the right team. 1. zoho\_desk·Read ticket details 2. zoho\_desk·Update the assignee and priority ✓Ticket routed Event triggers ## Start a run on Zoho Desk events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ----------------- | --------------------------- | | ticket.created | A ticket is created. | | ticket.updated | A ticket changes. | | im\_message.added | An instant message arrives. | Works with ## Zoho Desk works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Zoho Desk + SlackGive your agents full access to Slack.](/integrations/slack/)[Zoho Desk + GitHubGive your agents full access to GitHub.](/integrations/github/) FAQ ## Questions, answered ### Which plans support triggers? ### Does this cover every endpoint? ## Put an agent on Zoho Desk. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Zoom Integration - The Full API for Agents | Helios URL: https://www.heliosapp.com/integrations/zoom Description: Agents schedule and reschedule meetings, find join links, and turn AI Companion summaries into notes and follow-ups. Zoom trigger events start an agent when a meeting ends or its summary is ready. [← All integrations](/integrations/) Communication # Give your agents access to Zoom. Agents schedule and reschedule meetings, find join links, and turn AI Companion summaries into notes and follow-ups. Zoom trigger events start an agent when a meeting ends or its summary is ready. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) 5,000 free credits to start. Agent reach Zoom REST APIs for Meetings, Users, Team Chat, Phone, Contact Center, Rooms, and Zoom's other products The full surface, searched at run time. Connect with * Your own OAuth app Use a Server-to-Server OAuth app for the whole account, or a user-managed General app for one user. Helios sets up event subscriptions and shows events that Zoom does not accept as unavailable. Event triggers Yes · 6 events Plus manual, schedule, and signed webhook. Get started [Connect in Helios](https://app.heliosapp.com/)[Setup docs](/docs/integrations/apps/zoom/) What the agent can do ## What agents do with Zoom Helios searches the Zoom REST APIs for Meetings, Users, Team Chat, Phone, Contact Center, Rooms, and Zoom's other products at run time. The agent finds the endpoint the task needs and calls it. * Call Zoom APIs with the connection's permissions and product licenses. * Schedule, reschedule, and cancel meetings, with agendas and settings. * Read AI Companion meeting summaries and who attended, and list cloud recordings. * Send Team Chat messages, and read Zoom Phone call history and voicemails. * Start a run on the events Zoom's event subscriptions send, from meetings and recordings to Team Chat messages, phone calls, and Contact Center engagements. Examples ## Tasks you can hand to a Zoom agent ### Log every sales call in the CRM When a call's AI Companion summary is ready, the agent finds the account and records the summary and next steps. zoom · meeting.summary\_completed When a summary is ready for a meeting with 'Acme' in the topic, log it on the Attio company record. 1. zoom·read the meeting summary 2. attio·find the Acme company record 3. attio·add a note with the summary and next steps ✓Call logged on Acme * Summary of the renewal call added as a note * Next step: send the revised quote by Friday ### Follow up after every customer call When a customer call ends, the agent checks who attended and drafts a follow-up email for the host. zoom · meeting.ended When a meeting with 'Acme' in the topic ends, draft a follow-up email to the attendees. 1. zoom·list the meeting's participants 2. attio·find the open Acme deal 3. gmail·draft a follow-up to the attendees ✓Follow-up drafted * Addressed to the 3 Acme attendees * Recaps the call and proposes a date for the next one ### Schedule meetings from a request Ask in chat or from another workflow, and the agent books the meeting and replies with the join link. Manual run Book a 30-minute design review tomorrow at 3pm UTC and share the link in #design. 1. zoom·create the meeting 2. slack·post the join link to #design ✓Design review booked * Tomorrow, 15:00 to 15:30 UTC * Join link posted in #design Event triggers ## Start a run on Zoom events Attach any of these events to a workflow and filter on the fields that matter. Manual, schedule, and signed webhook triggers work too. | Event | What it means | | ----------------------------------- | ---------------------------------------------------------------------------------------------------------- | | meeting.ended | A meeting ends - the moment to send a follow-up or log the call. | | meeting.summary\_completed | An AI Companion summary is ready to copy into your CRM or notes. | | recording.completed | A cloud recording is ready, so an agent can share it with the people who missed the meeting. | | meeting.created | A meeting is scheduled. Filter on its topic to prepare an agenda or a brief. | | team\_chat.channel\_message\_posted | A message is posted in a Team Chat channel. Filter on the channel name to answer questions in one channel. | | phone.voicemail\_received | A Zoom Phone voicemail arrives, so an agent can log it or arrange a callback. | Works with ## Zoom works with the rest of your stack One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox. [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Zoom + SlackGive your agents full access to Slack.](/integrations/slack/)[![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Zoom + AttioGive your agents full access to Attio.](/integrations/attio/)[![](/static/img/assets/gmail-light.svg)![](/static/img/assets/gmail-dark.svg)Zoom + GmailGive your agents full access to Gmail.](/integrations/gmail/) FAQ ## Questions, answered ### How do I connect Zoom? ### What can an agent reach in Zoom? ### Which Zoom events can trigger an agent? ### Does it work on a free Zoom plan? ## Put an agent on Zoom. Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Data Processing Addendum | Helios URL: https://www.heliosapp.com/legal/dpa Description: What the Helios Data Processing Addendum covers and how to request a signed copy. [Subscribe](/legal/rss.xml) ## Data Processing Addendum Last updated September 7, 2026 ## 1\. What it covers The Data Processing Addendum (DPA) sets out how Argonaut HQ, Inc. ("Helios") processes personal data on your behalf when you use the Helios Service. It forms part of the [Terms of Service](https://www.heliosapp.com/legal/terms) or a separate written agreement between you and Helios. It covers the data your agents read and write through connected tools, the files you store in the Library, chat and run transcripts, and account data for your users. The vendors that may process this data are listed on the [subprocessors page](https://www.heliosapp.com/legal/subprocessors). ## 2\. How to request the signed DPA Email [support@heliosapp.com](mailto:support@heliosapp.com) from your work address with your organization name and the legal entity that should sign. We send a copy for signature and return the countersigned document. ## 3\. Sections 1. Definitions 2. Scope and roles of the parties 3. Processing instructions 4. Confidentiality and personnel 5. Security measures 6. Subprocessors 7. International transfers 8. Data subject requests 9. Personal data breaches 10. Deletion and return of data 11. Audit rights 12. Liability --- # Privacy Policy | Helios URL: https://www.heliosapp.com/legal/privacy Description: Our Privacy Policy governs your visit to heliosapp.com, and explains how we collect, safeguard and disclose information that results from your use of our Service. [Subscribe](/legal/rss.xml) ## Privacy Policy Last updated July 14, 2026 ## 1\. Introduction Welcome to Helios. At Helios, we believe in transparency and responsible data handling. This privacy policy explains what data we collect, and how we use data to provide you with our AI-powered workflow automation platform while respecting your privacy and maintaining security. Argonaut HQ, Inc ("us", "we", or "our") operates (hereinafter referred to as "Service"). Our Privacy Policy governs your visit to , and explains how we collect, and safeguard information that results from your use of our Service. We use your data to provide and improve Service. By using Service, you agree to the collection and use of information in accordance with this policy. Unless otherwise defined in this Privacy Policy, the terms used in this Privacy Policy have the same meanings as in our Terms and Conditions. Our Terms and Conditions ("Terms") govern all use of our Service and together with the Privacy Policy constitutes your agreement with us ("agreement"). ## 2\. Definitions * **SERVICE** means the website operated by Argonaut HQ, Inc * **PERSONAL DATA** means data about a living individual who can be identified from those data (or from those and other information either in our possession or likely to come into our possession). * **USAGE DATA** is data collected automatically either generated by the use of Service or from Service infrastructure itself (for example, the duration of a page visit). * **COOKIES** are small files stored on your device (computer or mobile device). * **DATA CONTROLLER** means a natural or legal person who (either alone or jointly or in common with other persons) determines the purposes for which and the manner in which any personal data are, or are to be, processed. For the purpose of this Privacy Policy, we are a Data Controller of your data. * **DATA PROCESSOR (OR SERVICE PROVIDER)** means any natural or legal person who processes the data on behalf of the Data Controller. We may use the services of various Service Providers in order to process your data more effectively. * **DATA SUBJECT** is any living individual who is the subject of Personal Data. * **THE USER** is the individual using our Service. The User corresponds to the Data Subject, who is the subject of Personal Data. ## 3\. Information Collection and Use We collect several different types of information for various purposes to provide and improve our Service to you. ## 4\. Types of Data Collected ### Personal Data While using our Service, we may ask you to provide us with certain personally identifiable information that can be used to contact or identify you ("Personal Data"). Personally identifiable information may include, but is not limited to: * Email address * First name and last name * Cookies and Usage Data * Rough location (e.g. city, state, country) We may use your Personal Data to contact you with newsletters, marketing or promotional materials and other information that may be of interest to you. You may opt out of receiving any, or all, of these communications from us by following the unsubscribe link. ### Usage Data We may also collect information that your browser sends whenever you visit our Service or when you access Service by or through a mobile device ("Usage Data"). This Usage Data may include information such as your computer's Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Service that you visit, the time and date of your visit, the time spent on those pages, unique device identifiers and other diagnostic data. When you access Service with a mobile device, this Usage Data may include information such as the type of mobile device you use, your mobile device unique ID, the IP address of your mobile device, your mobile operating system, the type of mobile Internet browser you use, unique device identifiers and other diagnostic data. ### Tracking Technologies and Cookies We use cookies and similar technologies on our websites and in the Service. They fall into three categories, matching the choices offered in our cookie banner: * **Strictly necessary.** Required for the Service to function - for example, authentication and session cookies, and the first-party cookie that records your consent choices (`helios_consent`). These do not require consent. * **Analytics.** Used, with your consent, to understand how our websites and Service are used - pages viewed, features used, approximate location derived from IP address, and device and browser information. * **Marketing.** Used, with your consent, by us and our advertising partners to measure marketing campaigns and attribute signups to their source. This includes first-party attribution cookies that store campaign parameters (such as UTM codes and advertising click identifiers) and tags or pixels from advertising platforms. **Consent comes first.** Except for strictly necessary cookies, our websites do not set cookies or load analytics or marketing technologies until you opt in through our cookie banner. You can change or withdraw your choices at any time using the "Cookie settings" link in the footer of our websites, or through your browser's cookie controls. Withdrawing consent stops the associated technologies from loading and running. **Session replay and interaction recording.** We do not use session replay on our public marketing websites. Within the logged-in Helios application, we may use session replay technology that records how you interact with the application - such as pages visited, mouse movements, clicks, scrolling, and form interactions - and that is designed to mask sensitive inputs such as passwords. We use these recordings to diagnose usability problems, investigate errors, and improve the Service. By creating an account and using the logged-in application you consent to this recording; if you have questions or objections, contact us at [support@heliosapp.com](mailto:support@heliosapp.com). ## 5\. Use of Data Argonaut HQ, Inc uses the collected data for various purposes: * to provide and maintain our Service; * to notify you about changes to our Service; * to allow you to participate in interactive features of our Service when you choose to do so; * to provide customer support; * to gather analysis or valuable information so that we can improve our Service; * to monitor the usage of our Service; * to detect, prevent and address technical issues; * to fulfill any other purpose for which you provide it; * to carry out our obligations and enforce our rights arising from any contracts entered into between you and us, including for billing and collection; * to provide you with notices about your account and/or subscription, including expiration and renewal notices, email-instructions, etc.; * to provide you with news, special offers and general information about other goods, services and events which we offer that are similar to those that you have already purchased or enquired about unless you have opted not to receive such information; * in any other way we may describe when you provide the information; * for any other purpose with your consent. **Helios**: Source code representation is stored for providing code intelligence services. However, this is not used for any AI model training. We have Zero Data Retention agreements in place with the AI model providers to ensure there is no access to any sensitive data. ## 6\. Retention of Data We will retain your Personal Data only for as long as is necessary for the purposes set out in this Privacy Policy. We will retain and use your Personal Data to the extent necessary to comply with our legal obligations (for example, if we are required to retain your data to comply with applicable laws), resolve disputes, and enforce our legal agreements and policies. We will also retain Usage Data for internal analysis purposes. Usage Data is generally retained for a shorter period, except when this data is used to strengthen the security or to improve the functionality of our Service, or we are legally obligated to retain this data for longer time periods. ## 7\. Transfer of Data Your information, including Personal Data, may be transferred to – and maintained on – computers located outside of your state, province, country or other governmental jurisdiction where the data protection laws may differ from those of your jurisdiction. Please note that we transfer the data, including Personal Data, to the United States or where our servers are located and process it there. Where we transfer Personal Data originating from the European Economic Area, the United Kingdom, or Switzerland to countries that have not received an adequacy decision, we rely on appropriate safeguards recognized under applicable law, such as the European Commission's Standard Contractual Clauses. Argonaut HQ, Inc will take all the steps reasonably necessary to ensure that your data is treated securely and in accordance with this Privacy Policy and no transfer of your Personal Data will take place to an organization or a country unless there are adequate controls in place including the security of your data and other personal information. ## 8\. Disclosure of Data We may disclose personal information that we collect, or you provide: ### Disclosure for Law Enforcement Under certain circumstances, we may be required to disclose your Personal Data if required to do so by law or in response to valid requests by public authorities. ### Business Transaction If we or our subsidiaries are involved in a merger, acquisition or asset sale, your Personal Data may be transferred. ### Other cases We may disclose your information also: * to our subsidiaries and affiliates; * to contractors, service providers, and other third parties we use to support our business; * to fulfil the purpose for which you provide it; * for the purpose of including your company's logo on our website; * for any other purpose disclosed by us when you provide the information; * with your consent in any other cases; * if we believe disclosure is necessary or appropriate to protect the rights, property, or safety of the Company, our customers, or others. ## 9\. Security of Data The security of your data is important to us. We strive to use commercially acceptable means to protect your Personal Data. We implement industry-standard security measures: * Regular security audits and penetration testing * Access controls and authentication safeguards ## 10\. Your Data Protection Rights Under General Data Protection Regulation (GDPR) If you are a resident of the European Union (EU) and European Economic Area (EEA), you have certain data protection rights, covered by GDPR. – See more at We aim to take reasonable steps to allow you to correct, amend, delete, or limit the use of your Personal Data. If you wish to be informed what Personal Data we hold about you and if you want it to be removed from our systems, please email us at [support@heliosapp.com](mailto:support@heliosapp.com). ### Legal Bases for Processing We process your Personal Data under the following legal bases (Article 6 GDPR): * **Performance of a contract** \- to provide and maintain the Service, manage your account, and handle billing; * **Legitimate interests** \- to secure and improve the Service, prevent fraud and abuse, and communicate with business contacts, where those interests are not overridden by your rights; * **Consent** \- for analytics and marketing cookies and similar technologies on our websites, and for marketing communications; you may withdraw consent at any time without affecting the lawfulness of processing before withdrawal; * **Legal obligation** \- to comply with applicable law, such as tax, accounting, and lawful requests from public authorities. In certain circumstances, you have the following data protection rights: * the right to access, update or to delete the information we have on you; * the right of rectification. You have the right to have your information rectified if that information is inaccurate or incomplete; * the right to object. You have the right to object to our processing of your Personal Data; * the right of restriction. You have the right to request that we restrict the processing of your personal information; * the right to data portability. You have the right to be provided with a copy of your Personal Data in a structured, machine-readable and commonly used format; * the right to withdraw consent. You also have the right to withdraw your consent at any time where we rely on your consent to process your personal information; Please note that we may ask you to verify your identity before responding to such requests. Please note, we may not be able to provide Service without some necessary data. You have the right to complain to a Data Protection Authority about our collection and use of your Personal Data. For more information, please contact your local data protection authority in the European Economic Area (EEA). ## 11\. Your Data Protection Rights under the California Privacy Protection Act (CalOPPA) CalOPPA is the first state law in the nation to require commercial websites and online services to post a privacy policy. The law's reach stretches well beyond California to require a person or company in the United States (and conceivable the world) that operates websites collecting personally identifiable information from California consumers to post a conspicuous privacy policy on its website stating exactly the information being collected and those individuals with whom it is being shared, and to comply with this policy. – See more at: According to CalOPPA we agree to the following: * users can visit our site anonymously; * our Privacy Policy link includes the word "Privacy", and can easily be found on the page specified above on the home page of our website; * users will be notified of any privacy policy changes on our Privacy Policy Page; * users are able to change their personal information by emailing us at [support@heliosapp.com](mailto:support@heliosapp.com). ## 12\. Your California Privacy Rights (CCPA, as amended by the CPRA) If you are a California resident, you are entitled to learn what data we collect about you, ask us to correct or delete your data, and opt out of its sale or sharing. ### Categories of personal information we collect In the preceding 12 months we have collected the following categories of personal information: identifiers (such as name, email address, and IP address); commercial information (such as subscription and billing records); internet or other electronic network activity information (such as pages visited, interactions with our websites and Service - including, in the logged-in application, session replay recordings - and cookie data); coarse geolocation derived from IP address; and professional information you choose to provide. We collect them from you directly, from your devices, and from our service providers, for the business and commercial purposes described in "Use of Data." ### Sale and sharing of personal information We do not sell personal information for money. With your opt-in consent, we allow advertising and analytics partners to collect internet activity information through cookies and tags on our websites, which may constitute "sharing" (cross-context behavioral advertising) - and in some cases a "sale" - under California law. Our websites do not load these technologies unless you opt in through our cookie banner, so no sale or sharing occurs for visitors who have not opted in - including browsers transmitting a Global Privacy Control (GPC) signal that have not opted in, consistent with that signal. We do not knowingly sell or share the personal information of consumers under 16 years of age. To opt out of sale or sharing (or to withdraw a previous opt-in), use the "Cookie settings" link in the footer of our websites, or email us at [support@heliosapp.com](mailto:support@heliosapp.com). ### Sensitive personal information We do not collect sensitive personal information as defined by the CPRA except as incidentally contained in content you choose to submit, and we do not use or disclose sensitive personal information to infer characteristics about you. To exercise your other rights, you can make certain requests and ask us: ### What personal information we have about you If you make this request, we will return to you: * The categories of personal information we have collected about you. * The categories of sources from which we collect your personal information. * The business or commercial purpose for collecting or selling your personal information. * The categories of third parties with whom we share personal information. * The specific pieces of personal information we have collected about you. * A list of categories of personal information that we have sold, along with the category of any other company we sold it to. If we have not sold your personal information, we will inform you of that fact. * A list of categories of personal information that we have disclosed for a business purpose, along with the category of any other company we shared it with. Please note, you are entitled to ask us to provide you with this information up to two times in a rolling twelve-month period. When you make this request, the information provided may be limited to the personal information we collected about you in the previous 12 months. ### To correct your personal information If you make this request, we will correct inaccurate personal information we maintain about you, taking into account the nature of the personal information and the purposes of the processing. ### To delete your personal information If you make this request, we will delete the personal information we hold about you as of the date of your request from our records and direct any service providers to do the same. In some cases, deletion may be accomplished through de-identification of the information. If you choose to delete your personal information, you may not be able to use certain functions that require your personal information to operate. Please note, if you ask us to delete your data or opt out of sale or sharing, it may impact your experience with us, and you may not be able to participate in certain programs or membership services which require the usage of your personal information to function. But in no circumstances will we discriminate against you for exercising your rights. To exercise your California data protection rights described above, please send your request(s) by one of the following means: By email: [support@heliosapp.com](mailto:support@heliosapp.com) Your data protection rights, described above, are covered by the California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA) effective January 1, 2023\. To find out more, visit the official California Legislative Information website. ## 13\. Service Providers We may employ third party companies and individuals to facilitate our Service ("Service Providers"), provide Service on our behalf, perform Service-related services or assist us in analyzing how our Service is used. These third parties have access to your Personal Data only to perform these tasks on our behalf and are obligated not to disclose or use it for any other purpose. We rely on third-party Service Providers to provide our Service. The list of subprocessors is available at . ## 14\. Children's Privacy Our Services are not intended for use by children under the age of 13 ("Children"). We do not knowingly collect personally identifiable information from Children under 13\. If you become aware that a Child has provided us with Personal Data, please contact us. If we become aware that we have collected Personal Data from Children without verification of parental consent, we take steps to remove that information from our servers. ## 15\. Changes to This Privacy Policy We may update our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page. We may let you know via email and/or a prominent notice on our Service, prior to the change becoming effective and update "effective date" at the top of this Privacy Policy. You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page. ## 16\. Contact Us If you have any questions about this Privacy Policy, please contact us: By email: [support@heliosapp.com](mailto:support@heliosapp.com) --- # Subprocessors | Helios URL: https://www.heliosapp.com/legal/subprocessors Description: List of third-party subprocessors used by Helios to deliver our services, including their roles and subprocessing activities. [Subscribe](/legal/rss.xml) ## Subprocessors Last updated September 16, 2026 ## 1\. Introduction To support delivery of our services, Argonaut HQ, Inc. ("Helios", "Company", "Argonaut") uses service providers that may store and process Customer Data (each, a "Subprocessor"). This page provides important information about the identity and role of each Subprocessor. Terms used on this page but not defined have the meaning set forth in the [Terms of Service](https://www.heliosapp.com/legal/terms) or superseding written agreement between Customer and Helios (the "Agreement"). ## 2\. Third-Party Subprocessors Helios may use the following Subprocessors to host Customer Data, provide infrastructure that helps with delivery of our Services, or perform other functions related to the Helios Service. Prior to engaging any third party Subprocessor, Helios performs diligence to evaluate their privacy, security and confidentiality practices. We collect several different types of information for various purposes to provide and improve our Service to you. | Entity | Subprocessing Activity | | ------------------------- | --------------------------------------------------------------- | | Amazon Web Services, Inc. | Cloud Service Provider | | Google LLC | Cloud Service Provider, Website Analytics, Email Communications | | Microsoft Azure | Cloud Service Provider | | Cloudflare, Inc. | Web Application Firewall | | Datadog, Inc. | Infrastructure Monitoring | | MacStadium, Inc. | macOS Cloud Infrastructure | | Neon, Inc. | Serverless Database Services | | UnifyGTM | Go-to-Market / Sales Intelligence | | Attio | CRM | | Slack Technologies, Inc. | Messaging Services | | Vercel Inc. | Web Hosting Provider | | GitHub, Inc. | Version Control and Developer Services | | Posthog, Inc. | Product Analytics & Session Replay (logged-in application) | | Atlas Support, Inc. | Customer Communications | | Linear Orbit | Project management and Tracking | | OpenAI, L.L.C. | AI Services | | Anthropic, PBC | AI Services | | Stripe, Inc. | Payment Processing | | Hetzner Online GmbH | Cloud Service Provider | | E2B Dev, Inc. | Cloud Sandboxes | | ClickHouse, Inc. | Data Storage and Analytics | | Incident.io Ltd. | Status Page and Incident Management | | Latitude.sh LTDA | Bare Metal Cloud Infrastructure | | UAB Cherry Servers | Bare Metal Cloud Infrastructure | --- # Terms of Service | Helios URL: https://www.heliosapp.com/legal/terms Description: Terms of Service for Helios. These Terms govern your use of our web pages and services operated by Argonaut HQ, Inc. [Subscribe](/legal/rss.xml) ## Terms of Service Last updated September 30, 2026 ## 1\. Introduction Welcome to Argonaut HQ, Inc ("Company", "we", "our", "us")! As you have just clicked our Terms of Service, please pause, grab a cup of coffee and carefully read the following pages. It will take you approximately 20 minutes. These Terms of Service ("Terms", "Terms of Service") govern your use of our web pages located at operated by Argonaut HQ, Inc Our Privacy Policy also governs your use of our Service and explains how we collect, safeguard and disclose information that results from your use of our web pages. Please read it here . Your agreement with us includes these Terms and our Privacy Policy ("Agreements"). You acknowledge that you have read and understood Agreements, and agree to be bound by them. If you do not agree with (or cannot comply with) Agreements, then you may not use the Service, but please let us know by emailing at [support@heliosapp.com](mailto:support@heliosapp.com) so we can try to find a solution. These Terms apply to all visitors, users and others who wish to access or use Service. These terms may be superseded by custom agreements with specific customers. Thank you for being responsible. ## 2\. Communications By creating an Account on our Service, you agree to subscribe to newsletters, marketing or promotional materials and other information we may send. However, you may opt out of receiving any, or all, of these communications from us by following the unsubscribe link or by emailing at [support@heliosapp.com](mailto:support@heliosapp.com). ## 3\. Purchases If you wish to purchase any product or service made available through Service ("Purchase"), you may be asked to supply certain information relevant to your Purchase including, without limitation, your credit card number, the expiration date of your credit card, your billing address, and your shipping information. You represent and warrant that: * You have the legal right to use any credit card(s) or other payment method(s) in connection with any Purchase; and that * The information you supply to us is true, correct and complete. We may employ the use of third party services for the purpose of facilitating payment and the completion of Purchases. By submitting your information, you grant us the right to provide the information to these third parties subject to our Privacy Policy. We reserve the right to refuse or cancel your order at any time for reasons including but not limited to: product or service availability, errors in the description or price of the product or service, error in your order or other reasons. We reserve the right to refuse or cancel your order if fraud or an unauthorized or illegal transaction is suspected. ## 4\. Subscriptions Some parts of Service are billed on a subscription basis ("Subscription(s)"). You will be billed in advance on a recurring and periodic basis ("Billing Cycle"). Billing cycles are set either on a monthly or annual basis, depending on the type of subscription plan you select when purchasing a Subscription. At the end of each Billing Cycle, your Subscription will automatically renew unless you cancel it or Argonaut HQ, Inc cancels it. You may cancel your Subscription renewal either through your online account management page or by contacting Argonaut HQ, Inc customer support team. A valid payment method, including credit card, is required to process the payment for your subscription. You shall provide Argonaut HQ, Inc with accurate and complete billing information including full name, address, state, zip code, telephone number, and a valid payment method information. By submitting such payment information, you automatically authorize Argonaut HQ, Inc to charge all Subscription fees incurred through your account to any such payment instruments. Should automatic billing fail to occur for any reason, Argonaut HQ, Inc will issue an electronic invoice indicating that you must proceed manually, within a certain deadline date, with the full payment corresponding to the billing period as indicated on the invoice. ## 5\. Free Trial Argonaut HQ, Inc may, at its sole discretion, offer a Subscription with a free trial for a limited period of time ("Free Trial"). You may be required to enter your billing information in order to sign up for Free Trial. If you do enter your billing information when signing up for Free Trial, you will not be charged by Argonaut HQ, Inc until Free Trial has expired. On the last day of Free Trial period, unless you cancelled your Subscription, you will be automatically charged the applicable Subscription fees for the type of Subscription you have selected. At any time and without notice, Argonaut HQ, Inc reserves the right to: * Modify Terms of Service of Free Trial offer, or * Cancel such Free Trial offer. ## 6\. Fee Changes Argonaut HQ, Inc, in its sole discretion and at any time, may modify Subscription fees for the Subscriptions. Any Subscription fee change will become effective at the end of the then-current Billing Cycle. Argonaut HQ, Inc will provide you with a reasonable prior notice of any change in Subscription fees to give you an opportunity to terminate your Subscription before such change becomes effective. Your continued use of Service after Subscription fee change comes into effect constitutes your agreement to pay the modified Subscription fee amount. ## 7\. Refunds We do not offer refunds for products that are billed on a usage based model. We may offer refunds for products that are billed on a subscription basis, at our sole discretion. ## 8\. Content Our Service allows you to post, link, store, share and otherwise make available certain information, text, graphics, videos, or other material ("Content"). You are responsible for Content that you post on or through Service, including its legality, reliability, and appropriateness. By posting Content on or through Service, You represent and warrant that: * Content is yours (you own it) and/or you have the right to use it and the right to grant us the rights and license as provided in these Terms, and * That the posting of your Content on or through Service does not violate the privacy rights, publicity rights, copyrights, contract rights or any other rights of any person or entity. We reserve the right to terminate the account of anyone found to be infringing on a copyright. You retain any and all of your rights to any Content you submit, post or display on or through Service and you are responsible for protecting those rights. We take no responsibility and assume no liability for Content you or any third party posts on or through Service. Argonaut HQ, Inc has the right but not the obligation to monitor all Content provided by users. You may not distribute, modify, transmit, reuse, download, repost, copy, or use Content, whether in whole or in part, for commercial purposes or for personal gain, without express advance written permission from us. **Source Code Protection.** We do not access, read, or analyze your source code, repositories, or other proprietary code ("Source Code") that you provide to or process through the Service, except as strictly necessary to provide the Service to you (for example, to execute builds or run workflows you have configured). We do not share, sell, license, or disclose your Source Code to any third party. Your Source Code remains your sole property at all times, and we claim no rights, ownership, or interest in it. ## 9\. Prohibited Uses You may use Service only for lawful purposes and in accordance with Terms. You agree not to use Service: * In any way that violates any applicable national or international law or regulation. * For the purpose of exploiting, harming, or attempting to exploit or harm minors in any way by exposing them to inappropriate content or otherwise. * To transmit, or procure the sending of, any advertising or promotional material, including any "junk mail", "chain letter," "spam," or any other similar solicitation. * To impersonate or attempt to impersonate Company, a Company employee, another user, or any other person or entity. * In any way that infringes upon the rights of others, or in any way is illegal, threatening, fraudulent, or harmful, or in connection with any unlawful, illegal, fraudulent, or harmful purpose or activity. * To engage in any other conduct that restricts or inhibits anyone's use or enjoyment of Service, or which, as determined by us, may harm or offend Company or users of Service or expose them to liability. Additionally, you agree not to: * Use Service in any manner that could disable, overburden, damage, or impair Service or interfere with any other party's use of Service, including their ability to engage in real time activities through Service. * Use any robot, spider, or other automatic device, process, or means to access Service for any purpose, including monitoring or copying any of the material on Service. * Use any manual process to monitor or copy any of the material on Service or for any other unauthorized purpose without our prior written consent. * Use any device, software, or routine that interferes with the proper working of Service. * Introduce any viruses, trojan horses, worms, logic bombs, or other material which is malicious or technologically harmful. * Attempt to gain unauthorized access to, interfere with, damage, or disrupt any parts of Service, the server on which Service is stored, or any server, computer, or database connected to Service. * Attack Service via a denial-of-service attack or a distributed denial-of-service attack. * Take any action that may damage or falsify Company rating. * Attempt to interfere with the proper working of Service without proper explicit permission. * Use the Service to compete with Argonaut HQ, Inc. * Otherwise attempt to interfere with the proper working of Service. Violation of any of these Terms will result in fines and penalties as determined by Argonaut HQ, Inc in its sole discretion. ## 10\. Analytics We may use third-party Service Providers as subprocessors to provide analytics services. Within the logged-in application, this includes technologies that record how you interact with the Service (session replay), as described in our Privacy Policy. We do not use session replay on our public marketing websites, and analytics and advertising technologies on those websites load only after you opt in through our cookie banner; you can change or withdraw your choices at any time via the "Cookie settings" link in the website footer. The list of subprocessors is available at . ## 11\. No Use By Minors Service is intended only for access and use by individuals at least eighteen (18) years old. By accessing or using any of the Company, you warrant and represent that you are at least eighteen (18) years of age and with the full authority, right, and capacity to enter into this agreement and abide by all of the terms and conditions of Terms. If you are not at least eighteen (18) years old, you are prohibited from both the access and usage of Service. ## 12\. Accounts When you create an account with us, you guarantee that you are above the age of 18, and that the information you provide us is accurate, complete, and current at all times. Inaccurate, incomplete, or obsolete information may result in the immediate termination of your account on Service. You are responsible for maintaining the confidentiality of your account and password, including but not limited to the restriction of access to your computer and/or account. You agree to accept responsibility for any and all activities or actions that occur under your account and/or password, whether your password is with our Service or a third-party service. You must notify us immediately upon becoming aware of any breach of security or unauthorized use of your account. You may not use as a username the name of another person or entity or that is not lawfully available for use, a name or trademark that is subject to any rights of another person or entity other than you, without appropriate authorization. You may not use as a username any name that is offensive, vulgar or obscene. We reserve the right to refuse service, terminate accounts, remove or edit content, or cancel orders at our sole discretion. ## 13\. Intellectual Property Service and its original content (excluding Content provided by users), features and functionality are and will remain the exclusive property of Argonaut HQ, Inc and its licensors. Service is protected by copyright, trademark, and other laws of the United States and foreign countries. Our trademarks and trade dress may not be used in connection with any product or service without the prior written consent of Argonaut HQ, Inc. Unless you tell us otherwise in writing, you allow us to use your company name and logo on our websites and in our marketing materials. We use them only to show that you use the Service. We will follow any brand guidelines you give us. We will not say that you endorse the Service. You can withdraw this permission at any time by emailing [support@heliosapp.com](mailto:support@heliosapp.com). We will remove your name and logo from our websites within a reasonable time. If you have a separate written agreement with us on this topic, that agreement applies instead. ## 14\. Error Reporting and Feedback You may provide us either directly at [support@heliosapp.com](mailto:support@heliosapp.com) or via third party sites and tools with information and feedback concerning errors, suggestions for improvements, ideas, problems, complaints, and other matters related to our Service ("Feedback"). You acknowledge and agree that: * You shall not retain, acquire or assert any intellectual property right or other right, title or interest in or to the Feedback; * Company may have development ideas similar to the Feedback; * Feedback does not contain confidential information or proprietary information from you or any third party; and * Company is not under any obligation of confidentiality with respect to the Feedback. In the event the transfer of the ownership to the Feedback is not possible due to applicable mandatory laws, you grant Company and its affiliates an exclusive, transferable, irrevocable, free-of-charge, sub-licensable, unlimited and perpetual right to use (including copy, modify, create derivative works, publish, distribute and commercialize) Feedback in any manner and for any purpose. ## 15\. Links To Other Web Sites Our Service may contain links to third party web sites or services that are not owned or controlled by Argonaut HQ, Inc. Argonaut HQ, Inc has no control over, and assumes no responsibility for the content, privacy policies, or practices of any third party web sites or services. We do not warrant the offerings of any of these entities/individuals or their websites. YOU ACKNOWLEDGE AND AGREE THAT ARGONAUT HQ, INC SHALL NOT BE RESPONSIBLE OR LIABLE, DIRECTLY OR INDIRECTLY, FOR ANY DAMAGE OR LOSS CAUSED OR ALLEGED TO BE CAUSED BY OR IN CONNECTION WITH USE OF OR RELIANCE ON ANY SUCH CONTENT, GOODS OR SERVICES AVAILABLE ON OR THROUGH ANY SUCH THIRD PARTY WEB SITES OR SERVICES. WE STRONGLY ADVISE YOU TO READ THE TERMS OF SERVICE AND PRIVACY POLICIES OF ANY THIRD PARTY WEB SITES OR SERVICES THAT YOU VISIT. ## 16\. Disclaimer Of Warranty THESE SERVICES ARE PROVIDED BY COMPANY ON AN "AS IS" AND "AS AVAILABLE" BASIS. COMPANY MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, AS TO THE OPERATION OF THEIR SERVICES, OR THE INFORMATION, CONTENT OR MATERIALS INCLUDED THEREIN. YOU EXPRESSLY AGREE THAT YOUR USE OF THESE SERVICES, THEIR CONTENT, AND ANY SERVICES OR ITEMS OBTAINED FROM US IS AT YOUR SOLE RISK. NEITHER COMPANY NOR ANY PERSON ASSOCIATED WITH COMPANY MAKES ANY WARRANTY OR REPRESENTATION WITH RESPECT TO THE COMPLETENESS, SECURITY, RELIABILITY, QUALITY, ACCURACY, OR AVAILABILITY OF THE SERVICES. WITHOUT LIMITING THE FOREGOING, NEITHER COMPANY NOR ANYONE ASSOCIATED WITH COMPANY REPRESENTS OR WARRANTS THAT THE SERVICES, THEIR CONTENT, OR ANY SERVICES OR ITEMS OBTAINED THROUGH THE SERVICES WILL BE ACCURATE, RELIABLE, ERROR-FREE, OR UNINTERRUPTED, THAT DEFECTS WILL BE CORRECTED, THAT THE SERVICES OR THE SERVER THAT MAKES IT AVAILABLE ARE FREE OF VIRUSES OR OTHER HARMFUL COMPONENTS OR THAT THE SERVICES OR ANY SERVICES OR ITEMS OBTAINED THROUGH THE SERVICES WILL OTHERWISE MEET YOUR NEEDS OR EXPECTATIONS. COMPANY HEREBY DISCLAIMS ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED, STATUTORY, OR OTHERWISE, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR PARTICULAR PURPOSE. THE FOREGOING DOES NOT AFFECT ANY WARRANTIES WHICH CANNOT BE EXCLUDED OR LIMITED UNDER APPLICABLE LAW. ## 17\. Limitation Of Liability EXCEPT AS PROHIBITED BY LAW, YOU WILL HOLD US AND OUR OFFICERS, DIRECTORS, EMPLOYEES, AND AGENTS NOT LIABLE FOR ANY INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGE, HOWEVER IT ARISES IN CONNECTION WITH THIS AGREEMENT. EXCEPT AS PROHIBITED BY LAW, IF THERE IS LIABILITY FOUND ON THE PART OF COMPANY, IT WILL BE LIMITED TO THE AGGREGATED AMOUNT PAID FOR THE PRODUCTS AND/OR SERVICES IN THE PREVIOUS 12 MONTHS OF THE SPECIFIC CLAIM ARISING, LESS COSTS AND EXPENSES TO PROVIDE THE PRODUCTS AND/OR SERVICES, AND UNDER NO CIRCUMSTANCES WILL THERE BE CONSEQUENTIAL OR PUNITIVE DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF PUNITIVE, INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE PRIOR LIMITATION OR EXCLUSION MAY NOT APPLY TO YOU. ## 18\. Termination We may terminate or suspend your account and bar access to Service immediately, without prior notice or liability, under our sole discretion, for any reason whatsoever and without limitation, including but not limited to a breach of Terms. If you wish to terminate your account, you may simply discontinue using Service. All provisions of Terms which by their nature should survive termination shall survive termination, including, without limitation, ownership provisions, warranty disclaimers, indemnity and limitations of liability. ## 19\. Governing Law These Terms shall be governed and construed in accordance with the laws of State of Delaware without regard to its conflict of law provisions. Our failure to enforce any right or provision of these Terms will not be considered a waiver of those rights. If any provision of these Terms is held to be invalid or unenforceable by a court, the remaining provisions of these Terms will remain in effect. These Terms constitute the entire agreement between us regarding our Service and supersede and replace any prior agreements we might have had between us regarding Service. ## 20\. Changes To Service We reserve the right to withdraw or amend our Service, and any service or material we provide via Service, in our sole discretion without notice. We will not be liable if for any reason all or any part of Service is unavailable at any time or for any period. From time to time, we may restrict access to some parts of Service, or the entire Service, to users, including registered users. ## 21\. Amendments To Terms We may amend Terms at any time by posting the amended terms on this site. It is your responsibility to review these Terms periodically. Your continued use of the Platform following the posting of revised Terms means that you accept and agree to the changes. You are expected to check this page frequently so you are aware of any changes, as they are binding on you. By continuing to access or use our Service after any revisions become effective, you agree to be bound by the revised terms. If you do not agree to the new terms, you are no longer authorized to use Service. ## 22\. Waiver And Severability No waiver by Company of any term or condition set forth in Terms shall be deemed a further or continuing waiver of such term or condition or a waiver of any other term or condition, and any failure of Company to assert a right or provision under Terms shall not constitute a waiver of such right or provision. If any provision of Terms is held by a court or other tribunal of competent jurisdiction to be invalid, illegal or unenforceable for any reason, such provision shall be eliminated or limited to the minimum extent such that the remaining provisions of Terms will continue in full force and effect. ## 23\. Acknowledgement BY USING SERVICE OR OTHER SERVICES PROVIDED BY US, YOU ACKNOWLEDGE THAT YOU HAVE READ THESE TERMS OF SERVICE AND AGREE TO BE BOUND BY THEM. ## 24\. Contact Us Please send your feedback, comments, requests for technical support: By email: [support@heliosapp.com](mailto:support@heliosapp.com). --- # Pricing - Pay for runs | Helios URL: https://www.heliosapp.com/pricing Description: Start with 5,000 free credits. Then $0.002 per credit, with spending limits and auto refill. Add the whole team at no extra cost. Pricing # Pay for the runs you make Start with 5,000 free credits. Then $0.002 per credit, with spending limits and auto refill. Add the whole team at no extra cost. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) * 5,000 free credits * Usage pricing * Every teammate included Plans ## Start free. Pay as you use it. Choose usage billing for day-to-day work, or talk to us about volume pricing and contract terms. ### Free Put your first workflow on a real task. $0 5,000 credits to start. [Get started free](https://app.heliosapp.com/) * Chat and workflows on any trigger * A sandbox for every run * All integrations with full API access * Databases and MCP servers * Full run transcripts * Community support ### Growth Most teams For teams with workflows running every day. $0.002per credit Usage billing with every teammate included. [Get started](https://app.heliosapp.com/) * Everything in Free * Credits billed as runs happen * Monthly spending limit you set * Auto refill so long runs keep going * Roles, groups, and service accounts * Share with an expiry date ### Enterprise For rolling workflows out across the company. Custom Custom credit volume and terms. [Talk to us](https://cal.com/suryao/helios) * Everything in Growth * SAML and OIDC SSO through WarpBuild auth * SCIM provisioning * Data processing agreement * Private networking to your systems * Invoice billing Compare ## What each plan includes Every plan runs the same product. The rows below show where credits, access controls, and paperwork differ. | Feature | Free | Growth | Enterprise | | ----------------------------------------- | --------------------- | ----------------------- | ---------------------- | | Credits | | | | | Credits included | 5,000 to start | 5,000 to start | Custom volume | | Price per credit | Free credits only | $0.002 | Custom | | Monthly spending limit | –Not included in Free | Included in Growth | Included in Enterprise | | Auto refill | –Not included in Free | Included in Growth | Included in Enterprise | | Runs | | | | | A sandbox for every run | Included in Free | Included in Growth | Included in Enterprise | | All integrations with full API access | Included in Free | Included in Growth | Included in Enterprise | | Databases and MCP servers | Included in Free | Included in Growth | Included in Enterprise | | Full run transcripts | Included in Free | Included in Growth | Included in Enterprise | | Library with proposed changes you approve | Included in Free | Included in Growth | Included in Enterprise | | CLI and terminal app | Included in Free | Included in Growth | Included in Enterprise | | Access | | | | | Roles and groups | –Not included in Free | Included in Growth | Included in Enterprise | | Service accounts | –Not included in Free | Included in Growth | Included in Enterprise | | Sharing with an expiry date | –Not included in Free | Included in Growth | Included in Enterprise | | SAML and OIDC SSO through WarpBuild auth | –Not included in Free | –Not included in Growth | Included in Enterprise | | SCIM provisioning | –Not included in Free | –Not included in Growth | Included in Enterprise | | Private networking to your systems | –Not included in Free | –Not included in Growth | Included in Enterprise | | Billing and support | | | | | Data processing agreement | –Not included in Free | –Not included in Growth | Included in Enterprise | | Invoice billing | –Not included in Free | –Not included in Growth | Included in Enterprise | | Support channel | Community | Email | Priority | Calculator ## Estimate a month of runs Pick how often workflows run, how long each run takes, and how heavy the model work is. The estimate updates as you move the sliders. Runs per month runs 1001K10K100K1M10M Average duration per run minhoursdays 1m10m1h8h1d7d Model tier (assumption) LightA small model and a few tool calls.\~10 credits/minStandardA frontier model reading and writing as it works.\~30 credits/minHeavyA frontier model with long context and many tool calls.\~80 credits/min Credits per run minute (edit the assumption) Credits per run 150 5 min × 30 credits/min Credits per month 45,000 300 runs Estimated monthly cost $90.00 at $0.002 per credit First month after free credits $80.00 40,000 paid credits How far the free credits go 33 runs covered About 3 days at this pace. Assumptions * This is an estimate. The credits a run uses depend on the model you pick and how long the sandbox stays open. * The model tiers are assumptions. Edit the credits per minute to match what your runs report. * Model usage is billed at 2x the provider cost. Sandbox time is billed at 1.5x cost. Every run reports the credits it used, so you see the real number after the first run. Credits ## What uses credits A credit is $0.002\. Two things draw credits during a run. Everything else is free. | Item | Uses credits | How it is metered | | ---------------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------- | | Model tokens | Yes | Every token the model reads and writes during a run. Billed at 2x the provider cost. | | Sandbox minutes | Yes | The time a run keeps its sandbox open. Billed at 1.5x cost for the vCPU and memory used. | | Triggers | No | Schedules, webhooks, and integration events cost nothing to set up or fire. The run they start is what uses credits. | | Seats | No | Invite everyone. People who watch, approve, or start runs are not charged. | | Integrations and MCP servers | No | Connect as many as you need. API calls the agent makes are covered by the run's tokens and sandbox time. | Spending limits ## Cap the month before it starts Usage pricing only works if the bill cannot surprise you. Limits are built into the product. ### A limit per product Helios and WarpBuild CI each get their own monthly spending limit. Set the Helios limit to the number you are comfortable with. Change it any time. ### Triggers stop at the limit When credits run out, scheduled, webhook, and event triggers stop starting runs. Nothing runs on credit you did not approve. ### Auto refill for long runs Turn on auto refill and Helios buys more credits when the balance drops below a threshold. The default threshold is $25 and the smallest refill is $10. ### One balance with WarpBuild Prepaid credits are shared between Helios and WarpBuild CI. Buy once and spend on either product under its own limit. The bill follows the work The meter in Helios is the run itself. An engineer who sets up ten workflows and an operator who checks them once a week both join for free. Each run reports the credits it used, and the spending limit keeps the month inside the number you chose. FAQ ## Billing questions ### What is a credit? ### How many credits does one run use? ### What happens when my credits run out? ### Can I spend more than my limit by accident? ### Do you charge per seat? ### Are credits shared with WarpBuild CI? ### Do you offer refunds? ### How does Enterprise billing work? ### How do I move from Free to Growth? ## Start with a single run 5,000 credits are enough to connect a tool, run a chat, and put the same prompt on a schedule. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Product - What an Agent Gets in Helios | Helios URL: https://www.heliosapp.com/product Description: Every Helios agent gets its own sandbox, the full API of each connected tool, shared context your team reviews, and one permissions model across the dashboard, CLI, and scripts. Product # What an agent gets in Helios A sandbox, the full API of each tool, shared context, and a permissions model that follows it into the CLI and your scripts. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) * 5,000 free credits to start * One sandbox per run * Full run transcripts [A real computer per runEvery run gets its own sandbox with a shell, files, and code execution.See the sandbox →](#code)[The full API of each toolAgents call the complete API of a connected tool, not a curated list of actions.See integrations →](/integrations/)[One permissions modelRoles cover the dashboard, the CLI, and your scripts. The agent never holds a raw token.See security →](/security/) Workflows ## Write the prompt once. Pick the trigger. * ### Four ways to start Run it by hand, on a schedule, from a signed webhook, or on an event. * ### Events from three tools GitHub fires 12 events, Slack 2, Plain 2\. Filters run before the agent starts. * ### Model and identity per workflow Each workflow names its model and runs as a service account you can disable. Prompt What should this workflow do?Every weekday morning, list the pull requests opened in helios/api in the last 24 hours. For each one, read the diff and write a two line summary. Post the digest to #eng-daily. Plain language. Name the tools, the judgment calls, and the shape of the output. Integrations The agent may use the full API of each one. * GitHub · helios/api * Slack · #eng-daily * \+ Add integration Triggers New trigger IntegrationScheduleWebhook Describe the schedule cron0 9 \* \* 1-5UTC Write the schedule in words. Helios turns it into a cron expression you can check. Add trigger Active triggers * Schedule · 0 9 \* \* 1-5Enabled× * Integration · github · pull\_request.openedEnabled× Chat ## Start in chat. See every step. * ### Every tool call is visible The endpoint, the payload, and the timing appear as the agent works. * ### A sandbox behind the chat When a step needs a script, the agent writes one and runs it. * ### Fork, stop, share Branch a chat, stop a run mid-step, or share it up to a chosen message. How can I help you? Describe the task ⌘I IntegrationsUpload file Send * Summarize what changed in #support this week * Which open PRs in helios/api touch billing? * Pull last month's invoices from Stripe into a CSV * Check the failed CI runs from last night Library ## Shared context, reviewed by people. * ### Mounted in every sandbox Agents read the Library at \~/context like any other folder. * ### Edits become a staged change A run's file changes wait as one change set with a side-by-side diff. * ### A person approves each file Nothing reaches the team until someone approves. A run cannot approve its own work. Review inbox · 3 pending Reset * refund-policy.mdPendingModified · weekly support digest run * oncall-rota.mdPendingModified · on-call rotation run * pricing-faq.mdPendingAdded · CRM cleanup run organization/support/refund-policy.md Proposed by the weekly support digest run. Modified. DiscardApprove # Refund policy -Refunds are handled case by case.+Refund within 14 days of purchase, no questions asked.+After 14 days, escalate to a support lead. Source: support handbook, section 3. Code ## Your environment, your terminal, your agent. * ### Built from your Dockerfile Helios builds the image and keeps every version with its build log. * ### Claude Code, already signed in Connect your Claude account once. Every sandbox starts authorized. * ### Launch, watch, attach from the CLI Run helios configure once, then drive agents from your own terminal. helios · configure $helios configure✓ API key saved✓ Project: acme-platform✓ Claude account connected✓ GitHub connected✓ Environment: node-22 (built from Dockerfile)→ Launching first agent… boot pulling image node-22:v3 boot cloning acme/platform into ~/workspace boot starting claude code✓ Agent running. Press Enter to attach. The install command and supported platforms are in the docs. [Install the CLI →](/docs/cli/install/) MCP ## MCP, in both directions. * ### Remote servers over HTTPS Point Helios at a Streamable HTTP server. Localhost and private ranges are rejected. * ### A tool allowlist per server The proxy hides tools you did not list and rejects calls to them. * ### Helios as a server Any MCP client can search the Helios API and call what it finds. Claude CodeCursorVS CodeClaude Desktop terminal $claude mcp add --transport http helios \ /mcp \ --header "Authorization: Bearer ${HELIOS_API_KEY}" Copy Add Helios to Claude Code, an IDE, or any MCP client. Your client searches the Helios API, then calls what it finds. ## Frequently asked questions ### What is a workflow? ### How do I write a schedule? ### Which tools can start a workflow from an event? ### Can I see what the agent is doing in a chat? ### Can an agent change shared files without a person? ### Which coding agent runs in the sandbox? ### Does the agent ever see an MCP server's token? ### What does a run cost? Keep going ## Keep reading Learn how to connect tools, manage access, and start from a template. [IntegrationsYour tools are already here.The full API of each service, three auth modes, and the trigger matrix.](/integrations/)[SecurityEvery run is isolated. No agent holds a token.Credential injection, encrypted secrets, roles with expiry, and spending limits.](/security/)[TemplatesStart from a template.Ready-made prompts and triggers for support digests, CRM cleanup, and recurring reports.](/templates/) ## Give your first agent a computer. Start with 5,000 free credits. Connect one tool, describe one task, and read the transcript. [Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios) --- # Security - Isolated Runs, No Tokens in the Sandbox | Helios URL: https://www.heliosapp.com/security Description: One sandbox per run. Credentials injected at the network layer. Envelope-encrypted secrets, signed webhooks, four resource roles, share expiry, spending limits, and full run transcripts. Security # Isolated runs. No agent holds a token. Every run gets its own sandbox. Credentials are added at the network layer, outside the sandbox. This page describes each control and names the limits. [Book a demo](https://cal.com/suryao/helios)[Get started free](https://app.heliosapp.com/) * One sandbox per run * Credentials never enter the sandbox * Full run transcripts Isolation ## Every agent works on its own computer An agent is a process on a real machine, and that machine is the security boundary. The sandbox exists for one run and then goes away. A fresh sandbox per run and per chat Every workflow run and every chat starts in a new cloud sandbox with its own filesystem, processes, and network egress. Code the agent writes, packages it installs, and files it downloads stay inside that boundary and are gone when the run ends. No sharing between runs Two runs never share a machine. A run cannot read another run's files or reach its processes. The blast radius of a bad instruction is one sandbox. A 30 minute limit A workflow run stops after 30 minutes. Long tasks are split into several runs on a schedule. No inbound traffic Sandboxes accept no public inbound connections. The agent reaches out to do its work. Nothing on the internet reaches in. Private networking, when you need it Connect sandboxes to your private network over Tailscale. Configure it once for the organization or for one project. Choose an API key or OIDC. With OIDC, Helios stores no Tailscale credential at all. Your own environment image Build the sandbox image from your Dockerfile when the default image is not enough. The same isolation rules apply to custom images. Credentials ## Agents use your tools without your keys The most valuable thing an agent touches is the credential that lets it act. Helios is built so the agent can act without ever holding it. Credentials stay on the Helios side When you connect GitHub, Slack, or Stripe, Helios stores the OAuth token or API key. The agent never receives it. Injected by the egress proxy The agent's code makes a normal API request from the sandbox. The request leaves through a proxy that attaches the credential for that host and that run. The response comes back. The key does not. The model sees a redacted config When an agent inspects how an integration is set up, encrypted fields are removed before the description reaches the model. It learns only that an integration is authenticated. Scoped to the resources you pinned Pin one repository, one channel, or one database to a workflow and that is what the agent can reach. The reach of a task is a decision someone made. Databases with the user you choose Connect Postgres, MySQL, or ClickHouse with the database user you pick, through an SSH tunnel if you need one. A read-only user gives the agent read-only access. One hour credentials for Library files When a run reads or writes Library files, it gets an S3 credential limited to the paths it was granted and valid for one hour. Secrets and variables ## Two kinds of values, treated differently Variables and secrets look alike in the UI and behave very differently. The difference is what an agent is allowed to see. Variables are configuration A variable is a plain value like a channel name, a repository slug, or a threshold. Agents receive variables as run context and refer to them by name in the prompt. Secrets are write-only A secret is encrypted with AES-256-GCM under its own data key, and that key is wrapped by a master key in AWS KMS. Once saved, the API never returns the plaintext to the UI or to an agent. Secrets never enter a prompt Agents do not receive secrets as text. They reach your tools through integrations, where Helios applies the credential outside the sandbox. Four scopes Set a value on the organization, a project, a user, or one workflow. The most specific level wins. Editing requires the editor role on that resource. Bring secrets from Infisical Connect Infisical with Universal Auth and reference a secret by its Infisical path. Helios resolves it when the run starts. | Variable | Secret | | | ---------------- | ------------------- | ------------------ | | Stored as | Plaintext | Envelope-encrypted | | Readable back | Yes | No | | Passed to agents | Yes, as run context | No | Access model ## Access controls for people and agents Who someone is comes from sign-in. What they can touch is decided by grants on each resource and by their role in the organization. Both are evaluated by Cedar on every request. One permissions model, everywhere Every request is checked by the same policy engine, whether it comes from the dashboard, the API, or a run. Permissions come from grants. Organizations are hard boundaries A principal and a resource must belong to the same organization. That rule outranks every grant. Groups and service accounts Put people and service accounts in groups and share with the group. A service account is a named identity for automation. Disable it and everything it ran stops. Sharing with expiry Share a workflow, project, or integration with a person, a group, or everyone in the organization. Set the share to expire after a day, a week, or a custom date. You can never share above your own role. Act as a person, by choice A service account can use your own GitHub or Slack login for a grant when you turn that on. Otherwise it uses the Helios app credential. SSO through WarpBuild auth Helios uses the shared WarpBuild sign-in. Login with GitHub, Google, or your identity provider over SAML 2.0 or OIDC. Contact support to enable SSO for your organization. | Scope | Role | What it allows | | ------------ | -------- | ------------------------------------------------------------------------ | | Resource | Viewer | Can see the resource. Cannot change it or act through it. | | Resource | Operator | Can also run it or work through it without changing what it is. | | Resource | Editor | Can also change it, including what lives inside it. | | Resource | Admin | Full control, including its secrets and the identities that act as it. | | Organization | Viewer | Can see the organization's groups and service accounts. Creates nothing. | | Organization | Member | Can also create projects and service accounts. | | Organization | Admin | Can also manage groups and who belongs to them. | Run history ## Read what every agent did Trust comes from being able to check. Every run leaves a record you can open. A full transcript for every run Each run keeps its reasoning, every tool call with its arguments and result, timing, and error codes. Open any past run and read exactly what the agent did. Tool calls as they happen In chat, each API call and shell command appears in the thread while the agent works. Stop the run at any point. Model calls are traced Helios traces every model call with Langfuse. The trace links the prompt, the response, and the cost to the run that made it. Sandbox lifecycle is recorded Sandbox creation, pause, resume, and shutdown arrive over signature-verified webhooks and are stored against the run and the organization that caused them. What is not here yet There is no notification when a run fails and no export of run history. Read the transcript in the dashboard or over the API. Spend controls ## A bill you can read and cap An agent that can run all night can also spend all night. Helios puts the ceiling in your hands. Everything is priced in credits Model calls and sandbox time are both charged in credits. You start with 5,000 free credits. After that, one credit costs $0.002. A spending limit per product Set a monthly limit for Helios, separate from the WarpBuild CI limit. Spend stops at the number you set. Triggers stop at zero When credits run out, scheduled and event triggers stop starting runs. Nothing queues up a bill you did not expect. Auto refill, if you want it Turn on auto refill with a threshold and an amount of your choosing. Leave it off and runs simply stop until you add credits. Cost per run in the record Model spend and sandbox cost are tracked per organization and visible next to the run that used them. Network and webhooks ## Control inbound and outbound access Agents accept work from outside. A webhook fires, an MCP server answers. Each doorway is checked before anything walks through it. Signed webhooks Every webhook trigger has its own secret. Each request carries an HMAC-SHA256 signature and a timestamp. Helios checks both with a timing-safe comparison and rejects anything older than five minutes. Secret rotation Rotate a webhook secret whenever you need to. The endpoint keeps its address. Only the signature changes. MCP servers that cannot point inward When you attach an external MCP server, Helios resolves and checks the destination before every connection. The URL must be HTTPS. Loopback, private and reserved ranges, link-local addresses, and cloud metadata endpoints are refused. Transport headers stay fixed You can send an MCP server up to twenty custom headers, including Authorization. Headers that define the transport itself, such as host and content-length, are refused. Encryption in transit and at rest Traffic to Helios and between Helios and your tools is encrypted in transit. Data at rest is encrypted. Secrets get a second envelope on top. Data and disclosure ## Where your data goes, and who to call No badges. A list of who holds your data, and an address for anyone who finds a problem. Where data lives Helios runs on cloud infrastructure in the United States. Every run executes in a cloud sandbox. Customer data is stored with the providers on the subprocessor list and nowhere else. Subprocessors Every vendor that touches customer data is listed with what it does. [See the subprocessor list](/legal/subprocessors/). Your data does not train models Helios does not use your prompts, files, or run output to train models. Model providers are listed as subprocessors. Data processing addendum A DPA is available for customers that need one. [Read how to request it](/legal/dpa/). Responsible disclosure Found a vulnerability? Email [support@heliosapp.com](mailto:support@heliosapp.com) with the steps to reproduce it. We reply to every report and will not take action against good-faith research. ## Questions from security reviews ### Where do agents run? ### Can an agent see the credentials for our integrations? ### How are secrets stored? ### Who in our company can see a workflow or its runs? ### Can agents reach our private network? ### What stops a webhook trigger from being abused? ### Do you have a SOC 2 report? ### Do you offer SSO? ### Can we see what an agent did after the fact? ## Bring your security review Walk through each control with the people who built it. [Book a demo](https://cal.com/suryao/helios)[Get started free](https://app.heliosapp.com/) --- # Workflow templates | Helios URL: https://www.heliosapp.com/templates Description: Workflow templates with the exact prompt, the trigger each one needs, and the integrations it uses. Copy the prompt, connect your tools, and run it. Templates # Workflows you can run today. 15 templates. Each one has the exact prompt, the trigger that starts it, and the integrations it uses. Copy the prompt, connect the tools, and read the first run. [Get started free](https://app.heliosapp.com/)[See use cases](/use-cases) 5,000 free credits to start. ## Engineering 04 [EngineeringPull request reviewerReviews every pull request against your conventions and leaves inline comments only where it found something concrete.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/pr-review-digest/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes a draft release on GitHub, and files a changelog entry in Notion.github · tag.created![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/github-release-notes/)[EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup to Slack every weekday morning.Weekdays at 9:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/daily-standup-digest/)[EngineeringIncident postmortem drafterRebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/incident-postmortem-drafter/) ## Support 03 [SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.slack · message.channel![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/templates/slack-support-triage/)[SupportPlain thread triageTriages every new Plain thread on arrival. Labels, priority, a draft reply, and an internal note with what it checked.plain · thread.thread\_created![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/plain-thread-summarizer/)[SupportDocumentation freshness auditChecks your written docs against the codebase every month and comments on the pages that have gone stale.Monthly on the 1st![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/notion-docs-freshness-audit/) ## Sales & RevOps 04 [Sales & RevOpsFailed payment recoveryFinds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/stripe-failed-payment-recovery/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to find the accounts drifting toward the exit.Mondays at 7:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/churn-risk-watchlist/)[Sales & RevOpsInbound lead enrichmentEnriches every new signup, scores it against your ICP by reading the company's own website, and routes the strong fits.Signup webhook![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/apollo-lead-enrichment/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing company fields, and flags deals that have gone quiet. Every night.Nightly at 2:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/attio-crm-hygiene/) ## Operations 02 [OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out.Mondays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/weekly-metrics-report/)[OperationsNightly data quality checksRuns your invariants against production every night and emails the on-call analyst which rows broke and since when.Nightly at 3:00am![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/templates/database-health-check/) ## Marketing 02 [MarketingReddit brand monitorSweeps the subreddits where your customers gather, judges which threads deserve a reply, and brings you a shortlist.Every 4 hours![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/reddit-brand-monitor/)[MarketingResearch brief writerResearches a topic across the live web and returns a sourced draft in your voice, with the open questions flagged.Run on demand![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)![](/static/img/assets/apify.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/google-docs-brief-writer/) ## Take a template and make it yours. Edit the prompt, connect your tools, and choose when the workflow should run. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Inbound lead enrichment template | Helios URL: https://www.heliosapp.com/templates/apollo-lead-enrichment Description: Enriches every new signup, scores it against your ICP by reading the company's own website, and routes the strong fits. [← All templates](/templates/) Sales & RevOps Signup webhook # Inbound lead enrichment Enriches every new signup, scores it against your ICP by reading the company's own website, and routes the strong fits. [Get started free](https://app.heliosapp.com/)[Copy the prompt](#prompt) 5,000 free credits to start. The prompt ## The workflow prompt Copy this prompt into a new workflow, connect the listed integrations, and configure its trigger. prompt.md When our signup webhook fires with a new user's email, enrich the person and their company in Apollo.Title, seniority, headcount, industry, funding stage.Then read the company's own website and tell me in two sentences what they do.Score fit from 0 to 100 against our ICP.B2B software companies, 50 to 500 employees, Series A through C, with an engineering team.Create or update the person and company in Attio with everything you found and the fit score.If the score is above 70, post to #inbound with the summary, the fit reasoning, and a suggested opening line based on something specific you learned about them.Assign the record to the owner for that territory. Copy the prompt Trigger ## What starts this workflow Signup webhook Runs when a signed webhook arrives. Helios checks the HMAC-SHA256 signature and hands the payload to the agent. ### Integrations it uses * [![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)Apollo](/integrations/apollo/) * [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Attio](/integrations/attio/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) Connect each service once. Helios stores the credential encrypted and injects it at the network layer on every run. The agent never holds the token. Example output ## What you get back Every run keeps its full transcript. The steps the agent took, each tool call, and the result. Lead scored 87/100 * Northwind · Series B fintech · 240 employees * Signup is Head of Platform * Routed to @dana with a suggested opener [Use this template](https://app.heliosapp.com/) New to Helios? Start with [Run your first workflow](/guides/run-your-first-agent/). Use cases ## The task behind this template [Sales & RevOpsLead enrichmentA signup or form response fires a webhook. The workflow enriches the person and company, scores fit against your definition, creates the CRM record, and tells the right rep.Signup webhook![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/typeform-light.svg)![](/static/img/assets/typeform-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/lead-enrichment/) Guides ## Set it up step by step [8 minUse secrets and variablesKeep the values a task needs out of the prompt. Variables hold configuration. Secrets hold credentials. The agent never sees a secret in plain text.](/guides/use-secrets-and-variables/)[15 minMove from Relay.app to HeliosRelay.app shut down on 16 July 2026\. Paid accounts are deleted on 14 September 2026\. Here is how each Relay concept maps to Helios, and what to export first.](/guides/move-from-relay-app/) Related templates ## Pair it with these [Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing company fields, and flags deals that have gone quiet. Every night.Nightly at 2:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/attio-crm-hygiene/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to find the accounts drifting toward the exit.Mondays at 7:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/churn-risk-watchlist/)[Sales & RevOpsFailed payment recoveryFinds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/stripe-failed-payment-recovery/) ## Run Inbound lead enrichment on your tools. Connect the integrations, paste the prompt, and pick the trigger. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Nightly CRM hygiene template | Helios URL: https://www.heliosapp.com/templates/attio-crm-hygiene Description: Merges duplicates, fills missing company fields, and flags deals that have gone quiet. Every night. [← All templates](/templates/) Sales & RevOps Nightly at 2:00am # Nightly CRM hygiene Merges duplicates, fills missing company fields, and flags deals that have gone quiet. Every night. [Get started free](https://app.heliosapp.com/)[Copy the prompt](#prompt) 5,000 free credits to start. The prompt ## The workflow prompt Copy this prompt into a new workflow, connect the listed integrations, and configure its trigger. prompt.md Every night at 2am, clean up our Attio workspace.Find company records that look like duplicates by domain or normalized name, and merge them, keeping the record with the most activity.Find companies missing headcount, industry, or funding stage, enrich them in Apollo, and fill only the empty fields.Never overwrite a value a person already set.Find deals in an open stage with no activity in 21 days and add a note tagging the owner asking whether it is still live.Post a summary to #revops.How many merged, how many enriched, how many flagged, and anything you skipped because you were unsure. Copy the prompt Trigger ## What starts this workflow Nightly at 2:00am Runs on a schedule. Describe the cadence in plain words and Helios writes the cron expression. Schedules run in UTC. ### Integrations it uses * [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Attio](/integrations/attio/) * [![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)Apollo](/integrations/apollo/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) Connect each service once. Helios stores the credential encrypted and injects it at the network layer on every run. The agent never holds the token. Example output ## What you get back Every run keeps its full transcript. The steps the agent took, each tool call, and the result. CRM hygiene pass complete * 61 records enriched * 9 duplicates merged * 14 deals flagged stale for their owners [Use this template](https://app.heliosapp.com/) New to Helios? Start with [Run your first workflow](/guides/run-your-first-agent/). Use cases ## The task behind this template [Sales & RevOpsLead enrichmentA signup or form response fires a webhook. The workflow enriches the person and company, scores fit against your definition, creates the CRM record, and tells the right rep.Signup webhook![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/typeform-light.svg)![](/static/img/assets/typeform-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/lead-enrichment/)[Sales & RevOpsCRM data syncA workflow computes usage from your database, joins it with billing state and support volume, and writes the result onto each account record every night.Nightly at 1:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)](/use-cases/crm-data-sync/) Guides ## Set it up step by step [8 minPut a workflow on a scheduleTurn a working prompt into a standing task. Describe the cadence the way you would say it out loud. Helios writes the cron expression.](/guides/put-an-agent-on-a-schedule/) Related templates ## Pair it with these [Sales & RevOpsInbound lead enrichmentEnriches every new signup, scores it against your ICP by reading the company's own website, and routes the strong fits.Signup webhook![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/apollo-lead-enrichment/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to find the accounts drifting toward the exit.Mondays at 7:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/churn-risk-watchlist/)[Sales & RevOpsFailed payment recoveryFinds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/stripe-failed-payment-recovery/) ## Run Nightly CRM hygiene on your tools. Connect the integrations, paste the prompt, and pick the trigger. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Churn risk watchlist template | Helios URL: https://www.heliosapp.com/templates/churn-risk-watchlist Description: Joins billing signals with product usage and support volume to find the accounts drifting toward the exit. [← All templates](/templates/) Sales & RevOps Mondays at 7:00am # Churn risk watchlist Joins billing signals with product usage and support volume to find the accounts drifting toward the exit. [Get started free](https://app.heliosapp.com/)[Copy the prompt](#prompt) 5,000 free credits to start. The prompt ## The workflow prompt Copy this prompt into a new workflow, connect the listed integrations, and configure its trigger. prompt.md Every Monday at 7am, build a churn risk list.Query Postgres for each account's product usage over the last 60 days and compute the trend against the 60 days before that.Read subscription status and payment history from Stripe.Count open and recently closed support threads per account in Plain.Score each account for churn risk and explain the score in one sentence.Usage decline, failed payments, support volume, or a combination.Write the score and the explanation onto the Attio account record.Post the top ten at-risk accounts to #revenue with the total ARR they represent, the reason for each, and a suggested next action for the owner. Copy the prompt Trigger ## What starts this workflow Mondays at 7:00am Runs on a schedule. Describe the cadence in plain words and Helios writes the cron expression. Schedules run in UTC. ### Integrations it uses * [Stripe](/integrations/stripe/) * [Databases](/integrations/databases/) * [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Attio](/integrations/attio/) * [![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)Plain](/integrations/plain/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) Connect each service once. Helios stores the credential encrypted and injects it at the network layer on every run. The agent never holds the token. Example output ## What you get back Every run keeps its full transcript. The steps the agent took, each tool call, and the result. 11 accounts at risk * $38k ARR represented * 6 driven by usage decline, 3 by failed payments * Each has a suggested next action for its owner [Use this template](https://app.heliosapp.com/) New to Helios? Start with [Run your first workflow](/guides/run-your-first-agent/). Use cases ## The task behind this template [OperationsBilling operationsA workflow watches Stripe for failed charges and starts recovery. A second one reconciles what you billed against what your own database recorded after the books close.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/billing-ops/)[Sales & RevOpsCRM data syncA workflow computes usage from your database, joins it with billing state and support volume, and writes the result onto each account record every night.Nightly at 1:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)](/use-cases/crm-data-sync/) Guides ## Set it up step by step [10 minConnect a databaseGive a workflow Postgres, MySQL, or ClickHouse. It reads the schema, writes real SQL, and checks the results in its own sandbox.](/guides/connect-a-database/) Related templates ## Pair it with these [Sales & RevOpsFailed payment recoveryFinds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/stripe-failed-payment-recovery/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing company fields, and flags deals that have gone quiet. Every night.Nightly at 2:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/attio-crm-hygiene/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out.Mondays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/weekly-metrics-report/) ## Run Churn risk watchlist on your tools. Connect the integrations, paste the prompt, and pick the trigger. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Standup without the meeting template | Helios URL: https://www.heliosapp.com/templates/daily-standup-digest Description: Reads yesterday's commits, merges, and review queue, then posts a standup to Slack every weekday morning. [← All templates](/templates/) Engineering Weekdays at 9:00am # Standup without the meeting Reads yesterday's commits, merges, and review queue, then posts a standup to Slack every weekday morning. [Get started free](https://app.heliosapp.com/)[Copy the prompt](#prompt) 5,000 free credits to start. The prompt ## The workflow prompt Copy this prompt into a new workflow, connect the listed integrations, and configure its trigger. prompt.md Every weekday at 9am, look at our GitHub org and gather everything that happened since 9am yesterday.Commits pushed, pull requests opened, pull requests merged, and pull requests still waiting for review.Group it by engineer.For each person write one line about what they shipped.Then list anything that looks blocked.A pull request open more than three days, a review requested more than a day ago with no response, or a failing check on a pull request that is otherwise ready.Post this to #standup as a single message.Keep it under twenty lines and leave out anyone with no activity. Copy the prompt Trigger ## What starts this workflow Weekdays at 9:00am Runs on a schedule. Describe the cadence in plain words and Helios writes the cron expression. Schedules run in UTC. ### Integrations it uses * [GitHub](/integrations/github/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) Connect each service once. Helios stores the credential encrypted and injects it at the network layer on every run. The agent never holds the token. Example output ## What you get back Every run keeps its full transcript. The steps the agent took, each tool call, and the result. Standup · Mar 6 * 5 engineers shipped 12 PRs * @sam blocked on a review for #2841 * Nothing red in CI overnight [Use this template](https://app.heliosapp.com/) New to Helios? Start with [Run your first workflow](/guides/run-your-first-agent/). Use cases ## The task behind this template [EngineeringPull request reviewA workflow reads each diff against your conventions and leaves a real review. A second workflow on a schedule posts the week's merged work, review backlog, and CI health.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/pr-review-digest/) Guides ## Set it up step by step [10 minRun your first workflowDescribe a task in plain words, give the agent one tool, and read the run. Ten minutes from an empty workspace to a transcript you can read end to end.](/guides/run-your-first-agent/)[8 minPut a workflow on a scheduleTurn a working prompt into a standing task. Describe the cadence the way you would say it out loud. Helios writes the cron expression.](/guides/put-an-agent-on-a-schedule/)[9 minShare with your teamHand a workflow to the people who need it. Four roles decide who may view, run, or edit. Every run leaves a transcript of what happened.](/guides/share-with-your-team/) Related templates ## Pair it with these [EngineeringPull request reviewerReviews every pull request against your conventions and leaves inline comments only where it found something concrete.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/pr-review-digest/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes a draft release on GitHub, and files a changelog entry in Notion.github · tag.created![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/github-release-notes/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out.Mondays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/weekly-metrics-report/) ## Run Standup without the meeting on your tools. Connect the integrations, paste the prompt, and pick the trigger. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Nightly data quality checks template | Helios URL: https://www.heliosapp.com/templates/database-health-check Description: Runs your invariants against production every night and emails the on-call analyst which rows broke and since when. [← All templates](/templates/) Operations Nightly at 3:00am # Nightly data quality checks Runs your invariants against production every night and emails the on-call analyst which rows broke and since when. [Get started free](https://app.heliosapp.com/)[Copy the prompt](#prompt) 5,000 free credits to start. The prompt ## The workflow prompt Copy this prompt into a new workflow, connect the listed integrations, and configure its trigger. prompt.md Every night at 3am, run our data quality checks against the production Postgres replica.Check that no order has a null currency, every account's plan is one of the four values in our enum, no invoice has a total below zero, every user row has a matching account, and the events table has received rows in each of the last 24 hours.For every failing check, find how many rows are affected, identify the earliest affected row and its timestamp, and look at what changed upstream around that time.Email the on-call analyst through Resend with only the failures, the affected row counts, the first occurrence, and the query you ran.When everything passes, send nothing. Copy the prompt Trigger ## What starts this workflow Nightly at 3:00am Runs on a schedule. Describe the cadence in plain words and Helios writes the cron expression. Schedules run in UTC. ### Integrations it uses * [Databases](/integrations/databases/) * [![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)Resend](/integrations/resend/) Connect each service once. Helios stores the credential encrypted and injects it at the network layer on every run. The agent never holds the token. Example output ## What you get back Every run keeps its full transcript. The steps the agent took, each tool call, and the result. 2 checks failed * \`orders.currency\` null on 41 rows since 02:10 * \`accounts.plan\` has 3 values outside the enum * 12 checks passed [Use this template](https://app.heliosapp.com/) New to Helios? Start with [Run your first workflow](/guides/run-your-first-agent/). Use cases ## The task behind this template [OperationsDatabase reportingA workflow reads your schema, writes the SQL, runs it, checks the results in its sandbox, and posts a report to the channel your team reads.Weekdays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/database-reporting/) Guides ## Set it up step by step [10 minConnect a databaseGive a workflow Postgres, MySQL, or ClickHouse. It reads the schema, writes real SQL, and checks the results in its own sandbox.](/guides/connect-a-database/)[10 minAttach an MCP serverPoint Helios at a remote MCP server, choose which of its tools workflows may call, and use Helios itself over MCP from other clients.](/guides/attach-an-mcp-server/)[8 minUse secrets and variablesKeep the values a task needs out of the prompt. Variables hold configuration. Secrets hold credentials. The agent never sees a secret in plain text.](/guides/use-secrets-and-variables/) Related templates ## Pair it with these [OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out.Mondays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/weekly-metrics-report/)[EngineeringIncident postmortem drafterRebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/incident-postmortem-drafter/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to find the accounts drifting toward the exit.Mondays at 7:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/churn-risk-watchlist/) ## Run Nightly data quality checks on your tools. Connect the integrations, paste the prompt, and pick the trigger. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Release notes writer template | Helios URL: https://www.heliosapp.com/templates/github-release-notes Description: Turns a new tag into release notes grouped by theme, publishes a draft release on GitHub, and files a changelog entry in Notion. [← All templates](/templates/) Engineering github · tag.created # Release notes writer Turns a new tag into release notes grouped by theme, publishes a draft release on GitHub, and files a changelog entry in Notion. [Get started free](https://app.heliosapp.com/)[Copy the prompt](#prompt) 5,000 free credits to start. The prompt ## The workflow prompt Copy this prompt into a new workflow, connect the listed integrations, and configure its trigger. prompt.md When a tag is created, compare it against the previous tag and read every merged pull request between them, including the bodies and the linked issues.Group the changes into Features, Improvements, Fixes, and Breaking changes.Write each entry for a user of the product.Say what changed for them and skip internal refactors.For any breaking change, include a short migration snippet.Publish a draft release on GitHub with these notes.Then create a matching entry in the Notion Changelog database with the same content and a link to the release. Copy the prompt Trigger ## What starts this workflow github · tag.created Runs when the event fires in the connected service. Filters keep the workflow on the events you want. Event triggers are available for GitHub, Slack, and Plain. ### Integrations it uses * [GitHub](/integrations/github/) * [Notion](/integrations/notion/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) Connect each service once. Helios stores the credential encrypted and injects it at the network layer on every run. The agent never holds the token. Example output ## What you get back Every run keeps its full transcript. The steps the agent took, each tool call, and the result. Draft release v2.8.0 * Features · 6 entries, led by scheduled exports * Fixes · 11 entries, grouped by area * Breaking · 1 entry, with a migration snippet [Use this template](https://app.heliosapp.com/) New to Helios? Start with [Run your first workflow](/guides/run-your-first-agent/). Use cases ## The task behind this template [EngineeringPull request reviewA workflow reads each diff against your conventions and leaves a real review. A second workflow on a schedule posts the week's merged work, review backlog, and CI health.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/pr-review-digest/) Guides ## Set it up step by step [12 minReact to GitHub eventsStart a run the moment a pull request opens, a build finishes, or a tag lands. Filter down to exactly the events you want.](/guides/react-to-github-events/)[7 minPin repositories as contextPin a GitHub repository to a workflow or a chat. The agent starts every run with it.](/guides/pin-context-resources/) Related templates ## Pair it with these [EngineeringPull request reviewerReviews every pull request against your conventions and leaves inline comments only where it found something concrete.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/pr-review-digest/)[EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup to Slack every weekday morning.Weekdays at 9:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/daily-standup-digest/)[SupportDocumentation freshness auditChecks your written docs against the codebase every month and comments on the pages that have gone stale.Monthly on the 1st![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/notion-docs-freshness-audit/) ## Run Release notes writer on your tools. Connect the integrations, paste the prompt, and pick the trigger. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Research brief writer template | Helios URL: https://www.heliosapp.com/templates/google-docs-brief-writer Description: Researches a topic across the live web and returns a sourced draft in your voice, with the open questions flagged. [← All templates](/templates/) Marketing Run on demand # Research brief writer Researches a topic across the live web and returns a sourced draft in your voice, with the open questions flagged. [Get started free](https://app.heliosapp.com/)[Copy the prompt](#prompt) 5,000 free credits to start. The prompt ## The workflow prompt Copy this prompt into a new workflow, connect the listed integrations, and configure its trigger. prompt.md I will give you a topic.Search the web and read at least a dozen credible sources.Prefer primary sources, official documentation, and recent writing over listicles.Before you draft, read the last three briefs in our Google Drive marketing folder so you match our voice, structure, and level of detail.Then write the brief in a new Google Doc.An executive summary, four to six sections, and a short conclusion.Link every factual claim to the source it came from.Where sources disagree, say so and present both.Where the research is thin, write what you found and leave an inline note saying the evidence is weak.Share the doc to the marketing folder and post the link in #marketing. Copy the prompt Trigger ## What starts this workflow Run on demand Runs when you start it. From the workflow page, from chat, from the CLI, or over the API. ### Integrations it uses * [![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)Google Docs](/integrations/google-docs/) * [Google Drive](/integrations/google-drive/) * [![](/static/img/assets/apify.svg)Apify](/integrations/apify/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) Connect each service once. Helios stores the credential encrypted and injects it at the network layer on every run. The agent never holds the token. Example output ## What you get back Every run keeps its full transcript. The steps the agent took, each tool call, and the result. \`SOC 2 Buyer's Brief\` created * 1,900 words across 5 sections * Every claim linked to a source * 4 open questions left as inline notes [Use this template](https://app.heliosapp.com/) New to Helios? Start with [Run your first workflow](/guides/run-your-first-agent/). Use cases ## The task behind this template [MarketingResearch briefsA workflow searches the web, reads what it finds, and writes a draft with every claim linked to its source. Give it your prior work and the draft matches your voice.Run on demand![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)![](/static/img/assets/apify.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/content-pipeline/)[MarketingCommunity monitoringA workflow sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space. It picks the threads worth a reply and brings them to your team.Every 4 hours![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/community-monitoring/) Guides ## Set it up step by step [8 minReview agent changes in the LibraryAgents propose edits to shared files. A person reviews the diff and approves or discards each one. Nothing reaches the team's files without approval.](/guides/review-agent-changes-in-the-library/) Related templates ## Pair it with these [MarketingReddit brand monitorSweeps the subreddits where your customers gather, judges which threads deserve a reply, and brings you a shortlist.Every 4 hours![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/reddit-brand-monitor/)[SupportDocumentation freshness auditChecks your written docs against the codebase every month and comments on the pages that have gone stale.Monthly on the 1st![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/notion-docs-freshness-audit/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes a draft release on GitHub, and files a changelog entry in Notion.github · tag.created![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/github-release-notes/) ## Run Research brief writer on your tools. Connect the integrations, paste the prompt, and pick the trigger. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Incident postmortem drafter template | Helios URL: https://www.heliosapp.com/templates/incident-postmortem-drafter Description: Rebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion. [← All templates](/templates/) Engineering Run on demand # Incident postmortem drafter Rebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion. [Get started free](https://app.heliosapp.com/)[Copy the prompt](#prompt) 5,000 free credits to start. The prompt ## The workflow prompt Copy this prompt into a new workflow, connect the listed integrations, and configure its trigger. prompt.md I will give you the name of an incident Slack channel.Read the entire channel including every thread.Work out when impact started, when we detected it, when we mitigated it, and when it fully resolved.Cite the message that tells you each.Then look at GitHub for every deploy, merge, and revert in the two hours before impact started, and read the diffs of the likely candidates.Build a minute by minute timeline.Draft a postmortem in the Notion Postmortems database with a summary, impact, timeline, contributing factors, what went well, and action items.Pull the action items from what people agreed to in the channel, with owners.State your assumptions wherever the channel is unclear. Copy the prompt Trigger ## What starts this workflow Run on demand Runs when you start it. From the workflow page, from chat, from the CLI, or over the API. ### Integrations it uses * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) * [GitHub](/integrations/github/) * [Notion](/integrations/notion/) Connect each service once. Helios stores the credential encrypted and injects it at the network layer on every run. The agent never holds the token. Example output ## What you get back Every run keeps its full transcript. The steps the agent took, each tool call, and the result. Postmortem drafted * 41-minute impact window rebuilt * Likely deploy identified as #2833 * 5 action items pulled from the discussion [Use this template](https://app.heliosapp.com/) New to Helios? Start with [Run your first workflow](/guides/run-your-first-agent/). Use cases ## The task behind this template [EngineeringIncident summariesA workflow rebuilds the timeline from your incident channel and the deploys around it. It names the likely change and drafts the write-up with the facts in place.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/incident-summaries/) Guides ## Set it up step by step [12 minReact to GitHub eventsStart a run the moment a pull request opens, a build finishes, or a tag lands. Filter down to exactly the events you want.](/guides/react-to-github-events/)[10 minAttach an MCP serverPoint Helios at a remote MCP server, choose which of its tools workflows may call, and use Helios itself over MCP from other clients.](/guides/attach-an-mcp-server/)[7 minPin repositories as contextPin a GitHub repository to a workflow or a chat. The agent starts every run with it.](/guides/pin-context-resources/) Related templates ## Pair it with these [EngineeringPull request reviewerReviews every pull request against your conventions and leaves inline comments only where it found something concrete.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/pr-review-digest/)[EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup to Slack every weekday morning.Weekdays at 9:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/daily-standup-digest/)[OperationsNightly data quality checksRuns your invariants against production every night and emails the on-call analyst which rows broke and since when.Nightly at 3:00am![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/templates/database-health-check/) ## Run Incident postmortem drafter on your tools. Connect the integrations, paste the prompt, and pick the trigger. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Documentation freshness audit template | Helios URL: https://www.heliosapp.com/templates/notion-docs-freshness-audit Description: Checks your written docs against the codebase every month and comments on the pages that have gone stale. [← All templates](/templates/) Support Monthly on the 1st # Documentation freshness audit Checks your written docs against the codebase every month and comments on the pages that have gone stale. [Get started free](https://app.heliosapp.com/)[Copy the prompt](#prompt) 5,000 free credits to start. The prompt ## The workflow prompt Copy this prompt into a new workflow, connect the listed integrations, and configure its trigger. prompt.md On the first of every month, audit our Engineering Docs in Notion against the codebase.For each page, find the files, environment variables, commands, and API routes it references, then read those files on the main branch of our GitHub repository.Flag a page as stale when it names something that no longer exists, describes behavior the code contradicts, or documents a default value that has changed.Leave a comment on each stale page saying exactly which line is wrong and what the code says now.Do not edit the pages themselves.Post a summary to #engineering listing the stale pages, and note any page you could not verify. Copy the prompt Trigger ## What starts this workflow Monthly on the 1st Runs on a schedule. Describe the cadence in plain words and Helios writes the cron expression. Schedules run in UTC. ### Integrations it uses * [Notion](/integrations/notion/) * [GitHub](/integrations/github/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) Connect each service once. Helios stores the credential encrypted and injects it at the network layer on every run. The agent never holds the token. Example output ## What you get back Every run keeps its full transcript. The steps the agent took, each tool call, and the result. 6 stale pages flagged * \`Auth Setup\` references a removed env var * \`Deploy Runbook\` names an old cluster * Each page commented with the specific line [Use this template](https://app.heliosapp.com/) New to Helios? Start with [Run your first workflow](/guides/run-your-first-agent/). Guides ## Set it up step by step [8 minReview agent changes in the LibraryAgents propose edits to shared files. A person reviews the diff and approves or discards each one. Nothing reaches the team's files without approval.](/guides/review-agent-changes-in-the-library/) Related templates ## Pair it with these [EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes a draft release on GitHub, and files a changelog entry in Notion.github · tag.created![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/github-release-notes/)[SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.slack · message.channel![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/templates/slack-support-triage/)[EngineeringPull request reviewerReviews every pull request against your conventions and leaves inline comments only where it found something concrete.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/pr-review-digest/) ## Run Documentation freshness audit on your tools. Connect the integrations, paste the prompt, and pick the trigger. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Plain thread triage template | Helios URL: https://www.heliosapp.com/templates/plain-thread-summarizer Description: Triages every new Plain thread on arrival. Labels, priority, a draft reply, and an internal note with what it checked. [← All templates](/templates/) Support plain · thread.thread\_created # Plain thread triage Triages every new Plain thread on arrival. Labels, priority, a draft reply, and an internal note with what it checked. [Get started free](https://app.heliosapp.com/)[Copy the prompt](#prompt) 5,000 free credits to start. The prompt ## The workflow prompt Copy this prompt into a new workflow, connect the listed integrations, and configure its trigger. prompt.md When a new thread is created in Plain, read it along with the customer record.Look up the customer's plan and payment state in Stripe.Search our Notion help center for the answer.Apply the right labels.Set priority from the plan tier.Enterprise is high.Everything else is normal unless the customer says they are blocked.Draft a reply and leave an internal note explaining what you checked.If the account is Enterprise and the thread sounds urgent, DM the account owner in Slack with a summary. Copy the prompt Trigger ## What starts this workflow plain · thread.thread\_created Runs when the event fires in the connected service. Filters keep the workflow on the events you want. Event triggers are available for GitHub, Slack, and Plain. ### Integrations it uses * [![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)Plain](/integrations/plain/) * [Stripe](/integrations/stripe/) * [Notion](/integrations/notion/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) Connect each service once. Helios stores the credential encrypted and injects it at the network layer on every run. The agent never holds the token. Example output ## What you get back Every run keeps its full transcript. The steps the agent took, each tool call, and the result. Thread triaged in 22 seconds * Labeled \`billing\` · priority \`high\` (Enterprise) * Draft reply cites the invoice settings doc * Internal note names Tuesday's failed charge [Use this template](https://app.heliosapp.com/) New to Helios? Start with [Run your first workflow](/guides/run-your-first-agent/). Use cases ## The task behind this template [SupportSupport triageA workflow reads each new thread as it arrives. It finds the customer, checks the plan and billing state, sets labels and priority, and drafts a reply from your docs.plain · thread.thread\_created![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/use-cases/support-triage/) Related templates ## Pair it with these [SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.slack · message.channel![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/templates/slack-support-triage/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to find the accounts drifting toward the exit.Mondays at 7:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/churn-risk-watchlist/)[Sales & RevOpsFailed payment recoveryFinds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/stripe-failed-payment-recovery/) ## Run Plain thread triage on your tools. Connect the integrations, paste the prompt, and pick the trigger. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Pull request reviewer template | Helios URL: https://www.heliosapp.com/templates/pr-review-digest Description: Reviews every pull request against your conventions and leaves inline comments only where it found something concrete. [← All templates](/templates/) Engineering github · pull\_request.opened # Pull request reviewer Reviews every pull request against your conventions and leaves inline comments only where it found something concrete. [Get started free](https://app.heliosapp.com/)[Copy the prompt](#prompt) 5,000 free credits to start. The prompt ## The workflow prompt Copy this prompt into a new workflow, connect the listed integrations, and configure its trigger. prompt.md When a pull request is opened or updated against main, read the full diff.Read CONTRIBUTING.md and the last twenty merged pull request reviews so you know what this team cares about.Check out the code and run the linter and the type checker.Leave a review with inline comments only where you found something concrete.An unhandled error path, a duplicated helper, a missing test for a new branch, a migration that is not backward compatible.Skip style nits the formatter already handles.If the change looks good, approve it with a one line summary.Post a link to your review in #eng and tag the author. Copy the prompt Trigger ## What starts this workflow github · pull\_request.opened Runs when the event fires in the connected service. Filters keep the workflow on the events you want. Event triggers are available for GitHub, Slack, and Plain. ### Integrations it uses * [GitHub](/integrations/github/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) Connect each service once. Helios stores the credential encrypted and injects it at the network layer on every run. The agent never holds the token. Example output ## What you get back Every run keeps its full transcript. The steps the agent took, each tool call, and the result. Review posted on PR #2841 * Flagged an unhandled error path in \`sync.ts:142\` * Suggested reusing \`parseCursor\` instead of a second parser * Confirmed the migration is backward compatible [Use this template](https://app.heliosapp.com/) New to Helios? Start with [Run your first workflow](/guides/run-your-first-agent/). Use cases ## The task behind this template [EngineeringPull request reviewA workflow reads each diff against your conventions and leaves a real review. A second workflow on a schedule posts the week's merged work, review backlog, and CI health.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/pr-review-digest/)[EngineeringIncident summariesA workflow rebuilds the timeline from your incident channel and the deploys around it. It names the likely change and drafts the write-up with the facts in place.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/incident-summaries/) Guides ## Set it up step by step [12 minReact to GitHub eventsStart a run the moment a pull request opens, a build finishes, or a tag lands. Filter down to exactly the events you want.](/guides/react-to-github-events/)[10 minAttach an MCP serverPoint Helios at a remote MCP server, choose which of its tools workflows may call, and use Helios itself over MCP from other clients.](/guides/attach-an-mcp-server/)[7 minPin repositories as contextPin a GitHub repository to a workflow or a chat. The agent starts every run with it.](/guides/pin-context-resources/) Related templates ## Pair it with these [EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup to Slack every weekday morning.Weekdays at 9:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/daily-standup-digest/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes a draft release on GitHub, and files a changelog entry in Notion.github · tag.created![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/github-release-notes/)[EngineeringIncident postmortem drafterRebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/incident-postmortem-drafter/) ## Run Pull request reviewer on your tools. Connect the integrations, paste the prompt, and pick the trigger. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Reddit brand monitor template | Helios URL: https://www.heliosapp.com/templates/reddit-brand-monitor Description: Sweeps the subreddits where your customers gather, judges which threads deserve a reply, and brings you a shortlist. [← All templates](/templates/) Marketing Every 4 hours # Reddit brand monitor Sweeps the subreddits where your customers gather, judges which threads deserve a reply, and brings you a shortlist. [Get started free](https://app.heliosapp.com/)[Copy the prompt](#prompt) 5,000 free credits to start. The prompt ## The workflow prompt Copy this prompt into a new workflow, connect the listed integrations, and configure its trigger. prompt.md Every four hours, search Reddit for mentions of our product name, our two main competitors, and the phrases people use to describe the problem we solve.Search the eight subreddits where our customers gather.For each mention, read the full comment tree so you understand the full context.Judge the sentiment and whether it deserves a reply from us.A question we can answer, a bug with a reproduction, a comparison thread, or praise worth thanking.Post only the threads worth acting on to #community, each with a link, a two line summary, the sentiment, and a suggested reply.Say how many mentions you reviewed and skipped so we know the coverage. Copy the prompt Trigger ## What starts this workflow Every 4 hours Runs on a schedule. Describe the cadence in plain words and Helios writes the cron expression. Schedules run in UTC. ### Integrations it uses * [Reddit](/integrations/reddit/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) Connect each service once. Helios stores the credential encrypted and injects it at the network layer on every run. The agent never holds the token. Example output ## What you get back Every run keeps its full transcript. The steps the agent took, each tool call, and the result. 3 threads worth a reply * One asks how we compare on pricing * One reports a real bug with a reproduction * 11 mentions reviewed and skipped [Use this template](https://app.heliosapp.com/) New to Helios? Start with [Run your first workflow](/guides/run-your-first-agent/). Use cases ## The task behind this template [MarketingResearch briefsA workflow searches the web, reads what it finds, and writes a draft with every claim linked to its source. Give it your prior work and the draft matches your voice.Run on demand![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)![](/static/img/assets/apify.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/content-pipeline/)[MarketingCommunity monitoringA workflow sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space. It picks the threads worth a reply and brings them to your team.Every 4 hours![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/community-monitoring/) Related templates ## Pair it with these [MarketingResearch brief writerResearches a topic across the live web and returns a sourced draft in your voice, with the open questions flagged.Run on demand![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)![](/static/img/assets/apify.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/google-docs-brief-writer/)[SupportDocumentation freshness auditChecks your written docs against the codebase every month and comments on the pages that have gone stale.Monthly on the 1st![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/notion-docs-freshness-audit/)[SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.slack · message.channel![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/templates/slack-support-triage/) ## Run Reddit brand monitor on your tools. Connect the integrations, paste the prompt, and pick the trigger. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Slack support triage template | Helios URL: https://www.heliosapp.com/templates/slack-support-triage Description: Watches your support channel, answers what your docs already cover, and escalates the rest with the account context attached. [← All templates](/templates/) Support slack · message.channel # Slack support triage Watches your support channel, answers what your docs already cover, and escalates the rest with the account context attached. [Get started free](https://app.heliosapp.com/)[Copy the prompt](#prompt) 5,000 free credits to start. The prompt ## The workflow prompt Copy this prompt into a new workflow, connect the listed integrations, and configure its trigger. prompt.md You watch the #support Slack channel.When a new message arrives, read the full thread and work out what the customer is asking.Search our help center in Notion and our past resolved threads in Plain for an answer.If you find one you are confident in, reply in the thread with the answer and a link to the source.If the question is new, or the customer sounds frustrated, look up their account in Attio, check their plan and payment state in Stripe, and post a summary in the thread tagging the account owner.Never guess at billing details.Escalate those every time.Keep replies short and plain. Copy the prompt Trigger ## What starts this workflow slack · message.channel Runs when the event fires in the connected service. Filters keep the workflow on the events you want. Event triggers are available for GitHub, Slack, and Plain. ### Integrations it uses * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) * [Notion](/integrations/notion/) * [![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)Plain](/integrations/plain/) * [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Attio](/integrations/attio/) * [Stripe](/integrations/stripe/) Connect each service once. Helios stores the credential encrypted and injects it at the network layer on every run. The agent never holds the token. Example output ## What you get back Every run keeps its full transcript. The steps the agent took, each tool call, and the result. Replied in thread · 34 seconds * Answered the SSO group mapping question * Linked the SCIM setup doc * Tagged @ops because the customer is on Enterprise [Use this template](https://app.heliosapp.com/) New to Helios? Start with [Run your first workflow](/guides/run-your-first-agent/). Use cases ## The task behind this template [SupportSupport triageA workflow reads each new thread as it arrives. It finds the customer, checks the plan and billing state, sets labels and priority, and drafts a reply from your docs.plain · thread.thread\_created![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/use-cases/support-triage/) Guides ## Set it up step by step [10 minRun your first workflowDescribe a task in plain words, give the agent one tool, and read the run. Ten minutes from an empty workspace to a transcript you can read end to end.](/guides/run-your-first-agent/)[9 minShare with your teamHand a workflow to the people who need it. Four roles decide who may view, run, or edit. Every run leaves a transcript of what happened.](/guides/share-with-your-team/)[15 minMove from Relay.app to HeliosRelay.app shut down on 16 July 2026\. Paid accounts are deleted on 14 September 2026\. Here is how each Relay concept maps to Helios, and what to export first.](/guides/move-from-relay-app/) Related templates ## Pair it with these [SupportPlain thread triageTriages every new Plain thread on arrival. Labels, priority, a draft reply, and an internal note with what it checked.plain · thread.thread\_created![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/plain-thread-summarizer/)[SupportDocumentation freshness auditChecks your written docs against the codebase every month and comments on the pages that have gone stale.Monthly on the 1st![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/notion-docs-freshness-audit/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to find the accounts drifting toward the exit.Mondays at 7:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/churn-risk-watchlist/) ## Run Slack support triage on your tools. Connect the integrations, paste the prompt, and pick the trigger. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Failed payment recovery template | Helios URL: https://www.heliosapp.com/templates/stripe-failed-payment-recovery Description: Finds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter. [← All templates](/templates/) Sales & RevOps Hourly # Failed payment recovery Finds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter. [Get started free](https://app.heliosapp.com/)[Copy the prompt](#prompt) 5,000 free credits to start. The prompt ## The workflow prompt Copy this prompt into a new workflow, connect the listed integrations, and configure its trigger. prompt.md Every hour, list charges in Stripe that failed in the last hour.For each one, find the customer and look up the matching account in Attio to get the billing contact and the account owner.Create a hosted payment update link in Stripe.Send an email from billing@ourdomain.com using Resend.Say plainly that the payment did not go through, include the update link, and say what happens if it stays unpaid.Keep it under 120 words and do not sound like a collections notice.If the account is on an Enterprise plan or worth more than $1,000 in MRR, also DM the account owner in Slack with the details.Log a note on the Attio record saying what you sent. Copy the prompt Trigger ## What starts this workflow Hourly Runs on a schedule. Describe the cadence in plain words and Helios writes the cron expression. Schedules run in UTC. ### Integrations it uses * [Stripe](/integrations/stripe/) * [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Attio](/integrations/attio/) * [![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)Resend](/integrations/resend/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) Connect each service once. Helios stores the credential encrypted and injects it at the network layer on every run. The agent never holds the token. Example output ## What you get back Every run keeps its full transcript. The steps the agent took, each tool call, and the result. 3 failed payments handled * $2,340 at risk across 3 accounts * Emails sent with hosted update links * 1 enterprise account escalated to @priya [Use this template](https://app.heliosapp.com/) New to Helios? Start with [Run your first workflow](/guides/run-your-first-agent/). Use cases ## The task behind this template [OperationsBilling operationsA workflow watches Stripe for failed charges and starts recovery. A second one reconciles what you billed against what your own database recorded after the books close.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/billing-ops/) Guides ## Set it up step by step [8 minUse secrets and variablesKeep the values a task needs out of the prompt. Variables hold configuration. Secrets hold credentials. The agent never sees a secret in plain text.](/guides/use-secrets-and-variables/)[15 minMove from Relay.app to HeliosRelay.app shut down on 16 July 2026\. Paid accounts are deleted on 14 September 2026\. Here is how each Relay concept maps to Helios, and what to export first.](/guides/move-from-relay-app/) Related templates ## Pair it with these [Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to find the accounts drifting toward the exit.Mondays at 7:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/churn-risk-watchlist/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing company fields, and flags deals that have gone quiet. Every night.Nightly at 2:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/attio-crm-hygiene/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out.Mondays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/weekly-metrics-report/) ## Run Failed payment recovery on your tools. Connect the integrations, paste the prompt, and pick the trigger. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Weekly metrics report template | Helios URL: https://www.heliosapp.com/templates/weekly-metrics-report Description: Queries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out. [← All templates](/templates/) Operations Mondays at 7:00am # Weekly metrics report Queries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out. [Get started free](https://app.heliosapp.com/)[Copy the prompt](#prompt) 5,000 free credits to start. The prompt ## The workflow prompt Copy this prompt into a new workflow, connect the listed integrations, and configure its trigger. prompt.md Every Monday at 7am, query our ClickHouse events table and our Postgres accounts table to build last week's metrics.Signups, activated accounts, weekly active accounts, total runs, revenue, and churn.Compute week over week and four week trends for each.Then look for anything unusual.A metric outside its recent range, a sudden concentration in one region or plan tier, a metric that moved in the opposite direction from its usual pair.Explain what you found.Post to #metrics with the headline numbers first, then the outliers, then a short note on what you checked and found normal.Include the SQL you ran as a thread reply. Copy the prompt Trigger ## What starts this workflow Mondays at 7:00am Runs on a schedule. Describe the cadence in plain words and Helios writes the cron expression. Schedules run in UTC. ### Integrations it uses * [Databases](/integrations/databases/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) Connect each service once. Helios stores the credential encrypted and injects it at the network layer on every run. The agent never holds the token. Example output ## What you get back Every run keeps its full transcript. The steps the agent took, each tool call, and the result. Metrics · week of Mar 3 * Signups 1,204 · up 8% week over week * Net revenue retention 112% * Error rate up 0.4pp, concentrated in one region [Use this template](https://app.heliosapp.com/) New to Helios? Start with [Run your first workflow](/guides/run-your-first-agent/). Use cases ## The task behind this template [OperationsDatabase reportingA workflow reads your schema, writes the SQL, runs it, checks the results in its sandbox, and posts a report to the channel your team reads.Weekdays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/database-reporting/)[OperationsBilling operationsA workflow watches Stripe for failed charges and starts recovery. A second one reconciles what you billed against what your own database recorded after the books close.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/billing-ops/)[Sales & RevOpsCRM data syncA workflow computes usage from your database, joins it with billing state and support volume, and writes the result onto each account record every night.Nightly at 1:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)](/use-cases/crm-data-sync/) Guides ## Set it up step by step [10 minRun your first workflowDescribe a task in plain words, give the agent one tool, and read the run. Ten minutes from an empty workspace to a transcript you can read end to end.](/guides/run-your-first-agent/)[8 minPut a workflow on a scheduleTurn a working prompt into a standing task. Describe the cadence the way you would say it out loud. Helios writes the cron expression.](/guides/put-an-agent-on-a-schedule/)[10 minConnect a databaseGive a workflow Postgres, MySQL, or ClickHouse. It reads the schema, writes real SQL, and checks the results in its own sandbox.](/guides/connect-a-database/) Related templates ## Pair it with these [OperationsNightly data quality checksRuns your invariants against production every night and emails the on-call analyst which rows broke and since when.Nightly at 3:00am![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/templates/database-health-check/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to find the accounts drifting toward the exit.Mondays at 7:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/churn-risk-watchlist/)[EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup to Slack every weekday morning.Weekdays at 9:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/daily-standup-digest/) ## Run Weekly metrics report on your tools. Connect the integrations, paste the prompt, and pick the trigger. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Use cases | Helios URL: https://www.heliosapp.com/use-cases Description: Tasks teams hand to Helios workflows today. Support triage, lead enrichment, pull request review, database reporting, billing operations, and more. Each runs on a schedule, a webhook, or a GitHub, Slack, or Plain event. Use cases # Tasks a workflow can run today. 9 tasks teams hand to Helios. Each one runs on a schedule, a webhook, or a GitHub, Slack, or Plain event. Each run gets its own sandbox and the full API of every connected tool. [Get started free](https://app.heliosapp.com/)[See templates](/templates) 5,000 free credits to start. ## Engineering 02 [EngineeringPull request reviewA workflow reads each diff against your conventions and leaves a real review. A second workflow on a schedule posts the week's merged work, review backlog, and CI health.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/pr-review-digest/)[EngineeringIncident summariesA workflow rebuilds the timeline from your incident channel and the deploys around it. It names the likely change and drafts the write-up with the facts in place.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/incident-summaries/) ## Support 01 [SupportSupport triageA workflow reads each new thread as it arrives. It finds the customer, checks the plan and billing state, sets labels and priority, and drafts a reply from your docs.plain · thread.thread\_created![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/use-cases/support-triage/) ## Sales & RevOps 02 [Sales & RevOpsLead enrichmentA signup or form response fires a webhook. The workflow enriches the person and company, scores fit against your definition, creates the CRM record, and tells the right rep.Signup webhook![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/typeform-light.svg)![](/static/img/assets/typeform-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/lead-enrichment/)[Sales & RevOpsCRM data syncA workflow computes usage from your database, joins it with billing state and support volume, and writes the result onto each account record every night.Nightly at 1:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)](/use-cases/crm-data-sync/) ## Operations 02 [OperationsDatabase reportingA workflow reads your schema, writes the SQL, runs it, checks the results in its sandbox, and posts a report to the channel your team reads.Weekdays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/database-reporting/)[OperationsBilling operationsA workflow watches Stripe for failed charges and starts recovery. A second one reconciles what you billed against what your own database recorded after the books close.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/use-cases/billing-ops/) ## Marketing 02 [MarketingResearch briefsA workflow searches the web, reads what it finds, and writes a draft with every claim linked to its source. Give it your prior work and the draft matches your voice.Run on demand![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)![](/static/img/assets/apify.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/content-pipeline/)[MarketingCommunity monitoringA workflow sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space. It picks the threads worth a reply and brings them to your team.Every 4 hours![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/use-cases/community-monitoring/) ## Pick a task and write the prompt. Start in chat. Then reuse the prompt as a workflow on a trigger. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Billing operations with Helios workflows | Helios URL: https://www.heliosapp.com/use-cases/billing-ops Description: A workflow watches Stripe for failed charges and starts recovery. A second one reconciles what you billed against what your own database recorded after the books close. [← All use cases](/use-cases/) Operations Hourly # Failed payments handled every hour. A workflow watches Stripe for failed charges and starts recovery. A second one reconciles what you billed against what your own database recorded after the books close. [Get started free](https://app.heliosapp.com/)[See the templates](#templates) 5,000 free credits to start. How it works ## Three steps to a workflow 1. Step 01 ### Connect Stripe and your database A restricted Stripe key covers reporting workflows. Add write scopes only where a workflow must act. Your database gives the agent the other side of the reconciliation. 2. Step 02 ### Describe the rules Say when to email a customer, when to escalate to an owner, and what a mismatch means. The agent applies judgment where a rules engine needs a hundred branches. 3. Step 03 ### Run it hourly and monthly Recovery runs every hour and looks at the last hour of charges. Reconciliation runs after the books close. Both post where your revenue team reads. The run ## What one run looks like Each line is a tool call. The agent finds the API it needs, reads the result, and acts. The full transcript stays on the run. Hourly Every hour, find failed charges from the last hour, start recovery, and escalate enterprise accounts. 1. stripe·list failed charges in the last hour 2. attio·look up the account owner and contact 3. stripe·create hosted payment update links 4. resend·send recovery emails 5. slack·notify owners in #revenue ✓3 failed payments handled * $2,340 at risk across 3 accounts * Emails sent from billing@yourdomain.com * 1 enterprise account escalated to @priya * Note added to each Attio record Integrations ## The tools this workflow uses Connect each one once. The agent gets its full API, and the credential stays at the network layer. * [Stripe](/integrations/stripe/) * [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Attio](/integrations/attio/) * [![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)Resend](/integrations/resend/) * [Databases](/integrations/databases/) Templates ## Start from a prompt that works Each template has the prompt, the trigger it needs, and the integrations it uses. [Sales & RevOpsFailed payment recoveryFinds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.Hourly![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/stripe-failed-payment-recovery/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to find the accounts drifting toward the exit.Mondays at 7:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/churn-risk-watchlist/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out.Mondays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/weekly-metrics-report/) FAQ ## Questions, answered ### Can the agent move money? ### Does it email customers on its own? ### How does reconciliation work? ### What about disputes and refunds? ## Put a workflow on billing operations. Write the prompt, pick the trigger, and read the first run. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Community monitoring with Helios workflows | Helios URL: https://www.heliosapp.com/use-cases/community-monitoring Description: A workflow sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space. It picks the threads worth a reply and brings them to your team. [← All use cases](/use-cases/) Marketing Every 4 hours # Someone reads every thread about you. A workflow sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space. It picks the threads worth a reply and brings them to your team. [Get started free](https://app.heliosapp.com/)[See the templates](#templates) 5,000 free credits to start. How it works ## Three steps to a workflow 1. Step 01 ### Name what to watch Subreddits, Discord channels, brand terms, competitor names, and the words people use for the problem. The agent reads full comment trees. 2. Step 02 ### Say what deserves attention A question you can answer, a bug with a reproduction, a comparison thread, a positive review worth thanking. The agent scores each thread and skips the rest. 3. Step 03 ### Get a short list Every few hours the run posts the threads worth a reply, with a suggested response and a link. Bugs with a reproduction can become GitHub issues. The run ## What one run looks like Each line is a tool call. The agent finds the API it needs, reads the result, and acts. The full transcript stays on the run. Every 4 hours Every four hours, find mentions of us and our competitors and flag the threads worth answering. 1. reddit·search 8 subreddits for brand and category terms 2. reddit·read comment trees on 6 threads 3. discord·read new #help threads 4. code·score sentiment and reply value 5. slack·post the shortlist to #community ✓3 threads worth a reply * One asks how we compare on pricing * One reports a real bug with a reproduction * One is a positive review worth thanking * 11 mentions reviewed and skipped Integrations ## The tools this workflow uses Connect each one once. The agent gets its full API, and the credential stays at the network layer. * [Reddit](/integrations/reddit/) * [Discord](/integrations/discord/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) * [GitHub](/integrations/github/) Templates ## Start from a prompt that works Each template has the prompt, the trigger it needs, and the integrations it uses. [MarketingReddit brand monitorSweeps the subreddits where your customers gather, judges which threads deserve a reply, and brings you a shortlist.Every 4 hours![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/reddit-brand-monitor/)[MarketingResearch brief writerResearches a topic across the live web and returns a sourced draft in your voice, with the open questions flagged.Run on demand![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)![](/static/img/assets/apify.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/google-docs-brief-writer/) FAQ ## Questions, answered ### Will the workflow post replies itself? ### How does it avoid flooding the channel? ### Can it file bugs it finds? ### How often should it run? ## Put a workflow on community monitoring. Write the prompt, pick the trigger, and read the first run. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Research briefs with Helios workflows | Helios URL: https://www.heliosapp.com/use-cases/content-pipeline Description: A workflow searches the web, reads what it finds, and writes a draft with every claim linked to its source. Give it your prior work and the draft matches your voice. [← All use cases](/use-cases/) Marketing Run on demand # Research, draft, and file a sourced brief. A workflow searches the web, reads what it finds, and writes a draft with every claim linked to its source. Give it your prior work and the draft matches your voice. [Get started free](https://app.heliosapp.com/)[See the templates](#templates) 5,000 free credits to start. How it works ## Three steps to a workflow 1. Step 01 ### Give it a topic and your voice Point the agent at a few published pieces so it learns how you write. Then give it a topic, an outline, or a keyword to build a brief around. 2. Step 02 ### Let it research in its sandbox The agent searches the web and reads pages. It can call an Apify actor for structured collection at scale. It groups what it finds before it writes. 3. Step 03 ### Get a draft with sources The draft lands in Notion or Google Docs. Every claim links to where it came from. Open questions stay as inline notes for you. The run ## What one run looks like Each line is a tool call. The agent finds the API it needs, reads the result, and acts. The full transcript stays on the run. Run on demand Research how growing teams evaluate SOC 2 tooling and draft a sourced brief in our voice. 1. web·search and read 14 sources 2. apify·scrape 6 vendor pricing pages 3. notion·read 3 prior briefs for voice 4. code·outline and group the findings 5. notion·write the brief with citations ✓\`SOC 2 Buyer's Brief\` created * 1,900 words across 5 sections * Every claim linked to a source * Timeline and cost table included * 4 open questions left as inline notes Integrations ## The tools this workflow uses Connect each one once. The agent gets its full API, and the credential stays at the network layer. * [Notion](/integrations/notion/) * [![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)Google Docs](/integrations/google-docs/) * [![](/static/img/assets/apify.svg)Apify](/integrations/apify/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) Templates ## Start from a prompt that works Each template has the prompt, the trigger it needs, and the integrations it uses. [MarketingResearch brief writerResearches a topic across the live web and returns a sourced draft in your voice, with the open questions flagged.Run on demand![](/static/img/assets/google-docs-light.svg)![](/static/img/assets/google-docs-dark.svg)![](/static/img/assets/apify.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/google-docs-brief-writer/)[MarketingReddit brand monitorSweeps the subreddits where your customers gather, judges which threads deserve a reply, and brings you a shortlist.Every 4 hours![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/reddit-brand-monitor/) FAQ ## Questions, answered ### Does the agent make things up? ### How does it learn our voice? ### Where does the draft go? ### Can it publish on its own? ## Put a workflow on research briefs. Write the prompt, pick the trigger, and read the first run. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # CRM data sync with Helios workflows | Helios URL: https://www.heliosapp.com/use-cases/crm-data-sync Description: A workflow computes usage from your database, joins it with billing state and support volume, and writes the result onto each account record every night. [← All use cases](/use-cases/) Sales & RevOps Nightly at 1:00am # A CRM that shows what customers do. A workflow computes usage from your database, joins it with billing state and support volume, and writes the result onto each account record every night. [Get started free](https://app.heliosapp.com/)[See the templates](#templates) 5,000 free credits to start. How it works ## Three steps to a workflow 1. Step 01 ### Connect the systems Your database holds usage. Stripe holds billing. Plain holds support threads. One workflow holds all three connections at once. 2. Step 02 ### Define health in plain words Describe what an at-risk account looks like and what expansion looks like. The agent computes the scores in its sandbox and explains each one in a note. 3. Step 03 ### Write it back every night Fields update on the account record. Owners see the change. Every write is traceable to the run that made it. The run ## What one run looks like Each line is a tool call. The agent finds the API it needs, reads the result, and acts. The full transcript stays on the run. Nightly at 1:00am Nightly, sync product usage, billing state, and support volume into the CRM as account health fields. 1. postgres·compute 30-day usage per account 2. stripe·read subscription and payment state 3. plain·count open threads per account 4. code·score health and map to tiers 5. attio·update 480 account records with a note ✓480 accounts synced * 31 moved into \`at risk\` * 18 flagged as expansion candidates * $38k ARR sits in the at-risk tier * Each record carries a note explaining the score Integrations ## The tools this workflow uses Connect each one once. The agent gets its full API, and the credential stays at the network layer. * [Databases](/integrations/databases/) * [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Attio](/integrations/attio/) * [Stripe](/integrations/stripe/) * [![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)Plain](/integrations/plain/) * [![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)Apollo](/integrations/apollo/) Templates ## Start from a prompt that works Each template has the prompt, the trigger it needs, and the integrations it uses. [Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing company fields, and flags deals that have gone quiet. Every night.Nightly at 2:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/attio-crm-hygiene/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to find the accounts drifting toward the exit.Mondays at 7:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/churn-risk-watchlist/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out.Mondays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/weekly-metrics-report/) FAQ ## Questions, answered ### Does it overwrite fields a rep edited? ### How do I check a change? ### How large a sync can it handle? ### What if the score looks wrong? ## Put a workflow on crm data sync. Write the prompt, pick the trigger, and read the first run. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Database reporting with Helios workflows | Helios URL: https://www.heliosapp.com/use-cases/database-reporting Description: A workflow reads your schema, writes the SQL, runs it, checks the results in its sandbox, and posts a report to the channel your team reads. [← All use cases](/use-cases/) Operations Weekdays at 7:00am # Ask your database a question every morning. A workflow reads your schema, writes the SQL, runs it, checks the results in its sandbox, and posts a report to the channel your team reads. [Get started free](https://app.heliosapp.com/)[See the templates](#templates) 5,000 free credits to start. How it works ## Three steps to a workflow 1. Step 01 ### Connect your database Add a Postgres, MySQL, or ClickHouse connection with read-only credentials. Reach a private database through an SSH tunnel so nothing is exposed to the internet. 2. Step 02 ### Describe the report Say what the team wants to know and what counts as unusual. The agent reads the schema, writes the queries, and shows the SQL it ran next to the answer. 3. Step 03 ### Put it on a schedule Describe the cadence in plain words. Helios turns it into a cron expression. The report shows up before standup every day. The run ## What one run looks like Each line is a tool call. The agent finds the API it needs, reads the result, and acts. The full transcript stays on the run. Weekdays at 7:00am Each morning, post yesterday's metrics with anything unusual called out. 1. clickhouse·read the schema and query 24h of events 2. postgres·join account metadata 3. code·compute trends and flag outliers 4. slack·post the report to #metrics ✓Metrics · Mar 6 * Runs 41.2k · up 6% day over day * Signups 128 · in line with the trend * Error rate up 0.4pp, concentrated in one region * Queries and assumptions attached to the run Integrations ## The tools this workflow uses Connect each one once. The agent gets its full API, and the credential stays at the network layer. * [Databases](/integrations/databases/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) * [![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)Resend](/integrations/resend/) Templates ## Start from a prompt that works Each template has the prompt, the trigger it needs, and the integrations it uses. [OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the outliers called out.Mondays at 7:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/weekly-metrics-report/)[OperationsNightly data quality checksRuns your invariants against production every night and emails the on-call analyst which rows broke and since when.Nightly at 3:00am![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)](/templates/database-health-check/) FAQ ## Questions, answered ### Which databases are supported? ### Can the agent write to my database? ### How does it know my schema? ### Can I see the SQL it ran? ## Put a workflow on database reporting. Write the prompt, pick the trigger, and read the first run. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Incident summaries with Helios workflows | Helios URL: https://www.heliosapp.com/use-cases/incident-summaries Description: A workflow rebuilds the timeline from your incident channel and the deploys around it. It names the likely change and drafts the write-up with the facts in place. [← All use cases](/use-cases/) Engineering Run on demand # The postmortem gets a first draft. A workflow rebuilds the timeline from your incident channel and the deploys around it. It names the likely change and drafts the write-up with the facts in place. [Get started free](https://app.heliosapp.com/)[See the templates](#templates) 5,000 free credits to start. How it works ## Three steps to a workflow 1. Step 01 ### Point it at the incident channel Give the agent the Slack channel and the repositories involved. It reads the whole conversation, including threads, and pulls the commits and deploys inside the impact window. 2. Step 02 ### Run it when the incident closes Start the run by hand from the workflow page, or from chat with the channel name. A schedule can also sweep for channels created in the last day. 3. Step 03 ### Start from a draft The postmortem lands in Notion with the timeline, the contributing factors, and the action items people agreed to in the channel. The run ## What one run looks like Each line is a tool call. The agent finds the API it needs, reads the result, and acts. The full transcript stays on the run. Run on demand Draft a postmortem from the #incident channel and the deploys around it. 1. slack·read #incident-2026-03-06 in full 2. github·list deploys and reverts in the window 3. github·read the diff for the suspect deploy 4. code·build the minute-by-minute timeline 5. notion·create the postmortem draft ✓Postmortem drafted * 41-minute impact window rebuilt * Likely deploy identified as #2833 * Detection took 12 minutes, alerting gap noted * 5 action items pulled from the discussion Integrations ## The tools this workflow uses Connect each one once. The agent gets its full API, and the credential stays at the network layer. * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) * [GitHub](/integrations/github/) * [Notion](/integrations/notion/) Templates ## Start from a prompt that works Each template has the prompt, the trigger it needs, and the integrations it uses. [EngineeringIncident postmortem drafterRebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion.Run on demand![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/incident-postmortem-drafter/)[EngineeringPull request reviewerReviews every pull request against your conventions and leaves inline comments only where it found something concrete.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/pr-review-digest/) FAQ ## Questions, answered ### How does it know when the incident started? ### Can it identify the cause? ### Where does the draft land? ### Can it run without a person starting it? ## Put a workflow on incident summaries. Write the prompt, pick the trigger, and read the first run. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Lead enrichment with Helios workflows | Helios URL: https://www.heliosapp.com/use-cases/lead-enrichment Description: A signup or form response fires a webhook. The workflow enriches the person and company, scores fit against your definition, creates the CRM record, and tells the right rep. [← All use cases](/use-cases/) Sales & RevOps Signup webhook # Every lead enriched, scored, and routed. A signup or form response fires a webhook. The workflow enriches the person and company, scores fit against your definition, creates the CRM record, and tells the right rep. [Get started free](https://app.heliosapp.com/)[See the templates](#templates) 5,000 free credits to start. How it works ## Three steps to a workflow 1. Step 01 ### Define a good customer Write your ideal customer in plain words. Size, stage, industry, and the signals that matter. The agent scores against that description. 2. Step 02 ### Point the webhook at Helios Send your signup, Typeform, or website form webhook to a Helios webhook trigger. It is signed with a secret you control. Each request starts a run. 3. Step 03 ### Land it in the CRM with context The agent creates or updates the record, attaches its research, assigns an owner by territory, and posts strong fits to the channel where your reps work. The run ## What one run looks like Each line is a tool call. The agent finds the API it needs, reads the result, and acts. The full transcript stays on the run. Signup webhook For each new signup, enrich the person and company, score fit against our ICP, and route strong fits. 1. apollo·enrich person and company by email domain 2. web·read the company site for positioning 3. code·score fit against the ICP definition 4. attio·create the record with the fit score 5. slack·post strong fits to #inbound ✓Lead scored 87/100 * Northwind · Series B fintech · 240 employees * Signup is Head of Platform * They shipped a Postgres migration last month * Routed to @dana with a suggested opener Integrations ## The tools this workflow uses Connect each one once. The agent gets its full API, and the credential stays at the network layer. * [![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)Apollo](/integrations/apollo/) * [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Attio](/integrations/attio/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) * [![](/static/img/assets/typeform-light.svg)![](/static/img/assets/typeform-dark.svg)Typeform](/integrations/typeform/) * [![](/static/img/assets/resend-light.svg)![](/static/img/assets/resend-dark.svg)Resend](/integrations/resend/) Templates ## Start from a prompt that works Each template has the prompt, the trigger it needs, and the integrations it uses. [Sales & RevOpsInbound lead enrichmentEnriches every new signup, scores it against your ICP by reading the company's own website, and routes the strong fits.Signup webhook![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/apollo-lead-enrichment/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing company fields, and flags deals that have gone quiet. Every night.Nightly at 2:00am![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)![](/static/img/assets/apollo-light.svg)![](/static/img/assets/apollo-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/attio-crm-hygiene/) FAQ ## Questions, answered ### Which enrichment source does it use? ### How is fit scored? ### What if the person cannot be matched? ### Can it run on a schedule instead of a webhook? ## Put a workflow on lead enrichment. Write the prompt, pick the trigger, and read the first run. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Pull request review with Helios workflows | Helios URL: https://www.heliosapp.com/use-cases/pr-review-digest Description: A workflow reads each diff against your conventions and leaves a real review. A second workflow on a schedule posts the week's merged work, review backlog, and CI health. [← All use cases](/use-cases/) Engineering github · pull\_request.opened # A reviewer on every pull request. A workflow reads each diff against your conventions and leaves a real review. A second workflow on a schedule posts the week's merged work, review backlog, and CI health. [Get started free](https://app.heliosapp.com/)[See the templates](#templates) 5,000 free credits to start. How it works ## Three steps to a workflow 1. Step 01 ### Teach it your conventions Point the agent at your contributing guide and let it read recent reviews. It learns what your team comments on. 2. Step 02 ### Add a GitHub trigger Run the reviewer on pull\_request.opened and pull\_request.synchronize. Filter by base branch. Add a label filter to opt pull requests in one at a time. 3. Step 03 ### Read the review, then the weekly digest The agent posts inline comments where they belong. A second workflow on a Friday schedule posts the digest to your engineering channel. The run ## What one run looks like Each line is a tool call. The agent finds the API it needs, reads the result, and acts. The full transcript stays on the run. github · pull\_request.opened Review new pull requests against our conventions and leave inline comments. 1. github·fetch the diff for PR #2841 2. github·read CONTRIBUTING.md and recent reviews 3. code·run the linter over the changed files 4. github·post a review with 3 inline comments 5. slack·notify the author in #eng ✓Review posted on PR #2841 * Flagged an unhandled error path in \`sync.ts:142\` * Suggested reusing \`parseCursor\` instead of a second parser * Confirmed the migration is backward compatible * Author notified with a link to the review Integrations ## The tools this workflow uses Connect each one once. The agent gets its full API, and the credential stays at the network layer. * [GitHub](/integrations/github/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) * [Notion](/integrations/notion/) Templates ## Start from a prompt that works Each template has the prompt, the trigger it needs, and the integrations it uses. [EngineeringPull request reviewerReviews every pull request against your conventions and leaves inline comments only where it found something concrete.github · pull\_request.opened![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/pr-review-digest/)[EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup to Slack every weekday morning.Weekdays at 9:00am![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/daily-standup-digest/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes a draft release on GitHub, and files a changelog entry in Notion.github · tag.created![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/github-release-notes/) FAQ ## Questions, answered ### Will it comment on every pull request? ### Can it run tests or a linter? ### Does it review again when new commits land? ### Who can change what the reviewer says? ## Put a workflow on pull request review. Write the prompt, pick the trigger, and read the first run. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Support triage with Helios workflows | Helios URL: https://www.heliosapp.com/use-cases/support-triage Description: A workflow reads each new thread as it arrives. It finds the customer, checks the plan and billing state, sets labels and priority, and drafts a reply from your docs. [← All use cases](/use-cases/) Support plain · thread.thread\_created # Every thread triaged before the queue opens. A workflow reads each new thread as it arrives. It finds the customer, checks the plan and billing state, sets labels and priority, and drafts a reply from your docs. [Get started free](https://app.heliosapp.com/)[See the templates](#templates) 5,000 free credits to start. How it works ## Three steps to a workflow 1. Step 01 ### Describe the triage you want Write the prompt in plain words. Name the labels, say how priority follows the plan tier, say when to escalate, and describe a good draft reply. Name the place your answers live. 2. Step 02 ### Start it on a Plain or Slack event Add a Plain thread created trigger, or watch a Slack support channel for new messages. The run starts a few seconds after the customer writes in. 3. Step 03 ### Read the run, then trust it Each run shows every tool call and every draft. Start with labels and internal notes. Give the workflow sending rights once the drafts hold up. The run ## What one run looks like Each line is a tool call. The agent finds the API it needs, reads the result, and acts. The full transcript stays on the run. plain · thread.thread\_created On each new thread, find the customer, set labels and priority, draft a reply, and escalate Enterprise accounts. 1. plain·read thread and customer record 2. stripe·check plan and payment state 3. notion·search the help center 4. plain·label \`billing\`, set priority \`high\` 5. plain·draft reply and add an internal note 6. slack·DM the account owner ✓Thread triaged in 22 seconds * Northwind · Enterprise · $4.2k MRR * Draft reply cites the invoice settings doc * Internal note names Tuesday's failed charge * Owner @priya sent the thread link Integrations ## The tools this workflow uses Connect each one once. The agent gets its full API, and the credential stays at the network layer. * [![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)Plain](/integrations/plain/) * [![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)Slack](/integrations/slack/) * [Notion](/integrations/notion/) * [Stripe](/integrations/stripe/) * [![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)Attio](/integrations/attio/) Templates ## Start from a prompt that works Each template has the prompt, the trigger it needs, and the integrations it uses. [SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.slack · message.channel![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/attio-light.svg)![](/static/img/assets/attio-dark.svg)](/templates/slack-support-triage/)[SupportPlain thread triageTriages every new Plain thread on arrival. Labels, priority, a draft reply, and an internal note with what it checked.plain · thread.thread\_created![](/static/img/assets/plain-light.svg)![](/static/img/assets/plain-dark.svg)![](/static/img/assets/slack-light.svg)![](/static/img/assets/slack-dark.svg)](/templates/plain-thread-summarizer/) FAQ ## Questions, answered ### Will the workflow reply to customers on its own? ### How does it know our answers? ### How fast does it pick up a new thread? ### What happens with a question it has never seen? ## Put a workflow on support triage. Write the prompt, pick the trigger, and read the first run. [Get started free](https://app.heliosapp.com/)[Read the docs](/docs) --- # Helios Documentation Base URL: https://www.heliosapp.com/docs # Proposing changes URL: https://www.heliosapp.com/docs/library/proposing-changes Description: Agents edit Library files inside their sandbox. Helios captures the edits after a short quiet period and stages them as a change. Nothing is live until a person approves it. --- title: "Proposing changes" excerpt: "How an agent's edits become a change waiting for review" description: "Agents edit Library files inside their sandbox. Helios captures the edits after a short quiet period and stages them as a change. Nothing is live until a person approves it." icon: GitPullRequest createdAt: "2026-09-07" updatedAt: "2026-09-07" --- {/* HOLD:PR-603 */} An agent proposes a change by editing files under `~/context` in its [sandbox](/docs/basics/sandboxes). There is no special command. The agent writes the file the way it would write any other file. ## From edit to change 1. The agent creates, edits, or deletes a file under `~/context`. 2. Helios waits for a quiet period of about 5 seconds after the agent last touched that folder. 3. Helios records which files changed and uploads them to a staging area that belongs to this session. 4. The staged files appear as one **change** in the Changes inbox. A change carries the session that produced it, the number of files, and the time. The live Library does not move at any point in this list. Staged files are copies. Other people and other agents still see the previous version until someone approves the change. See [reviewing changes](/docs/library/reviewing-changes). ## One change per session A change belongs to one chat or one workflow run. If the agent keeps editing, the same change is updated with the newer files. A change stays open until every file in it is approved or discarded. If the agent rewrites a file after you reviewed it, approving the old version is refused. Helios asks you to review the file again. ## Read-only folders A folder that is read-only for the run is still writable on disk inside the sandbox. The agent can change the file locally and keep working with it. Those edits still show up in the change, but they cannot be approved. Approval checks the access the run was granted. If you want an agent to be able to update a folder, give the person or [service account](/docs/access/service-accounts) the run belongs to editor access on that path. See [permissions](/docs/library/permissions). ## Scratch files Each run has its own scratch folder at `~/context/agent`. Use it for working files that only this run needs. Tell the agent to write drafts there and to move only the finished file into the shared tree. ## Pause and resume A sandbox stops after a period of inactivity. Edits that were staged but not yet approved are replayed when the sandbox resumes, so the agent picks up where it left off. ## Writing prompts for the Library Say where the file should go and what it is for. Paths are what the agent sees in the sandbox. ``` Read ~/context/organization/support/tone.md before you answer. Write the summary to ~/context/project/support-triage/digests/2026-09-07.md. Do not edit anything else under ~/context. ``` ## Next - **[Reviewing changes](/docs/library/reviewing-changes)** - approve or discard each file. - **[Limits](/docs/library/limits)** - file sizes and what is not possible yet. --- # Advanced URL: https://www.heliosapp.com/docs/advanced Description: Techniques for reliable unattended agents: scoping the task, guarding against unwanted events, persisting state, and calling Helios from your own code. --- title: "Advanced" excerpt: "Writing prompts for unattended agents, and driving Helios programmatically" description: "Techniques for reliable unattended agents: scoping the task, guarding against unwanted events, persisting state, and calling Helios from your own code." icon: Code createdAt: "2025-07-31" --- ## Writing prompts for unattended agents A [chat](/docs/basics/chat) prompt is a conversation opener - you can correct it as it goes. A [workflow](/docs/workflows) prompt is a standing instruction that has to survive events you didn't anticipate, with nobody watching. The difference matters. ### Say what to do when nothing should happen Most workflow runs should be uneventful. An agent that feels obliged to act will find something to do. Give it permission to stop: ``` When a pull request is opened in acme/api, review the diff for changes to authentication or billing code. If you find any, comment on the PR naming the files and why they need a second reviewer. Otherwise do nothing - do not comment, do not label. ``` A run that decides no action is required still succeeds. It just has no side effects. ### Make it verify first Agents are instructed to gather context with tools and to stop with a clear error when the context is unclear. Prompts that lean into this are more reliable: ``` Before posting, check whether a digest for this week already exists in the channel. If one does, stop. ``` ### Be concrete about the destination Name the channel, the repository, the table. If you'd rather not hardcode it, put it in a [variable](/docs/basics/variables-and-secrets) and refer to it by name - variables are passed into every run as context. ``` Post the digest to the Slack channel named in the DIGEST_CHANNEL variable. ``` ### Ask for the shape of output you want Helios classifies a run's output as `markdown`, `plainText`, or `json` based on what the agent produced. If you need structured data, ask for it: ``` Return a JSON array of objects with keys `repo`, `prCount`, and `riskyFiles`. ``` See [runs and outputs](/docs/workflows/runs-and-outputs). ## Carrying state between runs {/* HOLD:PR-601 */} Every run starts in a fresh sandbox. To carry state forward, keep it in a [Library](/docs/library/overview) file and approve the agent's change after each run: ``` Keep a file at ~/context/project/support/seen.json listing the issue numbers you've already processed. Skip any issue already in that list, and add each new one you handle. ``` Anything written outside `~/context`, under `$TMPDIR` for instance, disappears when the run ends. See [context](/docs/basics/memory). ## Testing a prompt before you schedule it Dispatch the workflow manually. A manual run can carry an arbitrary JSON input payload, which the agent receives as trigger context - so you can hand it a copy of a real GitHub webhook body and see exactly how it behaves, without waiting for the event. Then read the run's transcript. It records every tool call the agent made and everything that came back. When an agent does the wrong thing, the transcript almost always shows a prompt that was ambiguous. ## Driving Helios from your own code ### The API Everything the UI does is available over the Helios API, authenticated with an [API key](/docs/basics/roles-permissions#api-keys) scoped to `helios`. You can create and update workflows, dispatch runs with an input payload, poll run status, and read outputs. ### Triggering from another system A [webhook trigger](/docs/workflows/triggers) is usually the simplest integration point: your system signs a request with the trigger's secret and `POST`s a JSON body, and the agent receives it as context. Signing is HMAC-SHA256 over `"."`. ### From another agent Helios is exposed over MCP, so an agent you run elsewhere can search the Helios API and call it. See [MCP servers](/docs/basics/mcp-servers). ## Debugging **The run failed with a timeout.** Runs have a 30-minute limit. Narrow the task, or split it across several workflows. **The run failed before it started.** The workflow has no prompt, or your organization has exhausted its [credits](/docs/basics/pricing). **The agent couldn't reach a service.** Check the integration is connected and, for Slack and for GitHub organization installs, that the triggering user has authorized it individually. See [authentication](/docs/integrations/auth). **The agent acted on an event it should have ignored.** Filters narrow which events reach the agent, but the prompt is the second filter. Say plainly what should be ignored. --- # Quickstart URL: https://www.heliosapp.com/docs/quickstart Description: Connect a tool, run an agent in chat, then put it on a schedule - in about five minutes. --- title: "Quickstart" excerpt: "Hand an agent its first task" description: "Connect a tool, run an agent in chat, then put it on a schedule - in about five minutes." icon: FastForward createdAt: "2025-07-31" --- You'll connect a tool, get an agent to do a task in [chat](/docs/basics/chat), then save that task as a [workflow](/docs/workflows) so it runs on its own. ## Create a project A [project](/docs/basics/projects-and-sharing) groups related agents, integrations, and variables - and decides who can reach them. 1. Go to **Projects** and choose **Create Project**. 2. Name it after the work, e.g. "engineering digests". 3. Set its visibility: **Organization** so your team can use it, or **Restricted** to keep it to yourself. You already have a **Personal** project if you'd rather just experiment. ## Connect a tool 1. Open **Integrations** and pick a service - GitHub is a good first one. 2. Choose an authentication method. The **Helios app** is the fastest; you can also bring an API key or your own OAuth app. See [authentication](/docs/integrations/auth). 3. Authorize, and give the integration a name you'll recognize. Your agents can now call **any endpoint** of that service's API. There's no action list to pick from. ## Ask an agent to do it Open **Chat** and describe the task as you would to a new colleague: ``` Look at the pull requests opened in acme/api over the last week. Summarize what shipped, and call out anything touching authentication. ``` Watch what the agent does - you'll see it search the GitHub API, make calls, and reason about what came back. If the result isn't what you wanted, say so and let it correct. Pin the repository as an [integration resource](/docs/basics/integration-resources) and the agent gets authenticated access to it - enough to `git clone` and run your test suite. ## Put the agent on the task permanently Once the instructions work, they're a workflow. 1. In your project, choose **Create Workflow** and name it "Weekly PR digest". 2. Paste the prompt. Add whatever the unattended version needs - where the result should go, and what to do when there's nothing to report: ``` Every Monday, look at the pull requests opened in acme/api over the last week. Summarize what shipped and call out anything touching authentication. Post the summary to #eng-standup in Slack. If no pull requests were opened, do nothing. ``` 3. Add a **schedule trigger**. Type `every Monday at 9am Eastern` and Helios converts it to a cron expression for you, in UTC. 4. Connect Slack too, since the prompt now needs it. ## Run it and watch Dispatch the workflow manually to see it run right away. Every execution is a [run](/docs/workflows/runs-and-outputs) with the agent's full transcript: every tool call, every response, and the final output. If the agent did the wrong thing, the transcript shows you exactly where it went astray. Adjust the prompt and run it again. ## Where to go next 1. **[Triggers](/docs/workflows/triggers)** - schedules, signed webhooks, and events from connected integrations. 2. **[Integrations](/docs/integrations)** - everything you can connect. 3. **[Databases](/docs/integrations/databases)** - let agents query Postgres, MySQL, or ClickHouse. 4. **[MCP servers](/docs/basics/mcp-servers)** - bring your own tools. 5. **[Variables and secrets](/docs/basics/variables-and-secrets)** - configuration without hardcoding. 6. **[Roles and permissions](/docs/basics/roles-permissions)** - who can run what. 7. **[Writing better prompts](/docs/advanced)** - getting reliable results from unattended agents. ## Support Email support@heliosapp.com, or reach out through the in-app chat. --- # Troubleshooting URL: https://www.heliosapp.com/docs/troubleshooting Description: What to do when an agent reports authorization required, runs stop starting, a run times out, a webhook is rejected, an event trigger never fires, or a sandbox is paused. --- title: "Troubleshooting" excerpt: "Common failures and how to fix them" description: "What to do when an agent reports authorization required, runs stop starting, a run times out, a webhook is rejected, an event trigger never fires, or a sandbox is paused." icon: LifeBuoy createdAt: "2026-09-07" updatedAt: "2026-09-07" --- Start with the run transcript. Every [run](/docs/workflows/runs-and-outputs) and every [chat](/docs/basics/chat) keeps the full transcript, and the error is usually in the last few steps. ## "Authorization required" on GitHub or Slack [GitHub](/docs/integrations/apps/github) on an organization or enterprise install and [Slack](/docs/integrations/apps/slack) need a one-time authorization from each person. The integration is connected, but you have not authorized it yet. 1. Open **Integrations** and select the integration. 2. Complete the per-user authorization. 3. Run the agent again. {/* HOLD:PR-609 */} If the failing run belongs to a workflow that runs as a [service account](/docs/access/service-accounts), the account has no personal login. Either turn on **Act as me** on the account, or share the integration with the account using **The Helios app** as the credential mode. See [credential mode](/docs/access/credential-mode). ## Workflows stopped running If your organization has used all of its credits, new chats and runs are rejected before an agent starts. Triggers still fire, but every run fails immediately. Runs already in flight finish. Top up in your organization's billing settings. Workflows resume on their next trigger. Nothing needs to be re-enabled. See [pricing and credits](/docs/basics/pricing). ## A run failed after 30 minutes Every workflow run has a **30-minute execution limit**. When it is reached, the agent is stopped and the run is marked `failed` with a timeout error. - Narrow the task. A prompt that reviews ten repositories is better as ten workflows, or one workflow triggered per event. - Tell the agent to stop early when there is nothing to do. - Split a long task into a workflow that prepares and one that finishes, with the result handed over through an integration or the Library. Chats have no fixed limit, but a sandbox pauses after a period of inactivity. See [sandboxes](/docs/basics/sandboxes). ## Webhook returns 401 A webhook trigger rejects a request when the signature is wrong, when the timestamp is more than 5 minutes from server time, or when the `X-Helios-Signature` header is missing or does not start with `sha256=`. The response body is generic on purpose. Check the three usual causes. - The secret is signed as a UTF-8 string. Do not hex-decode it on one side. - The body is signed exactly as sent. A proxy that reformats JSON breaks the signature. - The clock on the sender is wrong by more than 5 minutes. Rotating the secret takes effect at once with no overlap. Every sender gets 401 until it has the new secret. See [triggers](/docs/workflows/triggers). ## An integration event never fires Work through these in order. The integration's page has the details for each step. 1. **The integration has the event.** Check the events table on its page. Integrations without events can be called by an agent but can't start a run. Use a schedule or a signed webhook instead. 2. **The connection is connected.** A connection whose status shows **Error** can't receive events. Fix the credential and save it again. 3. **The webhook exists.** Some integrations register their webhook automatically when you save the connection, which needs a permission named on their page. Others need you to create it by hand from **Manage** → **Webhook Setup**. GitHub connections that use a personal access token or your own GitHub App, Slack connections that use your own Slack app, and Plain all need the webhook set up by hand. 4. **The service didn't turn the webhook off.** Some services disable a webhook after repeated failed deliveries. Save the connection again to register it again. 5. **The filters match.** Remove only optional filters, cause the event again, and add them back once a run starts. Keep the required repository filter for every GitHub event and the branch filter for pushes. Slack events match only channels the Helios app can see. Open the connection and click **Webhook events** to see the events that matched a workflow. Dispatch the workflow manually with a sample payload to check that the prompt behaves before you wait for the real event. ## The sandbox is paused {/* HOLD:PR-603 */} A sandbox stops after roughly fifteen minutes without activity. In chat, the [Files panel](/docs/library/files-panel) then shows a notice that the sandbox is paused and switches to the last staged state. Nothing is lost. Send the agent another message and a fresh sandbox starts with the same files. Staged Library edits are replayed, and any change waiting for review is still in the Changes inbox. ## An agent cannot see a Library file {/* HOLD:PR-603 */} A file outside the run's scope reads as not found. Check that the person or service account the run belongs to can read that path, and share it as a **Library path** if not. See [Library permissions](/docs/library/permissions). ## A change cannot be approved {/* HOLD:PR-603 */} - **Conflict badge.** The live file changed after the agent staged its version. Ask the agent to redo the edit or discard it. - **Changed since review.** The agent rewrote the file after you opened the review. Reload and review again. - **Read-only.** The run was not allowed to write that folder, or you are not an editor on it. See [reviewing changes](/docs/library/reviewing-changes). ## Still stuck Email support@warpbuild.com, or use the in-app chat. Include the run id or the chat link. --- # What is Helios? URL: https://www.heliosapp.com/docs/what-is-helios Description: Helios runs AI agents in cloud sandboxes. Each agent gets a real computer, the full APIs of your tools, and shared files your team reviews, with SSO, roles, and encrypted secrets around it. --- title: "What is Helios?" excerpt: "Always-on AI agents that do your company's work" description: "Helios runs AI agents in cloud sandboxes. Each agent gets a real computer, the full APIs of your tools, and shared files your team reviews, with SSO, roles, and encrypted secrets around it." icon: Sun createdAt: "2025-07-31" --- Helios is a platform for **always-on AI agents**. You describe a task in plain English; an agent picks it up, works it in its own cloud computer, and reports back. There is one agent runtime, and you reach it two ways: - **[Chat](/docs/basics/chat)** - talk to an agent interactively. Attach files, pin the repositories it should work in, share the transcript with a teammate. - **[Workflows](/docs/workflows)** - put an agent on the task permanently. Save the same instructions as a prompt and attach triggers: a schedule, a webhook, or an event from a connected integration. Same agent, two modes. Anything you can get an agent to do in Chat, you can hand off to a Workflow. ## What an agent has ### A real computer Every agent runs in its own isolated [cloud sandbox](/docs/basics/sandboxes) with a filesystem, a shell, and the ability to install packages and execute code. It can read and write files, search and scrape the web, and read the shared files in your [Library](/docs/library/overview). ### The full API of every tool you connect Helios does not ship a curated list of actions per service. Each [integration](/docs/integrations) has its entire API surface indexed, and agents search that index and call whatever endpoint the task needs. Authentication is applied server-side, so an agent acts on your behalf without ever holding your credentials. Integrations cover tools such as GitHub, Slack, Notion, Stripe, and Google Workspace. The [integrations](/docs/integrations) page lists them all. Agents also get direct access to your [Postgres, MySQL, and ClickHouse databases](/docs/integrations/databases) and any external [MCP server](/docs/basics/mcp-servers) you attach. ### Shared context, reviewed by people {/* HOLD:PR-603 */} Pin a [repository or other integration resource](/docs/basics/integration-resources) so an agent always knows which one you mean. Keep playbooks and reference files in the [Library](/docs/library/overview), where every run reads them. When an agent edits a Library file, a person reviews the diff and approves or discards it. See [context](/docs/basics/memory) for what carries between runs. ### Controls your team can live with Everyone delegates work; IT keeps the controls. Helios supports [SAML and OIDC single sign-on with SCIM provisioning](/docs/basics/sso-scim), [organization roles and per-resource access control](/docs/basics/roles-permissions), [envelope-encrypted secrets](/docs/basics/variables-and-secrets), signed webhooks with rotation, and an isolated sandbox for every run. ## What a task looks like A workflow is a prompt plus its triggers. There is nothing to wire up. ``` Every weekday at 9am, look at every pull request opened in acme/api in the last 24 hours. For each one, summarize what changed and flag anything that touches billing or authentication. Post the digest to #eng-standup. ``` Attach a [schedule](/docs/workflows/triggers) for `0 9 * * 1-5`, connect GitHub and Slack, and the task runs itself. Each execution is recorded as a [run](/docs/workflows/runs-and-outputs) with its full transcript, every tool call, and a structured result. ## Compliance and security For security documentation, see the [security page](/security) or contact support@heliosapp.com. No data passing through Helios is used for training or improving AI models. Helios stores data for managing and running your agents, and for providing the relevant functionality to users, in accordance with our data retention policy. ## Where to go next - **[Quickstart](/docs/quickstart)** - connect a tool and hand an agent its first task. - **[Key concepts](/docs/basics/concepts)** - the vocabulary, in one page. - **[Workflows](/docs/workflows)** - prompts, triggers, runs, and outputs. - **[Integrations](/docs/integrations)** - what's connected and how to authenticate it. - **[Roles and permissions](/docs/basics/roles-permissions)** - who can do what. --- # Audit logs URL: https://www.heliosapp.com/docs/access/audit-logs Description: The Helios audit log: what is recorded, who can see it, the monthly fee, filters and CSV download, retention and where events are stored. --- title: "Audit logs" excerpt: "Who changed what in your Helios organization, and when" description: "The Helios audit log: what is recorded, who can see it, the monthly fee, filters and CSV download, retention and where events are stored." icon: ScrollText createdAt: "2026-10-26" updatedAt: "2026-10-26" --- The audit log records every change made in your Helios organization: who made it, what changed, when, and from where. Organization admins can view it, filter it and download it as CSV from **Audit Logs** in the sidebar, at `/helios/audit-logs`. You must be an **organization admin**, and your organization needs an **active subscription**. Audit logs add **$400/month** once you turn them on. ## What is recorded Every change made through the Helios app, the CLI or the API is recorded. Reads are not. Changes are recorded for: - **Access**: grants and their revocation, groups and their members, service accounts, and resources linked to or unlinked from a project. - **Projects and workflows**: projects, agent workflows and their trigger secrets, chat sharing and chat participants. - **Variables and secrets** at the user, project and organization level. The name is recorded. The value never is. - **Connections**: integrations, database connections, MCP servers, network configuration, and outbound webhook targets. - **Sandboxes**: sandbox images and image versions, sandbox environments, sandbox launches and kills, and configuration overrides. - **Organization**: the audit log switch itself, and a request to delete the organization. Not recorded: chat turns, workflow runs and tool calls, Library file edits, sandbox session traffic, webhooks received from providers, and personal preferences. A request that was refused because the caller was not allowed to make the change is recorded with the outcome **Denied**. Requests that fail for other reasons, such as invalid input or an error on our side, are not recorded. Each event has the following fields. | Field | What it holds | | --- | --- | | Actor | Who made the change: a user, a service account or WarpBuild staff. A change made with an API key is attributed to the user who owns the key and marked as made with an API key. Changes made by WarpBuild staff appear as **WarpBuild support**. | | Action | What was done, as `.`, for example `group.created` or `integration.deleted`. | | Target | The type, id and name of what was changed, for example a group or an integration. | | Outcome | **Success**, or **Denied** when the caller was not allowed to make the change. Nothing changes on a denied request. | | Time | When it happened, in UTC. | | Changes | For some actions, the fields that changed with their values before and after, for example a grant's role or a group's members. Variable and secret values are never included. | | Request | The IP address, user agent, HTTP method and path, status code and request id of the request that made the change. | ## Who can see it Only organization admins can open the page or call the API. Members and viewers cannot. ## Turning it on and the fee Events are recorded for every organization from the start, whether or not the log is turned on. Turning it on gives admins access to the log, including the events recorded before it was turned on, and adds **$400/month** to your subscription. To turn it on, open **Audit Logs** in the sidebar and click **Turn on audit logs**, then confirm. The fee is billed at the end of each billing period and is not prorated, so the period you turn it on carries the full fee. Credits are used before your card when the invoice is created. If the fee uses them up, Helios stops until more are added. To turn it off, open the **More actions** menu (⋯) at the top of the page and choose **Turn off audit logs**. The log stays on until the end of the month, and that month's fee is billed as usual. After that the fee stops and admins lose access to the log until it is turned on again. To change your mind before then, choose **Keep audit logs** on the same page. Events keep being recorded. ## Filtering The page shows the last 30 days by default, newest first, 20 events per page. Pick another date range at the top of the page, and filter by: - **Action**: one action name, typed exactly, for example `group.created`. - **Actor**: one person or one service account. - **Target id**: the id of one resource, for example a project or an integration. - **Outcome**: Success or Denied. Click an event to open it. The panel shows what changed, the actor, the target and the request. The filters and the open event are in the page URL, so a link to a filtered view or to a single event can be shared with another admin. ## Download Click **Download CSV** at the top of the page. The file has the events that match the current date range and filters, newest first, up to 10,000 of them. For a larger range, narrow the dates and download more than once. ## Retention and storage The log holds the last 13 months of events. Each event is also written, as it happens, to write-once storage, where it is locked. Nobody, including WarpBuild, can change or delete it. Helios stores audit events in the United States. ## API The log is available through the API for organization admins. Authenticate with an [API key](/docs/basics/roles-permissions#api-keys) scoped to Helios. `GET /audit-events` lists events, newest first, and takes the same filters as the page: `startDate`, `endDate`, `actorId`, `action`, `targetType`, `targetId`, `outcome`, `page` and `perPage`. `format=csv` downloads them as CSV. `GET /audit-events/{id}` returns one event. The API answers `402` while the log is turned off. ```bash curl "https:///audit-events?startDate=2026-10-01T00:00:00Z&action=group.created" \ -H "Authorization: Bearer " ``` ## Related - **[Team management](/docs/access/team-management)** - organization roles, and who counts as an admin. - **[Roles and permissions](/docs/basics/roles-permissions)** - what each role can do, and API keys. --- # Credential mode URL: https://www.heliosapp.com/docs/access/credential-mode Description: When you share an integration, choose whether the grantee's agents call it with their own authorization or with the Helios app identity. This matters for GitHub and Slack. --- title: "Credential mode" excerpt: "Connect as your own account or as the Helios app" description: "When you share an integration, choose whether the grantee's agents call it with their own authorization or with the Helios app identity. This matters for GitHub and Slack." icon: KeyRound createdAt: "2026-09-07" updatedAt: "2026-09-07" --- {/* HOLD:PR-609 */} Most integrations hold one credential and every agent call uses it. See [authentication](/docs/integrations/auth). Two integrations are different. **GitHub** on an organization or enterprise install and **Slack** ask each person to authorize once, so that agent actions carry the right identity. When you [share](/docs/access/sharing) one of those integrations, the share dialog has a **Connects as** choice. | Option | Agent calls use | | --- | --- | | **Their own account** | The grantee's own per-user authorization. This is the default. | | **The Helios app** | The app identity the integration was installed with. | ## Their own account The grantee must complete the per-user authorization for the integration. Until they do, their agents stop with "authorization required" on that integration. Actions in GitHub or Slack are attributed to the person. Access that comes through a project grant always works this way. Only a grant made directly on the integration carries a mode. ## The Helios app Calls use the app identity. Nobody has to authorize individually. Actions appear as the Helios app or bot. Use this for shared automations where no single person should be the author. If any live grant that reaches the caller uses the Helios app, directly, through a [group](/docs/access/groups), or org-wide, that mode wins over a personal one. ## Changing the mode later The access list on the integration shows the mode on each row, for example "Operator · Helios app". Open the row's role menu to switch **Connects as** without sharing again. ## Service accounts A [service account](/docs/access/service-accounts) has no personal GitHub or Slack login. Give it one of these. - A grant on the integration with **Connects as** set to **The Helios app**. - **Act as me** on the service account, so it uses your authorization. ## Where the choice shows The dialog shows **Connects as** for every integration. It only changes behaviour for integrations that require per-user authorization, which today are GitHub and Slack. ## Related - **[Authentication](/docs/integrations/auth)** - per-user authorization. - **[GitHub](/docs/integrations/apps/github)** and **[Slack](/docs/integrations/apps/slack)**. --- # Groups URL: https://www.heliosapp.com/docs/access/groups Description: A group is a named set of people and service accounts. Share a resource with the group and every member gets the role. --- title: "Groups" excerpt: "Share with a whole team at once" description: "A group is a named set of people and service accounts. Share a resource with the group and every member gets the role." icon: Users createdAt: "2026-09-07" updatedAt: "2026-09-07" --- A **group** is a named set of people and [service accounts](/docs/access/service-accounts). When you [share](/docs/access/sharing) a resource with a group, every member gets the role. Add someone to the group later and they get the same access without a new grant. ## Managing groups Open **Groups** in the sidebar, at `/helios/groups`. Only organization admins can create or change groups. - **New group** creates a group. Give it a name that describes the team, for example "support". - Open a group to add or remove members. Members can be people or service accounts. - Rename or delete a group from the same page. Deleting a group removes every grant that was made to it. ## Using a group Pick the group as the principal in the share dialog. The access list shows the grant on the group, and each member's effective role includes it. A common shape is one group per team, shared on the team's project at `editor`, with the rest of the organization at `viewer` or `operator`. ## From the CLI {/* HOLD:PR-619 */} ```bash helios group list helios group create support helios group member add support user: helios group member add support sa:nightly-digest helios group member remove support user: helios group rename support customer-support helios group delete customer-support ``` Group commands need the organization admin role, like the dashboard. ## Related - **[Sharing](/docs/access/sharing)** - **[Team management](/docs/access/team-management)** - who is in the organization at all. --- # Service accounts URL: https://www.heliosapp.com/docs/access/service-accounts Description: A service account is a non-human identity. Assign it to a workflow with Runs as, share resources with it, and disable it to stop every run that uses it. --- title: "Service accounts" excerpt: "The identity a workflow runs as" description: "A service account is a non-human identity. Assign it to a workflow with Runs as, share resources with it, and disable it to stop every run that uses it." icon: Bot createdAt: "2026-09-07" updatedAt: "2026-09-07" --- A **service account** is an identity that a [workflow](/docs/workflows) runs as. It has its own grants, so what an unattended run can reach does not depend on the person who happened to create the workflow. There are two kinds. | Kind | What it is | | --- | --- | | Project default | Every project has one. It is created with the project and cannot be renamed or deleted. It shows as **Default** with the project name. | | Named | An account you create, with a name you choose. | ## Creating one Open **Service Accounts** in the sidebar, at `/helios/service-accounts`, and choose **New service account**. Rename it inline to something that says what it is for, such as "nightly-digest". Each account has a detail view with two lists. - **Used in** shows the workflows that run as this account. - **Has access to** shows every grant the account holds. ## Giving it access A new named account has no access. [Share](/docs/access/sharing) the integrations, projects, and [Library paths](/docs/library/permissions) the workflow needs with the account, at the lowest role that works. An integration shared at `operator` is enough for an agent to call it. You can also add a service account to a [group](/docs/access/groups) and share with the group. ## Runs as On a workflow page, the **Runs as** control shows which account the workflow uses. Open it to pick **Project default** or any named account you can assign, or follow **Manage service accounts** to the accounts page. When the run starts, the agent gets exactly the service account's access. ## Disabling an account Each named account has a switch that disables it. A disabled account cannot start runs. Workflows that run as it fail until the account is enabled again. Use this to stop an automation quickly without editing every workflow. ## Sharing the account itself A service account can be shared at `viewer` or `admin`, with people or groups but not org-wide. `admin` lets someone rename, disable, or assign the account and change its identity settings. ## Act as me {/* HOLD:PR-609 */} Some integrations need a person's own authorization. Today that is [GitHub](/docs/integrations/apps/github) on organization installs and [Slack](/docs/integrations/apps/slack). A run under a service account would normally stop with "authorization required" on those. The **Identity** section on a named service account has an **Act as me** switch. Turn it on and the account uses your GitHub or Slack authorization when a run calls those integrations. Actions appear as you. - You can only point a service account at yourself. Nobody can make it act as a teammate. - Only admins of the service account can change the switch. - Project default accounts do not have this section. The other way to avoid "authorization required" is to share the integration with the account using the Helios app identity. See [credential mode](/docs/access/credential-mode). ## From the CLI {/* HOLD:PR-619 */} ```bash helios service-account list helios service-account create nightly-digest helios service-account assign nightly-digest helios service-account unassign helios service-account disable nightly-digest helios service-account enable nightly-digest helios service-account delete nightly-digest ``` `assign` sets **Runs as** for the workflow. `unassign` puts it back on the project default. ## Related - **[Sharing](/docs/access/sharing)** - **[Credential mode](/docs/access/credential-mode)** - **[Runs and outputs](/docs/workflows/runs-and-outputs)** --- # Sharing URL: https://www.heliosapp.com/docs/access/sharing Description: Open the share dialog on any resource, pick who gets access and at which role, and set an expiry. The same grants can be made from the CLI. --- title: "Sharing" excerpt: "Share a resource with a person, a group, a service account, or everyone" description: "Open the share dialog on any resource, pick who gets access and at which role, and set an expiry. The same grants can be made from the CLI." icon: Share2 createdAt: "2026-09-07" updatedAt: "2026-09-07" --- Every resource in Helios has a share button. It opens a dialog where you choose who gets access, at what role, and for how long. The dialog works the same way for projects, workflows, chats, integrations, MCP servers, database connections, service accounts, and Library paths. For how resources inherit access from their project, see [projects and sharing](/docs/basics/projects-and-sharing). ## Who you can share with | Principal | Notes | | --- | --- | | A person | Any member of the organization. | | A [group](/docs/access/groups) | Every member of the group gets the role. | | A [service account](/docs/access/service-accounts) | Gives a workflow that runs as that account access to the resource. | | Everyone in the organization | Shown with an **Org-wide** badge in the access list. | ## Roles The share dialog offers four roles. The dashboard labels them by what they allow. | Role | Label | Allows | | --- | --- | --- | | `viewer` | Can view | Read the resource and its runs. | | `operator` | Can run | Everything a viewer can, plus trigger runs and use the resource from an agent. | | `editor` | Can edit | Everything an operator can, plus create, change, and delete. | | `admin` | Full access | Everything an editor can, plus change who has access. | You can never grant a role above your own on that resource. See [roles and permissions](/docs/basics/roles-permissions) for how roles resolve. Some resource types restrict the choices. - **Chats** can only be shared at `viewer`, only with people or groups, and default to a one day expiry. - **Service accounts** can be shared at `viewer` or `admin`, and not org-wide. - **Integrations, MCP servers, and database connections** default to `operator`. - **Projects** default to `editor`. **Workflows** default to `operator`. ## Expiry Every grant can expire. The options are **No expiry**, **1 day**, **1 week**, or **Custom** with a date you choose. An expired grant disappears from the access list and the person loses access at that time. ## The access list Below the dialog, the access list shows every grant on the resource, including grants inherited from the project. From here you can change a role or revoke a grant. {/* HOLD:PR-609 */} For integrations, each row also shows how the grantee connects. See [credential mode](/docs/access/credential-mode). ## Sharing a Library path {/* HOLD:PR-603 */} Library folders are shared through the same dialog with the **Library path** grant type. The levels are **viewer** and **editor**. See [Library permissions](/docs/library/permissions). ## From the CLI {/* HOLD:PR-619 */} The `helios` CLI makes the same grants, so sharing can be scripted. ```bash helios share workflow/ --with group:support --role operator --expires 2026-10-01 helios share integration/ --with sa:nightly-digest --role operator helios unshare workflow/ --from user: helios access list workflow/ helios shared list ``` Principals are `everyone`, `user:`, `group:`, and `sa:`. Add `--json` to any command for machine-readable output. The same rules apply as in the dashboard. You cannot grant above your own role, and grants to a project's default service account are refused because they could not be revoked. ## Related - **[Roles and permissions](/docs/basics/roles-permissions)** - **[Groups](/docs/access/groups)** - **[Service accounts](/docs/access/service-accounts)** --- # Team management URL: https://www.heliosapp.com/docs/access/team-management Description: Members are managed in the organization settings that Helios shares with WarpBuild. Invite by email, pick a role, and remove people when they leave. --- title: "Team management" excerpt: "Invite people, remove them, and set their organization role" description: "Members are managed in the organization settings that Helios shares with WarpBuild. Invite by email, pick a role, and remove people when they leave." icon: UserPlus createdAt: "2026-09-07" updatedAt: "2026-09-07" --- Helios is part of your WarpBuild organization. People are invited and removed in the shared WarpBuild organization settings. Only organization admins can do this. ## Inviting people 1. Open **Settings**, then **Account**. The page lists every user and pending invitation. 2. Choose **Invite Users**. 3. Enter one or more email addresses, separated by commas, spaces, or new lines. 4. Pick a role and choose **Send Invitations**. Each person receives an email. The invitation stays listed as pending until they accept it. You can remove a pending invitation from the same list. If your organization uses SSO or SCIM, people can be provisioned automatically instead. See [SSO and SCIM](/docs/basics/sso-scim). ## Organization roles Every member has one organization role. | Role | What it means | | --- | --- | | `admin` | Manages members, billing, SSO, SCIM, API keys, and the audit log. Full access to every resource. | | `member` | A normal user. | | `viewer` | Read-only at the account layer. | Change the role from the row's menu. See [roles and permissions](/docs/basics/roles-permissions) for how the organization role combines with grants on projects and resources. The last admin in an organization cannot be demoted or removed. ## Removing people Remove a member from the same list. Their grants are removed with them. Workflows they created stay in their projects and keep running under their [service account](/docs/access/service-accounts) settings. Shared integrations they connected keep working, since the credential belongs to the integration and not to the person. ## Beyond membership Membership gets someone into the organization. What they can reach is decided by [projects](/docs/basics/projects-and-sharing), [sharing](/docs/access/sharing), and [groups](/docs/access/groups). --- # Chat URL: https://www.heliosapp.com/docs/basics/chat Description: Chat is the interactive way to use a Helios agent. It has the same computer, tools, and integrations a workflow does. --- title: "Chat" excerpt: "Talk to your agents - files, forking, sharing, and pinned context" description: "Chat is the interactive way to use a Helios agent. It has the same computer, tools, and integrations a workflow does." icon: MessageSquare createdAt: "2026-07-09" --- Chat is the interactive way to work with an agent. You give it a task, watch it work, and steer it as it goes. It is the same agent runtime that [workflows](/docs/workflows) use - the same [sandbox](/docs/basics/sandboxes), the same [integrations](/docs/integrations), the same [database](/docs/integrations/databases) and [MCP](/docs/basics/mcp-servers) access. Chat is where you figure out how a task should be done. Once it works, save the instructions as a workflow and put the agent on it permanently. ## Files Upload files to a chat and the agent finds them in its sandbox. The agent is told the path of each file you attach, so you can refer to them naturally. "Reconcile the CSV I just uploaded against the payments table." Uploads belong to the chat. Deleting the chat deletes them. ## Pinned resources Pin a GitHub repository to a chat and the agent gets authenticated access to it - Helios injects a short-lived, repository-scoped token at the network layer, so the agent can clone and work in the repo without ever seeing a credential. Pinning also disambiguates: when you say "the repo", the agent knows which one. See [integration resources](/docs/basics/integration-resources). ## Forking Fork a chat to branch off from where it is. The fork copies the full message history, so the new agent starts with everything the original was told. Use it to try a different approach without losing the path you were on. ## Sharing a transcript Share a chat to get a public link to its transcript. - You choose the **cutoff message**. Everything up to and including it is visible; everything after it is withheld - so you can keep working in the chat without extending what you shared. - The link exposes only the chat's title and those messages. It does not expose your Library files, your integrations, or the agent's sandbox. - **Anyone with the link can read it.** There is no sign-in check. Treat a share link as public. - Unshare at any time to revoke the link. Re-sharing an already-shared chat updates the cutoff, keeping the same link. ## Chat and workflows | | Chat | Workflow | | --- | --- | --- | | Started by | You, interactively | A [trigger](/docs/workflows/triggers) | | Instructions | Each message | A saved prompt | | Workspace | Per chat | Per workflow, shared by all its runs | | Output | The conversation | A recorded [run](/docs/workflows/runs-and-outputs) | Both bill the same way - see [pricing](/docs/basics/pricing). --- # Key concepts URL: https://www.heliosapp.com/docs/basics/concepts Description: Agents, chats, workflows, triggers, runs, sandboxes, integrations, projects, and roles - what each term means in Helios. --- title: "Key concepts" excerpt: "The Helios vocabulary, in one page" description: "Agents, chats, workflows, triggers, runs, sandboxes, integrations, projects, and roles - what each term means in Helios." icon: BookOpen createdAt: "2025-07-31" --- ## Agent An AI model working a task inside its own [sandbox](/docs/basics/sandboxes), with access to a shell, a filesystem, code execution, the web, your [integrations](/docs/integrations), your databases, and any attached [MCP servers](/docs/basics/mcp-servers). There is one agent runtime. You reach it through **chat** or through a **workflow**. ## Chat An interactive session with an agent. Attach files, pin a repository, fork the conversation, share a read-only transcript. See [chat](/docs/basics/chat). ## Workflow An agent put on a task permanently: a **prompt** plus one or more **triggers**. There is nothing to wire up - the prompt is the task. See [workflows](/docs/workflows). ## Trigger What causes a workflow to run. Four types: | Type | Fires when | | --- | --- | | **Manual** | You dispatch it, optionally with an input payload. | | **Schedule** | A cron expression matches. Schedules run in UTC. | | **Webhook** | A signed HTTP request arrives at the trigger's URL. | | **Integration** | An event arrives from a connected integration, such as a new pull request. | See [triggers](/docs/workflows/triggers). ## Run One execution of a workflow. A run records the trigger context, the agent's full transcript, the result, and a status: `queued`, `running`, `succeeded`, `failed`, `pending_cancel`, or `cancelled`. See [runs and outputs](/docs/workflows/runs-and-outputs). ## Sandbox The isolated cloud computer an agent runs in. Its filesystem is discarded when the run ends. Shared files come from the Library, mounted under `~/context`. Outbound network access is closed by default and opened per host, with credentials injected at the network layer so the agent never holds them. See [sandboxes](/docs/basics/sandboxes). ## Integration An external service connected to Helios. The credential behind it is stored server-side and never reaches the agent. Helios indexes the service's **entire API**, and agents search that index and call whatever endpoint the task needs - not a curated list of actions. See [integrations](/docs/integrations). ## Integration resource A specific object inside an integration, pinned to a chat or workflow. GitHub repositories can be pinned. Pinning both disambiguates ("the repo") and grants scoped, credential-free access. See [integration resources](/docs/basics/integration-resources). ## Project The container for related workflows, chats, integrations, variables, and secrets - and the unit of access control. Resources inherit access from their project. Everyone gets a **Personal** project. See [projects and sharing](/docs/basics/projects-and-sharing). ## Roles Two layers. Your **organization role** is `admin`, `member`, or `viewer`, and says what you can create. Your **resource role** on a given project or workflow is `viewer`, `operator`, `editor`, or `admin`, and comes from a grant. A grant can name a person, a group, a service account, or everyone in the organization. See [roles and permissions](/docs/basics/roles-permissions). ## Group A named set of people and service accounts. Grant a role to the group once and every member gets it. ## Service account The identity a workflow runs as. Every project has a default service account, and you can create named ones. A service account holds resource roles like a person does, and can be disabled. ## Environment The image a sandbox starts from. Helios ships a default environment. You can build your own from a Dockerfile, with versions and build logs. {/* HOLD:PR-600 */} ## Library The shared file store. It has organization, project, and personal trees, mounted into every sandbox. Agents propose changes to it. People review and approve them. See [the Library](/docs/library/overview). ## Visibility Whether a resource is **restricted** (explicit grants only) or **organization** (everyone gets a role). Managed for projects and integrations. Workflows inherit from their project. ## Variables and secrets **Variables** are plaintext configuration, passed into every run as context. **Secrets** are envelope-encrypted, write-only, and never enter an agent's context. Both are scoped at the organization, project, user, or workflow level, with the most specific level winning. See [variables and secrets](/docs/basics/variables-and-secrets). ## Credits Usage is metered in Helios credits, derived from actual model spend. See [pricing](/docs/basics/pricing). ## MCP The Model Context Protocol. Attach external MCP servers to give your agents more tools; or drive Helios itself over MCP from your own agent. See [MCP servers](/docs/basics/mcp-servers). --- # Integration resources URL: https://www.heliosapp.com/docs/basics/integration-resources Description: Integration resources attach a specific object from a connected service, such as a GitHub repository, to a chat or workflow as scoped, authenticated context. --- title: "Integration resources" excerpt: "Pin a specific repository so an agent knows which one you mean" description: "Integration resources attach a specific object from a connected service, such as a GitHub repository, to a chat or workflow as scoped, authenticated context." icon: Pin createdAt: "2026-07-09" --- An [integration](/docs/integrations) gives an agent access to a whole service. An **integration resource** narrows that down to a specific object inside it, and pins it to a chat or a workflow. Pinning does two things: 1. **It disambiguates.** When the prompt says "the repo", the agent knows exactly which repository that is. You don't have to spell out `acme/api` in every instruction. 2. **It grants scoped, credential-free access.** Helios mints a short-lived token scoped to just that resource and injects it into the agent's outbound requests at the network layer. The agent can clone and work in the repository; it never sees a credential it could leak. ## What can be pinned **GitHub repositories**. You can pin more than one. Other integrations are reachable from any chat or workflow through their full API. They have no pinnable object type. ## Pinning to a chat Open the chat's resource picker, choose your GitHub integration, and select one or more repositories. The agent is told which repositories are attached and can `git clone` them immediately. ## Pinning to a workflow A workflow's pinned resources apply to every run of it. Set them once on the workflow; each run gets freshly minted access. This is what makes a repo-scoped workflow prompt work: ``` When a pull request is opened, check out the branch, run the test suite, and comment on the PR with any failures. ``` The agent has the repository, the checkout, and the ability to run code - because the repository is pinned and the sandbox is a [real computer](/docs/basics/sandboxes). ## Related - **[GitHub integration](/docs/integrations/apps/github)** - connecting and authorizing. - **[Sandboxes](/docs/basics/sandboxes)** - how credential injection works. --- # Keyboard shortcuts URL: https://www.heliosapp.com/docs/basics/keyboard-shortcuts Description: Global shortcuts and two-key navigation sequences for Helios and settings. --- title: "Keyboard shortcuts" excerpt: "Move around Helios without touching the mouse" description: "Global shortcuts and two-key navigation sequences for Helios and settings." icon: Keyboard createdAt: "2025-07-31" --- Press `⌘ + /` anywhere to see this list in the app. ## General | Shortcut | Action | | --- | --- | | `⌘ + /` | Show keyboard shortcuts | | `⌘ + K` | Open command menu | | `⌘ + B` | Toggle sidebar | | `/` | Search | | `⌥ + T` | Toggle theme | ## Navigation Two-key sequences: press the first key, release, then press the second. | Shortcut | Action | | --- | --- | | `g` then `h` | Go to Helios | | `g` then `s` | Go to Settings | ### Within Helios | Shortcut | Action | | --- | --- | | `h` then `c` | Chat | | `h` then `w` | Workflows | | `h` then `i` | Integrations | | `h` then `d` | Databases | | `h` then `m` | MCP servers | | `h` then `v` | Variables | | `h` then `a` | Audit logs | ### Within Settings | Shortcut | Action | | --- | --- | | `s` then `a` | Account | | `s` then `b` | Billing | | `s` then `k` | API keys | ## Platform notes On Windows and Linux, use `Ctrl` wherever `⌘` appears. Shortcuts are unavailable on mobile. If a shortcut doesn't fire, check that focus isn't inside a text field and that your browser hasn't claimed the combination - Firefox binds `⌘ + K` to the address bar. --- # MCP servers URL: https://www.heliosapp.com/docs/basics/mcp-servers Description: Connect any remote MCP server so Helios agents can call its tools, and expose Helios itself over MCP to your own agents. --- title: "MCP servers" excerpt: "Attach external MCP servers to your agents - and use Helios as one" description: "Connect any remote MCP server so Helios agents can call its tools, and expose Helios itself over MCP to your own agents." icon: Plug createdAt: "2026-07-09" --- The Model Context Protocol (MCP) is how agents discover and call tools that live outside the platform they run on. Helios speaks it in both directions. ## Attaching an external MCP server Register a remote MCP server and its tools become available to your agents, alongside their [integrations](/docs/integrations) and [database access](/docs/integrations/databases). | Field | Notes | | --- | --- | | Name | Lowercase slug, e.g. `internal-search`. | | URL | Must be **HTTPS**. Helios speaks Streamable HTTP. | | Description | Shown to the agent so it knows when to reach for this server. | | Authentication | `none`, bearer token, custom headers, or OAuth 2.0. | | Tool filter | An allowlist of tool names. | | Timeout | Per-call, 1–60 seconds. Defaults to 5 seconds. | Only remote servers over HTTPS are supported - there is no `stdio` transport. URLs pointing at localhost, link-local addresses, cloud metadata endpoints, or private network ranges are rejected. ### Authentication - **Bearer** - Helios sends `Authorization: Bearer `. - **Headers** - supply your own header names and values, up to 20 of them. `Authorization` is allowed; transport headers that Helios controls (`host`, `content-length`, `connection`, `transfer-encoding`, `keep-alive`, `upgrade`, `te`, `trailer`, `content-type`, `accept`) are rejected. Header names must be unique, and each value may be up to 8192 characters. - **OAuth 2.0** - authorization code flow with PKCE. Helios stores the refresh token and refreshes access tokens as needed. Credentials are [envelope-encrypted](/docs/basics/variables-and-secrets) and are never returned by the API or exposed to the agent. The authentication type is fixed when you create the server. To change it, create a new server entry. ### Tool filtering The tool filter is an allowlist, enforced server-side on both discovery and invocation. A tool not on the list is hidden from the agent, and a call to it is rejected even if the agent somehow names it. Leave the filter empty to expose every tool the server offers. Use it. Most MCP servers expose more than any one task needs, and a narrower surface makes the agent both safer and more accurate. ### How agents use them Each attached MCP server is handed to a dedicated subagent. Your agent delegates to it - "find the open incidents for service X" - and the subagent discovers the server's tool catalog, picks the right call, and returns the result. This keeps a large external tool catalog from crowding the main agent's context. ### Scope MCP servers are stored per organization and are visible to the user who created them. Agents running in a project pick up the servers available to that project. ## Using Helios as an MCP server Helios exposes itself over MCP, so your own agents - Claude Code, or anything else that speaks MCP - can drive Helios. Connect to the Helios MCP endpoint over Streamable HTTP and authenticate with the same bearer token you would use against the Helios API. See [API keys](/docs/basics/roles-permissions#api-keys). It exposes two tools: | Tool | Purpose | | --- | --- | | `find_relevant_apis` | Semantic search across the Helios API to find the right endpoint for a task. | | `call_api` | Call that endpoint, authenticated as you. | This is the same full-API pattern Helios uses for its own integrations. An agent searches the API surface and calls what it needs. Through it, your agent can list projects, create and trigger workflows, read runs, manage integrations and database connections, and start chats. --- # Context URL: https://www.heliosapp.com/docs/basics/memory Description: Helios agents start each run in a fresh sandbox. The Library carries files between runs, and only approved changes reach it. Helios also records how an agent used an API before. --- title: "Context" excerpt: "What an agent keeps between runs, and what it does not" description: "Helios agents start each run in a fresh sandbox. The Library carries files between runs, and only approved changes reach it. Helios also records how an agent used an API before." icon: Brain createdAt: "2026-07-09" updatedAt: "2026-09-07" --- {/* HOLD:PR-601 */} {/* HOLD:PR-603 */} Every run starts in a fresh [sandbox](/docs/basics/sandboxes). This page lists what carries over from one run to the next and what does not. ## What persists **Library files.** The [Library](/docs/library/overview) is the shared file store for your organization, its projects, and each person. Helios mounts the folders a run may see under `~/context` in the sandbox. Playbooks, templates, and reference files live there, and every run reads the same copy. **Approved changes.** An agent can edit files under `~/context`. Those edits become a proposed change. A person reviews the diff and approves or discards each file. Only approved files reach the Library, so a later run sees them. See [proposing changes](/docs/library/proposing-changes) and [reviewing changes](/docs/library/reviewing-changes). **Pinned resources.** A [repository or other integration resource](/docs/basics/integration-resources) pinned to a chat or a workflow stays pinned for every run. **Chat history.** A chat keeps its own message history. [Forking a chat](/docs/basics/chat) copies that history into a new chat. Workflows do not see chat history. **API memory.** When an agent works out how to complete a task against an [integration's API](/docs/integrations), Helios records the procedure. The next agent that takes a similar task against the same integration starts from that record. This memory is scoped to your organization and the integration. It stores only the shape of the API calls. The contents of your records are never stored. It is managed by Helios and cannot be viewed or edited. Instructions in the prompt always take precedence. ## What does not persist **The sandbox filesystem.** Anything an agent writes outside `~/context` disappears when the run ends. That includes `$TMPDIR`, installed packages, and the agent's own scratch folder at `~/context/agent`. **Unapproved edits.** A proposed change that nobody approves never reaches the Library. The next run does not see it. To carry state between workflow runs, ask the agent to keep a file in the Library and approve the change after each run. See [Library overview](/docs/library/overview). --- # Pricing and credits URL: https://www.heliosapp.com/docs/basics/pricing Description: Helios meters usage in credits based on the model tokens your agents consume. There are no per-action or per-integration fees. --- title: "Pricing and credits" excerpt: "Usage is metered in credits, derived from actual model spend" description: "Helios meters usage in credits based on the model tokens your agents consume. There are no per-action or per-integration fees." icon: DollarSign createdAt: "2025-07-31" --- Helios bills for what your agents actually consume: **model usage**. There are no per-action fees, no per-integration fees, and no charge for connecting a tool or attaching an [MCP server](/docs/basics/mcp-servers). ## Credits Usage is metered in **Helios credits**. ``` 1,000,000 credits = $1.00 ``` Every model call an agent makes - in [chat](/docs/basics/chat) or in a [workflow run](/docs/workflows/runs-and-outputs) - is priced at its underlying token cost and converted to credits. Usage is attributed to the organization that owns the chat or workflow. ## What drives cost **How much the agent has to read and think.** A digest over ten pull requests costs more than one over two. An agent that has to search an unfamiliar API costs more the first time than the tenth, because it [remembers](/docs/basics/memory) what worked. **How long it runs.** A workflow that wakes up every five minutes and finds nothing to do still pays for the model call that decided there was nothing to do. If a task doesn't need to run that often, don't schedule it that often. **Not what it touches.** Calling a hundred GitHub endpoints in one run costs the same as calling one, apart from the tokens spent reading the responses. ## Keeping cost down - **Scope the trigger.** [Filters](/docs/workflows/triggers) on integration events stop irrelevant events from ever starting a run. A `push` filtered to `main` is far cheaper than one on every branch. - **Let the agent stop early.** A prompt that says "if nothing changed, do nothing" ends the run in one turn. - **Prefer schedules to polling.** A schedule that runs hourly costs a twelfth of one that runs every five minutes. - **Keep state in the Library.** A record of what has already been handled stops an agent from re-reading the same data every run. See [advanced](/docs/advanced). ## When credits run out If your organization has exhausted its credits, new chats and workflow runs are rejected before an agent starts. Runs already in flight finish. Existing workflows, integrations, and data are untouched - top up and they resume on the next trigger. ## Billing Usage is reported continuously and billed through Stripe. See your organization's billing settings for current balance, usage history, and plan. The [audit log](/docs/access/audit-logs) is a flat add-on: $400 a month, added to your subscription when an admin turns it on. --- # Projects and sharing URL: https://www.heliosapp.com/docs/basics/projects-and-sharing Description: A project groups related workflows, chats, integrations, and variables, and is the unit of access control in Helios. --- title: "Projects and sharing" excerpt: "Organize agents into projects and decide who can reach them" description: "A project groups related workflows, chats, integrations, and variables, and is the unit of access control in Helios." icon: FolderOpen createdAt: "2026-07-09" --- A **project** groups related work: [workflows](/docs/workflows), chats, [integrations](/docs/integrations), [variables and secrets](/docs/basics/variables-and-secrets). More importantly, a project is the unit of access control. Resources inside it inherit their access from it, so granting a teammate access to a project grants them access to everything in it - which is almost always what you want. ## Your personal project Every user gets a **Personal** project in each organization they belong to. It is restricted to you and it's where ad-hoc chats land. Use it to try things; move work into a shared project when it matters to someone other than you. ## Creating a project Any member can create a project. The creator becomes its `admin`. Give it a name that describes the work. "support triage" ages better than "support team's stuff". ## Sharing a project Open the project's permissions to control who can reach it. There are two dials. **Visibility** decides the baseline: - **Restricted** - only people you grant access to, explicitly. - **Organization** - everyone in the organization gets access, at a role you choose. **Grants** give a specific person, group, or service account a specific [role](/docs/basics/roles-permissions) on the project: `viewer`, `operator`, `editor`, or `admin`. A grant can expire after a day, a week, or a date you choose. An explicit grant adds to the baseline. The common shape is an organization-visible project at the `operator` role, so everyone can see the agents and run them, with `editor` granted to the handful of people who maintain the prompts. A restricted project must always keep at least one explicit admin. Helios won't let you remove the last one. ## Sharing integrations [Integrations](/docs/integrations) have their own visibility, managed the same way. Connect GitHub once at organization visibility and every project's agents can use it. Credentials are never exposed by sharing an integration. Users of a shared integration can have agents act through it. Only an `admin` of the integration can read the credential behind it. ## Sharing a chat transcript Sharing a [chat](/docs/basics/chat) is a different thing entirely - it produces a **public link** to a read-only transcript, up to a message you choose. It doesn't grant access to Helios, and anyone with the link can read it. Use it to show a colleague what an agent did. To work together, share the project. ## Sharing databases and MCP servers [Database connections](/docs/integrations/databases) and [MCP servers](/docs/basics/mcp-servers) are shared the same way as integrations. Each one belongs to one or more projects and can carry its own grants. ## Related - **[Roles and permissions](/docs/basics/roles-permissions)** - what each role can do. - **[SSO and SCIM](/docs/basics/sso-scim)** - provisioning people into the organization. --- # Roles and permissions URL: https://www.heliosapp.com/docs/basics/roles-permissions Description: Helios has two layers of access control. An organization role says what you can create. A resource role says what you can do to a specific project, workflow, chat, or integration. --- title: "Roles and permissions" excerpt: "Organization roles, resource roles, and how the two relate" description: "Helios has two layers of access control. An organization role says what you can create. A resource role says what you can do to a specific project, workflow, chat, or integration." icon: Shield createdAt: "2025-07-31" --- Access in Helios has two layers, and it helps to keep them apart. 1. **Organization role** - what you can create in the organization. 2. **Resource role** - what you can do to a specific project, workflow, chat, integration, database connection, MCP server, or Library folder. ## Organization roles Every member of an organization carries exactly one organization role. | Role | What it means | | --- | --- | | `admin` | Everything `member` can do, plus manage members, billing, SSO, SCIM, and groups. | | `member` | Can create projects and service accounts. | | `viewer` | Can see the organization's groups and service accounts, but creates nothing. | The last admin in an organization cannot be demoted or removed. An organization role never grants access to a resource by itself. Access to a resource always comes from a grant, either on the resource or on the project it belongs to. ## Resource roles Access to each resource is granted by a resource role. The roles are cumulative. Each one includes everything below it. | Role | Allows | | --- | --- | | `viewer` | See the resource. For a workflow, that includes its runs and their transcripts. | | `operator` | Use it. Trigger a workflow, cancel a run, send a message in a chat, or let an agent act through an integration. | | `editor` | Change it. Edit a prompt, create workflows in a project, update or delete the resource. | | `admin` | Full control. Read its credential and manage the service accounts that act as it. | Concretely, for a [workflow](/docs/workflows), a `viewer` can read it and see its runs. An `operator` can also trigger it and cancel runs. An `editor` can also edit the prompt and delete the workflow. The share dialog shows these roles as **Can view**, **Can run**, **Can edit**, and **Full access**. ## Grants A grant gives a role on a resource to a principal. A principal is one of: - a **person**, - a **group** of people and service accounts, - a **service account**, the identity a workflow runs as, - or **everyone** in the organization. A grant can expire. When you share a resource, choose no expiry, one day, one week, or a custom date. ### Who can share Sharing is not a separate role. Anyone holding a grant on a resource can share it, but never above their own role. A `viewer` can only pass on `viewer`. You cannot lower or remove your own access. Ask another admin of the resource to do it. ## Inheritance through projects Workflows, integrations, MCP servers, and database connections belong to a [project](/docs/basics/projects-and-sharing) and inherit its grants. Grant someone `editor` on a project and they can edit every workflow in it, without a per-workflow grant. A grant on the resource itself adds to what the project gives. This is why the project is the right unit to think about when granting access. Chats do not inherit. The person who started a chat has full access to it. A chat inside a shared project is not readable by everyone with access to the project. ## Visibility Every resource is either: - **Restricted** - reachable only through explicit grants, or through the project it belongs to. - **Organization** - everyone in the organization holds a role on it. You choose which role. Making a resource organization-visible is how you share it with the whole team. See [projects and sharing](/docs/basics/projects-and-sharing). ## API keys API keys authenticate machines and the Helios CLI. Create them under **Settings → API keys**. A key is shown once, at creation. Afterwards only its last four characters are visible. Keys can be personal or owned by the organization. A key's owner, or an organization admin, can rename, disable, set an expiry, or delete it. To rotate a key, create a new one and delete the old. ## Related - **[Projects and sharing](/docs/basics/projects-and-sharing)** - organizing and granting access. - **[SSO and SCIM](/docs/basics/sso-scim)** - federating identity and provisioning users. - **[Variables and secrets](/docs/basics/variables-and-secrets)** - who can read what. --- # Sandboxes URL: https://www.heliosapp.com/docs/basics/sandboxes Description: Helios agents run in isolated cloud sandboxes with a shell, a filesystem, code execution, web access, and the Library mounted read-only or read-write. --- title: "Sandboxes" excerpt: "Every agent gets its own isolated cloud computer" description: "Helios agents run in isolated cloud sandboxes with a shell, a filesystem, code execution, web access, and the Library mounted read-only or read-write." icon: Box createdAt: "2026-07-09" --- Every Helios agent runs inside its own **sandbox** - an isolated cloud computer, provisioned per chat or per workflow run. Nothing is shared between sandboxes. This is what separates an agent from a chatbot. It doesn't describe the work; it does the work, on a machine, with tools. ## What's inside **A shell and a filesystem.** The agent can run commands, read, write, and edit files, and search across them. **Code execution.** The default environment is Debian with a build toolchain, `git`, `jq`, and a JavaScript / TypeScript runtime. The agent installs what else it needs. You can also build your own environment from a Dockerfile. **Web access.** The agent can search the web and scrape a URL into clean markdown. **Your tools.** [Integrations](/docs/integrations) (the full API of each connected service), [databases](/docs/integrations/databases), and any attached [MCP servers](/docs/basics/mcp-servers). ## Files {/* HOLD:PR-601 */} The sandbox filesystem belongs to one run. When the run ends, the filesystem is discarded. Shared files come from the [Library](/docs/library/overview). Helios mounts the Library folders the run may see under `~/context`. The agent reads them from disk. Edits under `~/context` are staged as a proposed change that a person approves or discards. Nothing reaches the Library without approval. Agents are told to use `$TMPDIR` for scratch work. See [context](/docs/basics/memory) for what carries between runs. ## Lifetime A sandbox stays alive while the agent is active and shuts down after a period of inactivity, roughly fifteen minutes. The next message in a chat or the next run of a workflow gets a fresh sandbox with the same Library mounts. Workflow runs have a hard **30-minute execution limit**. See [runs and outputs](/docs/workflows/runs-and-outputs). ## Isolation and credentials Sandboxes start with **outbound network access closed**. Helios opens access to specific hosts only as the agent's task requires, and injects the necessary authentication at the network layer. This is the important part: **the agent never holds your credentials.** When it calls the GitHub API or clones a pinned repository, Helios attaches a short-lived, narrowly scoped token to the outbound request. Nothing readable as a secret exists inside the sandbox for a prompt injection to exfiltrate. Your [secrets](/docs/basics/variables-and-secrets) are envelope-encrypted at rest and are never passed into the agent's context. ## Database access is deliberately narrow The agent reaches your databases through a dedicated tool. The credentials stay with Helios. Queries run read-only, with a statement timeout and a row limit. See [databases](/docs/integrations/databases) and [database security](/docs/integrations/databases-security) for how to bound this further on your side. --- # SSO and SCIM URL: https://www.heliosapp.com/docs/basics/sso-scim Description: Federate identity into Helios with SAML 2.0 or OIDC, provision and deprovision users automatically with SCIM 2.0. --- title: "SSO and SCIM" excerpt: "SAML and OIDC single sign-on, with SCIM user provisioning" description: "Federate identity into Helios with SAML 2.0 or OIDC, provision and deprovision users automatically with SCIM 2.0." icon: KeyRound createdAt: "2026-07-09" --- Helios supports **SAML 2.0** and **OIDC** single sign-on, and **SCIM 2.0** for automated user provisioning. Both are configured per organization. Helios speaks the standards, so any SAML 2.0 or OIDC identity provider will connect. JumpCloud is tested in production. If you're setting up another provider and something doesn't line up, tell us and we'll work through it with you. Contact support@heliosapp.com to enable SSO for your organization. You'll receive a one-time setup link; opening it shows the values your identity provider needs and lets you submit your configuration. ## SAML Your IdP needs two values from Helios, both shown on your setup page: | Field | Value | | --- | --- | | ACS URL (Assertion Consumer Service) | `https:///api/v1/auth/sso/saml2/callback/` | | Entity ID / Audience | `https:///api/v1/auth/sso/saml2/sp/metadata` | You can supply your IdP's configuration three ways: a **metadata URL**, an uploaded **metadata XML** document, or **manually** (sign-in URL plus signing certificate). JumpCloud publishes metadata advertising only the HTTP-POST binding. Helios initiates sign-in over HTTP-Redirect and handles this automatically - no change is needed on your side. IdP-initiated sign-in works; users land on the Helios onboarding page. ## OIDC Supply your provider's **issuer URL**, **client ID**, and **client secret**. Register this callback URL with your provider: ``` https:///api/v1/auth/sso/callback/ ``` ## Just-in-time provisioning When SSO is configured and SCIM is not, users are provisioned on first sign-in: - If the user has a **pending invitation** to the organization, they join with the role from that invitation. - Otherwise they join as a **`viewer`** - read-only at the account layer. An admin promotes them from there. See [roles and permissions](/docs/basics/roles-permissions) for what each organization role means. An invited user whose organization has SSO configured must sign in through SSO before accepting the invitation. ## SCIM SCIM 2.0 lets your identity provider create and remove Helios users automatically. Enable it per organization, then generate a bearer token from your organization settings. | Field | Value | | --- | --- | | Base URL | `https:///api/v1/auth/scim/v2` | | Authentication | OAuth bearer token | The token is shown once. Generating a new token replaces the old one immediately. Helios advertises support for `PATCH` and filtering; bulk operations, sorting, and password change are not supported. ### What SCIM provisions **Users.** A user created through SCIM joins the organization with the `member` role. **Groups are not supported.** There is no `/Groups` endpoint, and there is no group-to-role mapping. Every SCIM-provisioned user receives the `member` role, and an admin must promote them from there. ### Deprovisioning **Setting `active: false` does not deactivate a Helios user.** Many identity providers deprovision by patching a user to inactive; Helios ignores that attribute. Only a SCIM `DELETE` on the user removes their access, ending their sessions and deleting the user. Configure your IdP to send `DELETE` on deprovisioning, and verify it does before relying on it. ### SCIM and SSO together When SCIM is enabled for an organization, **SCIM becomes the sole authority on membership**. Just-in-time provisioning is skipped and manual invitations are rejected. Add and remove people in your identity provider. ## What Helios does not do Being explicit, so you can plan around it: - **No domain verification.** Helios does not verify ownership of your email domain. - **No organization-wide SSO enforcement.** An existing member who also has a password or social login can still use it. SSO is enforced only when accepting an invitation. ## Related - **[Roles and permissions](/docs/basics/roles-permissions)** - organization roles and API keys. - **[Projects and sharing](/docs/basics/projects-and-sharing)** - granting access once people are in. - **[Audit logs](/docs/access/audit-logs)** - who changed what in your organization, and when. --- # Variables and secrets URL: https://www.heliosapp.com/docs/basics/variables-and-secrets Description: Variables are plaintext configuration passed to your agents. Secrets are envelope-encrypted values that never enter an agent's context. --- title: "Variables and secrets" excerpt: "Reusable configuration and envelope-encrypted secrets, scoped by level" description: "Variables are plaintext configuration passed to your agents. Secrets are envelope-encrypted values that never enter an agent's context." icon: Key createdAt: "2025-07-31" --- Helios stores two kinds of key-value data. They look similar and behave very differently. | | Variable | Secret | | --- | --- | --- | | Stored as | Plaintext | Envelope-encrypted | | Readable back | Yes | No - write-only | | Passed to agents | Yes, as run context | No | ## Variables A variable is non-sensitive configuration: an environment name, a channel to post to, a repository slug, a threshold. Every [workflow run](/docs/workflows/runs-and-outputs) receives the variables visible to its project as context the agent may use. They arrive as context, so you refer to them by name in the prompt and let the agent do the rest: ``` Post the digest to the Slack channel named in the DIGEST_CHANNEL variable. Skip the run entirely if ENVIRONMENT is not "production". ``` Variables are stored in plaintext, are readable by anyone who can read the resource they're scoped to, and are passed into the agent's context. Never put a credential in a variable. ## Secrets A secret is a sensitive value. Helios encrypts it with **envelope encryption**: a unique data key is generated per secret from AWS KMS, used to encrypt the value with AES-256-GCM, and then itself stored encrypted under a KMS master key. The plaintext data key is discarded immediately. Decryption requires a KMS call bound to that specific record. Secrets are write-only. Once saved, the API never returns the plaintext - not to the UI, and not to an agent. Secrets are not injected into agent prompts. Agents authenticate to your tools through [integrations](/docs/integrations), where Helios applies credentials server-side and injects short-lived tokens at the network layer - so the agent acts on your behalf without ever holding a credential. See [sandboxes](/docs/basics/sandboxes). The same envelope encryption protects your [integration credentials](/docs/integrations/auth), [database connection strings and SSH keys](/docs/integrations/databases), and [MCP server credentials](/docs/basics/mcp-servers). ## Scoping and precedence Variables and secrets are each set at one of four levels: 1. **Workflow** (most specific) 2. **User** 3. **Project** 4. **Organization** (most general) When the same key exists at several levels, **the most specific level wins**. Set `DIGEST_CHANNEL` at the organization level for a sane default, then override it on the one workflow that should post somewhere else. A key must be unique within a level, but the same key may appear at different levels - that is the point. ## Managing them Variables and secrets live under the project or organization they're scoped to. Creating and editing them requires the `editor` role on that resource. Listing them requires `viewer`. See [roles and permissions](/docs/basics/roles-permissions). Rotating a secret is a plain edit: save the new value, then revoke the old one at the provider. Runs already in flight continue with the value they started with. --- # Commands URL: https://www.heliosapp.com/docs/cli/commands Description: Reference for the helios command groups, global flags, and JSON output when piped. --- title: "Commands" excerpt: "Every command group with one example each" description: "Reference for the helios command groups, global flags, and JSON output when piped." icon: List createdAt: "2026-09-07" --- {/* HOLD:PR-624 HOLD:PR-619 */} {/* HOLD:PR-805 The webhook row and the Webhooks section ship with the helios-outbound-webhooks change. */} Every command follows the same shape. ```bash helios [arguments] [flags] ``` Run any group without a command to see its help. ```bash helios workflow --help ``` ## Output The CLI picks the output format from where it is going. In a terminal it prints tables. When you pipe it, it prints JSON. ```bash helios workflow list | jq '.[].id' ``` You can force a format. ```bash helios workflow list --json helios workflow list --output table ``` Pick only the fields you want. ```bash helios chat list --json --fields id,title ``` Errors are JSON too when the format is JSON. Every failure maps to an exit code and prints the server message. A 403 says there is no access, or the resource does not exist. ## Global flags These flags work on every command. | Flag | What it does | |---|---| | `-o, --output ` | `json`, `table`, or `text`. Default picks by terminal. | | `--json` | Short for `--output json`. | | `-q, --quiet` | Minimal output. | | `-v, --verbose` | Debug details on stderr. | | `--no-input` | Never prompt. Fail if input is needed. | | `--yes` | Confirm destructive commands without asking. | | `--project ` | Project scope for this one call. | | `--context ` | Use a named context. | | `--server ` | Point at a different Helios server. | | `--limit `, `--offset ` | Page through list results. | | `--fields ` | Comma-separated output fields. | | `--dry-run` | Preview changes without applying. | | `--no-color` | Disable ANSI colors. | Environment variables `HELIOS_API_KEY`, `HELIOS_SERVER`, and `HELIOS_PROJECT` set the same values without flags. ## Command groups | Group | Commands | Example | |---|---|---| | `auth` | `login`, `logout`, `list`, `status`, `whoami` | `helios auth whoami` | | `chat` | `new`, `send`, `list`, `use`, `get`, `fork`, `rename`, `delete`, `share`, `export` | `helios chat send "Summarize open PRs in acme/api"` | | `workflow` | `list`, `get`, `create`, `update`, `delete`, `trigger`, `runs`, `run-get`, `run-output`, `cancel` | `helios workflow trigger ` | | `project` | `list`, `use`, `get`, `create`, `update`, `delete` | `helios project use "engineering digests"` | | `integration` | `list`, `get`, `test`, `connect`, `finish`, `wait`, `authorize`, `authorization` | `helios integration connect github` | | `variable` | `list`, `get` | `helios variable get REGION` | | `secret` | `list`, `get`, `create`, `update`, `delete` | `helios secret create --name DB_URL --value ` | | `mcp-server` | `list`, `get`, `test` | `helios mcp-server test ` | | `network` | `list`, `get`, `set`, `delete` | `helios network get` | | `webhook` | `list`, `create`, `update`, `pause`, `resume`, `delete`, `secret show`, `secret rotate`, `test`, `deliveries`, `resend` | `helios webhook deliveries --status failed` | | `share`, `unshare` | Grant or revoke a role on any resource | `helios share workflow/ --with group:oncall --role operator` | | `access` | `list` | `helios access list workflow/` | | `shared` | `list` | `helios shared list` | | `group` | `list`, `get`, `create`, `rename`, `delete`, `member add`, `member remove` | `helios group member add oncall user:` | | `service-account` | `list`, `get`, `create`, `rename`, `disable`, `enable`, `delete`, `assign`, `unassign` | `helios service-account disable deploy-bot` | | `code` | `list`, `launch`, `get`, `attach`, `kill`, `logs`, `events`, `environments`, `images`, `apply`, `iac` | `helios code launch --attach` | | `context` | `create`, `use`, `list`, `current`, `set`, `delete`, `path` | `helios context current` | | `search` | Search across resources | `helios search "digest"` | | `skills` | `install`, `uninstall`, `list` | `helios skills install claude-code` | | `mcp` | `list`, `status`, `test` | `helios mcp status` | | `configure` | Guided setup | `helios configure --redo iac` | | `doctor` | Check system readiness | `helios doctor` | | `docs` | Show CLI documentation | `helios docs` | | `schema` | Dump the command tree as JSON | `helios schema --tree` | | `completion` | Shell completions | `helios completion zsh` | | `update` | Update the binary | `helios update --check` | | `version` | Version, commit, build date | `helios version` | ## Chat Start a chat in the terminal app, or send one message and read the answer. ```bash helios chat -p "List the failing runs from this week" ``` Continue the last chat with `-c`. Resume a specific one with `-r `. ```bash helios chat send "And who owns them?" --continue ``` ## Workflows Trigger a workflow and watch its runs. ```bash helios workflow trigger --input '{"repo":"acme/api"}' helios workflow runs --watch ``` Read the transcript of one run. ```bash helios workflow run-output ``` Create a workflow with a schedule trigger. ```bash helios workflow create --name "Weekly PR digest" --prompt "..." --trigger-cron "0 9 * * 1" ``` ## Integrations Connect an OAuth integration from the terminal. The command prints the id and an auth URL and returns at once. ```bash helios integration connect github ``` Open the URL in a browser. Then wait for the connection to finish. ```bash helios integration wait --timeout 600 ``` For a GitHub org install, each person authorizes their own user. ```bash helios integration authorize helios integration wait --until authorized ``` Filter the list by service or status. ```bash helios integration list --service github --status connected ``` Credential-based integrations such as Stripe and Resend are connected from the dashboard. See [authentication](/docs/integrations/auth). ## Webhooks Create a webhook target, then send it a test event to turn it on. ```bash helios webhook create --name "Run failures" --url https://hooks.example.com/helios --events workflow.run.failed helios webhook test ``` See [CLI webhooks](/docs/cli/webhooks) for every command and flag. ## Access See [projects and access](/docs/cli/projects-and-access) for `share`, `unshare`, `access`, `shared`, `group`, and `service-account`. ## Machine-readable schema Agents and scripts can read the full command tree, with every flag and argument, as JSON. ```bash helios schema --tree ``` Pass a command path to get one subtree. ```bash helios schema code launch ``` --- # Configure URL: https://www.heliosapp.com/docs/cli/configure Description: helios configure signs you in and picks a project. Progress is saved, so you can stop and come back. --- title: "Configure" excerpt: "From API key to a running agent in one guided flow" description: "helios configure signs you in and picks a project. Progress is saved, so you can stop and come back." icon: Settings createdAt: "2026-09-07" --- {/* HOLD:PR-624 */} `helios configure` is a guided setup that runs in your terminal. ```bash helios configure ``` It runs in three steps. The third step is optional. ## Paste your API key {/* HOLD:PR-624 The wizard links to /settings/api-keys in the dashboard. Confirm that key type exists before publishing. */} Create an API key in the dashboard under **Settings** and then **API keys**. Paste it into the wizard. The CLI verifies the key against the server and saves it. You can also sign in without the wizard. ```bash helios auth login --api-key ``` The key is stored in a named account. See `helios auth list`. ## Pick your project The wizard lists every project you can reach. Pick one with the arrow keys and press Enter. Every later command runs inside this project. You can change it at any time. ```bash helios project use ``` See [projects and access](/docs/cli/projects-and-access). ## Start using Helios The last screen confirms the setup. Press Enter to open the terminal app. ## Resume and redo Progress is saved to `~/.helios/onboarding.json`. If you quit, run `helios configure` again and it continues where you stopped. Once setup is complete, `helios configure` prints the status of each step. To run one step again, name it. ```bash helios configure --redo iac ``` ```bash helios configure --redo launch ``` ## Non-interactive use When there is no terminal, for example in CI, `helios configure` prints the onboarding status and exits. Sign in with `helios auth login --api-key` or set `HELIOS_API_KEY` instead. ## Where things are stored ```bash helios context path ``` This prints the config folder. Accounts, contexts, and the active project live there. --- # Helios CLI URL: https://www.heliosapp.com/docs/cli Description: One binary that runs the Helios terminal app, scripts every part of Helios with JSON output, and sets up cloud coding agents. --- title: "Helios CLI" excerpt: "Helios in your terminal" description: "One binary that runs the Helios terminal app, scripts every part of Helios with JSON output, and sets up cloud coding agents." icon: Terminal createdAt: "2026-09-07" --- {/* HOLD:PR-624 HOLD:PR-619 Every page in this folder describes the CLI from PRs 619 and 624. Do not publish until both merge. */} The `helios` command is one binary. It does three things. 1. **A terminal app.** Run `helios` and you get chat, workflows, projects, and access in a full-screen app. 2. **A scriptable CLI.** Every command has a plain form. When you pipe the output, it prints JSON. CI and other agents can drive it. 3. **A guided setup.** `helios configure` takes you from an API key to a running cloud coding agent. ## Start here ```bash helios configure ``` Then open the app. ```bash helios ``` Or run a single command and read JSON. ```bash helios workflow list --json ``` ## What you can do from the terminal | Area | Commands | |---|---| | Chat with an agent | `helios chat`, `helios chat send`, `helios chat list` | | Workflows and runs | `helios workflow trigger`, `helios workflow runs` | | Projects | `helios project use`, `helios project list` | | Sharing and access | `helios share`, `helios access list`, `helios group`, `helios service-account` | | Integrations | `helios integration connect`, `helios integration wait` | ## Pages - [Install](/docs/cli/install) - [Configure](/docs/cli/configure) - [Commands](/docs/cli/commands) - [Projects and access](/docs/cli/projects-and-access) The CLI and the dashboard use the same permissions model. Anything you can share in the app you can share from a shell. See [roles and permissions](/docs/basics/roles-permissions). --- # Install URL: https://www.heliosapp.com/docs/cli/install Description: Install the Helios CLI on macOS or Linux, check the install, and keep it up to date. --- title: "Install" excerpt: "Get the helios binary on your machine" description: "Install the Helios CLI on macOS or Linux, check the install, and keep it up to date." icon: Download createdAt: "2026-09-07" --- {/* HOLD:PR-624 */} The CLI ships as a single binary for macOS and Linux on x86_64 and arm64. There is nothing else to install. ## Install script {/* HOLD:PR-624 The install script in apps/helios-cli/scripts/install.sh names https://helios.dev/install.sh. Confirm the hosted URL before publishing. */} ```bash curl -fsSL https://helios.dev/install.sh | bash ``` The script does the following. 1. Detects your operating system and CPU. 2. Downloads the matching binary from `packages.heliosapp.com`. 3. Verifies the SHA-256 checksum. It stops if the checksum does not match. 4. Moves the binary to `/usr/local/bin/helios`. It asks for `sudo` only if that folder is not writable. To install a specific version, pass it to the script. ```bash curl -fsSL https://helios.dev/install.sh | bash -s v1.2.3 ``` To install somewhere else, set `HELIOS_INSTALL_DIR` first. ```bash HELIOS_INSTALL_DIR="$HOME/.local/bin" bash -c "$(curl -fsSL https://helios.dev/install.sh)" ``` ## Build from source The CLI is the `@pangea/helios-cli` package in the Helios repository. It builds with [Bun](https://bun.sh). ```bash cd apps/helios-cli bun install bun run build ``` The binary lands at `dist/helios`. ## Check the install ```bash helios version ``` This prints the version, commit, and build date. ```bash helios doctor ``` This checks that your machine is ready. Run it if something looks wrong later. ## Update ```bash helios update ``` To check for a new version without installing it, add `--check`. ```bash helios update --check ``` ## Shell completion Generate a completion script for your shell and source it from your profile. ```bash helios completion zsh ``` ## Next step Run [`helios configure`](/docs/cli/configure) to sign in and pick a project. --- # Projects and access URL: https://www.heliosapp.com/docs/cli/projects-and-access Description: Pick the active project with project use, HELIOS_PROJECT, or --project. Share resources, audit access, and manage groups and service accounts from the CLI. --- title: "Projects and access" excerpt: "Scope every command to a project and share from a shell" description: "Pick the active project with project use, HELIOS_PROJECT, or --project. Share resources, audit access, and manage groups and service accounts from the CLI." icon: Users createdAt: "2026-09-07" --- {/* HOLD:PR-619 */} Every command runs inside one project. The CLI shares the permissions model of the dashboard, so the same four roles and the same rules apply. Read [roles and permissions](/docs/basics/roles-permissions) for the model itself. ## The active project Set the active project by id or by name. ```bash helios project use "engineering digests" ``` The CLI picks the project in this order. The first match wins. 1. The `--project ` flag on the command. 2. The `HELIOS_PROJECT` environment variable. 3. The project saved by `helios project use`. ```bash HELIOS_PROJECT= helios workflow list ``` ```bash helios workflow list --project ``` After login the personal project is active. `project list` shows each project's role and visibility and marks the active one. ```bash helios project list ``` Check who you are, which project is active, and your role in it. ```bash helios auth whoami ``` Every list command respects the active project. `workflow get` also shows your effective role on that workflow. ## Share a resource Grant a role on any resource to a person, a group, a service account, or everyone in the org. ```bash helios share workflow/ --with group:oncall --role operator ``` Add an expiry date. ```bash helios share chat/ --with user: --role viewer --expires 2026-10-01 ``` Revoke a direct grant. ```bash helios unshare workflow/ --from group:oncall ``` **Resource types.** `project`, `workflow`, `chat`, `integration`, `mcp-server`, `db-connection`, `service-account`. **Principals.** `everyone`, `user:`, `group:`, `sa:`. **Roles.** `viewer`, `operator`, `editor`, `admin`. You cannot grant a role above your own. Chats can only be shared as viewer, expire in one day, and cannot be shared with everyone. Service accounts can be shared as viewer or admin only. Grants to a project's default service account are refused because they could not be revoked. ## Audit access See your effective role and every grant on a resource, direct or inherited. ```bash helios access list workflow/ ``` Pipe it for a scripted audit. ```bash helios access list project/ --json ``` See everything others have shared with you. ```bash helios shared list ``` ## Groups Groups need the org admin role. ```bash helios group create oncall --member user: --member sa:deploy-bot helios group list helios group get oncall helios group rename oncall on-call helios group member add on-call user: helios group member remove on-call sa:deploy-bot helios group delete on-call --yes ``` Deleting a group removes every grant it holds. ## Service accounts A service account is an identity a workflow can run as. Each project has a default account. You can also create named accounts. ```bash helios service-account create deploy-bot helios service-account list helios service-account get deploy-bot ``` `get` shows which workflows use the account and what it has access to. Make a workflow run as an account. The account needs an operator grant on the workflow first. ```bash helios share workflow/ --with sa:deploy-bot --role operator helios service-account assign deploy-bot ``` Revert the workflow to run as its owner. ```bash helios service-account unassign ``` Disable an account to stop every run that uses it. Enable it to resume. ```bash helios service-account disable deploy-bot helios service-account enable deploy-bot ``` Rename or delete a named account. Deleting removes its grants. ```bash helios service-account rename deploy-bot release-bot helios service-account delete release-bot --yes ``` ## Errors HTTP failures map to exit codes and print the server message. A 403 means you have no access, or the resource does not exist. The CLI does not tell these apart. --- # Webhooks URL: https://www.heliosapp.com/docs/cli/webhooks Description: Manage webhook targets with helios webhook. Create a target, verify it with a test event, rotate its secret, and read or resend its deliveries. --- title: "Webhooks" excerpt: "Create, test and debug webhook targets from a shell" description: "Manage webhook targets with helios webhook. Create a target, verify it with a test event, rotate its secret, and read or resend its deliveries." icon: Webhook createdAt: "2026-10-12" --- {/* HOLD:PR-805 Webhooks are not released yet. Publish this page when the helios-outbound-webhooks change ships. */} The `helios webhook` commands call the same API as **Settings > Webhooks**, with your API key. The same [permissions](/docs/webhooks/access) apply. A command you are not allowed to run prints the `403` error and exits with a non-zero code. | Command | What it does | |---|---| | `list` | List the targets you can see. | | `create` | Create a target. It stays unverified until a test gets a `2xx`. | | `update ` | Change the name, URL, events or payload version. | | `pause `, `resume ` | Stop and restart deliveries. | | `delete ` | Delete a target and its delivery history. | | `secret show `, `secret rotate ` | Reveal or replace the signing secret. | | `test ` | Send a test event and print the result. | | `deliveries ` | List deliveries with filters. | | `resend ` | Send one delivery again. | ## Create and verify a target Create a target in the active project, or in your personal scope when the active project is your personal project (the default right after `helios auth login`). Pass the event types as a comma-separated list. See [event types](/docs/webhooks/events) for every type. ```bash helios webhook create --name "Run failures" \ --url https://hooks.example.com/helios \ --events workflow.run.failed,workflow.run.cancelled ``` The output includes the signing secret. Save it now. You can reveal it again later with `secret show`. | Flag | What it does | |---|---| | `--name ` | Target name. Required. | | `--url ` | HTTPS URL on port 443. Required. | | `--events ` | Comma-separated event types. Required. | | `--scope ` | `project`, `org` or `personal`. Defaults to `project`, or `personal` when the active project is your personal project. | | `--project ` | Project for a project target. Defaults to the active project. | | `--payload-version ` | Payload version. Defaults to the latest. | | `--idempotency-key ` | Send the same key again to get the first target back instead of a second one. | The new target is `unverified`. Send a test event to turn it on. ```bash helios webhook test ``` The command prints the delivery ID, the HTTP status, the failure reason and the target status. It exits with a non-zero code when the test did not get a `2xx`. A target accepts 10 test events per hour. Create an organization target or a personal target with `--scope`. ```bash helios webhook create --scope personal --name "My chats" \ --url https://hooks.example.com/chats --events chat.turn.completed,chat.turn.failed ``` ## List and update targets ```bash helios webhook list helios webhook list --scope org helios webhook list --project ``` The table shows each target's status and reason, its events, its success rate over the last 24 hours and your role on it. ```bash helios webhook update --events workflow.run.failed,workflow.run.succeeded helios webhook update --payload-version 2026-10-01 ``` `--events` replaces the whole list. A new `--url` sets the target back to `unverified`, so run `test` again after it. ## Pause, resume and delete ```bash helios webhook pause helios webhook resume helios webhook delete --yes ``` `pause` and `delete` ask for confirmation unless you pass `--yes`. While a target is paused, its events are dropped and cannot be resent. Deliveries that were waiting for a retry end with `target_disabled`. You can resend those after you resume. See [target status](/docs/webhooks/delivery#target-status). Turn back on, Confirm URL and Resend all failed since are in **Settings > Webhooks**. ## Signing secret ```bash helios webhook secret show helios webhook secret rotate ``` `secret show` asks for confirmation. Pass `--yes` to skip it in a script. With `--no-input` and no `--yes`, it stops without showing the secret. Every reveal is logged with your user ID. After `secret rotate`, the previous secret stays valid for 24 hours. See [check the signature](/docs/webhooks#check-the-signature). ## Deliveries List a target's deliveries from the last 24 hours. ```bash helios webhook deliveries ``` Narrow the list. ```bash helios webhook deliveries --status failed helios webhook deliveries --event-type workflow.run.failed --since 2026-10-01T00:00:00Z helios webhook deliveries --resource-id ``` | Flag | What it does | |---|---| | `--status ` | `pending`, `sending`, `succeeded` or `failed`. | | `--event-type ` | One event type. | | `--since