# Helios
> Helios is an always-on AI agent platform. Describe a job in plain English and Helios agents run it on schedules, webhooks, or integration events - each with a full cloud computer and the complete APIs of your tools: Slack, GitHub, Notion, Stripe, and more.
---
# Helios - Agents That Show Up to Work
URL: https://www.heliosapp.com/
Description: Always-on AI agents for your company's work. Each agent gets a full cloud computer, the complete APIs of every tool you use, and memory that carries between runs - with SSO, roles, and audit for your team.
# Agents with Integrationsthat do work.
Helios agents run around the clock - on schedules, on events, on demand. Each one gets a full cloud computer, the complete APIs of your tools, and memory that carries between runs.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
* SOC 2 Type II
* SSO, roles & audit
⏰every Monday 9:00am
Every Monday morning, read last week's support conversations, group them into themes, and post a digest to #support-leads with the three issues worth fixing.
1. plain·list threads · last 7 days
2. postgres·join accounts on customer\_id
3. code·run cluster-themes.ts
4. slack·post digest to #support-leads
✓Weekly support digest posted
* 142 conversations · 6 recurring themes
* Top theme: invoice confusion (31 threads, 4 enterprise accounts)
* Draft fix proposals attached as digest.md
Reach
## Agents that reach everything you work in.
One task can move between your CRM, your warehouse, and a tool you wired up yourself - inside a single run.
### The full API of every tool
Agents search the entire OpenAPI spec of a connected service at run time and call whichever endpoint the task needs. Credentials stay server-side.
[Browse integrations →](/integrations/)
### Your databases, directly
Connect Postgres, MySQL, or ClickHouse - through an SSH tunnel when you need one - and let an agent query the numbers itself, the moment the task calls for them.
[Connect a database →](/integrations/databases/)
### Anything with an MCP server
Attach an MCP server and its tools join your agents' toolbox. Helios speaks MCP outward too, so your own clients can drive Helios agents.
[Explore MCP →](/product/mcp/)
⏰daily 7:00am
Reconcile yesterday's failed payments: pull them from Stripe, check what each customer owes in our warehouse, and open a thread in #billing for anyone above $1,000.
1. stripe·list charges · status=failed
2. clickhouse·query outstanding\_balance by account
3. mcp · internal-billing·check dunning eligibility
4. slack·open thread in #billing
✓9 failed payments reconciled
* 3 accounts above $1,000 - thread opened with owner tagged
* 6 retried automatically, no action needed
Memory
## Every run makes the next one sharper.
Context, files, and learnings carry across runs, so an agent picks up exactly where it left off - and gets better at the task the longer it holds it.
What it learned
Corrections, preferences, and the shape of your data stick. Tell an agent once that enterprise accounts route to the on-call lead, and every future run knows it.
The files it made
Each agent keeps a persistent workspace. Yesterday's export, script, and report are still there tomorrow, ready to build on.
The context you pinned
Pin a GitHub repository as a scoped resource and the agent treats it as standing context on every run.
⏰every Friday 4:00pm
Run the churn-risk review again for this week.
1. memory·recall scoring rules from 12 prior runs
2. workspace·read churn-model.ts
3. postgres·query usage · trailing 30 days
4. attio·update 4 records · risk tier
✓Churn watchlist refreshed
* Reused last week's thresholds - no re-briefing needed
* 2 accounts escalated, 1 recovered since last run
Controls
## Everyone can delegate. IT stays in control.
Hand work to agents across the company while identity, access, and audit stay where your security review expects them.
### SSO
SAML and OIDC single sign-on with your existing identity provider.
### SCIM provisioning
Accounts and group membership sync from your directory, joiners through leavers.
### Roles
Admin, member, and viewer roles at the organization level, with resource-level access on top.
### Sandbox isolation
Every agent run executes in its own cloud sandbox, isolated from your infrastructure and from other runs.
### Encrypted secrets
AES-256-GCM envelope encryption, each secret under its own key wrapped by AWS KMS. Scoped credentials attach at the egress layer, so the model never handles a raw key.
### Signed webhooks
Inbound webhook triggers are signature-verified, and secrets rotate on demand.
### SOC 2 Type II
Independently audited controls covering security, availability, and confidentiality.
### Usage limits
Usage-based credits with organization limits, so a runaway task stays a small one.
### Run history
Every run keeps its trigger, tool calls, and output as a durable audit trail.
[Read how Helios handles security →](/security/)
Integrations
## Connect a tool once. Your agents get all of it.
Helios searches each service's OpenAPI spec at run time, so an agent can call whichever endpoint the task calls for - with your credentials attached server-side.
[GitHubDeveloper tools](/integrations/github/)[SlackCommunication](/integrations/slack/)[GmailGoogle Workspace](/integrations/gmail/)[Google SheetsGoogle Workspace](/integrations/google-sheets/)[Google DocsGoogle Workspace](/integrations/google-docs/)[Google DriveGoogle Workspace](/integrations/google-drive/)[NotionDocs & knowledge](/integrations/notion/)[AttioSales & CRM](/integrations/attio/)[ApolloSales & CRM](/integrations/apollo/)[StripeBilling](/integrations/stripe/)[ResendEmail](/integrations/resend/)[PlainSupport](/integrations/plain/)[DiscordCommunity](/integrations/discord/)[RedditCommunity](/integrations/reddit/)[TypeformForms](/integrations/typeform/)[ApifyWeb data](/integrations/apify/)[WarpBuildDeveloper tools](/integrations/warpbuild/)[DatabasesData](/integrations/databases/)
[All integrations →](/integrations/)
How it works
## Hand off the task once.
An agent takes a plain-English brief and does the work - in chat, on a trigger, or straight from Slack.
1. 01
### Describe the task
Write what you want done in plain English, the way you would brief a new teammate. Name the tools it should use and the shape of the output you want back.
2. 02
### The agent gets a computer and your tools
Helios starts an isolated cloud sandbox with code execution, a file system, and web access, then hands the agent the complete APIs of every tool your team has connected.
3. 03
### Run it now, or forever
Ask in chat when you need something now, or put the same agent on a schedule, a signed webhook, or an event from GitHub, Slack, or Plain. It answers wherever you call it - the app, Slack, or your own MCP client.
## Frequently asked questions
### What is Helios?
### What can agents actually do?
### How do triggers work?
### What does it cost?
### Is Helios secure?
### How is Helios different from workflow tools?
## Put an agent on the task today.
Start free, describe the first task in plain English, and watch it run. Bring your team when you are ready - SSO, roles, and audit are waiting.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# About Helios - The Team Behind Your Agents | Helios
URL: https://www.heliosapp.com/about
Description: Helios is built by the WarpBuild team and backed by Y Combinator. We build always-on AI agents that do real work for companies.
Company
## About Helios
We build always-on agents that do real work.
Helios gives a company a workforce of AI agents. You describe a task in plain English and hand it off. The agent gets a full cloud computer, the complete APIs of the tools you already use, your databases, and memory that carries from one run to the next. It shows up on a schedule, on an event, or whenever you ask.
The work that keeps a company running is recurring and unglamorous: triaging support, chasing leads, reading pull requests, pulling the same report every Monday morning. It deserves a worker, not a weekly reminder. Helios puts one on the task permanently, and your team keeps the controls - SSO, roles, and a record of every run.
We are the team behind WarpBuild, where we spent years building CI infrastructure that thousands of engineers run their builds on. We learned what people trust automation with, and what they will not. Helios is the same instinct applied to the rest of the work: real infrastructure, honest controls, and a product that does what it says.
We are a team of engineers who have built together for years, with a shared taste for developer tools, infrastructure, and making something people want. We are backed by Y Combinator and by investors who support builders working on big, ambitious ideas.
Backed by
## Put an agent on the task
Start free with 5,000 credits, or walk through a real task with us.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Enterprise - Every Team Delegates, IT Stays in Control | Helios
URL: https://www.heliosapp.com/enterprise
Description: Roll out AI agents across your company with SAML and OIDC SSO, SCIM provisioning, role-based access, resource-level sharing, and usage controls.
Enterprise
# Every team delegates. IT stays in control.
Anyone in your company can describe a task in plain English and hand it to an agent. Your administrators decide who signs in, what each agent can reach, and what the whole thing is allowed to spend.
[Book a demo](https://cal.com/suryao/helios)[Get started free](https://app.heliosapp.com/)
For teams
## Hand off the work that repeats
Describe the task the way you would explain it to a new hire. The agent gets a cloud computer, the full APIs of the tools your team already uses, and memory of every run before this one.
⏰Mondays at 8:00 AM
Every Monday morning, pull last week's closed-won deals from Attio, match them against Stripe invoices, and post a revenue recap in #sales with anything that looks unbilled.
1. attio·list closed-won deals
2. stripe·match invoices by company
3. code·reconcile and format recap
4. slack·post to #sales
✓Weekly revenue recap posted
* 14 deals closed · $86,400 booked
* 2 deals closed-won with no invoice - flagged
The people closest to the work know it best. On Helios they write the task down once, choose when it should run, and get their week back. No engineer has to translate it into anything.
Tasks by team
[Support](/solutions/support/)[Sales & RevOps](/solutions/sales-and-revops/)[Marketing](/solutions/marketing/)[Engineering](/solutions/engineering/)[Operations](/solutions/operations/)
For IT
## Set it up once, from your own admin settings
Identity, roles, and reach are configured where you would expect them. Nobody has to file a ticket with us to get single sign-on turned on.
### Single sign-on
Connect your identity provider over SAML 2.0 or OIDC, and set it up yourself from your own admin settings. People sign in with the credentials they already have.
### Just-in-time provisioning
The first time somebody signs in through your provider, their Helios account is created for them, in the right organization, with the role you chose.
### SCIM provisioning
Keep Helios in step with your directory. Users are created, updated, and deactivated from the same place you already manage everyone else.
### Organization roles
Admins run the organization. Members build and run agents. Viewers can look without touching. The role someone holds is the role they hold everywhere.
### Resource-level access
Every agent, project, and integration carries its own roles - admin, editor, and user - so the person who owns a task decides who else can edit it and who can only run it.
### Visibility you choose
Keep a resource restricted to the people it was shared with, or open it to the whole organization. The default is the safer one.
### Scoped credentials
Integration credentials are held server-side. Agents call the APIs through Helios, so the tokens for your Slack workspace and your production database never end up in a prompt.
### API keys
Drive Helios from your own systems with scoped API keys, and revoke one the moment it should stop working.
Governance
## Spend you can predict
Agents that run around the clock need a budget with edges. Helios gives your administrators the controls before the invoice does.
### Usage-based credits
Agents draw credits as they work - model tokens, tool calls, sandbox time. Spend tracks the work that got done, so a team that runs one task a week pays for one task a week. There are no seats to count.
### Spending limits
Set the ceiling your organization can spend in a period. Finance gets a number they chose rather than a number they discovered.
### Auto-refill, with a brake
Balances top themselves back up so long-running tasks keep going. After three failed refills, Helios stops trying and tells you - a card problem stays a card problem instead of becoming a runaway bill.
### Run history
Every run keeps its trigger, its steps, its outputs, and what it cost. When someone asks what an agent did last Tuesday, the answer is a link.
Deployment & scale
## Infrastructure that stays out of your way
### Runs in the Helios cloud
There is nothing to install and nothing to keep patched. Agents spin up when a trigger fires and shut down when the task is finished.
### One sandbox per run
Each run gets its own cloud computer, with its own filesystem and its own network egress. Work from one run never sits in the machine another run inherits.
### A frontier model, tuned
Agents run on Claude Sonnet, tuned for long-running tool use. Every team gets the same judgment on every task, from the one-off question to the workflow that runs a thousand times a day.
### Scale is a scheduling problem
Add agents and triggers as fast as your teams find work to hand off. Credits meter what runs, so growth shows up as usage on the plan you already have.
Security
## Your security team gets the whole picture
How agents are isolated, where credentials live, how secrets are encrypted, and what an agent is allowed to reach - written down in detail, so a review can start before a call does.
[Read the security overview](/security/)
* SOC 2 Type II
* Isolated sandbox per run
* Envelope-encrypted secrets
* Server-side credentials
* Signed webhooks
* GDPR
## Questions your team will ask
### How does a rollout usually go?
### Which identity providers work with Helios?
### How do people get accounts, and how do they lose them?
### How do we control what an agent is allowed to reach?
### Can we see what our agents have been doing?
### How does billing work for a company?
### Is our data used to train models?
## Bring us the task nobody wants
Walk us through the work your team keeps redoing. We will put an agent on it with you and show you the controls on the way.
[Book a demo](https://cal.com/suryao/helios)[Get started free](https://app.heliosapp.com/)
---
# Guides - Get Your First Agent Working | Helios
URL: https://www.heliosapp.com/guides
Description: Step-by-step guides: run your first agent, put it on a schedule, react to GitHub events, connect a database, attach MCP servers, and share with your team.
Guides
# Get your first agent working.
The basics track, in the order you meet them: run an agent, put it on a trigger, give it reach, give it context, and hand it to your team.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
1. [01Run your first agentDescribe a task in plain English, give the agent a tool to reach for, and watch it work. Ten minutes from an empty workspace to a run you can read end to end.10 min](/guides/run-your-first-agent/)
2. [02Put an agent on a scheduleTurn a working prompt into a standing task. Describe the cadence the way you would say it out loud, and Helios writes the cron expression for you.8 min](/guides/put-an-agent-on-a-schedule/)
3. [03React to GitHub eventsStart an agent the moment a pull request opens, a build goes red, or a tag lands - filtered down to exactly the events you want it on.12 min](/guides/react-to-github-events/)
4. [04Connect a databaseGive an agent Postgres, MySQL, or ClickHouse. It introspects the schema, writes real SQL, and reasons over the results in its own sandbox.10 min](/guides/connect-a-database/)
5. [05Attach an MCP serverBring your own tools. Point Helios at any MCP server, choose which of its tools agents may call, and they become part of the agent's reach.10 min](/guides/attach-an-mcp-server/)
6. [06Pin repositories as contextGive an agent standing context: pin a GitHub repository and the agent carries it into every run without being told again.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, and both are scoped to the level where they belong.8 min](/guides/use-secrets-and-variables/)
8. [08Share with your teamHand an agent to the people who need it. Roles decide who may edit, visibility decides who may see, and every run leaves a record of what happened.9 min](/guides/share-with-your-team/)
## Start with the first guide.
Ten minutes from an empty workspace to an agent run you can read end to end.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Attach an MCP server - Guide | Helios
URL: https://www.heliosapp.com/guides/attach-an-mcp-server
Description: Bring your own tools. Point Helios at any MCP server, choose which of its tools agents may call, and they become part of the agent's reach.
[← All guides](/guides/)
10 min read
# Attach an MCP server
Bring your own tools. Point Helios at any MCP server, choose which of its tools agents may call, and they become part of the agent's reach.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
1. 01
### Add the server URL
From Settings → MCP Servers, add a server by its streamable HTTP endpoint. Helios validates the URL against its SSRF protections before it connects, so an attached server cannot be pointed at your internal network.
2. 02
### Choose how it authenticates
Servers connect with no auth, a bearer token, custom headers, or an OAuth flow. Tokens and headers are stored envelope-encrypted and attached server-side at call time, the same way integration credentials are.
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 are handing your agents.
4. 04
### Filter down to the tools you want
A tool filter narrows the server to a named subset. A server that exposes forty tools can contribute the three that matter to a task, which keeps the agent focused and the blast radius small.
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 manually. The run record shows each MCP tool call the agent made alongside its integration calls, so a mixed run reads as one story.
6. 06
### Point another agent at Helios
MCP runs both directions. Helios exposes its own API over MCP, so an agent living somewhere else searches the Helios API surface for the endpoint it needs and calls it - listing projects, creating a workflow, reading its runs. The same credentials and the same roles apply from that side.
Keep going
## Next in the track
[10 minRun your first agentDescribe a task in plain English, give the agent a tool to reach for, and watch it work. Ten minutes from an empty workspace to a run 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, and both are scoped to the level where they belong.](/guides/use-secrets-and-variables/)[7 minPin repositories as contextGive an agent standing context: pin a GitHub repository and the agent carries it into every run without being told again.](/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, leaves inline comments, and posts a weekly digest of review load and CI health.◆github · pull\_request.opened](/templates/pr-review-digest/)[EngineeringIncident postmortem drafterReconstructs the incident timeline from Slack and GitHub, names the triggering change, and drafts the write-up in Notion.▶Run on demand](/templates/incident-postmortem-drafter/)[OperationsNightly data quality checksRuns your invariants against production every night and tells the on-call analyst which rows broke and since when.⏰Nightly at 3:00am](/templates/database-health-check/)
## Try it in your workspace.
Start free, connect a tool, and describe the first task in plain English.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Connect a database - Guide | Helios
URL: https://www.heliosapp.com/guides/connect-a-database
Description: Give an agent Postgres, MySQL, or ClickHouse. It introspects the schema, writes real SQL, and reasons over the results in its own sandbox.
[← All guides](/guides/)
10 min read
# Connect a database
Give an agent Postgres, MySQL, or ClickHouse. It introspects the schema, writes real SQL, and reasons over the results in its own sandbox.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
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. A reporting agent with a read-only credential has no path to a write, because the permission is enforced by your database - which is exactly where that decision belongs.
2. 02
### Add the connection
From Settings → Integrations, add a Postgres, MySQL, or ClickHouse connection with a host, port, database, and credentials. Everything is stored envelope-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, configure an SSH tunnel on the connection. Agents connect through the bastion you specify, so nothing has to be exposed to the public internet to make this work.
4. 04
### Ask a question in plain English
Run a manual agent that asks something you already know the answer to. It introspects tables, columns, types, and keys, writes the SQL, runs it, and explains the result. Comparing its answer against the one you knew is the fastest way to see whether it understood your schema.
5. 05
### Read the SQL it wrote
Every run records the queries the agent ran and the rows they returned, so a report always traces back to the exact SQL. When a number looks wrong, the query that produced it is one click away.
6. 06
### Schedule the task
Attach a cron trigger and the report shows up before standup, every morning. Memory carries what the agent learned about your schema across runs, so the fifth report starts smarter than the first.
Keep going
## Next in the track
[7 minPin repositories as contextGive an agent standing context: pin a GitHub repository and the agent carries it into every run without being told again.](/guides/pin-context-resources/)[8 minPut an agent on a scheduleTurn a working prompt into a standing task. Describe the cadence the way you would say it out loud, and Helios writes the cron expression for you.](/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, and both are scoped to the level where they belong.](/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 anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)[OperationsNightly data quality checksRuns your invariants against production every night and tells the on-call analyst which rows broke and since when.⏰Nightly at 3:00am](/templates/database-health-check/)[OperationsKPI sheet refreshPulls from the warehouse every morning and writes the finished tables into the sheet leadership already opens.⏰Daily at 6:00am](/templates/google-sheets-kpi-sync/)
## Try it in your workspace.
Start free, connect a tool, and describe the first task in plain English.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Pin repositories as context - Guide | Helios
URL: https://www.heliosapp.com/guides/pin-context-resources
Description: Give an agent standing context: pin a GitHub repository and the agent carries it into every run without being told again.
[← All guides](/guides/)
7 min read
# Pin repositories as context
Give an agent standing context: pin a GitHub repository and the agent carries it into every run without being told again.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
1. 01
### Find the repository the agent keeps looking up
Read a few runs and notice which codebase the agent reaches for every single time - the service it reviews, the repo whose conventions it checks. That is the repository worth pinning.
2. 02
### Pin it as an integration resource
An integration resource scopes a connection down to one specific thing: one repository rather than the whole GitHub org. The pin carries the integration it belongs to, so credentials come along and stay server-side.
3. 03
### Attach it to the workflow or chat
Pinned repositories become standing context for the agent. It knows the codebase exists before you mention it, and it starts from the repo instead of searching for it again on every run.
4. 04
### Use pinning to narrow reach
Pinning is a scoping decision as much as a convenience one. An agent pinned to one repository has a smaller surface than an agent roaming the whole org, and its prompts get shorter as a result.
5. 05
### Let memory build on top of it
Pinned repositories give the agent the same starting context every run. Memory carries what it learned across runs - escalation rules, schema shapes, naming conventions. Together they mean the fifth run knows more than the first without you rewriting the prompt.
Keep going
## Next in the track
[10 minRun your first agentDescribe a task in plain English, give the agent a tool to reach for, and watch it work. Ten minutes from an empty workspace to a run you can read end to end.](/guides/run-your-first-agent/)[12 minReact to GitHub eventsStart an agent the moment a pull request opens, a build goes red, or a tag lands - filtered down to exactly the events you want it on.](/guides/react-to-github-events/)[9 minShare with your teamHand an agent to the people who need it. Roles decide who may edit, visibility decides who may see, and every run leaves a record 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, leaves inline comments, and posts a weekly digest of review load and CI health.◆github · pull\_request.opened](/templates/pr-review-digest/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.◆github · tag.created](/templates/github-release-notes/)[EngineeringIncident postmortem drafterReconstructs the incident timeline from Slack and GitHub, names the triggering change, and drafts the write-up in Notion.▶Run on demand](/templates/incident-postmortem-drafter/)
## Try it in your workspace.
Start free, connect a tool, and describe the first task in plain English.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Put an agent on a schedule - Guide | 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, and Helios writes the cron expression for you.
[← All guides](/guides/)
8 min read
# Put an agent on a schedule
Turn a working prompt into a standing task. Describe the cadence the way you would say it out loud, and Helios writes the cron expression for you.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
1. 01
### Start from a prompt that already works
Run the agent manually until the output is what you want. A schedule multiplies whatever the prompt does, so a task that is 80% right becomes 80% right every morning at 7am.
2. 02
### Add a cron trigger
Open the workflow's triggers and add a schedule. Describe the cadence in plain English - \`every weekday at 7am\`, \`the first of every month\`, \`every four hours\` - and Helios turns it into a cron expression you can inspect and edit directly.
3. 03
### Set the timezone before you save
Schedules run against the timezone you choose, which matters most for tasks that mean something to a person: a standup digest at 9am is useless if it lands at 9am UTC for a team in California.
4. 04
### Make the task idempotent
Tell the agent what window it covers - \`since your last run\`, \`the last 24 hours\` - and what to skip. Runs that overlap or retry should not send the same email twice, and the prompt is where you say so.
5. 05
### Let memory carry the thread
Agent memory persists between runs, so a weekly digest can call out what changed since the last one rather than restating the same context every Friday. Say what you want it to remember and it carries that forward.
6. 06
### Watch the first few scheduled runs
Check the run history after the first two or three fires. Look at what the agent actually did on a quiet day and on a busy one - the interesting failures live at the edges, not in the average case.
Keep going
## Next in the track
[10 minRun your first agentDescribe a task in plain English, give the agent a tool to reach for, and watch it work. Ten minutes from an empty workspace to a run you can read end to end.](/guides/run-your-first-agent/)[12 minReact to GitHub eventsStart an agent the moment a pull request opens, a build goes red, or a tag lands - filtered down to exactly the events you want it on.](/guides/react-to-github-events/)[10 minConnect a databaseGive an agent Postgres, MySQL, or ClickHouse. It introspects the schema, writes real SQL, and reasons over 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 so nobody has to attend one.⏰Weekdays at 9:00am](/templates/daily-standup-digest/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing firmographics, and flags deals that have gone quiet - every night, without anyone remembering.⏰Nightly at 2:00am](/templates/attio-crm-hygiene/)
## Try it in your workspace.
Start free, connect a tool, and describe the first task in plain English.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# React to GitHub events - Guide | Helios
URL: https://www.heliosapp.com/guides/react-to-github-events
Description: Start an agent the moment a pull request opens, a build goes red, or a tag lands - filtered down to exactly the events you want it on.
[← All guides](/guides/)
12 min read
# React to GitHub events
Start an agent the moment a pull request opens, a build goes red, or a tag lands - filtered down to exactly the events you want it on.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
1. 01
### Connect GitHub and choose the repositories
Authorize GitHub from Settings → Integrations and select which repositories the connection covers. That selection is the ceiling on everything an agent can reach, so start with one repository while you build confidence.
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\`. Choose the event where the work actually begins.
3. 03
### Filter the trigger down
Field filters keep the agent off the pull requests you did not mean. Filter by base branch so it ignores work on long-lived feature branches, or by label so a PR opts in one at a time - \`agent-review\` on the pull requests you want, and nothing else fires.
4. 04
### Write the prompt against the event payload
The agent 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 rather than an approving review, and gate it behind a label. Add the label to a handful of your own pull requests, read what it wrote, then widen the filter once the reviews are worth reading.
6. 06
### Decide who can change it
A workflow that comments on pull requests is a workflow your team will read closely. Org roles decide who may edit it - admins and editors change the prompt, users run it - and resource visibility keeps it scoped to the team that owns it.
Keep going
## Next in the track
[10 minRun your first agentDescribe a task in plain English, give the agent a tool to reach for, and watch it work. Ten minutes from an empty workspace to a run you can read end to end.](/guides/run-your-first-agent/)[8 minPut an agent on a scheduleTurn a working prompt into a standing task. Describe the cadence the way you would say it out loud, and Helios writes the cron expression for you.](/guides/put-an-agent-on-a-schedule/)[9 minShare with your teamHand an agent to the people who need it. Roles decide who may edit, visibility decides who may see, and every run leaves a record 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, leaves inline comments, and posts a weekly digest of review load and CI health.◆github · pull\_request.opened](/templates/pr-review-digest/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.◆github · tag.created](/templates/github-release-notes/)[EngineeringIncident postmortem drafterReconstructs the incident timeline from Slack and GitHub, names the triggering change, and drafts the write-up in Notion.▶Run on demand](/templates/incident-postmortem-drafter/)
## Try it in your workspace.
Start free, connect a tool, and describe the first task in plain English.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Run your first agent - Guide | Helios
URL: https://www.heliosapp.com/guides/run-your-first-agent
Description: Describe a task in plain English, give the agent a tool to reach for, and watch it work. Ten minutes from an empty workspace to a run you can read end to end.
[← All guides](/guides/)
10 min read
# Run your first agent
Describe a task in plain English, give the agent a tool to reach for, and watch it work. Ten minutes from an empty workspace to a run you can read end to end.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
1. 01
### Connect one integration
Open Settings → Integrations and authorize a single service - Slack and GitHub are the easiest first connections. Helios stores the credential envelope-encrypted and attaches it server-side, so it never appears in a prompt or in the agent's sandbox.
2. 02
### Create a workflow
A workflow is an agent with a standing task. Give it a name that says what it does - \`Daily standup digest\` beats \`Workflow 1\` when you have twenty of them and a run fails at 3am.
3. 03
### Write the prompt in plain English
Say what the agent should do, which sources it should read, and what a good result looks like. Be specific about the boundaries: what to skip, when to escalate, and what to do when it is unsure. The prompt is the whole configuration - there is nothing else to wire up.
4. 04
### Give it the context it needs
Every agent runs on Claude Sonnet, tuned for long-running tool use - so the configuration that matters is context. If the task works in a codebase, pin the GitHub repository; if it needs a threshold or an API key, store it as a variable or secret.
5. 05
### Run it manually and read the run
Trigger the run yourself the first time. The run record shows every tool call the agent made, the arguments it passed, and what came back. This is where you learn whether your prompt said what you meant, so read it before you automate anything.
6. 06
### Refine the prompt, then add a trigger
Adjust the sentence that produced the wrong behavior and run it again. Once two or three manual runs look right, attach a trigger and the agent starts picking up the task on its own.
Keep going
## Next in the track
[8 minPut an agent on a scheduleTurn a working prompt into a standing task. Describe the cadence the way you would say it out loud, and Helios writes the cron expression for you.](/guides/put-an-agent-on-a-schedule/)[7 minPin repositories as contextGive an agent standing context: pin a GitHub repository and the agent carries it into every run without being told again.](/guides/pin-context-resources/)[9 minShare with your teamHand an agent to the people who need it. Roles decide who may edit, visibility decides who may see, and every run leaves a record 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 so nobody has to attend one.⏰Weekdays at 9:00am](/templates/daily-standup-digest/)[SupportMorning inbox triageReads what arrived overnight, labels it, drafts the easy replies, and hands you a ranked list of what needs a human.⏰Weekdays at 7:30am](/templates/gmail-inbox-triage/)[SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.◆slack · new message in #supportP](/templates/slack-support-triage/)
## Try it in your workspace.
Start free, connect a tool, and describe the first task in plain English.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Share with your team - Guide | Helios
URL: https://www.heliosapp.com/guides/share-with-your-team
Description: Hand an agent to the people who need it. Roles decide who may edit, visibility decides who may see, and every run leaves a record of what happened.
[← All guides](/guides/)
9 min read
# Share with your team
Hand an agent to the people who need it. Roles decide who may edit, visibility decides who may see, and every run leaves a record of what happened.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
1. 01
### Understand the three roles
An admin manages the organization, its members, and its connections. An editor changes a workflow's prompt, model, and triggers. A user runs a workflow and reads its results. Most teams end up with a handful of editors and everyone else as a user.
2. 02
### Set visibility on the workflow
A restricted workflow is visible only to the people you grant access. An organization workflow is visible to everyone in the org. Start restricted while a task is still finding its shape, then open it up once the output is worth reading.
3. 03
### Bring your identity provider
SAML and OIDC single sign-on put access under the same control as the rest of your stack, and SCIM provisioning means a person who leaves the directory loses their agents with them. Admins configure both from the organization settings.
4. 04
### Let people run what they cannot edit
The two-sided arrangement is the point: give the whole team the user role so anyone can hand a task to an agent, and keep the prompt, the credentials, and the triggers with the people responsible for them.
5. 05
### Point everyone at the run history
Every run records the tool calls the agent made, the arguments, and the results. When someone asks why an agent wrote that field or sent that message, the answer is a link rather than a conversation.
6. 06
### Share a chat, and let people fork it
A chat can be shared by link, up to whichever message you choose, so the half you were still thinking out loud in stays yours. Anyone can fork the shared chat to keep going from that point with their own copy of the conversation and its files, and the original is untouched.
Keep going
## Next in the track
[10 minRun your first agentDescribe a task in plain English, give the agent a tool to reach for, and watch it work. Ten minutes from an empty workspace to a run 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, and both are scoped to the level where they belong.](/guides/use-secrets-and-variables/)[12 minReact to GitHub eventsStart an agent the moment a pull request opens, a build goes red, or a tag lands - filtered down to exactly the events you want it on.](/guides/react-to-github-events/)
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 so nobody has to attend one.⏰Weekdays at 9:00am](/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 · new message in #supportP](/templates/slack-support-triage/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)
## Try it in your workspace.
Start free, connect a tool, and describe the first task in plain English.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Use secrets and variables - Guide | 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, and both are scoped to the level where they belong.
[← All guides](/guides/)
8 min read
# Use secrets and variables
Keep the values a task needs out of the prompt. Variables hold configuration, secrets hold credentials, and both are scoped to the level where they belong.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
1. 01
### Know which one you need
A variable holds a value you would be happy to read in a run record: a channel name, a threshold, a sending address. A secret holds anything you would not: an API token, a signing key, a password. Secrets are envelope-encrypted at rest and stay masked everywhere they are displayed.
2. 02
### Store it at the right level
Values live at the organization, project, workflow, or user level. Put the sending domain at the organization level so every agent shares it, and put the one-off token at the workflow level so it stops where that task stops. The narrowest level that works is the right one.
3. 03
### Reference it from the prompt
Name the variable in the prompt and the agent resolves it at run time. A secret is injected into the sandbox when it is needed and never lands in the prompt text, so the value stays out of the run record that everyone on the team can read.
4. 04
### Rotate without touching a prompt
Because the value lives beside the workflow instead of inside it, 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
### Keep credentials in integrations where you can
Reach for a secret when a task needs a value Helios does not already hold. Connected integrations already attach their credentials server-side, so the API token for Slack or Stripe belongs in the integration rather than a secret you manage by hand.
Keep going
## Next in the track
[10 minConnect a databaseGive an agent Postgres, MySQL, or ClickHouse. It introspects the schema, writes real SQL, and reasons over the results in its own sandbox.](/guides/connect-a-database/)[10 minAttach an MCP serverBring your own tools. Point Helios at any MCP server, choose which of its tools agents may call, and they become part of the agent's reach.](/guides/attach-an-mcp-server/)[9 minShare with your teamHand an agent to the people who need it. Roles decide who may edit, visibility decides who may see, and every run leaves a record 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](/templates/stripe-failed-payment-recovery/)[Sales & RevOpsOnboarding email that reads the accountChecks what each new account has actually set up and sends the message that helps them next, rather than the next message in a sequence.⏰Daily at 9:00am](/templates/resend-onboarding-sequence/)[OperationsNightly data quality checksRuns your invariants against production every night and tells the on-call analyst which rows broke and since when.⏰Nightly at 3:00am](/templates/database-health-check/)
## Try it in your workspace.
Start free, connect a tool, and describe the first task in plain English.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Integrations - Full API Access for Your Agents | Helios
URL: https://www.heliosapp.com/integrations
Description: Helios agents get the complete API of every connected tool - GitHub, Slack, Gmail, Notion, Stripe, your databases, and more - with credentials handled server-side.
Integrations
# Full API access to every tool your agents touch.
Connect a service once. Your agents search its complete API at run time and call whichever endpoint the task needs, with credentials attached server-side. 18 services today, plus your databases and any MCP server.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
## Developer tools
02
[GitHubGive your agents full access to GitHub.](/integrations/github/)[WarpBuildGive your agents full access to WarpBuild.](/integrations/warpbuild/)
## Communication
01
[SlackGive your agents full access to Slack.](/integrations/slack/)
## Google Workspace
04
[GmailGive your agents full access to Gmail.](/integrations/gmail/)[Google SheetsGive your agents full access to Google Sheets.](/integrations/google-sheets/)[Google DocsGive your agents full access to Google Docs.](/integrations/google-docs/)[Google DriveGive your agents full access to Google Drive.](/integrations/google-drive/)
## Docs & knowledge
01
[NotionGive your agents full access to Notion.](/integrations/notion/)
## Sales & CRM
02
[AttioGive your agents full access to Attio.](/integrations/attio/)[ApolloGive your agents full access to Apollo.](/integrations/apollo/)
## Billing
01
[StripeGive your agents full access to Stripe.](/integrations/stripe/)
## Email
01
[ResendGive your agents full access to Resend.](/integrations/resend/)
## Support
01
[PPlainGive your agents full access to Plain.](/integrations/plain/)
## Community
02
[DiscordGive your agents full access to Discord.](/integrations/discord/)[RedditGive your agents full access to Reddit.](/integrations/reddit/)
## Forms
01
[TypeformGive your agents full access to Typeform.](/integrations/typeform/)
## Web data
01
[ApifyGive your agents full access to Apify.](/integrations/apify/)
## Data
01
[DatabasesGive your agents full access to your databases.](/integrations/databases/)
## Connect your first tool today.
Authorize a service, describe the task, and let an agent take it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Apify Integration - Full API Access for AI 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
# 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)
Capabilities
## What agents do with Apify
Helios vector-searches the Apify API surface at run time, so an agent reaches for whichever endpoint the task needs.
* 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.
Use cases
## 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
Cross-app recipes
## Apify works alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[Apify + RedditGive your agents full access to Reddit.](/integrations/reddit/)[Apify + Google SheetsGive your agents full access to Google Sheets.](/integrations/google-sheets/)[Apify + Google DocsGive your agents full access to Google Docs.](/integrations/google-docs/)
Templates
## Ready-to-run Apify agents
Copy the prompt, connect your tools, and put an agent on the task.
[MarketingCompetitor pricing & changelog watchScrapes competitor pricing pages and changelogs every week and reports only what actually changed.⏰Mondays at 6:00am](/templates/apify-competitor-scraper/)[MarketingSEO keyword briefReads what already ranks for a keyword, finds what everyone missed, and writes a brief your writer can work from.▶Run on demand](/templates/seo-keyword-brief/)[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](/templates/google-docs-brief-writer/)
Use cases
## Where Apify agents earn their keep
[Content pipelineAn agent searches the web, reads what it finds, and writes a sourced draft into a real document. Give it your voice and your prior work, and the first draft already sounds like you.](/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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Apollo Integration - Full API Access for AI 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 real definition rather than a saved filter.
[← All integrations](/integrations/)
Sales & CRM
# 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 real definition rather than a saved filter.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
Capabilities
## What agents do with Apollo
Helios vector-searches the Apollo API surface at run time, so an agent reaches for whichever endpoint the task needs.
* 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.
Use cases
## 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
Cross-app recipes
## Apollo works alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[Apollo + AttioGive your agents full access to Attio.](/integrations/attio/)[Apollo + ResendGive your agents full access to Resend.](/integrations/resend/)[Apollo + TypeformGive your agents full access to Typeform.](/integrations/typeform/)
Templates
## Ready-to-run Apollo agents
Copy the prompt, connect your tools, and put an agent on the task.
[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](/templates/apollo-lead-enrichment/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing firmographics, and flags deals that have gone quiet - every night, without anyone remembering.⏰Nightly at 2:00am](/templates/attio-crm-hygiene/)[Sales & RevOpsTypeform lead routerReads each form response, enriches the company, routes it to sales or support, and replies while the person still has your tab open.⇄Typeform response webhookP+1](/templates/typeform-lead-router/)
Use cases
## Where Apollo agents earn their keep
[Lead enrichmentWhen someone signs up or fills a form, an agent enriches the person and their company, scores fit against your definition of a good customer, creates the CRM record, and tells the right rep.](/use-cases/lead-enrichment/)[Email outreachAn agent finds the threads that went quiet, reads the conversation, and drafts a follow-up grounded in the last real next step. Onboarding sequences read the account before they send.](/use-cases/email-outreach/)[Form routingA response arrives and an agent reads what the person wrote, enriches their company, decides where it belongs, and files it - as a deal, a support thread, or a reply within minutes.P+1](/use-cases/form-routing/)[CRM data syncAn agent computes usage from your database, joins it with billing health and support volume, and writes the result onto the account record every night.P](/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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Attio Integration - Full API Access for AI 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
# 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)
Capabilities
## What agents do with Attio
Helios vector-searches the Attio API surface at run time, so an agent reaches for whichever endpoint the task needs.
* 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.
Use cases
## 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
Cross-app recipes
## Attio works alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[Attio + ApolloGive your agents full access to Apollo.](/integrations/apollo/)[Attio + StripeGive your agents full access to Stripe.](/integrations/stripe/)[Attio + TypeformGive your agents full access to Typeform.](/integrations/typeform/)
Templates
## Ready-to-run Attio agents
Copy the prompt, connect your tools, and put an agent on the task.
[SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.◆slack · new message in #supportP](/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](/templates/stripe-failed-payment-recovery/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.⏰Mondays at 7:00amP](/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](/templates/apollo-lead-enrichment/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing firmographics, and flags deals that have gone quiet - every night, without anyone remembering.⏰Nightly at 2:00am](/templates/attio-crm-hygiene/)[Sales & RevOpsTypeform lead routerReads each form response, enriches the company, routes it to sales or support, and replies while the person still has your tab open.⇄Typeform response webhookP+1](/templates/typeform-lead-router/)
Use cases
## Where Attio agents earn their keep
[Support triageAn agent reads each incoming thread the moment it arrives, identifies the customer, checks their plan and history, labels and prioritizes it, and drafts a reply grounded in your documentation.P](/use-cases/support-triage/)[Lead enrichmentWhen someone signs up or fills a form, an agent enriches the person and their company, scores fit against your definition of a good customer, creates the CRM record, and tells the right rep.](/use-cases/lead-enrichment/)[Billing operationsAn agent watches Stripe for failed charges and starts recovery, reconciles what you billed against what your own system recorded, and reports the revenue numbers every morning.](/use-cases/billing-ops/)[Email outreachAn agent finds the threads that went quiet, reads the conversation, and drafts a follow-up grounded in the last real next step. Onboarding sequences read the account before they send.](/use-cases/email-outreach/)[Form routingA response arrives and an agent reads what the person wrote, enriches their company, decides where it belongs, and files it - as a deal, a support thread, or a reply within minutes.P+1](/use-cases/form-routing/)[CRM data syncAn agent computes usage from your database, joins it with billing health and support volume, and writes the result onto the account record every night.P](/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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Databases Integration - Full API Access for AI 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)
Capabilities
## What agents do with Databases
Agents introspect your schema, write real SQL, and reason over the results in their own sandbox, with credentials handled server-side.
* 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.
* Memory carries what an agent learns about your schema from one run to the next.
Use cases
## 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 instead of a dashboard nobody opens.
⏰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
Cross-app recipes
## Your databases work alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[Databases + Google SheetsGive your agents full access to Google Sheets.](/integrations/google-sheets/)[Databases + StripeGive your agents full access to Stripe.](/integrations/stripe/)[Databases + AttioGive your agents full access to Attio.](/integrations/attio/)
Templates
## Ready-to-run database agents
Copy the prompt, connect your tools, and put an agent on the task.
[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.⏰Mondays at 7:00amP](/templates/churn-risk-watchlist/)[Sales & RevOpsOnboarding email that reads the accountChecks what each new account has actually set up and sends the message that helps them next, rather than the next message in a sequence.⏰Daily at 9:00am](/templates/resend-onboarding-sequence/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)[OperationsKPI sheet refreshPulls from the warehouse every morning and writes the finished tables into the sheet leadership already opens.⏰Daily at 6:00am](/templates/google-sheets-kpi-sync/)[OperationsNightly data quality checksRuns your invariants against production every night and tells the on-call analyst which rows broke and since when.⏰Nightly at 3:00am](/templates/database-health-check/)
Use cases
## Where database agents earn their keep
[Database reportingAn agent introspects your schema, writes the SQL, runs it, analyzes the results in its own sandbox, and posts a report your team reads - instead of a dashboard nobody opens.](/use-cases/database-reporting/)[Billing operationsAn agent watches Stripe for failed charges and starts recovery, reconciles what you billed against what your own system recorded, and reports the revenue numbers every morning.](/use-cases/billing-ops/)[Email outreachAn agent finds the threads that went quiet, reads the conversation, and drafts a follow-up grounded in the last real next step. Onboarding sequences read the account before they send.](/use-cases/email-outreach/)[Weekly digestsAn agent reads a week of activity across the tools your team uses, separates decisions from chatter, and posts a digest people actually read.](/use-cases/weekly-digests/)[CRM data syncAn agent computes usage from your database, joins it with billing health and support volume, and writes the result onto the account record every night.P](/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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Discord Integration - Full API Access for AI 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)
Capabilities
## What agents do with Discord
Helios vector-searches the Discord API surface at run time, so an agent reaches for whichever endpoint the task needs.
* 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.
Use cases
## 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
Cross-app recipes
## Discord works alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[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/)
Templates
## Ready-to-run Discord agents
Copy the prompt, connect your tools, and put an agent on the task.
[MarketingDiscord community digestReads every channel each evening, surfaces unanswered questions, and files real bug reports as GitHub issues.⏰Daily at 7:00pm](/templates/discord-community-digest/)
Use cases
## Where Discord agents earn their keep
[Community monitoringAn agent sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space, judges which threads deserve an answer, and brings them to your team.](/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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# GitHub Integration - Full API Access for AI 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 rather than a fixed menu of actions. 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 rather than a fixed menu of actions. 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)
Capabilities
## What agents do with GitHub
Helios vector-searches the GitHub API surface at run time, so an agent reaches for whichever endpoint the task needs.
* 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.
Use cases
## 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%
Triggers
## Wake an agent on GitHub events
Attach any of these events to a workflow and filter on the fields that matter. The agent starts within seconds of the event landing.
| 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. |
Cross-app recipes
## GitHub works alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[GitHub + SlackGive your agents full access to Slack.](/integrations/slack/)[GitHub + NotionGive your agents full access to Notion.](/integrations/notion/)[GitHub + WarpBuildGive your agents full access to WarpBuild.](/integrations/warpbuild/)
Templates
## Ready-to-run GitHub agents
Copy the prompt, connect your tools, and put an agent on the task.
[EngineeringPull request reviewerReviews every pull request against your conventions, leaves inline comments, and posts a weekly digest of review load and CI health.◆github · pull\_request.opened](/templates/pr-review-digest/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.◆github · tag.created](/templates/github-release-notes/)[EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup so nobody has to attend one.⏰Weekdays at 9:00am](/templates/daily-standup-digest/)[EngineeringIncident postmortem drafterReconstructs the incident timeline from Slack and GitHub, names the triggering change, and drafts the write-up in Notion.▶Run on demand](/templates/incident-postmortem-drafter/)[EngineeringCI cost & speed reportAttributes build spend to the workflows driving it, finds the jobs that got slower, and names the change responsible.⏰Mondays at 7:00am](/templates/warpbuild-ci-cost-report/)[MarketingDiscord community digestReads every channel each evening, surfaces unanswered questions, and files real bug reports as GitHub issues.⏰Daily at 7:00pm](/templates/discord-community-digest/)[SupportDocumentation freshness auditChecks your written docs against the actual codebase every month and comments on the pages that have gone stale.⏰Monthly on the 1st](/templates/notion-docs-freshness-audit/)
Use cases
## Where GitHub agents earn their keep
[PR review & digestAn agent reads each diff against your conventions and leaves a real review. A second agent summarizes the week: what merged, what is waiting, and how CI is holding up.](/use-cases/pr-review-digest/)[Incident summariesAn agent reconstructs the timeline from your incident channel and the deploys around it, identifies the triggering change, and drafts the write-up with the facts already assembled.](/use-cases/incident-summaries/)[Weekly digestsAn agent reads a week of activity across the tools your team uses, separates decisions from chatter, and posts a digest people actually read.](/use-cases/weekly-digests/)[Community monitoringAn agent sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space, judges which threads deserve an answer, and brings them to your team.](/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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Gmail Integration - Full API Access for AI 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
# 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)
Capabilities
## What agents do with Gmail
Helios vector-searches the Gmail API surface at run time, so an agent reaches for whichever endpoint the task needs.
* 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.
Use cases
## 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
Cross-app recipes
## Gmail works alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[Gmail + Google SheetsGive your agents full access to Google Sheets.](/integrations/google-sheets/)[Gmail + AttioGive your agents full access to Attio.](/integrations/attio/)[Gmail + ResendGive your agents full access to Resend.](/integrations/resend/)
Templates
## Ready-to-run Gmail agents
Copy the prompt, connect your tools, and put an agent on the task.
[SupportMorning inbox triageReads what arrived overnight, labels it, drafts the easy replies, and hands you a ranked list of what needs a human.⏰Weekdays at 7:30am](/templates/gmail-inbox-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](/templates/apollo-lead-enrichment/)
Use cases
## Where Gmail agents earn their keep
[Lead enrichmentWhen someone signs up or fills a form, an agent enriches the person and their company, scores fit against your definition of a good customer, creates the CRM record, and tells the right rep.](/use-cases/lead-enrichment/)[Email outreachAn agent finds the threads that went quiet, reads the conversation, and drafts a follow-up grounded in the last real next step. Onboarding sequences read the account before they send.](/use-cases/email-outreach/)
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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Google Docs Integration - Full API Access for AI 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
# 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)
Capabilities
## What agents do with Google Docs
Helios vector-searches the Google Docs API surface at run time, so an agent reaches for whichever endpoint the task needs.
* 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.
Use cases
## 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
Cross-app recipes
## Google Docs works alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[Google Docs + Google DriveGive your agents full access to Google Drive.](/integrations/google-drive/)[Google Docs + NotionGive your agents full access to Notion.](/integrations/notion/)[Google Docs + ApifyGive your agents full access to Apify.](/integrations/apify/)
Templates
## Ready-to-run Google Docs agents
Copy the prompt, connect your tools, and put an agent on the task.
[MarketingSEO keyword briefReads what already ranks for a keyword, finds what everyone missed, and writes a brief your writer can work from.▶Run on demand](/templates/seo-keyword-brief/)[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](/templates/google-docs-brief-writer/)
Use cases
## Where Google Docs agents earn their keep
[Content pipelineAn agent searches the web, reads what it finds, and writes a sourced draft into a real document. Give it your voice and your prior work, and the first draft already sounds like you.](/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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Google Drive Integration - Full API Access for AI Agents | Helios
URL: https://www.heliosapp.com/integrations/google-drive
Description: Agents find files, read them, organize folders, and manage sharing. Each agent has a real computer, so it can download a file, open it, analyze it, and write the result back to Drive.
[← All integrations](/integrations/)
Google Workspace
# Give your agents full access to Google Drive.
Agents find files, read them, organize folders, and manage sharing. Each agent has a real computer, so it can download a file, open it, analyze it, and write the result back to Drive.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
Capabilities
## What agents do with Google Drive
Helios vector-searches the Google Drive API surface at run time, so an agent reaches for whichever endpoint the task needs.
* Search the Drive API surface at run time and call any endpoint your scopes allow.
* Search files and folders with Drive's full query syntax.
* Download files into the sandbox to read, parse, and analyze with code.
* Create folders, move files, rename, and organize by content.
* Upload generated artifacts - reports, exports, cleaned data - back to Drive.
* Read and update sharing permissions on the files a task touches.
Use cases
## Tasks you can hand to a Google Drive agent
### Organize a folder that got out of hand
The agent reads what each file actually contains, 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. It opens each one, pulls the fields you name, and writes a table.
Read every contract in \`Vendor Agreements\` and build a renewal table.
1. google-drive·download 28 PDFs
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 report as PDF
3. google-drive·upload to \`Reports/2025\`
✓March report filed
* Uploaded to \`Reports/2025/March.pdf\`
* Shared with the leadership group
Cross-app recipes
## Google Drive works alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[Google Drive + Google DocsGive your agents full access to Google Docs.](/integrations/google-docs/)[Google Drive + Google SheetsGive your agents full access to Google Sheets.](/integrations/google-sheets/)[Google Drive + GmailGive your agents full access to Gmail.](/integrations/gmail/)
Templates
## Ready-to-run Google Drive agents
Copy the prompt, connect your tools, and put an agent on the task.
[OperationsDrive organizer & access auditFiles loose documents by what they actually contain, and reports anything shared beyond your domain.⏰Sundays at 8:00pm](/templates/google-drive-file-organizer/)[MarketingSEO keyword briefReads what already ranks for a keyword, finds what everyone missed, and writes a brief your writer can work from.▶Run on demand](/templates/seo-keyword-brief/)[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](/templates/google-docs-brief-writer/)
Use cases
## Where Google Drive agents earn their keep
[Content pipelineAn agent searches the web, reads what it finds, and writes a sourced draft into a real document. Give it your voice and your prior work, and the first draft already sounds like you.](/use-cases/content-pipeline/)
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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Google Sheets Integration - Full API Access for AI 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
# 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)
Capabilities
## What agents do with Google Sheets
Helios vector-searches the Google Sheets API surface at run time, so an agent reaches for whichever endpoint the task needs.
* 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.
Use cases
## 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
Cross-app recipes
## Google Sheets works alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[Google Sheets + DatabasesGive your agents full access to your databases.](/integrations/databases/)[Google Sheets + Google DriveGive your agents full access to Google Drive.](/integrations/google-drive/)[Google Sheets + StripeGive your agents full access to Stripe.](/integrations/stripe/)
Templates
## Ready-to-run Google Sheets agents
Copy the prompt, connect your tools, and put an agent on the task.
[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)[OperationsKPI sheet refreshPulls from the warehouse every morning and writes the finished tables into the sheet leadership already opens.⏰Daily at 6:00am](/templates/google-sheets-kpi-sync/)[OperationsDrive organizer & access auditFiles loose documents by what they actually contain, and reports anything shared beyond your domain.⏰Sundays at 8:00pm](/templates/google-drive-file-organizer/)
Use cases
## Where Google Sheets agents earn their keep
[Database reportingAn agent introspects your schema, writes the SQL, runs it, analyzes the results in its own sandbox, and posts a report your team reads - instead of a dashboard nobody opens.](/use-cases/database-reporting/)[Billing operationsAn agent watches Stripe for failed charges and starts recovery, reconciles what you billed against what your own system recorded, and reports the revenue numbers every morning.](/use-cases/billing-ops/)
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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Notion Integration - Full API Access for AI 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)
Capabilities
## What agents do with Notion
Helios vector-searches the Notion API surface at run time, so an agent reaches for whichever endpoint the task needs.
* 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.
Use cases
## 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
Cross-app recipes
## Notion works alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[Notion + SlackGive your agents full access to Slack.](/integrations/slack/)[Notion + GitHubGive your agents full access to GitHub.](/integrations/github/)[Notion + Google DocsGive your agents full access to Google Docs.](/integrations/google-docs/)
Templates
## Ready-to-run Notion agents
Copy the prompt, connect your tools, and put an agent on the task.
[SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.◆slack · new message in #supportP](/templates/slack-support-triage/)[SupportPlain thread triage & weekly themesTriages every incoming Plain thread on arrival, then clusters the week into the themes product should hear about.◆plain · thread.createdP](/templates/plain-thread-summarizer/)[SupportMorning inbox triageReads what arrived overnight, labels it, drafts the easy replies, and hands you a ranked list of what needs a human.⏰Weekdays at 7:30am](/templates/gmail-inbox-triage/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.◆github · tag.created](/templates/github-release-notes/)[EngineeringIncident postmortem drafterReconstructs the incident timeline from Slack and GitHub, names the triggering change, and drafts the write-up in Notion.▶Run on demand](/templates/incident-postmortem-drafter/)[MarketingReddit brand monitorSweeps the subreddits where your customers gather, judges which threads deserve a reply, and brings you a shortlist.⏰Every 4 hours](/templates/reddit-brand-monitor/)[MarketingDiscord community digestReads every channel each evening, surfaces unanswered questions, and files real bug reports as GitHub issues.⏰Daily at 7:00pm](/templates/discord-community-digest/)[MarketingCompetitor pricing & changelog watchScrapes competitor pricing pages and changelogs every week and reports only what actually changed.⏰Mondays at 6:00am](/templates/apify-competitor-scraper/)[SupportDocumentation freshness auditChecks your written docs against the actual codebase every month and comments on the pages that have gone stale.⏰Monthly on the 1st](/templates/notion-docs-freshness-audit/)
Use cases
## Where Notion agents earn their keep
[Support triageAn agent reads each incoming thread the moment it arrives, identifies the customer, checks their plan and history, labels and prioritizes it, and drafts a reply grounded in your documentation.P](/use-cases/support-triage/)[PR review & digestAn agent reads each diff against your conventions and leaves a real review. A second agent summarizes the week: what merged, what is waiting, and how CI is holding up.](/use-cases/pr-review-digest/)[Incident summariesAn agent reconstructs the timeline from your incident channel and the deploys around it, identifies the triggering change, and drafts the write-up with the facts already assembled.](/use-cases/incident-summaries/)[Content pipelineAn agent searches the web, reads what it finds, and writes a sourced draft into a real document. Give it your voice and your prior work, and the first draft already sounds like you.](/use-cases/content-pipeline/)[Weekly digestsAn agent reads a week of activity across the tools your team uses, separates decisions from chatter, and posts a digest people actually read.](/use-cases/weekly-digests/)[Community monitoringAn agent sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space, judges which threads deserve an answer, and brings them to your team.](/use-cases/community-monitoring/)
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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Plain Integration - Full API Access for AI 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/)
P
Support
# 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)
Capabilities
## What agents do with Plain
Helios vector-searches the Plain API surface at run time, so an agent reaches for whichever endpoint the task needs.
* 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.
Use cases
## 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.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.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
Triggers
## Wake an agent on Plain events
Attach any of these events to a workflow and filter on the fields that matter. The agent starts within seconds of the event landing.
| Event | What it means |
| -------------- | ------------------------------------------------------------------------------- |
| thread.created | A customer opens a new thread - the moment to triage, label, and draft a reply. |
| chat.received | A live chat message arrives and an agent can answer or route it immediately. |
Cross-app recipes
## Plain works alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[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 agents
Copy the prompt, connect your tools, and put an agent on the task.
[SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.◆slack · new message in #supportP](/templates/slack-support-triage/)[SupportPlain thread triage & weekly themesTriages every incoming Plain thread on arrival, then clusters the week into the themes product should hear about.◆plain · thread.createdP](/templates/plain-thread-summarizer/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.⏰Mondays at 7:00amP](/templates/churn-risk-watchlist/)[Sales & RevOpsTypeform lead routerReads each form response, enriches the company, routes it to sales or support, and replies while the person still has your tab open.⇄Typeform response webhookP+1](/templates/typeform-lead-router/)
Use cases
## Where Plain agents earn their keep
[Support triageAn agent reads each incoming thread the moment it arrives, identifies the customer, checks their plan and history, labels and prioritizes it, and drafts a reply grounded in your documentation.P](/use-cases/support-triage/)[Form routingA response arrives and an agent reads what the person wrote, enriches their company, decides where it belongs, and files it - as a deal, a support thread, or a reply within minutes.P+1](/use-cases/form-routing/)[CRM data syncAn agent computes usage from your database, joins it with billing health and support volume, and writes the result onto the account record every night.P](/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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Reddit Integration - Full API Access for AI 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)
Capabilities
## What agents do with Reddit
Helios vector-searches the Reddit API surface at run time, so an agent reaches for whichever endpoint the task needs.
* 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.
Use cases
## 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
Cross-app recipes
## Reddit works alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[Reddit + DiscordGive your agents full access to Discord.](/integrations/discord/)[Reddit + NotionGive your agents full access to Notion.](/integrations/notion/)[Reddit + ApifyGive your agents full access to Apify.](/integrations/apify/)
Templates
## Ready-to-run Reddit agents
Copy the prompt, connect your tools, and put an agent on the task.
[MarketingReddit brand monitorSweeps the subreddits where your customers gather, judges which threads deserve a reply, and brings you a shortlist.⏰Every 4 hours](/templates/reddit-brand-monitor/)
Use cases
## Where Reddit agents earn their keep
[Community monitoringAn agent sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space, judges which threads deserve an answer, and brings them to your team.](/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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Resend Integration - Full API Access for AI 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
# 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)
Capabilities
## What agents do with Resend
Helios vector-searches the Resend API surface at run time, so an agent reaches for whichever endpoint the task needs.
* 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.
Use cases
## Tasks you can hand to a Resend agent
### Run an onboarding sequence that reads the account
Instead of a fixed drip, 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 data rather than a template with slots.
⏰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
Cross-app recipes
## Resend works alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[Resend + StripeGive your agents full access to Stripe.](/integrations/stripe/)[Resend + DatabasesGive your agents full access to your databases.](/integrations/databases/)[Resend + AttioGive your agents full access to Attio.](/integrations/attio/)
Templates
## Ready-to-run Resend agents
Copy the prompt, connect your tools, and put an agent on the task.
[Sales & RevOpsFailed payment recoveryFinds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.⏰Hourly](/templates/stripe-failed-payment-recovery/)[Sales & RevOpsTypeform lead routerReads each form response, enriches the company, routes it to sales or support, and replies while the person still has your tab open.⇄Typeform response webhookP+1](/templates/typeform-lead-router/)[Sales & RevOpsOnboarding email that reads the accountChecks what each new account has actually set up and sends the message that helps them next, rather than the next message in a sequence.⏰Daily at 9:00am](/templates/resend-onboarding-sequence/)[OperationsNightly data quality checksRuns your invariants against production every night and tells the on-call analyst which rows broke and since when.⏰Nightly at 3:00am](/templates/database-health-check/)
Use cases
## Where Resend agents earn their keep
[Database reportingAn agent introspects your schema, writes the SQL, runs it, analyzes the results in its own sandbox, and posts a report your team reads - instead of a dashboard nobody opens.](/use-cases/database-reporting/)[Billing operationsAn agent watches Stripe for failed charges and starts recovery, reconciles what you billed against what your own system recorded, and reports the revenue numbers every morning.](/use-cases/billing-ops/)[Email outreachAn agent finds the threads that went quiet, reads the conversation, and drafts a follow-up grounded in the last real next step. Onboarding sequences read the account before they send.](/use-cases/email-outreach/)[Form routingA response arrives and an agent reads what the person wrote, enriches their company, decides where it belongs, and files it - as a deal, a support thread, or a reply within minutes.P+1](/use-cases/form-routing/)
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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Slack Integration - Full API Access for AI 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
# 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)
Capabilities
## What agents do with Slack
Helios vector-searches the Slack API surface at run time, so an agent reaches for whichever endpoint the task needs.
* 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.
Use cases
## 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
Triggers
## Wake an agent on Slack events
Attach any of these events to a workflow and filter on the fields that matter. The agent starts within seconds of the event landing.
| Event | What it means |
| ---------------- | -------------------------------------------------------------------------------------------------- |
| message.channels | A new message lands in a public channel. Filter by channel so one agent watches one room. |
| message.groups | A new message lands in a private channel the connection has joined, with the same channel filters. |
Cross-app recipes
## Slack works alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[Slack + GitHubGive your agents full access to GitHub.](/integrations/github/)[PSlack + PlainGive your agents full access to Plain.](/integrations/plain/)[Slack + NotionGive your agents full access to Notion.](/integrations/notion/)
Templates
## Ready-to-run Slack agents
Copy the prompt, connect your tools, and put an agent on the task.
[SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.◆slack · new message in #supportP](/templates/slack-support-triage/)[SupportPlain thread triage & weekly themesTriages every incoming Plain thread on arrival, then clusters the week into the themes product should hear about.◆plain · thread.createdP](/templates/plain-thread-summarizer/)[SupportMorning inbox triageReads what arrived overnight, labels it, drafts the easy replies, and hands you a ranked list of what needs a human.⏰Weekdays at 7:30am](/templates/gmail-inbox-triage/)[EngineeringPull request reviewerReviews every pull request against your conventions, leaves inline comments, and posts a weekly digest of review load and CI health.◆github · pull\_request.opened](/templates/pr-review-digest/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.◆github · tag.created](/templates/github-release-notes/)[EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup so nobody has to attend one.⏰Weekdays at 9:00am](/templates/daily-standup-digest/)[EngineeringIncident postmortem drafterReconstructs the incident timeline from Slack and GitHub, names the triggering change, and drafts the write-up in Notion.▶Run on demand](/templates/incident-postmortem-drafter/)[EngineeringCI cost & speed reportAttributes build spend to the workflows driving it, finds the jobs that got slower, and names the change responsible.⏰Mondays at 7:00am](/templates/warpbuild-ci-cost-report/)[Sales & RevOpsFailed payment recoveryFinds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.⏰Hourly](/templates/stripe-failed-payment-recovery/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.⏰Mondays at 7:00amP](/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](/templates/apollo-lead-enrichment/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing firmographics, and flags deals that have gone quiet - every night, without anyone remembering.⏰Nightly at 2:00am](/templates/attio-crm-hygiene/)[Sales & RevOpsTypeform lead routerReads each form response, enriches the company, routes it to sales or support, and replies while the person still has your tab open.⇄Typeform response webhookP+1](/templates/typeform-lead-router/)[Sales & RevOpsOnboarding email that reads the accountChecks what each new account has actually set up and sends the message that helps them next, rather than the next message in a sequence.⏰Daily at 9:00am](/templates/resend-onboarding-sequence/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)[OperationsNightly data quality checksRuns your invariants against production every night and tells the on-call analyst which rows broke and since when.⏰Nightly at 3:00am](/templates/database-health-check/)[OperationsDrive organizer & access auditFiles loose documents by what they actually contain, and reports anything shared beyond your domain.⏰Sundays at 8:00pm](/templates/google-drive-file-organizer/)[MarketingReddit brand monitorSweeps the subreddits where your customers gather, judges which threads deserve a reply, and brings you a shortlist.⏰Every 4 hours](/templates/reddit-brand-monitor/)[MarketingDiscord community digestReads every channel each evening, surfaces unanswered questions, and files real bug reports as GitHub issues.⏰Daily at 7:00pm](/templates/discord-community-digest/)[MarketingCompetitor pricing & changelog watchScrapes competitor pricing pages and changelogs every week and reports only what actually changed.⏰Mondays at 6:00am](/templates/apify-competitor-scraper/)[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](/templates/google-docs-brief-writer/)[SupportDocumentation freshness auditChecks your written docs against the actual codebase every month and comments on the pages that have gone stale.⏰Monthly on the 1st](/templates/notion-docs-freshness-audit/)
Use cases
## Where Slack agents earn their keep
[Support triageAn agent reads each incoming thread the moment it arrives, identifies the customer, checks their plan and history, labels and prioritizes it, and drafts a reply grounded in your documentation.P](/use-cases/support-triage/)[Lead enrichmentWhen someone signs up or fills a form, an agent enriches the person and their company, scores fit against your definition of a good customer, creates the CRM record, and tells the right rep.](/use-cases/lead-enrichment/)[PR review & digestAn agent reads each diff against your conventions and leaves a real review. A second agent summarizes the week: what merged, what is waiting, and how CI is holding up.](/use-cases/pr-review-digest/)[Incident summariesAn agent reconstructs the timeline from your incident channel and the deploys around it, identifies the triggering change, and drafts the write-up with the facts already assembled.](/use-cases/incident-summaries/)[Database reportingAn agent introspects your schema, writes the SQL, runs it, analyzes the results in its own sandbox, and posts a report your team reads - instead of a dashboard nobody opens.](/use-cases/database-reporting/)[Content pipelineAn agent searches the web, reads what it finds, and writes a sourced draft into a real document. Give it your voice and your prior work, and the first draft already sounds like you.](/use-cases/content-pipeline/)[Weekly digestsAn agent reads a week of activity across the tools your team uses, separates decisions from chatter, and posts a digest people actually read.](/use-cases/weekly-digests/)[Form routingA response arrives and an agent reads what the person wrote, enriches their company, decides where it belongs, and files it - as a deal, a support thread, or a reply within minutes.P+1](/use-cases/form-routing/)[Community monitoringAn agent sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space, judges which threads deserve an answer, and brings them to your team.](/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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Stripe Integration - Full API Access for AI 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)
Capabilities
## What agents do with Stripe
Helios vector-searches the Stripe API surface at run time, so an agent reaches for whichever endpoint the task needs.
* 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.
Use cases
## 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
Cross-app recipes
## Stripe works alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[Stripe + AttioGive your agents full access to Attio.](/integrations/attio/)[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 agents
Copy the prompt, connect your tools, and put an agent on the task.
[SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.◆slack · new message in #supportP](/templates/slack-support-triage/)[SupportPlain thread triage & weekly themesTriages every incoming Plain thread on arrival, then clusters the week into the themes product should hear about.◆plain · thread.createdP](/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](/templates/stripe-failed-payment-recovery/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.⏰Mondays at 7:00amP](/templates/churn-risk-watchlist/)[OperationsKPI sheet refreshPulls from the warehouse every morning and writes the finished tables into the sheet leadership already opens.⏰Daily at 6:00am](/templates/google-sheets-kpi-sync/)
Use cases
## Where Stripe agents earn their keep
[Support triageAn agent reads each incoming thread the moment it arrives, identifies the customer, checks their plan and history, labels and prioritizes it, and drafts a reply grounded in your documentation.P](/use-cases/support-triage/)[Billing operationsAn agent watches Stripe for failed charges and starts recovery, reconciles what you billed against what your own system recorded, and reports the revenue numbers every morning.](/use-cases/billing-ops/)[CRM data syncAn agent computes usage from your database, joins it with billing health and support volume, and writes the result onto the account record every night.P](/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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Typeform Integration - Full API Access for AI 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
# 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)
Capabilities
## What agents do with Typeform
Helios vector-searches the Typeform API surface at run time, so an agent reaches for whichever endpoint the task needs.
* 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.
Use cases
## 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 instead of a chart of averages.
⏰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
Cross-app recipes
## Typeform works alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[Typeform + AttioGive your agents full access to Attio.](/integrations/attio/)[Typeform + ApolloGive your agents full access to Apollo.](/integrations/apollo/)[PTypeform + PlainGive your agents full access to Plain.](/integrations/plain/)
Templates
## Ready-to-run Typeform agents
Copy the prompt, connect your tools, and put an agent on the task.
[Sales & RevOpsTypeform lead routerReads each form response, enriches the company, routes it to sales or support, and replies while the person still has your tab open.⇄Typeform response webhookP+1](/templates/typeform-lead-router/)
Use cases
## Where Typeform agents earn their keep
[Lead enrichmentWhen someone signs up or fills a form, an agent enriches the person and their company, scores fit against your definition of a good customer, creates the CRM record, and tells the right rep.](/use-cases/lead-enrichment/)[Form routingA response arrives and an agent reads what the person wrote, enriches their company, decides where it belongs, and files it - as a deal, a support thread, or a reply within minutes.P+1](/use-cases/form-routing/)
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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# WarpBuild Integration - Full API Access for AI 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
# 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)
Capabilities
## What agents do with WarpBuild
Helios vector-searches the WarpBuild API surface at run time, so an agent reaches for whichever endpoint the task needs.
* 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.
Use cases
## 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
Cross-app recipes
## WarpBuild works alongside the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next without a handoff.
[WarpBuild + GitHubGive your agents full access to GitHub.](/integrations/github/)[WarpBuild + SlackGive your agents full access to Slack.](/integrations/slack/)[WarpBuild + DatabasesGive your agents full access to your databases.](/integrations/databases/)
Templates
## Ready-to-run WarpBuild agents
Copy the prompt, connect your tools, and put an agent on the task.
[EngineeringIncident postmortem drafterReconstructs the incident timeline from Slack and GitHub, names the triggering change, and drafts the write-up in Notion.▶Run on demand](/templates/incident-postmortem-drafter/)[EngineeringCI cost & speed reportAttributes build spend to the workflows driving it, finds the jobs that got slower, and names the change responsible.⏰Mondays at 7:00am](/templates/warpbuild-ci-cost-report/)
Use cases
## Where WarpBuild agents earn their keep
[Incident summariesAn agent reconstructs the timeline from your incident channel and the deploys around it, identifies the triggering change, and drafts the write-up with the facts already assembled.](/use-cases/incident-summaries/)[Weekly digestsAn agent reads a week of activity across the tools your team uses, separates decisions from chatter, and posts a digest people actually read.](/use-cases/weekly-digests/)
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, describe the task in plain English, and let it run on your schedule or your events.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# 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
* SOC 2 compliance
## 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 April 8, 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 |
---
# 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 July 14, 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.
## 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 - Simple, Usage-Based | Helios
URL: https://www.heliosapp.com/pricing
Description: Start free. Pay for what your agents use, with clear per-task cost examples. Enterprise plans with SSO, SCIM, and custom controls.
# You pay for work done
Start with 5,000 credits, free. After that your agents draw credits as they run - $0.002 each, with no seats and no monthly minimum. Enterprise adds SSO, SCIM, and custom controls.
### Free
Put your first agent on a real task
Free
5,000 credits to start
[Get started free](https://app.heliosapp.com/)
* Agents in chat and on triggers
* A cloud sandbox for every run
* Every integration, full API access
* Your databases and MCP servers
* Memory that carries across runs
* Community support
### Growth
For teams with agents on the task every day
$0.002/credit
Usage-based. No seats, no monthly minimum.
[Get started](https://app.heliosapp.com/)
* Everything in Free, plus:
* Credits billed as agents work
* Spending limits you set
* Auto-refill to keep long tasks running
* Email support
### Enterprise
For rolling agents out across the company
Custom
Custom credit volume and terms
[Talk to us](https://cal.com/suryao/helios)
* Everything in Growth, plus:
* SAML and OIDC single sign-on
* SCIM user provisioning
* Custom controls and volume pricing
* Security and compliance review
* Priority support and onboarding
What a task costs
## Three tasks, priced out
A credit is $0.002 on the Growth plan. Most tasks land somewhere between a fraction of a cent and a few cents per run, depending on the model you choose and how much reading the agent has to do.
Support triage
◆Slack message in #support
When someone posts in #support, read the thread, check our runbooks, and reply with the fix or route it to the right engineer.
1. slack·read thread in #support
2. notion·search support runbooks
3. slack·reply in thread
✓Thread answered and routed
* matched runbook: password reset loop
* escalated: no
10–30 creditsabout $0.02–$0.06 per run
Nightly database report
⏰Every night at 2:00 AM
Every night, pull yesterday's signups and revenue from Postgres, chart the trend against last week, and post the summary to #metrics.
1. postgres·query signups and revenue
2. code·run analysis.ts
3. slack·post summary to #metrics
✓Nightly report delivered
* signups: 412 (+8.1% WoW)
* chart attached: revenue\_7d.png
40–120 creditsabout $0.08–$0.24 per run
Pull request digest
◆pull\_request.opened
When a pull request opens, read the diff, summarize the risk for reviewers, and leave a comment with what to look at first.
1. github·read pull request diff
2. memory·recall past reviews on this service
3. github·post review comment
✓Reviewer digest posted
* files: 14 · risk: touches billing writes
25–80 creditsabout $0.05–$0.16 per run
These are illustrative estimates, not a quote. What a run actually costs depends on the model you pick, how much the agent reads and writes, and how many tool calls the task takes. Every run reports its own usage, so you can see the real number the first time an agent works for you.
## Compare plan features
Feature
Free
Growth
Enterprise
Credits
Credits to start
5,000
5,000
Custom volume
Credit price
\-
$0.002
Custom
Per-seat pricing
None
None
None
Spending limits
\-
Auto-refill
\-
Agents & triggers
Agents
Unlimited
Unlimited
Unlimited
Chat with your agents
Cloud sandbox per run
Scheduled triggers
Signed webhook triggers
Integration event triggers
Run history and outputs
Reach
Integrations
All
All
All
Full API access
Databases
MCP servers
Web search and scraping
Frontier agent model
API keys
Memory & context
Memory across runs
Persistent workspace files
Pinned repositories
Variables and secrets
Access & controls
Organization roles
Resource roles and sharing
Encrypted secrets
Webhook signing and rotation
SAML and OIDC SSO
\-
\-
SCIM provisioning
\-
\-
Support
Community support
Email support
\-
Priority support
\-
\-
Onboarding
\-
\-
Security and compliance review
\-
\-
### What is a credit?
### How many credits does one task use?
### What model do agents run on?
### What happens when my credits run out?
### Do you charge per seat?
### Are there limits on how many agents or triggers I can create?
### What comes with the Enterprise plan?
### Is my data used to train models?
### How do I move from Free to Growth?
## Hand an agent your first task
Your 5,000 credits are enough to see an agent work. Bring a task you would rather stop doing.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Platform - How Helios Agents Work | Helios
URL: https://www.heliosapp.com/product
Description: Every Helios agent runs on its own cloud computer with frontier models, code execution, web access, your integrations' full APIs, your databases, and MCP.
Platform
# Every agent gets a real computer.
Helios runs each agent in its own isolated cloud sandbox: frontier models, code execution, a file system, and live web access - wired to the full APIs of your tools, your databases, and any MCP server you attach.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
▶run now
Our Q3 usage looks off. Pull the numbers from the warehouse, work out which accounts drove the change, and write me a memo.
1. clickhouse·query events · Q2 vs Q3 by account
2. code·run cohort-delta.ts · group by account
3. web·search funding news for top 5 accounts
4. workspace·write q3-usage-memo.md
5. google-docs·create doc · share with #revops
✓Q3 usage memo delivered
* Change traced to 3 accounts that migrated off the legacy endpoint
* Two raised a round this quarter - expansion candidates flagged
* Chart and raw CSV saved to the agent's workspace
The sandbox
## A computer of its own.
Each run starts in an isolated cloud sandbox, walled off from your infrastructure and from every other run.
### Code execution
Agents run shell commands and write scripts inside the sandbox. When a task needs a join, a chart, or a one-off parser, the agent writes the code and runs it.
### A file system
Read and write real files. Download an export, transform it, keep the intermediate artifacts, and hand back the finished document.
### Web search and scraping
Search the live web and pull the contents of a page into the run, so an agent can research a company or check a status page before it acts.
### A persistent workspace
The sandbox is disposable. The workspace endures - files written on Monday are still there on Friday, backed by durable object storage.
The model
## A frontier model, tuned for the task.
Every agent runs on Claude Sonnet, tuned for long-running tool use - reading APIs, writing code, and checking its own work across a run.
One model, deliberately chosen, means every task gets the same judgment - the scheduled report and the one-off research question alike. The rest of the agent - its computer, its tools, its memory - is built around it.
▶run · on demand
Research the three competitors we lost deals to last month and summarize how they price.
1. attio·list closed-lost · reason=competitor
2. web·search pricing pages · 3 vendors
3. apify·scrape pricing tables
4. notion·update Competitive Landscape
✓Competitive brief updated
* 3 vendors · pricing model, entry price, and enterprise gate
* Sources cited inline for the sales team
The tools
## Reach that matches the task.
An agent is only as useful as what it can touch. Helios hands it everything your team already works in.
### The full API of every integration
Helios indexes each service's complete OpenAPI spec and lets the agent search it at run time, so it can call whichever endpoint the task needs. Credentials are attached server-side and stay out of the model's view.
### Your databases
Connect Postgres, MySQL, or ClickHouse - over an SSH tunnel where your network requires one - and let agents query production data directly.
### Any MCP server
Attach an MCP server and its tools join the agent's toolbox. Helios speaks MCP outward too, so your own clients can drive Helios agents.
Enterprise ready
Secrets are envelope-encrypted with AES-256-GCM, each under its own key wrapped by AWS KMS. Scoped integration credentials attach to outbound requests at the egress layer and carry an expiry, so the model never handles a raw key. Agent runs happen in isolated sandboxes, every run keeps an audit trail of its trigger and tool calls, and access to each integration, workflow, and chat is governed by organization roles and resource-level sharing. Helios is SOC 2 Type II compliant.
[Security →](/security/)[Enterprise →](/enterprise/)
Memory
## The work compounds.
Learnings, files, and pinned context carry from one run into the next.
### Memory across runs
Corrections and preferences persist. Teach an agent your escalation rules once and every future run applies them.
### Pinned repositories
Pin a GitHub repository as a scoped resource and the agent carries it as standing context on every run.
### Variables and secrets
Store the values a task needs - an API key, a threshold, a channel name - encrypted and reusable across every agent you run.
Two modes
## The same agent, on demand or on duty.
Talk to an agent in Chat when you need something now. Save that agent as a Workflow to put it on the task permanently. Same runtime, same tools, same memory.
Which enterprise accounts opened a support thread this week and have a renewal inside 60 days?
1. plain·list threads · 7 days
2. postgres·join renewals on account\_id
✓4 accounts match
* Answered in chat · 12 seconds
⏰every Monday 8:00am
Do that every Monday and post it to #customer-success.
1. plain·list threads · 7 days
2. postgres·join renewals on account\_id
3. slack·post #customer-success
✓Workflow saved and scheduled
* Runs forever · full run history kept
Keep going
## Go deeper
The runtime is one story. Here is how teams put it to work.
[ChatTalk to your agentsDelegate in conversation, upload files, pin the repositories an agent should know about, and share the session with your team.](/product/chat/)[WorkflowsPut an agent on the taskA plain-English prompt and a trigger. Cron, signed webhooks, integration events, or on demand.](/product/workflows/)[Use caseDatabase reportingWatch an agent query your warehouse, analyze the result in code, and deliver the report where your team reads it.](/use-cases/database-reporting/)
## Give an agent a computer.
Start free, describe the first task, and watch the run unfold step by step.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Chat - Talk to Your Agents | Helios
URL: https://www.heliosapp.com/product/chat
Description: Hand work to a Helios agent in chat. Upload files, pin channels and repos as context, share sessions with your team, and fork conversations.
Chat
# Talk to your agents. Hand off the work.
Ask for something the way you would ask a colleague. The agent goes to your tools, does the task on its own computer, and comes back with the result - and with the files it made along the way.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
▶chat · file attached
Here's the churn CSV from the board deck. Cross-check it against our warehouse, find the accounts we mislabeled, and open Attio records for the ones still active.
1. workspace·read churn-q3.csv · 214 rows
2. postgres·query subscriptions by account\_id
3. code·reconcile and diff · 11 mismatches
4. attio·update 7 records · status=active
✓11 mislabeled accounts found
* 7 still active - Attio records corrected
* 4 genuinely churned - confirmed against last invoice
* reconciliation.csv saved to the workspace
Context
## Give it the context once.
An agent does better work when it knows where to look. Point it at the channels, repos, databases, and files that matter.
### Pin the resources it should know
Attach a Slack channel, a GitHub repository, or a database connection to the conversation as a scoped resource. The agent treats it as standing context for everything you ask next.
### Upload the files it needs
Drop a CSV, a contract, or a screenshot into the chat. The file lands in the agent's workspace, where it can open it, transform it, and hand something back.
### Everything the runtime gives it
Chat runs on the same agent as Workflows: an isolated cloud sandbox, code execution, the full APIs of your integrations, your databases, and memory of what you have taught it.
Pinned repositories
## Scoped to exactly what you name.
Pinning a repository narrows an agent to the codebase you want it working on.
Pin a GitHub repository and the agent carries it as standing context - it works in that codebase without rediscovering it each time. The pin carries the integration it belongs to, so the credentials come along and stay server-side. Everything else the agent reaches - channels, databases, documents - comes through your connected integrations on demand.
▶pinned · helios/api
What did people complain about in #support this week that we haven't filed an issue for?
1. slack·read #support · last 7 days
2. github·search issues in helios/api
3. code·match complaints to open issues
✓3 unfiled complaints
* CSV export timeout · mentioned 6 times
* SAML login redirect loop · 2 enterprise accounts
* Draft issue bodies ready to file
Collaboration
## One conversation, the whole team.
A chat that solved a problem is worth keeping - and worth passing on.
### Fork a conversation
Branch from any chat to try a different approach, keeping the original thread and everything it already worked out.
### Share a public link
Publish a conversation up to a chosen message and send the link to anyone. The rest of the thread stays private.
### Share with your team
Keep a chat restricted to the people you name, or open it to everyone in your organization. Roles decide who can read it and who can drive it.
Enterprise ready
Every chat is a governed resource. Keep it restricted to the people you name or open it to your whole organization, with organization roles and resource-level access deciding who can read it and who can drive it. Public share links expose only the messages you choose. Agent runs happen in isolated sandboxes, scoped credentials attach at the egress layer, and Helios is SOC 2 Type II compliant.
[Security →](/security/)[Enterprise →](/enterprise/)
From chat to standing task
## When you want it every week, save it.
A chat that keeps earning its keep becomes a workflow. Same agent, same tools, same memory - now on a trigger.
⏰every Monday 9:00am
Do this every Monday and post the unfiled complaints to #product.
1. slack·read #support · last 7 days
2. github·search issues in helios/api
3. slack·post #product
✓Workflow created from this chat
* Runs every Monday · full run history kept
Keep going
## Where teams take it next
[WorkflowsPut an agent on the taskTurn the conversation into a standing task on a schedule, a webhook, or an integration event.](/product/workflows/)[IntegrationSlackRead channels, follow threads, post answers - with the full Slack API behind it.](/integrations/slack/)[Use caseSupport triageSee a full run: read the queue, group the themes, route what needs a human.](/use-cases/support-triage/)
## Ask an agent for something.
Start free, open a chat, and hand it the first task. Bring your team when it earns its place.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# MCP - Extend Your Agents | Helios
URL: https://www.heliosapp.com/product/mcp
Description: Attach any MCP server to give Helios agents new tools, and use Helios itself over MCP from your own clients. Auth, tool filtering, and security built in.
MCP
# MCP, in both directions.
Attach any MCP server and its tools join your agents' toolbox. Helios speaks MCP outward too, so your own clients can put Helios agents to work.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
◆plain · thread.created
When a customer escalates, check their entitlement in our internal billing service and post the answer in the thread.
1. plain·read thread · customer\_id
2. mcp · internal-billing·get\_entitlement
3. mcp · internal-billing·list\_overage\_events
4. plain·reply in thread
✓Entitlement answered in 8s
* Enterprise plan · 2 overages this cycle
* Answer posted before the customer refreshed
Attach a server
## Bring any tool that speaks MCP.
Your internal services, your vendor's server, your own scripts. If it speaks MCP, your agents can use it.
### OAuth
Point Helios at the server's authorization and token endpoints, set the scopes, and let it hold the grant for you.
### Bearer token
Paste a token. It is encrypted at rest and attached to outbound calls server-side, out of the model's reach.
### Custom headers
Some servers want their own header. Set up to twenty of them - Authorization included - and Helios sends them on every call, holding back the transport-level headers that would break the connection.
### No auth
For a public or internal server that needs no credential, attach the URL and go.
Tool filtering
## Choose exactly which tools an agent gets.
An MCP server may expose forty tools. Allow the handful your task needs and Helios refuses the rest.
Filtering happens at the proxy, before a call ever reaches the upstream server. A tool that is not on the allowlist is turned away, whatever the agent decides to try. It is the difference between handing an agent a read-only reporting tool and handing it the whole administrative surface of a system.
▶mcp · oncall · 3 of 22 tools allowed
Summarize this quarter's incidents from our internal on-call service.
1. mcp · oncall·list\_incidents · allowed
2. mcp · oncall·get\_incident · allowed
3. code·group by service · rank by minutes
4. notion·write quarterly incident review
✓Incident review drafted
* 31 incidents · 4 services account for 78% of downtime
* Write tools stayed out of reach for this run
Helios over MCP
## Your clients, our agents.
Helios is an MCP server as well as an MCP client. Reach your agents from the tools you already have open.
### Drive Helios from your client
Point an MCP client at Helios and it gains the tools Helios exposes, so you can reach your agents from wherever you already work.
### The same identity and controls
Calls over MCP carry the same authentication as calls through the app, and land against the same organization roles and resource-level access.
### One agent, many front doors
Chat, workflows, and MCP all drive the same runtime, the same tools, and the same memory.
Enterprise ready
Helios connects to MCP servers over streamable HTTP with protections against requests to internal network addresses. Server credentials - OAuth grants, bearer tokens, and custom headers - are envelope-encrypted with AES-256-GCM under keys wrapped by AWS KMS, and attach at the egress layer, so the model never handles a raw token. Tool allowlists are enforced at the proxy, and every MCP call an agent makes is recorded in the run's audit trail. Helios is SOC 2 Type II compliant.
[Security →](/security/)[Enterprise →](/enterprise/)
Keep going
## Extend from here
[GuideAttach an MCP serverWalk through connecting a server, choosing an auth method, and allowing the tools your agents should have.](/guides/attach-an-mcp-server/)[PlatformThe agent runtimeMCP tools sit alongside your integrations, your databases, and the agent's own computer.](/product/)[WorkflowsPut it on a triggerAn agent with your MCP tools, running on a schedule or the moment an event lands.](/product/workflows/)
## Hand your agents a new tool.
Start free, attach a server, allow the tools you trust, and watch an agent use them.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Workflows - Put an Agent on the Task | Helios
URL: https://www.heliosapp.com/product/workflows
Description: Describe a task in plain English and Helios runs it forever - on cron schedules, signed webhooks, integration events, or on demand. Full run history and structured outputs.
Workflows
# Put an agent on the task permanently.
A workflow is a prompt and a trigger. Describe the task once and the agent runs it forever - on a schedule, on a signed webhook, or the moment something happens in GitHub, Slack, or Plain.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
◆github · pull\_request.labeled
When a pull request is labeled \`needs-review\`, read the diff, check it against our conventions, and leave a review. Escalate to #eng-leads if it touches billing.
1. github·fetch diff for PR #2841
2. github·read CONTRIBUTING.md at head
3. code·analyze changed paths
4. github·post review · 3 inline comments
5. slack·notify #eng-leads
✓Review posted · run succeeded
* Flagged an unhandled error path in sync.ts:142
* Touches billing - escalated to #eng-leads
* Output: markdown · 41s · full trace kept
Definition
## Three things make a workflow.
Describe the task in plain English, give it the context it needs, and say when it should happen.
### A prompt
The task, written in plain English. Name the tools it should reach for, the judgment calls it should make, and the shape of the answer you want back.
### Context
Pin the GitHub repositories the task should carry, and give it variables and secrets - encrypted, and reusable across every workflow you run.
### A trigger
When the task should happen: on demand, on a schedule, on a signed webhook, or on an event from a tool your team already uses.
Triggers
## Four ways a task starts.
Pick the one that matches how the work actually arrives.
### Manual
Run it yourself, whenever. The way you test a task before you trust it to a schedule.
### Cron
Write the schedule the way you would say it - "every weekday at 8am, New York time" - and Helios turns it into a cron expression for you.
### Webhook
Call the workflow from your own systems. Every request is signature-verified with a shared secret you can rotate on demand.
### Integration events
React the moment something happens in GitHub, Slack, or Plain - with filters so only the events you care about wake the agent.
Integration events
## React to what happens in your tools.
Filters run before the agent does. Match on a repository, a label, a branch, or a channel, and only the events that pass wake a run.
### GitHub
Pull requests opened, closed, synchronized, or labeled. Issues opened, closed, or labeled. Pushes, tags, releases, comments, and finished Actions runs. Filter by repository, branch, or label.
### Slack
Messages in a public or private channel, filtered to the channel you name - so an agent watches #support and nothing else.
### Plain
A thread is created or a customer replies, so an agent can triage the conversation before anyone opens the queue.
Enterprise ready
Webhook triggers are verified with an HMAC signature over the request body and a timestamp, so a replayed or forged call is rejected before an agent starts. Rotate a webhook secret whenever you need to. Every run executes in an isolated sandbox with scoped credentials attached at the egress layer, and its trigger, tool calls, and output are kept as an audit trail. Helios is SOC 2 Type II compliant.
[Security →](/security/)[Enterprise →](/enterprise/)
Runs
## Every run leaves a record.
See what fired the task, which tools the agent reached for, what it produced, and how long it took.
A run moves from queued to running, then lands as succeeded, failed, or cancelled. Open any run to replay the trigger payload and the steps the agent took to get to its answer. Results come back typed - as markdown, plain text, or JSON - so whatever reads the output next knows what it is holding.
⏰daily 2:00am UTC
Every night, check yesterday's failed CI runs and file an issue for anything that failed twice.
1. github·list workflow\_runs · conclusion=failure
2. code·group by job · find repeats
3. github·open issue · label=flaky
✓Run succeeded · 1m 12s
* 2 repeat failures · 1 issue filed, 1 already open
* Output: json · handed to the on-call dashboard
Keep going
## Tasks teams already hand off
[Use casePR review & digestAn agent reviews every pull request as it opens and digests the week for the people who missed it.](/use-cases/pr-review-digest/)[IntegrationGitHubThe full GitHub API plus the event catalog that wakes an agent the moment a PR lands.](/integrations/github/)[MCPExtend the toolboxAttach an MCP server and your workflows gain tools of your own - your internal services, your vendor's server.](/product/mcp/)
## Describe the task once.
Start free, write the prompt, pick the trigger, and let the agent hold the task from here.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Security - Built for Trust | Helios
URL: https://www.heliosapp.com/security
Description: SOC 2 Type II. Isolated sandboxes per agent, envelope-encrypted secrets, signed webhooks, SSO and SCIM, resource-level roles, and server-side credential handling.
Security
# Built for trust
An agent that can run code, read your database, and act in your tools has to be worth trusting with all three. This page describes how Helios isolates agents, where credentials live, how secrets are encrypted, and what your administrators control.
* SOC 2 Type II
* GDPR
* Sandbox isolation per run
Architecture
## Every agent works on its own computer
A Helios agent is a process on a real machine, and that machine is the security boundary. Everything an agent does - the code it runs, the files it writes, the calls it makes - happens inside a sandbox that exists for one run and then goes away.
One sandbox per run
Every run of every agent starts in a fresh cloud sandbox with its own filesystem, its own processes, and its own network egress. Code the agent writes, packages it installs, and files it downloads all live inside that boundary and go away with it.
Isolation between runs
Two runs never share a machine. A run cannot read another run's files, reach another run's processes, or inherit anything a previous agent left behind. The blast radius of a bad instruction is one sandbox.
No inbound traffic
Sandboxes are created with public traffic switched off. An agent reaches out to do its work; nothing on the internet reaches in.
Sandboxes run on E2B
The sandbox layer is provided by E2B, which appears on our subprocessor list alongside every other vendor that touches customer data.
State persists on purpose
What carries across runs is what you asked to carry: an agent's memory and the files in its workspace, stored durably and reattached to the next run. Nothing carries over as a side effect of a machine being reused, because the machine is not reused.
Lifecycle events are recorded
Sandbox creation, pause, resume, and shutdown arrive over signature-verified webhooks and land in an audit table, tagged with the run and organization that caused them.
Credentials
## Agents use your tools without holding 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 being trusted with the credential itself.
Credentials live server-side
When you connect Slack or GitHub or Stripe, the credential is stored by Helios. Agents call those APIs through Helios, which attaches the credential at the edge of the request. The token stays on our side of the line.
The model does not hold your tokens
An agent asks Helios to call an endpoint. Helios makes the call. What comes back to the agent is the response, not the key that unlocked it - so a token cannot leak into a prompt, a log line, or a file the agent wrote.
Even direct calls are credential-free
Some tasks need to talk to a host straight from the sandbox. For those, Helios attaches the credential to the run's outbound requests at the network layer, scoped to the specific host it was pinned to and set to expire. The agent's code makes the request. It still never holds the key.
The model sees a redacted config
When an agent inspects how an integration is configured, the encrypted fields are stripped before the description ever reaches the model. It learns that an integration is authenticated, not what authenticated it.
Envelope-encrypted secrets
Every secret you store is encrypted with AES-256-GCM under its own data encryption key, and that key is itself wrapped by a master key in AWS KMS. One wrapped key opens one secret. Rotating or revoking a secret touches nothing else.
Data controls
## You decide what an agent can reach
Access is scoped in layers, and the layers compose: the credential Helios holds, the project the agent lives in, and the specific resources it has been pinned to.
Scoped variables and secrets
A variable or secret belongs to the whole organization, to a single project, or to one task. A project's agents see the project's values and the organization's values, and nothing belonging to a project they were not put in.
Pinned integration resources
Pin a specific GitHub repository to an agent, and that is the codebase it works with. The reach of a task becomes a decision somebody made, written down, rather than whatever the credential happened to allow.
Databases on your terms
Connect Postgres, MySQL, or ClickHouse, optionally through an SSH tunnel, with the database user you choose. If that user can only read one schema, that is what the agent can do.
Memory belongs to the agent that earned it
What an agent learns across runs is stored against that agent and reattached to its next run, so context compounds where the work happens.
Identity & access
## Two layers of roles, one source of truth
Who someone is comes from your identity provider. What they can touch is decided twice: once for the organization, and again for each resource inside it.
SAML 2.0 and OIDC
Connect the identity provider you already run. JumpCloud customers are in production today, and any provider that speaks SAML 2.0 or OIDC will connect. Administrators configure it themselves, from organization settings.
Just-in-time provisioning
The first sign-in through your provider creates the account, in the right organization, with the role you assigned. No invitations to chase.
SCIM
Helios follows your directory. Create a user there and the account appears here; deactivate them there and their access ends here.
Resource visibility
Every resource is either restricted to the people it has been shared with, or visible to the whole organization. You choose per resource.
| Scope | Role | What it allows |
| ------------ | ------ | ---------------------------------------------------------------------------- |
| Organization | Admin | Runs the organization: identity, members, billing, and every resource in it. |
| Organization | Member | Creates agents, connects integrations, and runs work. |
| Organization | Viewer | Reads what has been shared with them, and changes nothing. |
| Resource | Admin | Owns this agent, project, or integration - including who else gets access. |
| Resource | Editor | Changes how this resource works, and runs it. |
| Resource | User | Runs this resource and reads its output. |
Network & webhooks
## The ways in are the ways you opened
Agents accept work from the outside - a webhook fires, an MCP server answers. Each of those doorways is checked before anything walks through it.
Signed webhooks
Every webhook trigger carries an HMAC-SHA256 signature computed with a secret belonging to that webhook alone, plus a timestamp. Helios checks the signature with a timing-safe comparison and rejects anything older than five minutes, so a URL somebody found is not a way to start your tasks.
Secret rotation
Rotate a webhook secret whenever you need to. The endpoint keeps its address; only the signature changes.
MCP connections that refuse to be redirected
When you attach an external MCP server, Helios resolves and checks the destination before it connects, and again before every connection after that. The URL must be HTTPS. Loopback and localhost, private and reserved IPv4 ranges, IPv6 loopback and link-local and unique-local addresses, and the cloud metadata endpoints are all refused - so an MCP server URL cannot be aimed back at internal infrastructure.
Transport headers stay ours
You can send an MCP server the headers it needs, including Authorization, up to twenty of them. The headers that define the transport itself - host, content-length, connection, transfer-encoding, and the rest - are refused, so a server configuration cannot quietly rewrite the request underneath it.
Encryption in transit and at rest
Traffic to Helios and between Helios and your tools is encrypted in transit. Data at rest is encrypted, and secrets get a second envelope on top.
Compliance
## Certified, and specific about it
### SOC 2 Type II
Helios is SOC 2 Type II certified. The audit covers the controls behind everything on this page - how we handle access, change management, and the infrastructure your agents run on - observed over time rather than on one good day.
### GDPR
We process customer data as a processor, on your instructions, in line with GDPR.
### Subprocessors
Every vendor that touches customer data is listed, with what they do and where. E2B runs the sandboxes. Model providers run the models.
[See the subprocessor list](/legal/subprocessors/)
### Your data does not train models
No data passing through Helios is used to train or improve AI models, and we hold zero data retention agreements with the model providers we work with. Your prompts, your files, and the output of your runs stay yours.
## Questions we get from security reviews
### Is our data used to train models?
### Where do agents actually run?
### Can an agent see the credentials for our integrations?
### Who in our company can see a given agent or its runs?
### How are secrets stored?
### What stops a webhook trigger from being abused?
### Can we restrict what a specific agent is allowed to touch?
### Are you SOC 2 certified?
## Bring your security review
Start an agent on a real task today, or walk the architecture through with the people who built it.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Solutions - Agents for Every Team | Helios
URL: https://www.heliosapp.com/solutions
Description: Support, sales, marketing, engineering, and operations teams hand recurring work to Helios agents - with the controls IT requires.
Solutions
# Agents for every team.
Support, sales, marketing, engineering, and operations each have work that repeats. Hand it to an agent that runs on your triggers, reaches your tools, and remembers what happened last time - with the controls IT requires.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
[SupportAn agent on the queue, around the clock.P+1](/solutions/support/)[Sales & RevOpsPipeline hygiene that happens without anyone remembering it.+2](/solutions/sales-and-revops/)[MarketingResearch, drafts, and monitoring that never stop running.+2](/solutions/marketing/)[EngineeringAn agent on every pull request, every failure, every release.+1](/solutions/engineering/)[OperationsThe reports, checks, and syncs nobody wants to own.+2](/solutions/operations/)
## Find the task your team keeps redoing.
Describe it once. An agent picks it up from there, around the clock.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# AI Agents for Engineering Teams | Helios
URL: https://www.heliosapp.com/solutions/engineering
Description: Helios agents review diffs, explain red builds, triage issues, and write the release notes. GitHub events start them the moment work happens, and each agent has a real computer to run the analysis it needs.
[← All solutions](/solutions/)
Engineering
# An agent on every pull request, every failure, every release.
Helios agents review diffs, explain red builds, triage issues, and write the release notes. GitHub events start them the moment work happens, and each agent has a real computer to run the analysis it needs.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The tasks
## Work your engineering team can hand off
Task 01
### Review every pull request as it opens
The agent reads the diff, checks it against your conventions, and leaves a review with concrete suggestions before a human opens the tab.
* [GitHub](/integrations/github/)
* [Slack](/integrations/slack/)
◆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 analysis over the changed files
4. github·post a 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 the migration is backward compatible
Task 02
### Explain a red build
When a workflow run finishes red, the agent pulls the logs, isolates the first real failure, and posts a plain-English explanation with the likely cause.
* [GitHub](/integrations/github/)
* [Slack](/integrations/slack/)
◆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 the step logs
3. code·isolate the first failing assertion
4. slack·post the 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
Task 03
### Draft the incident write-up
After an incident, the agent reconstructs the timeline from the channel and the commits, and drafts a postmortem with the facts already assembled.
* [Slack](/integrations/slack/)
* [GitHub](/integrations/github/)
* [Notion](/integrations/notion/)
Draft a postmortem from the #incident channel and the deploys around it.
1. slack·read #incident-2025-03-06 in full
2. github·list deploys and reverts in the window
3. code·build the timeline
4. notion·create the postmortem draft
✓Postmortem drafted
* 41-minute impact window reconstructed
* Triggering deploy identified as #2833
* 5 action items pulled from the discussion
Task 04
### Keep an eye on CI cost and speed
A weekly agent attributes build spend to the workflows driving it, finds the jobs that got slower, and names the change that did it.
* [WarpBuild](/integrations/warpbuild/)
* [GitHub](/integrations/github/)
* [Slack](/integrations/slack/)
⏰Mondays at 7:00am
Weekly, report CI spend and the jobs that got slower.
1. warpbuild·pull last week's job and spend data
2. github·find the PRs that changed those workflows
3. code·attribute spend and correlate slowdowns
4. slack·post the report to #platform
✓CI spend · week of Mar 3
* $3,140 total · up 12% week over week
* \`e2e\` p95 rose from 8m to 19m after #2790
* One workflow doubled after a matrix change
Task 05
### Ship the release notes with the release
On every tag the agent walks the merged work, groups it by theme, and publishes notes to GitHub and your docs.
* [GitHub](/integrations/github/)
* [Notion](/integrations/notion/)
◆github · tag.created
When a tag is created, draft release notes and publish them.
1. github·compare v2.7.0...v2.8.0
2. github·publish the draft release
3. notion·create the changelog entry
✓v2.8.0 notes published
* Features - 6 entries, led by scheduled exports
* Fixes - 11 entries, grouped by area
* Breaking - 1 entry, with a migration snippet
Reach
## The tools engineering agents reach for
Each agent gets the complete API of every service you connect, with credentials attached server-side.
* [GitHub](/integrations/github/)
* [Slack](/integrations/slack/)
* [WarpBuild](/integrations/warpbuild/)
* [Notion](/integrations/notion/)
* [Databases](/integrations/databases/)
* [Discord](/integrations/discord/)
Controls
## Everyone delegates. IT stays in control.
Agents run in isolated cloud sandboxes, one per run, with no path to each other. GitHub credentials are envelope-encrypted and scoped to the repositories you choose, webhook triggers are signed with a secret you can rotate, and org roles decide who may edit a workflow that comments on your pull requests.
[Enterprise →](/enterprise/)[Security →](/security/)
* SAML and OIDC SSO with SCIM provisioning
* Org roles and resource-level sharing
* Envelope-encrypted secrets, handled server-side
* SOC 2 Type II, with an isolated sandbox per agent
Use cases
## Engineering tasks in detail
[PR review & digestAn agent reads each diff against your conventions and leaves a real review. A second agent summarizes the week: what merged, what is waiting, and how CI is holding up.](/use-cases/pr-review-digest/)[Incident summariesAn agent reconstructs the timeline from your incident channel and the deploys around it, identifies the triggering change, and drafts the write-up with the facts already assembled.](/use-cases/incident-summaries/)
Templates
## Start from a working agent
Every template ships with the prompt, the trigger, and the integrations it needs.
[EngineeringPull request reviewerReviews every pull request against your conventions, leaves inline comments, and posts a weekly digest of review load and CI health.◆github · pull\_request.opened](/templates/pr-review-digest/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.◆github · tag.created](/templates/github-release-notes/)[EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup so nobody has to attend one.⏰Weekdays at 9:00am](/templates/daily-standup-digest/)[EngineeringIncident postmortem drafterReconstructs the incident timeline from Slack and GitHub, names the triggering change, and drafts the write-up in Notion.▶Run on demand](/templates/incident-postmortem-drafter/)[EngineeringCI cost & speed reportAttributes build spend to the workflows driving it, finds the jobs that got slower, and names the change responsible.⏰Mondays at 7:00am](/templates/warpbuild-ci-cost-report/)
Guides
## Get the first one running
[12 minReact to GitHub eventsStart an agent the moment a pull request opens, a build goes red, or a tag lands - filtered down to exactly the events you want it on.](/guides/react-to-github-events/)[10 minAttach an MCP serverBring your own tools. Point Helios at any MCP server, choose which of its tools agents may call, and they become part of the agent's reach.](/guides/attach-an-mcp-server/)[10 minRun your first agentDescribe a task in plain English, give the agent a tool to reach for, and watch it work. Ten minutes from an empty workspace to a run you can read end to end.](/guides/run-your-first-agent/)
## Give your engineering team an agent.
Describe the task in plain English, attach a trigger, and let it work while you sleep.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# AI Agents for Marketing Teams | Helios
URL: https://www.heliosapp.com/solutions/marketing
Description: Helios agents read the web, watch the communities where your customers gather, keep competitive intelligence current, and turn a rough outline into a real draft. Each agent has a computer, so it collects the data and does the analysis in the same run.
[← All solutions](/solutions/)
Marketing
# Research, drafts, and monitoring that never stop running.
Helios agents read the web, watch the communities where your customers gather, keep competitive intelligence current, and turn a rough outline into a real draft. Each agent has a computer, so it collects the data and does the analysis in the same run.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The tasks
## Work your marketing team can hand off
Task 01
### Draft from live research
Hand an agent a topic. It searches the web, reads what it finds, and returns a sourced draft in a document your team can edit.
* [Google Docs](/integrations/google-docs/)
* [Apify](/integrations/apify/)
* [Slack](/integrations/slack/)
Research how growing teams evaluate SOC 2 tooling and draft a brief.
1. web·search and read 14 sources
2. code·outline and cluster the findings
3. google-docs·write the brief with citations
4. slack·share the draft in #marketing
✓\`SOC 2 Buyer's Brief\` created
* 1,900 words across 5 sections
* Every claim linked to a source
* Timeline and cost table included
Task 02
### Watch every place your brand comes up
An agent sweeps Reddit and your Discord for mentions, judges which threads deserve an answer, and posts the shortlist to your team.
* [Reddit](/integrations/reddit/)
* [Discord](/integrations/discord/)
* [Slack](/integrations/slack/)
⏰Every 4 hours
Every few hours, find brand mentions and flag the ones worth answering.
1. reddit·search 8 subreddits for brand terms
2. discord·read new #help 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
Task 03
### Keep competitive intelligence current
A weekly agent scrapes competitor pricing and changelogs, diffs them against last week, and reports only what actually changed.
* [Apify](/integrations/apify/)
* [Notion](/integrations/notion/)
* [Slack](/integrations/slack/)
⏰Mondays at 6:00am
Weekly, scrape competitor pricing and changelogs and report changes.
1. apify·scrape 9 pricing pages and 5 changelogs
2. code·diff against last week's snapshot
3. notion·append to \`Competitive Intel\`
4. slack·post the changes to #competitive
✓2 pricing changes, 3 new features
* Competitor A raised its team tier to $29/seat
* Competitor B added a usage-based plan
* Competitor C shipped SAML SSO
Task 04
### Turn the community into product feedback
The agent mines scattered complaints and wishes across Reddit and Discord into structured, deduplicated entries your product team reads.
* [Reddit](/integrations/reddit/)
* [Discord](/integrations/discord/)
* [Notion](/integrations/notion/)
⏰Monthly on the 1st
Monthly, extract feature requests from the community and file them.
1. reddit·collect a month of brand mentions
2. discord·read a month of #feedback
3. code·extract and dedupe requests
4. notion·create rows in \`Feedback\`
✓9 requests filed
* Ranked by how often each came up
* 3 match existing roadmap items and were linked
Reach
## The tools marketing agents reach for
Each agent gets the complete API of every service you connect, with credentials attached server-side.
* [Apify](/integrations/apify/)
* [Reddit](/integrations/reddit/)
* [Discord](/integrations/discord/)
* [Notion](/integrations/notion/)
* [Google Docs](/integrations/google-docs/)
* [Resend](/integrations/resend/)
* [Typeform](/integrations/typeform/)
Controls
## Everyone delegates. IT stays in control.
Marketing agents work with public data and your own drafts, and the same controls apply. Workflows carry a visibility setting, roles decide who can edit an agent, and secrets stay envelope-encrypted so an API key for a scraping service never lands in a prompt.
[Enterprise →](/enterprise/)[Security →](/security/)
* SAML and OIDC SSO with SCIM provisioning
* Org roles and resource-level sharing
* Envelope-encrypted secrets, handled server-side
* SOC 2 Type II, with an isolated sandbox per agent
Use cases
## Marketing tasks in detail
[Content pipelineAn agent searches the web, reads what it finds, and writes a sourced draft into a real document. Give it your voice and your prior work, and the first draft already sounds like you.](/use-cases/content-pipeline/)[Form routingA response arrives and an agent reads what the person wrote, enriches their company, decides where it belongs, and files it - as a deal, a support thread, or a reply within minutes.P+1](/use-cases/form-routing/)[Community monitoringAn agent sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space, judges which threads deserve an answer, and brings them to your team.](/use-cases/community-monitoring/)
Templates
## Start from a working agent
Every template ships with the prompt, the trigger, and the integrations it needs.
[MarketingReddit brand monitorSweeps the subreddits where your customers gather, judges which threads deserve a reply, and brings you a shortlist.⏰Every 4 hours](/templates/reddit-brand-monitor/)[MarketingCompetitor pricing & changelog watchScrapes competitor pricing pages and changelogs every week and reports only what actually changed.⏰Mondays at 6:00am](/templates/apify-competitor-scraper/)[MarketingSEO keyword briefReads what already ranks for a keyword, finds what everyone missed, and writes a brief your writer can work from.▶Run on demand](/templates/seo-keyword-brief/)[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](/templates/google-docs-brief-writer/)[MarketingDiscord community digestReads every channel each evening, surfaces unanswered questions, and files real bug reports as GitHub issues.⏰Daily at 7:00pm](/templates/discord-community-digest/)
Guides
## Get the first one running
[10 minRun your first agentDescribe a task in plain English, give the agent a tool to reach for, and watch it work. Ten minutes from an empty workspace to a run you can read end to end.](/guides/run-your-first-agent/)[8 minPut an agent on a scheduleTurn a working prompt into a standing task. Describe the cadence the way you would say it out loud, and Helios writes the cron expression for you.](/guides/put-an-agent-on-a-schedule/)[7 minPin repositories as contextGive an agent standing context: pin a GitHub repository and the agent carries it into every run without being told again.](/guides/pin-context-resources/)
## Give your marketing team an agent.
Describe the task in plain English, attach a trigger, and let it work while you sleep.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# AI Agents for Operations Teams | Helios
URL: https://www.heliosapp.com/solutions/operations
Description: Helios agents query your databases, reconcile your systems, run the nightly checks, and put the numbers where your team already looks. Describe the task once and it runs every morning without a person in the loop.
[← All solutions](/solutions/)
Operations
# The reports, checks, and syncs nobody wants to own.
Helios agents query your databases, reconcile your systems, run the nightly checks, and put the numbers where your team already looks. Describe the task once and it runs every morning without a person in the loop.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The tasks
## Work your operations team can hand off
Task 01
### Publish the morning report
The agent runs the queries, computes the derived metrics, calls out what looks unusual, and posts a report people read instead of a dashboard nobody opens.
* [Databases](/integrations/databases/)
* [Slack](/integrations/slack/)
⏰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 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
Task 02
### Run the nightly data quality checks
The agent checks the invariants you care about. When one breaks it says which rows, since when, and what ran upstream.
* [Databases](/integrations/databases/)
* [Resend](/integrations/resend/)
⏰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
Task 03
### Reconcile billing against your own records
The agent compares what Stripe billed with what your system says it should have billed, and reports every mismatch with the invoice id.
* [Stripe](/integrations/stripe/)
* [Databases](/integrations/databases/)
* [Google Sheets](/integrations/google-sheets/)
⏰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 against recorded usage
4. google-sheets·write the reconciliation tab
✓5 mismatches found
* 2 accounts under-billed by $1,180 total
* 3 accounts billed for a cancelled add-on
* Everything else matches
Task 04
### Keep the systems in sync
Product usage becomes CRM fields, spreadsheet rows, or an email. The agent handles the shape change in code and writes it where it belongs.
* [Databases](/integrations/databases/)
* [Attio](/integrations/attio/)
⏰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
Task 05
### Keep files and access tidy
A scheduled agent sweeps shared folders for files exposed beyond your domain and reports each one with its sharing settings.
* [Google Drive](/integrations/google-drive/)
* [Slack](/integrations/slack/)
⏰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
Reach
## The tools operations agents reach for
Each agent gets the complete API of every service you connect, with credentials attached server-side.
* [Databases](/integrations/databases/)
* [Stripe](/integrations/stripe/)
* [Google Sheets](/integrations/google-sheets/)
* [Google Drive](/integrations/google-drive/)
* [Slack](/integrations/slack/)
* [Resend](/integrations/resend/)
* [Attio](/integrations/attio/)
Controls
## Everyone delegates. IT stays in control.
Operations agents touch your most sensitive systems, so the controls sit where they belong. Database credentials are envelope-encrypted and can reach private networks over an SSH tunnel; read-only roles make a reporting agent incapable of writing; org roles and resource visibility decide who can run or edit each task.
[Enterprise →](/enterprise/)[Security →](/security/)
* SAML and OIDC SSO with SCIM provisioning
* Org roles and resource-level sharing
* Envelope-encrypted secrets, handled server-side
* SOC 2 Type II, with an isolated sandbox per agent
Use cases
## Operations tasks in detail
[Database reportingAn agent introspects your schema, writes the SQL, runs it, analyzes the results in its own sandbox, and posts a report your team reads - instead of a dashboard nobody opens.](/use-cases/database-reporting/)[Billing operationsAn agent watches Stripe for failed charges and starts recovery, reconciles what you billed against what your own system recorded, and reports the revenue numbers every morning.](/use-cases/billing-ops/)[Weekly digestsAn agent reads a week of activity across the tools your team uses, separates decisions from chatter, and posts a digest people actually read.](/use-cases/weekly-digests/)
Templates
## Start from a working agent
Every template ships with the prompt, the trigger, and the integrations it needs.
[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)[OperationsNightly data quality checksRuns your invariants against production every night and tells the on-call analyst which rows broke and since when.⏰Nightly at 3:00am](/templates/database-health-check/)[OperationsKPI sheet refreshPulls from the warehouse every morning and writes the finished tables into the sheet leadership already opens.⏰Daily at 6:00am](/templates/google-sheets-kpi-sync/)[OperationsDrive organizer & access auditFiles loose documents by what they actually contain, and reports anything shared beyond your domain.⏰Sundays at 8:00pm](/templates/google-drive-file-organizer/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.⏰Mondays at 7:00amP](/templates/churn-risk-watchlist/)
Guides
## Get the first one running
[10 minConnect a databaseGive an agent Postgres, MySQL, or ClickHouse. It introspects the schema, writes real SQL, and reasons over the results in its own sandbox.](/guides/connect-a-database/)[8 minPut an agent on a scheduleTurn a working prompt into a standing task. Describe the cadence the way you would say it out loud, and Helios writes the cron expression for you.](/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, and both are scoped to the level where they belong.](/guides/use-secrets-and-variables/)
## Give your operations team an agent.
Describe the task in plain English, attach a trigger, and let it work while you sleep.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# AI Agents for Sales & RevOps Teams | Helios
URL: https://www.heliosapp.com/solutions/sales-and-revops
Description: Helios agents enrich every lead as it arrives, keep the CRM honest, brief reps before their calls, and recover the revenue that quietly slips away. The work runs on schedules and events, so your team sells while the busywork takes care of itself.
[← All solutions](/solutions/)
Sales & RevOps
# Pipeline hygiene that happens without anyone remembering it.
Helios agents enrich every lead as it arrives, keep the CRM honest, brief reps before their calls, and recover the revenue that quietly slips away. The work runs on schedules and events, so your team sells while the busywork takes care of itself.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The tasks
## Work your sales & revops team can hand off
Task 01
### Enrich and route inbound within the minute
A form fills or a signup lands. The agent enriches the person and company, scores fit against your definition of a good customer, and routes it to an owner with a summary.
* [Typeform](/integrations/typeform/)
* [Apollo](/integrations/apollo/)
* [Attio](/integrations/attio/)
* [Slack](/integrations/slack/)
⇄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 in 90 seconds
* Northwind · 240 employees · Series B
* Fit score 87 · assigned to @dana
* Their stated use case summarized on the deal
Task 02
### Keep the CRM clean every night
An overnight agent merges duplicates, fills missing firmographics, and flags deals that have gone quiet, writing a note that explains each change.
* [Attio](/integrations/attio/)
* [Apollo](/integrations/apollo/)
⏰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·flag deals with no activity in 21 days
✓CRM hygiene pass complete
* 61 records enriched
* 9 duplicates merged
* 14 deals flagged stale for their owners
Task 03
### Brief every rep before the call
Each morning the agent assembles usage, billing health, support history, and recent news into a briefing note on the account record.
* [Attio](/integrations/attio/)
* [Databases](/integrations/databases/)
* [Stripe](/integrations/stripe/)
⏰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 the 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
Task 04
### Recover the revenue that slips
When a payment fails, the agent reaches the right contact with a working link and tells the account owner before the customer churns.
* [Stripe](/integrations/stripe/)
* [Attio](/integrations/attio/)
* [Resend](/integrations/resend/)
* [Slack](/integrations/slack/)
⏰Hourly
Every hour, find failed charges and start recovery.
1. stripe·list failed charges in the last hour
2. attio·look up the account owner and contact
3. resend·send a payment update email
4. slack·notify the 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
Task 05
### Build target lists from a description
Describe the accounts you want in a sentence. The agent searches, verifies each company against its own website, and hands back a list with a reason to reach out.
* [Apollo](/integrations/apollo/)
* [Google Sheets](/integrations/google-sheets/)
* [Attio](/integrations/attio/)
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
Reach
## The tools sales & revops agents reach for
Each agent gets the complete API of every service you connect, with credentials attached server-side.
* [Attio](/integrations/attio/)
* [Apollo](/integrations/apollo/)
* [Stripe](/integrations/stripe/)
* [Typeform](/integrations/typeform/)
* [Resend](/integrations/resend/)
* [Databases](/integrations/databases/)
* [Gmail](/integrations/gmail/)
Controls
## Everyone delegates. IT stays in control.
Revenue data stays under your admins' control. Give reporting agents read-only Stripe keys, scope CRM credentials to the objects a task touches, and use resource visibility so a pipeline workflow stays with the revenue team. Every field an agent writes is traceable to the run that wrote it.
[Enterprise →](/enterprise/)[Security →](/security/)
* SAML and OIDC SSO with SCIM provisioning
* Org roles and resource-level sharing
* Envelope-encrypted secrets, handled server-side
* SOC 2 Type II, with an isolated sandbox per agent
Use cases
## Sales & RevOps tasks in detail
[Lead enrichmentWhen someone signs up or fills a form, an agent enriches the person and their company, scores fit against your definition of a good customer, creates the CRM record, and tells the right rep.](/use-cases/lead-enrichment/)[Email outreachAn agent finds the threads that went quiet, reads the conversation, and drafts a follow-up grounded in the last real next step. Onboarding sequences read the account before they send.](/use-cases/email-outreach/)[CRM data syncAn agent computes usage from your database, joins it with billing health and support volume, and writes the result onto the account record every night.P](/use-cases/crm-data-sync/)
Templates
## Start from a working agent
Every template ships with the prompt, the trigger, and the integrations it needs.
[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](/templates/apollo-lead-enrichment/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing firmographics, and flags deals that have gone quiet - every night, without anyone remembering.⏰Nightly at 2:00am](/templates/attio-crm-hygiene/)[Sales & RevOpsTypeform lead routerReads each form response, enriches the company, routes it to sales or support, and replies while the person still has your tab open.⇄Typeform response webhookP+1](/templates/typeform-lead-router/)[Sales & RevOpsFailed payment recoveryFinds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.⏰Hourly](/templates/stripe-failed-payment-recovery/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.⏰Mondays at 7:00amP](/templates/churn-risk-watchlist/)
Guides
## Get the first one running
[10 minRun your first agentDescribe a task in plain English, give the agent a tool to reach for, and watch it work. Ten minutes from an empty workspace to a run you can read end to end.](/guides/run-your-first-agent/)[8 minPut an agent on a scheduleTurn a working prompt into a standing task. Describe the cadence the way you would say it out loud, and Helios writes the cron expression for you.](/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, and both are scoped to the level where they belong.](/guides/use-secrets-and-variables/)
## Give your sales & revops team an agent.
Describe the task in plain English, attach a trigger, and let it work while you sleep.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# AI Agents for Support Teams | Helios
URL: https://www.heliosapp.com/solutions/support
Description: Helios agents read every incoming thread, identify the customer, check their plan and their history, and draft an answer grounded in your docs. Your team arrives to a triaged queue and spends its day on the conversations that need a person.
[← All solutions](/solutions/)
Support
# An agent on the queue, around the clock.
Helios agents read every incoming thread, identify the customer, check their plan and their history, and draft an answer grounded in your docs. Your team arrives to a triaged queue and spends its day on the conversations that need a person.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The tasks
## Work your support team can hand off
Task 01
### Triage every thread as it lands
The moment a customer writes in, an agent labels the thread, sets priority from the account tier, and leaves an internal note with everything the responder needs.
* [PPlain](/integrations/plain/)
* [Stripe](/integrations/stripe/)
* [Notion](/integrations/notion/)
◆plain · thread.created
On each new thread: identify the customer, label, set priority, and draft a reply.
1. plain·read thread and customer record
2. stripe·check plan and payment health
3. notion·search the help center
4. plain·label, prioritize, and draft a reply
✓Thread triaged in 22 seconds
* Labeled \`billing\` · priority \`high\` (Enterprise)
* Draft reply cites the invoice settings doc
* Internal note names Tuesday's failed charge
Task 02
### Answer the questions you have answered before
An agent searches resolved threads and your documentation, replies when it is confident, and escalates the rest with a summary attached.
* [Slack](/integrations/slack/)
* [PPlain](/integrations/plain/)
* [Notion](/integrations/notion/)
◆slack · new message in #support
Answer questions we have resolved before; escalate anything new.
1. slack·read the question in thread
2. plain·search resolved threads for a match
3. notion·read the referenced doc
4. slack·reply in thread with the answer
✓Answered in thread
* Matched 3 prior threads on SSO group mapping
* Replied with steps and a doc link
* Left the sources in an internal note
Task 03
### Escalate the accounts that matter
When a high-value customer is unhappy, the agent assembles the account context and pages the owner before anyone has to notice.
* [PPlain](/integrations/plain/)
* [Attio](/integrations/attio/)
* [Slack](/integrations/slack/)
◆plain · 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
Task 04
### Tell product what customers keep asking
A weekly agent clusters the queue into themes, counts them, and turns recurring pain into something the product team can act on.
* [PPlain](/integrations/plain/)
* [Notion](/integrations/notion/)
* [Slack](/integrations/slack/)
⏰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. notion·write to \`Support Themes\`
4. slack·post the summary 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
Reach
## The tools support agents reach for
Each agent gets the complete API of every service you connect, with credentials attached server-side.
* [PPlain](/integrations/plain/)
* [Slack](/integrations/slack/)
* [Notion](/integrations/notion/)
* [Stripe](/integrations/stripe/)
* [Attio](/integrations/attio/)
* [Gmail](/integrations/gmail/)
Controls
## Everyone delegates. IT stays in control.
Support agents reach customer data through credentials your admins hold. Connections are envelope-encrypted, resource visibility keeps a workflow scoped to the team that owns it, and every run leaves a full record of the calls the agent made. Start with agents that draft and label, then grant sending once the drafts earn your trust.
[Enterprise →](/enterprise/)[Security →](/security/)
* SAML and OIDC SSO with SCIM provisioning
* Org roles and resource-level sharing
* Envelope-encrypted secrets, handled server-side
* SOC 2 Type II, with an isolated sandbox per agent
Use cases
## Support tasks in detail
[Support triageAn agent reads each incoming thread the moment it arrives, identifies the customer, checks their plan and history, labels and prioritizes it, and drafts a reply grounded in your documentation.P](/use-cases/support-triage/)
Templates
## Start from a working agent
Every template ships with the prompt, the trigger, and the integrations it needs.
[SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.◆slack · new message in #supportP](/templates/slack-support-triage/)[SupportPlain thread triage & weekly themesTriages every incoming Plain thread on arrival, then clusters the week into the themes product should hear about.◆plain · thread.createdP](/templates/plain-thread-summarizer/)[SupportMorning inbox triageReads what arrived overnight, labels it, drafts the easy replies, and hands you a ranked list of what needs a human.⏰Weekdays at 7:30am](/templates/gmail-inbox-triage/)[SupportDocumentation freshness auditChecks your written docs against the actual codebase every month and comments on the pages that have gone stale.⏰Monthly on the 1st](/templates/notion-docs-freshness-audit/)
Guides
## Get the first one running
[10 minRun your first agentDescribe a task in plain English, give the agent a tool to reach for, and watch it work. Ten minutes from an empty workspace to a run you can read end to end.](/guides/run-your-first-agent/)[7 minPin repositories as contextGive an agent standing context: pin a GitHub repository and the agent carries it into every run without being told again.](/guides/pin-context-resources/)[9 minShare with your teamHand an agent to the people who need it. Roles decide who may edit, visibility decides who may see, and every run leaves a record of what happened.](/guides/share-with-your-team/)
## Give your support team an agent.
Describe the task in plain English, attach a trigger, and let it work while you sleep.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Templates - Ready-to-Run Agent Tasks | Helios
URL: https://www.heliosapp.com/templates
Description: Curated agent templates with real prompts, triggers, and integrations. Copy one, connect your tools, and put an agent on the task in minutes.
Templates
# Agents you can run today.
24 curated tasks, each with the exact prompt, the trigger that starts it, and the integrations it reaches for. Copy one, connect your tools, and it goes to work.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
## Support
04
[SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.◆slack · new message in #supportP](/templates/slack-support-triage/)[SupportPlain thread triage & weekly themesTriages every incoming Plain thread on arrival, then clusters the week into the themes product should hear about.◆plain · thread.createdP](/templates/plain-thread-summarizer/)[SupportMorning inbox triageReads what arrived overnight, labels it, drafts the easy replies, and hands you a ranked list of what needs a human.⏰Weekdays at 7:30am](/templates/gmail-inbox-triage/)[SupportDocumentation freshness auditChecks your written docs against the actual codebase every month and comments on the pages that have gone stale.⏰Monthly on the 1st](/templates/notion-docs-freshness-audit/)
## Sales & RevOps
06
[Sales & RevOpsFailed payment recoveryFinds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.⏰Hourly](/templates/stripe-failed-payment-recovery/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.⏰Mondays at 7:00amP](/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](/templates/apollo-lead-enrichment/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing firmographics, and flags deals that have gone quiet - every night, without anyone remembering.⏰Nightly at 2:00am](/templates/attio-crm-hygiene/)[Sales & RevOpsTypeform lead routerReads each form response, enriches the company, routes it to sales or support, and replies while the person still has your tab open.⇄Typeform response webhookP+1](/templates/typeform-lead-router/)[Sales & RevOpsOnboarding email that reads the accountChecks what each new account has actually set up and sends the message that helps them next, rather than the next message in a sequence.⏰Daily at 9:00am](/templates/resend-onboarding-sequence/)
## Marketing
05
[MarketingReddit brand monitorSweeps the subreddits where your customers gather, judges which threads deserve a reply, and brings you a shortlist.⏰Every 4 hours](/templates/reddit-brand-monitor/)[MarketingDiscord community digestReads every channel each evening, surfaces unanswered questions, and files real bug reports as GitHub issues.⏰Daily at 7:00pm](/templates/discord-community-digest/)[MarketingCompetitor pricing & changelog watchScrapes competitor pricing pages and changelogs every week and reports only what actually changed.⏰Mondays at 6:00am](/templates/apify-competitor-scraper/)[MarketingSEO keyword briefReads what already ranks for a keyword, finds what everyone missed, and writes a brief your writer can work from.▶Run on demand](/templates/seo-keyword-brief/)[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](/templates/google-docs-brief-writer/)
## Engineering
05
[EngineeringPull request reviewerReviews every pull request against your conventions, leaves inline comments, and posts a weekly digest of review load and CI health.◆github · pull\_request.opened](/templates/pr-review-digest/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.◆github · tag.created](/templates/github-release-notes/)[EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup so nobody has to attend one.⏰Weekdays at 9:00am](/templates/daily-standup-digest/)[EngineeringIncident postmortem drafterReconstructs the incident timeline from Slack and GitHub, names the triggering change, and drafts the write-up in Notion.▶Run on demand](/templates/incident-postmortem-drafter/)[EngineeringCI cost & speed reportAttributes build spend to the workflows driving it, finds the jobs that got slower, and names the change responsible.⏰Mondays at 7:00am](/templates/warpbuild-ci-cost-report/)
## Operations
04
[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)[OperationsKPI sheet refreshPulls from the warehouse every morning and writes the finished tables into the sheet leadership already opens.⏰Daily at 6:00am](/templates/google-sheets-kpi-sync/)[OperationsNightly data quality checksRuns your invariants against production every night and tells the on-call analyst which rows broke and since when.⏰Nightly at 3:00am](/templates/database-health-check/)[OperationsDrive organizer & access auditFiles loose documents by what they actually contain, and reports anything shared beyond your domain.⏰Sundays at 8:00pm](/templates/google-drive-file-organizer/)
## Take a template and make it yours.
The prompt is the whole configuration. Edit it in plain English and the agent follows.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Competitor pricing & changelog watch - Agent Template | Helios
URL: https://www.heliosapp.com/templates/apify-competitor-scraper
Description: Scrapes competitor pricing pages and changelogs every week and reports only what actually changed.
[← All templates](/templates/)
Marketing
# Competitor pricing & changelog watch
Scrapes competitor pricing pages and changelogs every week and reports only what actually changed.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
Every Monday at 6am, use Apify to scrape the pricing page and the changelog of each of our nine competitors. Read the results and extract, for each competitor, their plan names, prices, seat limits, and the features they list on each tier, plus any changelog entries published in the last seven days. Compare all of this against last week's snapshot, which you saved in your workspace. Report only what changed: a price move, a new or removed plan, a new feature on a tier, a shipped feature in the changelog. Save this week's snapshot for next time. Append the changes to the `Competitive Intel` database in Notion and post them to #competitive. When nothing changed, say so in one line.
Trigger
## What starts this agent
⏰Mondays at 6:00am
Runs on a schedule. Describe the cadence in plain English and Helios turns it into a cron expression for you.
### Integrations required
* [Apify](/integrations/apify/)
* [Notion](/integrations/notion/)
* [Slack](/integrations/slack/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
2 pricing changes, 3 new features
* Competitor A raised its team tier to $29/seat
* Competitor B added a usage-based plan
* Competitor C shipped SAML SSO
[Use this template](https://app.heliosapp.com/)
New to Helios? Start with [Run your first agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Content pipelineAn agent searches the web, reads what it finds, and writes a sourced draft into a real document. Give it your voice and your prior work, and the first draft already sounds like you.](/use-cases/content-pipeline/)[Community monitoringAn agent sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space, judges which threads deserve an answer, and brings them to your team.](/use-cases/community-monitoring/)
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](/templates/reddit-brand-monitor/)[MarketingSEO keyword briefReads what already ranks for a keyword, finds what everyone missed, and writes a brief your writer can work from.▶Run on demand](/templates/seo-keyword-brief/)[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](/templates/google-docs-brief-writer/)
## Run Competitor pricing & changelog watch on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Inbound lead enrichment - Agent 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
# 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/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
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 actually 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 grounded in something specific you learned about them. Assign the record to the owner for that territory.
Trigger
## What starts this agent
⇄Signup webhook
Runs when a signed webhook arrives. Helios verifies the signature and hands the payload straight to the agent.
### Integrations required
* [Apollo](/integrations/apollo/)
* [Attio](/integrations/attio/)
* [Slack](/integrations/slack/)
* [Gmail](/integrations/gmail/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
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 agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Lead enrichmentWhen someone signs up or fills a form, an agent enriches the person and their company, scores fit against your definition of a good customer, creates the CRM record, and tells the right rep.](/use-cases/lead-enrichment/)[Email outreachAn agent finds the threads that went quiet, reads the conversation, and drafts a follow-up grounded in the last real next step. Onboarding sequences read the account before they send.](/use-cases/email-outreach/)[Form routingA response arrives and an agent reads what the person wrote, enriches their company, decides where it belongs, and files it - as a deal, a support thread, or a reply within minutes.P+1](/use-cases/form-routing/)
Related templates
## Pair it with these
[Sales & RevOpsTypeform lead routerReads each form response, enriches the company, routes it to sales or support, and replies while the person still has your tab open.⇄Typeform response webhookP+1](/templates/typeform-lead-router/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing firmographics, and flags deals that have gone quiet - every night, without anyone remembering.⏰Nightly at 2:00am](/templates/attio-crm-hygiene/)[Sales & RevOpsOnboarding email that reads the accountChecks what each new account has actually set up and sends the message that helps them next, rather than the next message in a sequence.⏰Daily at 9:00am](/templates/resend-onboarding-sequence/)
## Run Inbound lead enrichment on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Nightly CRM hygiene - Agent Template | Helios
URL: https://www.heliosapp.com/templates/attio-crm-hygiene
Description: Merges duplicates, fills missing firmographics, and flags deals that have gone quiet - every night, without anyone remembering.
[← All templates](/templates/)
Sales & RevOps
# Nightly CRM hygiene
Merges duplicates, fills missing firmographics, and flags deals that have gone quiet - every night, without anyone remembering.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
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 as the survivor. Find companies missing headcount, industry, or funding stage, enrich them in Apollo, and fill only the empty fields - never overwrite a value a human 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.
Trigger
## What starts this agent
⏰Nightly at 2:00am
Runs on a schedule. Describe the cadence in plain English and Helios turns it into a cron expression for you.
### Integrations required
* [Attio](/integrations/attio/)
* [Apollo](/integrations/apollo/)
* [Slack](/integrations/slack/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
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 agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Lead enrichmentWhen someone signs up or fills a form, an agent enriches the person and their company, scores fit against your definition of a good customer, creates the CRM record, and tells the right rep.](/use-cases/lead-enrichment/)[CRM data syncAn agent computes usage from your database, joins it with billing health and support volume, and writes the result onto the account record every night.P](/use-cases/crm-data-sync/)
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](/templates/apollo-lead-enrichment/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.⏰Mondays at 7:00amP](/templates/churn-risk-watchlist/)[Sales & RevOpsTypeform lead routerReads each form response, enriches the company, routes it to sales or support, and replies while the person still has your tab open.⇄Typeform response webhookP+1](/templates/typeform-lead-router/)
## Run Nightly CRM hygiene on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Churn risk watchlist - Agent Template | Helios
URL: https://www.heliosapp.com/templates/churn-risk-watchlist
Description: Joins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.
[← All templates](/templates/)
Sales & RevOps
# Churn risk watchlist
Joins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
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.
Trigger
## What starts this agent
⏰Mondays at 7:00am
Runs on a schedule. Describe the cadence in plain English and Helios turns it into a cron expression for you.
### Integrations required
* [Stripe](/integrations/stripe/)
* [Databases](/integrations/databases/)
* [Attio](/integrations/attio/)
* [PPlain](/integrations/plain/)
* [Slack](/integrations/slack/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
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 agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Billing operationsAn agent watches Stripe for failed charges and starts recovery, reconciles what you billed against what your own system recorded, and reports the revenue numbers every morning.](/use-cases/billing-ops/)[CRM data syncAn agent computes usage from your database, joins it with billing health and support volume, and writes the result onto the account record every night.P](/use-cases/crm-data-sync/)
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](/templates/stripe-failed-payment-recovery/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing firmographics, and flags deals that have gone quiet - every night, without anyone remembering.⏰Nightly at 2:00am](/templates/attio-crm-hygiene/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)
## Run Churn risk watchlist on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Standup without the meeting - Agent Template | Helios
URL: https://www.heliosapp.com/templates/daily-standup-digest
Description: Reads yesterday's commits, merges, and review queue, then posts a standup so nobody has to attend one.
[← All templates](/templates/)
Engineering
# Standup without the meeting
Reads yesterday's commits, merges, and review queue, then posts a standup so nobody has to attend one.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
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.
Trigger
## What starts this agent
⏰Weekdays at 9:00am
Runs on a schedule. Describe the cadence in plain English and Helios turns it into a cron expression for you.
### Integrations required
* [GitHub](/integrations/github/)
* [Slack](/integrations/slack/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
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 agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[PR review & digestAn agent reads each diff against your conventions and leaves a real review. A second agent summarizes the week: what merged, what is waiting, and how CI is holding up.](/use-cases/pr-review-digest/)[Weekly digestsAn agent reads a week of activity across the tools your team uses, separates decisions from chatter, and posts a digest people actually read.](/use-cases/weekly-digests/)
Related templates
## Pair it with these
[EngineeringPull request reviewerReviews every pull request against your conventions, leaves inline comments, and posts a weekly digest of review load and CI health.◆github · pull\_request.opened](/templates/pr-review-digest/)[EngineeringCI cost & speed reportAttributes build spend to the workflows driving it, finds the jobs that got slower, and names the change responsible.⏰Mondays at 7:00am](/templates/warpbuild-ci-cost-report/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)
## Run Standup without the meeting on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Nightly data quality checks - Agent Template | Helios
URL: https://www.heliosapp.com/templates/database-health-check
Description: Runs your invariants against production every night and tells the on-call analyst which rows broke and since when.
[← All templates](/templates/)
Operations
# Nightly data quality checks
Runs your invariants against production every night and tells the on-call analyst which rows broke and since when.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
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.
Trigger
## What starts this agent
⏰Nightly at 3:00am
Runs on a schedule. Describe the cadence in plain English and Helios turns it into a cron expression for you.
### Integrations required
* [Databases](/integrations/databases/)
* [Resend](/integrations/resend/)
* [Slack](/integrations/slack/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
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 agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Database reportingAn agent introspects your schema, writes the SQL, runs it, analyzes the results in its own sandbox, and posts a report your team reads - instead of a dashboard nobody opens.](/use-cases/database-reporting/)
Related templates
## Pair it with these
[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)[OperationsKPI sheet refreshPulls from the warehouse every morning and writes the finished tables into the sheet leadership already opens.⏰Daily at 6:00am](/templates/google-sheets-kpi-sync/)[EngineeringIncident postmortem drafterReconstructs the incident timeline from Slack and GitHub, names the triggering change, and drafts the write-up in Notion.▶Run on demand](/templates/incident-postmortem-drafter/)
## Run Nightly data quality checks on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Discord community digest - Agent Template | Helios
URL: https://www.heliosapp.com/templates/discord-community-digest
Description: Reads every channel each evening, surfaces unanswered questions, and files real bug reports as GitHub issues.
[← All templates](/templates/)
Marketing
# Discord community digest
Reads every channel each evening, surfaces unanswered questions, and files real bug reports as GitHub issues.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
Every evening at 7pm, read the last 24 hours of messages across our Discord server. Write a digest for #community in Slack: how many messages, the main themes people discussed, and every question still unanswered after two hours, oldest first, with a link to each. Then look for messages that describe a real bug with enough detail to reproduce. For each one, search our GitHub repository for an existing issue. If none matches, open an issue with a clear title, the reproduction steps as the reporter described them, and a link back to the Discord thread. Reply in that thread with the issue link so the reporter knows it was heard.
Trigger
## What starts this agent
⏰Daily at 7:00pm
Runs on a schedule. Describe the cadence in plain English and Helios turns it into a cron expression for you.
### Integrations required
* [Discord](/integrations/discord/)
* [GitHub](/integrations/github/)
* [Slack](/integrations/slack/)
* [Notion](/integrations/notion/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
Community · Mar 6
* 142 messages · 4 themes
* 7 questions unanswered, oldest 9h
* 2 bug reports filed as issues
[Use this template](https://app.heliosapp.com/)
New to Helios? Start with [Run your first agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Community monitoringAn agent sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space, judges which threads deserve an answer, and brings them to your team.](/use-cases/community-monitoring/)
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](/templates/reddit-brand-monitor/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.◆github · tag.created](/templates/github-release-notes/)[SupportDocumentation freshness auditChecks your written docs against the actual codebase every month and comments on the pages that have gone stale.⏰Monthly on the 1st](/templates/notion-docs-freshness-audit/)
## Run Discord community digest on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Release notes writer - Agent Template | Helios
URL: https://www.heliosapp.com/templates/github-release-notes
Description: Turns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.
[← All templates](/templates/)
Engineering
# Release notes writer
Turns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
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 rather than a contributor to it - say what changed for them, and skip internal refactors entirely. For any breaking change, include a short migration snippet. Publish the 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.
Trigger
## What starts this agent
◆github · tag.created
Runs when the event fires in the connected service. Filter on the fields that matter so only the runs you want wake the agent.
### Integrations required
* [GitHub](/integrations/github/)
* [Notion](/integrations/notion/)
* [Slack](/integrations/slack/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
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 agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[PR review & digestAn agent reads each diff against your conventions and leaves a real review. A second agent summarizes the week: what merged, what is waiting, and how CI is holding up.](/use-cases/pr-review-digest/)
Related templates
## Pair it with these
[EngineeringPull request reviewerReviews every pull request against your conventions, leaves inline comments, and posts a weekly digest of review load and CI health.◆github · pull\_request.opened](/templates/pr-review-digest/)[MarketingDiscord community digestReads every channel each evening, surfaces unanswered questions, and files real bug reports as GitHub issues.⏰Daily at 7:00pm](/templates/discord-community-digest/)[SupportDocumentation freshness auditChecks your written docs against the actual codebase every month and comments on the pages that have gone stale.⏰Monthly on the 1st](/templates/notion-docs-freshness-audit/)
## Run Release notes writer on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Morning inbox triage - Agent Template | Helios
URL: https://www.heliosapp.com/templates/gmail-inbox-triage
Description: Reads what arrived overnight, labels it, drafts the easy replies, and hands you a ranked list of what needs a human.
[← All templates](/templates/)
Support
# Morning inbox triage
Reads what arrived overnight, labels it, drafts the easy replies, and hands you a ranked list of what needs a human.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
Every weekday at 7:30am, read every email that arrived in my inbox since yesterday morning. Group them into: needs a reply from me, can be answered with a standard response, and can be archived. Apply a Gmail label to each group. For the ones that can be answered with a standard response, write a draft reply in the thread - match my tone from my sent mail, keep it under six sentences, and leave the draft unsent. For anything that needs me, rank it by urgency and DM me the list in Slack with a one-line summary of each and why it needs my attention. Archive newsletters and automated notifications unless they mention a production incident.
Trigger
## What starts this agent
⏰Weekdays at 7:30am
Runs on a schedule. Describe the cadence in plain English and Helios turns it into a cron expression for you.
### Integrations required
* [Gmail](/integrations/gmail/)
* [Slack](/integrations/slack/)
* [Notion](/integrations/notion/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
31 messages triaged
* 4 drafts ready to review and send
* 22 labeled and archived
* 5 flagged for you, ranked by urgency
[Use this template](https://app.heliosapp.com/)
New to Helios? Start with [Run your first agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Support triageAn agent reads each incoming thread the moment it arrives, identifies the customer, checks their plan and history, labels and prioritizes it, and drafts a reply grounded in your documentation.P](/use-cases/support-triage/)[Email outreachAn agent finds the threads that went quiet, reads the conversation, and drafts a follow-up grounded in the last real next step. Onboarding sequences read the account before they send.](/use-cases/email-outreach/)
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 · new message in #supportP](/templates/slack-support-triage/)[SupportPlain thread triage & weekly themesTriages every incoming Plain thread on arrival, then clusters the week into the themes product should hear about.◆plain · thread.createdP](/templates/plain-thread-summarizer/)[Sales & RevOpsOnboarding email that reads the accountChecks what each new account has actually set up and sends the message that helps them next, rather than the next message in a sequence.⏰Daily at 9:00am](/templates/resend-onboarding-sequence/)
## Run Morning inbox triage on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Research brief writer - Agent 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
# 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/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
I will give you a topic. Search the web and read at least a dozen credible sources, preferring 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 rather than filling the gap. Share the doc to the marketing folder and post the link in #marketing.
Trigger
## What starts this agent
▶Run on demand
Runs when you ask for it, from the app, from chat, or over the API.
### Integrations required
* [Google Docs](/integrations/google-docs/)
* [Google Drive](/integrations/google-drive/)
* [Apify](/integrations/apify/)
* [Slack](/integrations/slack/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
\`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 agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Content pipelineAn agent searches the web, reads what it finds, and writes a sourced draft into a real document. Give it your voice and your prior work, and the first draft already sounds like you.](/use-cases/content-pipeline/)
Related templates
## Pair it with these
[MarketingSEO keyword briefReads what already ranks for a keyword, finds what everyone missed, and writes a brief your writer can work from.▶Run on demand](/templates/seo-keyword-brief/)[MarketingCompetitor pricing & changelog watchScrapes competitor pricing pages and changelogs every week and reports only what actually changed.⏰Mondays at 6:00am](/templates/apify-competitor-scraper/)[SupportDocumentation freshness auditChecks your written docs against the actual codebase every month and comments on the pages that have gone stale.⏰Monthly on the 1st](/templates/notion-docs-freshness-audit/)
## Run Research brief writer on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Drive organizer & access audit - Agent Template | Helios
URL: https://www.heliosapp.com/templates/google-drive-file-organizer
Description: Files loose documents by what they actually contain, and reports anything shared beyond your domain.
[← All templates](/templates/)
Operations
# Drive organizer & access audit
Files loose documents by what they actually contain, and reports anything shared beyond your domain.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
Every Sunday at 8pm, do two things with our Google Drive. First, look at everything in the `Shared Uploads` folder, read enough of each file to know what it is, propose a folder structure by document type and year, create those folders, and move the files. Never delete anything; group near-duplicates into a `Review` folder instead. Second, audit the `Finance` folder: list every file whose sharing settings allow anyone with the link, or grant access to an email address outside our domain. DM the finance lead in Slack with that list, the sharing setting on each file, and a suggested revocation. Post a summary of the organizing work to #ops.
Trigger
## What starts this agent
⏰Sundays at 8:00pm
Runs on a schedule. Describe the cadence in plain English and Helios turns it into a cron expression for you.
### Integrations required
* [Google Drive](/integrations/google-drive/)
* [Slack](/integrations/slack/)
* [Google Sheets](/integrations/google-sheets/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
340 files organized · 3 shared externally
* 7 folders created by document type
* 1 file open to anyone with the link
* 2 shared with a former contractor
[Use this template](https://app.heliosapp.com/)
New to Helios? Start with [Run your first agent](/guides/run-your-first-agent/).
Related templates
## Pair it with these
[OperationsKPI sheet refreshPulls from the warehouse every morning and writes the finished tables into the sheet leadership already opens.⏰Daily at 6:00am](/templates/google-sheets-kpi-sync/)[SupportDocumentation freshness auditChecks your written docs against the actual codebase every month and comments on the pages that have gone stale.⏰Monthly on the 1st](/templates/notion-docs-freshness-audit/)[SupportMorning inbox triageReads what arrived overnight, labels it, drafts the easy replies, and hands you a ranked list of what needs a human.⏰Weekdays at 7:30am](/templates/gmail-inbox-triage/)
## Run Drive organizer & access audit on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# KPI sheet refresh - Agent Template | Helios
URL: https://www.heliosapp.com/templates/google-sheets-kpi-sync
Description: Pulls from the warehouse every morning and writes the finished tables into the sheet leadership already opens.
[← All templates](/templates/)
Operations
# KPI sheet refresh
Pulls from the warehouse every morning and writes the finished tables into the sheet leadership already opens.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
Every morning at 6am, refresh our KPI spreadsheet. Query Postgres and ClickHouse for signups, activation rate, weekly active accounts, MRR, and net revenue retention, each for yesterday and for the trailing 7 and 28 days. Write the results into the `KPIs` tab, one row per day, appending rather than overwriting history. Preserve the existing formatting and the charts that reference the range. If any metric moved more than 20% against its 28-day average, add a note in the `Anomalies` tab with the metric, the values, and the date. Then reconcile the revenue figure against Stripe and flag any difference greater than $100.
Trigger
## What starts this agent
⏰Daily at 6:00am
Runs on a schedule. Describe the cadence in plain English and Helios turns it into a cron expression for you.
### Integrations required
* [Google Sheets](/integrations/google-sheets/)
* [Databases](/integrations/databases/)
* [Stripe](/integrations/stripe/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
KPI sheet updated
* Signups 1,204 · up 8% week over week
* Activation 41% · flat
* Revenue matches Stripe to the cent
[Use this template](https://app.heliosapp.com/)
New to Helios? Start with [Run your first agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Database reportingAn agent introspects your schema, writes the SQL, runs it, analyzes the results in its own sandbox, and posts a report your team reads - instead of a dashboard nobody opens.](/use-cases/database-reporting/)
Related templates
## Pair it with these
[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)[OperationsNightly data quality checksRuns your invariants against production every night and tells the on-call analyst which rows broke and since when.⏰Nightly at 3:00am](/templates/database-health-check/)[OperationsDrive organizer & access auditFiles loose documents by what they actually contain, and reports anything shared beyond your domain.⏰Sundays at 8:00pm](/templates/google-drive-file-organizer/)
## Run KPI sheet refresh on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Incident postmortem drafter - Agent Template | Helios
URL: https://www.heliosapp.com/templates/incident-postmortem-drafter
Description: Reconstructs the incident timeline from Slack and GitHub, names the triggering change, and drafts the write-up in Notion.
[← All templates](/templates/)
Engineering
# Incident postmortem drafter
Reconstructs the incident timeline from Slack and GitHub, names the triggering change, and drafts the write-up in Notion.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
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, and 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: summary, impact, timeline, contributing factors, what went well, and action items. Pull the action items from what people actually agreed to in the channel, with owners. State your assumptions explicitly wherever the channel is ambiguous.
Trigger
## What starts this agent
▶Run on demand
Runs when you ask for it, from the app, from chat, or over the API.
### Integrations required
* [Slack](/integrations/slack/)
* [GitHub](/integrations/github/)
* [Notion](/integrations/notion/)
* [WarpBuild](/integrations/warpbuild/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
Postmortem drafted
* 41-minute impact window reconstructed
* Triggering 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 agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Incident summariesAn agent reconstructs the timeline from your incident channel and the deploys around it, identifies the triggering change, and drafts the write-up with the facts already assembled.](/use-cases/incident-summaries/)
Related templates
## Pair it with these
[EngineeringPull request reviewerReviews every pull request against your conventions, leaves inline comments, and posts a weekly digest of review load and CI health.◆github · pull\_request.opened](/templates/pr-review-digest/)[EngineeringCI cost & speed reportAttributes build spend to the workflows driving it, finds the jobs that got slower, and names the change responsible.⏰Mondays at 7:00am](/templates/warpbuild-ci-cost-report/)[OperationsNightly data quality checksRuns your invariants against production every night and tells the on-call analyst which rows broke and since when.⏰Nightly at 3:00am](/templates/database-health-check/)
## Run Incident postmortem drafter on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Documentation freshness audit - Agent Template | Helios
URL: https://www.heliosapp.com/templates/notion-docs-freshness-audit
Description: Checks your written docs against the actual codebase every month and comments on the pages that have gone stale.
[← All templates](/templates/)
Support
# Documentation freshness audit
Checks your written docs against the actual codebase every month and comments on the pages that have gone stale.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
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, ordered by how many people viewed them, and note any page you could not verify.
Trigger
## What starts this agent
⏰Monthly on the 1st
Runs on a schedule. Describe the cadence in plain English and Helios turns it into a cron expression for you.
### Integrations required
* [Notion](/integrations/notion/)
* [GitHub](/integrations/github/)
* [Slack](/integrations/slack/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
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 agent](/guides/run-your-first-agent/).
Related templates
## Pair it with these
[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.◆github · tag.created](/templates/github-release-notes/)[MarketingDiscord community digestReads every channel each evening, surfaces unanswered questions, and files real bug reports as GitHub issues.⏰Daily at 7:00pm](/templates/discord-community-digest/)[SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.◆slack · new message in #supportP](/templates/slack-support-triage/)
## Run Documentation freshness audit on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Plain thread triage & weekly themes - Agent Template | Helios
URL: https://www.heliosapp.com/templates/plain-thread-summarizer
Description: Triages every incoming Plain thread on arrival, then clusters the week into the themes product should hear about.
[← All templates](/templates/)
Support
# Plain thread triage & weekly themes
Triages every incoming Plain thread on arrival, then clusters the week into the themes product should hear about.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
When a new thread is created in Plain, read it along with the customer record. Look up the customer's plan and payment health 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. Separately, every Friday at 3pm, read all threads from the past seven days, cluster them by theme, count each cluster, and post the top themes to #product with example threads.
Trigger
## What starts this agent
◆plain · thread.created
Runs when the event fires in the connected service. Filter on the fields that matter so only the runs you want wake the agent.
### Integrations required
* [PPlain](/integrations/plain/)
* [Stripe](/integrations/stripe/)
* [Notion](/integrations/notion/)
* [Slack](/integrations/slack/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
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 agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Support triageAn agent reads each incoming thread the moment it arrives, identifies the customer, checks their plan and history, labels and prioritizes it, and drafts a reply grounded in your documentation.P](/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 · new message in #supportP](/templates/slack-support-triage/)[SupportMorning inbox triageReads what arrived overnight, labels it, drafts the easy replies, and hands you a ranked list of what needs a human.⏰Weekdays at 7:30am](/templates/gmail-inbox-triage/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.⏰Mondays at 7:00amP](/templates/churn-risk-watchlist/)
## Run Plain thread triage & weekly themes on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Pull request reviewer - Agent Template | Helios
URL: https://www.heliosapp.com/templates/pr-review-digest
Description: Reviews every pull request against your conventions, leaves inline comments, and posts a weekly digest of review load and CI health.
[← All templates](/templates/)
Engineering
# Pull request reviewer
Reviews every pull request against your conventions, leaves inline comments, and posts a weekly digest of review load and CI health.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
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 actually 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.
Trigger
## What starts this agent
◆github · pull\_request.opened
Runs when the event fires in the connected service. Filter on the fields that matter so only the runs you want wake the agent.
### Integrations required
* [GitHub](/integrations/github/)
* [Slack](/integrations/slack/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
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 agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[PR review & digestAn agent reads each diff against your conventions and leaves a real review. A second agent summarizes the week: what merged, what is waiting, and how CI is holding up.](/use-cases/pr-review-digest/)[Incident summariesAn agent reconstructs the timeline from your incident channel and the deploys around it, identifies the triggering change, and drafts the write-up with the facts already assembled.](/use-cases/incident-summaries/)[Weekly digestsAn agent reads a week of activity across the tools your team uses, separates decisions from chatter, and posts a digest people actually read.](/use-cases/weekly-digests/)
Related templates
## Pair it with these
[EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup so nobody has to attend one.⏰Weekdays at 9:00am](/templates/daily-standup-digest/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.◆github · tag.created](/templates/github-release-notes/)[EngineeringIncident postmortem drafterReconstructs the incident timeline from Slack and GitHub, names the triggering change, and drafts the write-up in Notion.▶Run on demand](/templates/incident-postmortem-drafter/)
## Run Pull request reviewer on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Reddit brand monitor - Agent 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
# 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/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
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 context rather than the headline. 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.
Trigger
## What starts this agent
⏰Every 4 hours
Runs on a schedule. Describe the cadence in plain English and Helios turns it into a cron expression for you.
### Integrations required
* [Reddit](/integrations/reddit/)
* [Slack](/integrations/slack/)
* [Notion](/integrations/notion/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
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 agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Community monitoringAn agent sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space, judges which threads deserve an answer, and brings them to your team.](/use-cases/community-monitoring/)
Related templates
## Pair it with these
[MarketingDiscord community digestReads every channel each evening, surfaces unanswered questions, and files real bug reports as GitHub issues.⏰Daily at 7:00pm](/templates/discord-community-digest/)[MarketingCompetitor pricing & changelog watchScrapes competitor pricing pages and changelogs every week and reports only what actually changed.⏰Mondays at 6:00am](/templates/apify-competitor-scraper/)[MarketingSEO keyword briefReads what already ranks for a keyword, finds what everyone missed, and writes a brief your writer can work from.▶Run on demand](/templates/seo-keyword-brief/)
## Run Reddit brand monitor on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Onboarding email that reads the account - Agent Template | Helios
URL: https://www.heliosapp.com/templates/resend-onboarding-sequence
Description: Checks what each new account has actually set up and sends the message that helps them next, rather than the next message in a sequence.
[← All templates](/templates/)
Sales & RevOps
# Onboarding email that reads the account
Checks what each new account has actually set up and sends the message that helps them next, rather than the next message in a sequence.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
Every day at 9am, query Postgres for accounts created in the last fourteen days. For each account, work out the furthest onboarding milestone they have reached: signed up, connected an integration, created a workflow, put a workflow on a trigger, invited a teammate. Then decide which single message would help them most right now and send it with Resend from hello@ourdomain.com. Write each email fresh, reference the specific thing they have and have not done, keep it under 100 words, and include exactly one link. Skip accounts that already reached the last milestone, and skip anyone who received an email from this agent in the last three days. Post a summary of who got what to #growth.
Trigger
## What starts this agent
⏰Daily at 9:00am
Runs on a schedule. Describe the cadence in plain English and Helios turns it into a cron expression for you.
### Integrations required
* [Resend](/integrations/resend/)
* [Databases](/integrations/databases/)
* [Slack](/integrations/slack/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
46 onboarding emails sent
* 19 nudged to connect their first integration
* 14 shown how to schedule a task
* 13 invited to add a teammate
[Use this template](https://app.heliosapp.com/)
New to Helios? Start with [Run your first agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Email outreachAn agent finds the threads that went quiet, reads the conversation, and drafts a follow-up grounded in the last real next step. Onboarding sequences read the account before they send.](/use-cases/email-outreach/)
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](/templates/apollo-lead-enrichment/)[SupportMorning inbox triageReads what arrived overnight, labels it, drafts the easy replies, and hands you a ranked list of what needs a human.⏰Weekdays at 7:30am](/templates/gmail-inbox-triage/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)
## Run Onboarding email that reads the account on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# SEO keyword brief - Agent Template | Helios
URL: https://www.heliosapp.com/templates/seo-keyword-brief
Description: Reads what already ranks for a keyword, finds what everyone missed, and writes a brief your writer can work from.
[← All templates](/templates/)
Marketing
# SEO keyword brief
Reads what already ranks for a keyword, finds what everyone missed, and writes a brief your writer can work from.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
I will give you a target keyword. Search the web for it and read the ten pages that currently rank highest, using Apify to scrape them when they resist a simple fetch. For each one note its structure, its word count, the questions it answers, and the questions it skips. Then write a content brief in Google Docs containing: the search intent in one sentence, a recommended outline with H2s and H3s, the questions every competing page answers that we must cover, the gaps nobody addressed that we can own, the entities and terms that appear across the top results, and a suggested title and meta description. Cite the URL behind every observation. Share the doc with the marketing folder in Drive.
Trigger
## What starts this agent
▶Run on demand
Runs when you ask for it, from the app, from chat, or over the API.
### Integrations required
* [Apify](/integrations/apify/)
* [Google Docs](/integrations/google-docs/)
* [Google Drive](/integrations/google-drive/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
Brief for “ai agent platform”
* 10 ranking pages analyzed, median 2,400 words
* 4 content gaps nobody covers
* Outline with 7 H2s and a FAQ block
[Use this template](https://app.heliosapp.com/)
New to Helios? Start with [Run your first agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Content pipelineAn agent searches the web, reads what it finds, and writes a sourced draft into a real document. Give it your voice and your prior work, and the first draft already sounds like you.](/use-cases/content-pipeline/)
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](/templates/google-docs-brief-writer/)[MarketingCompetitor pricing & changelog watchScrapes competitor pricing pages and changelogs every week and reports only what actually changed.⏰Mondays at 6:00am](/templates/apify-competitor-scraper/)[MarketingReddit brand monitorSweeps the subreddits where your customers gather, judges which threads deserve a reply, and brings you a shortlist.⏰Every 4 hours](/templates/reddit-brand-monitor/)
## Run SEO keyword brief on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Slack support triage - Agent 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 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/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
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 health in Stripe, and post a summary in the thread tagging the account owner. Never guess at billing specifics - escalate those every time. Keep replies short and write like a helpful teammate.
Trigger
## What starts this agent
◆slack · new message in #support
Runs when the event fires in the connected service. Filter on the fields that matter so only the runs you want wake the agent.
### Integrations required
* [Slack](/integrations/slack/)
* [Notion](/integrations/notion/)
* [PPlain](/integrations/plain/)
* [Attio](/integrations/attio/)
* [Stripe](/integrations/stripe/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
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 agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Support triageAn agent reads each incoming thread the moment it arrives, identifies the customer, checks their plan and history, labels and prioritizes it, and drafts a reply grounded in your documentation.P](/use-cases/support-triage/)[Form routingA response arrives and an agent reads what the person wrote, enriches their company, decides where it belongs, and files it - as a deal, a support thread, or a reply within minutes.P+1](/use-cases/form-routing/)
Related templates
## Pair it with these
[SupportPlain thread triage & weekly themesTriages every incoming Plain thread on arrival, then clusters the week into the themes product should hear about.◆plain · thread.createdP](/templates/plain-thread-summarizer/)[SupportMorning inbox triageReads what arrived overnight, labels it, drafts the easy replies, and hands you a ranked list of what needs a human.⏰Weekdays at 7:30am](/templates/gmail-inbox-triage/)[SupportDocumentation freshness auditChecks your written docs against the actual codebase every month and comments on the pages that have gone stale.⏰Monthly on the 1st](/templates/notion-docs-freshness-audit/)
## Run Slack support triage on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Failed payment recovery - Agent 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
# 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/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
Every hour, list charges in Stripe that failed since your last run. 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: explain 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.
Trigger
## What starts this agent
⏰Hourly
Runs on a schedule. Describe the cadence in plain English and Helios turns it into a cron expression for you.
### Integrations required
* [Stripe](/integrations/stripe/)
* [Attio](/integrations/attio/)
* [Resend](/integrations/resend/)
* [Slack](/integrations/slack/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
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 agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Billing operationsAn agent watches Stripe for failed charges and starts recovery, reconciles what you billed against what your own system recorded, and reports the revenue numbers every morning.](/use-cases/billing-ops/)
Related templates
## Pair it with these
[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.⏰Mondays at 7:00amP](/templates/churn-risk-watchlist/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing firmographics, and flags deals that have gone quiet - every night, without anyone remembering.⏰Nightly at 2:00am](/templates/attio-crm-hygiene/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)
## Run Failed payment recovery on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Typeform lead router - Agent Template | Helios
URL: https://www.heliosapp.com/templates/typeform-lead-router
Description: Reads each form response, enriches the company, routes it to sales or support, and replies while the person still has your tab open.
[← All templates](/templates/)
Sales & RevOps
# Typeform lead router
Reads each form response, enriches the company, routes it to sales or support, and replies while the person still has your tab open.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
When a Typeform response arrives, read every answer including the open-text ones and the hidden fields. Decide whether this is a sales enquiry or a support request based on what they wrote, rather than which form field they picked. For sales: enrich the company in Apollo, create a deal in Attio, assign it to the owner for that territory, notify them in #inbound with a summary of the stated use case, and send the person a reply through Resend that references what they actually asked for. For support: find or create the customer in Plain, open a thread with the full response attached, and set priority from their plan. Reply within five minutes either way.
Trigger
## What starts this agent
⇄Typeform response webhook
Runs when a signed webhook arrives. Helios verifies the signature and hands the payload straight to the agent.
### Integrations required
* [Typeform](/integrations/typeform/)
* [Apollo](/integrations/apollo/)
* [Attio](/integrations/attio/)
* [Resend](/integrations/resend/)
* [PPlain](/integrations/plain/)
* [Slack](/integrations/slack/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
Routed and answered in 3 minutes
* Northwind · 240 employees · Series B
* Fit score 87 · assigned to @dana by territory
* Reply referenced their goal of consolidating tools
[Use this template](https://app.heliosapp.com/)
New to Helios? Start with [Run your first agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Lead enrichmentWhen someone signs up or fills a form, an agent enriches the person and their company, scores fit against your definition of a good customer, creates the CRM record, and tells the right rep.](/use-cases/lead-enrichment/)[Form routingA response arrives and an agent reads what the person wrote, enriches their company, decides where it belongs, and files it - as a deal, a support thread, or a reply within minutes.P+1](/use-cases/form-routing/)
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](/templates/apollo-lead-enrichment/)[SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.◆slack · new message in #supportP](/templates/slack-support-triage/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing firmographics, and flags deals that have gone quiet - every night, without anyone remembering.⏰Nightly at 2:00am](/templates/attio-crm-hygiene/)
## Run Typeform lead router on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# CI cost & speed report - Agent Template | Helios
URL: https://www.heliosapp.com/templates/warpbuild-ci-cost-report
Description: Attributes build spend to the workflows driving it, finds the jobs that got slower, and names the change responsible.
[← All templates](/templates/)
Engineering
# CI cost & speed report
Attributes build spend to the workflows driving it, finds the jobs that got slower, and names the change responsible.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
Every Monday at 7am, pull last week's job history and spend data from WarpBuild. Attribute spend to each repository and workflow, and compare it against the previous week. Identify the three workflows that grew the most in cost and the three jobs whose p95 duration grew the most. For each one, look at the GitHub pull requests that changed that workflow file or its dependencies in the past two weeks, and say which change most likely caused the increase. Also report median and p95 queue time across the fleet, and the overall CI pass rate. Post this to #platform as a short report. Lead with the total and the week-over-week change.
Trigger
## What starts this agent
⏰Mondays at 7:00am
Runs on a schedule. Describe the cadence in plain English and Helios turns it into a cron expression for you.
### Integrations required
* [WarpBuild](/integrations/warpbuild/)
* [GitHub](/integrations/github/)
* [Slack](/integrations/slack/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
CI spend · week of Mar 3
* $3,140 total · up 12% week over week
* \`e2e\` p95 rose from 8m to 19m after #2790
* \`build-matrix\` queues 4m before it starts
[Use this template](https://app.heliosapp.com/)
New to Helios? Start with [Run your first agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Incident summariesAn agent reconstructs the timeline from your incident channel and the deploys around it, identifies the triggering change, and drafts the write-up with the facts already assembled.](/use-cases/incident-summaries/)
Related templates
## Pair it with these
[EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup so nobody has to attend one.⏰Weekdays at 9:00am](/templates/daily-standup-digest/)[EngineeringPull request reviewerReviews every pull request against your conventions, leaves inline comments, and posts a weekly digest of review load and CI health.◆github · pull\_request.opened](/templates/pr-review-digest/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)
## Run CI cost & speed report on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Weekly metrics report - Agent 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 anomalies called out.
[← All templates](/templates/)
Operations
# Weekly metrics report
Queries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
The prompt
## This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
The promptCopy
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 correlate - and explain what you found. Post to #metrics with the headline numbers first, then the anomalies, then a short note on what you checked and found normal. Include the SQL you ran as a thread reply.
Trigger
## What starts this agent
⏰Mondays at 7:00am
Runs on a schedule. Describe the cadence in plain English and Helios turns it into a cron expression for you.
### Integrations required
* [Databases](/integrations/databases/)
* [Slack](/integrations/slack/)
* [Google Sheets](/integrations/google-sheets/)
Authorize each service once. Helios stores the credential envelope-encrypted and attaches it server-side on every run.
Example output
## What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
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 agent](/guides/run-your-first-agent/).
Use cases
## The task behind this template
[Database reportingAn agent introspects your schema, writes the SQL, runs it, analyzes the results in its own sandbox, and posts a report your team reads - instead of a dashboard nobody opens.](/use-cases/database-reporting/)[Billing operationsAn agent watches Stripe for failed charges and starts recovery, reconciles what you billed against what your own system recorded, and reports the revenue numbers every morning.](/use-cases/billing-ops/)[Weekly digestsAn agent reads a week of activity across the tools your team uses, separates decisions from chatter, and posts a digest people actually read.](/use-cases/weekly-digests/)[CRM data syncAn agent computes usage from your database, joins it with billing health and support volume, and writes the result onto the account record every night.P](/use-cases/crm-data-sync/)
Related templates
## Pair it with these
[OperationsKPI sheet refreshPulls from the warehouse every morning and writes the finished tables into the sheet leadership already opens.⏰Daily at 6:00am](/templates/google-sheets-kpi-sync/)[OperationsNightly data quality checksRuns your invariants against production every night and tells the on-call analyst which rows broke and since when.⏰Nightly at 3:00am](/templates/database-health-check/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.⏰Mondays at 7:00amP](/templates/churn-risk-watchlist/)
## Run Weekly metrics report on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Use Cases - Work Agents Handle | Helios
URL: https://www.heliosapp.com/use-cases
Description: Support triage, lead enrichment, PR digests, database reporting, billing ops, and more - real tasks Helios agents run every day.
Use cases
# The work agents pick up.
12 tasks teams hand to Helios agents today. Each one runs on a trigger, reaches your tools through their full APIs, and carries what it learned into the next run.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
## Support
[Support solutions →](/solutions/support/)
[Support triageAn agent reads each incoming thread the moment it arrives, identifies the customer, checks their plan and history, labels and prioritizes it, and drafts a reply grounded in your documentation.P](/use-cases/support-triage/)
## Sales & RevOps
[Sales & RevOps solutions →](/solutions/sales-and-revops/)
[Lead enrichmentWhen someone signs up or fills a form, an agent enriches the person and their company, scores fit against your definition of a good customer, creates the CRM record, and tells the right rep.](/use-cases/lead-enrichment/)[Email outreachAn agent finds the threads that went quiet, reads the conversation, and drafts a follow-up grounded in the last real next step. Onboarding sequences read the account before they send.](/use-cases/email-outreach/)[CRM data syncAn agent computes usage from your database, joins it with billing health and support volume, and writes the result onto the account record every night.P](/use-cases/crm-data-sync/)
## Marketing
[Marketing solutions →](/solutions/marketing/)
[Content pipelineAn agent searches the web, reads what it finds, and writes a sourced draft into a real document. Give it your voice and your prior work, and the first draft already sounds like you.](/use-cases/content-pipeline/)[Form routingA response arrives and an agent reads what the person wrote, enriches their company, decides where it belongs, and files it - as a deal, a support thread, or a reply within minutes.P+1](/use-cases/form-routing/)[Community monitoringAn agent sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space, judges which threads deserve an answer, and brings them to your team.](/use-cases/community-monitoring/)
## Engineering
[Engineering solutions →](/solutions/engineering/)
[PR review & digestAn agent reads each diff against your conventions and leaves a real review. A second agent summarizes the week: what merged, what is waiting, and how CI is holding up.](/use-cases/pr-review-digest/)[Incident summariesAn agent reconstructs the timeline from your incident channel and the deploys around it, identifies the triggering change, and drafts the write-up with the facts already assembled.](/use-cases/incident-summaries/)
## Operations
[Operations solutions →](/solutions/operations/)
[Database reportingAn agent introspects your schema, writes the SQL, runs it, analyzes the results in its own sandbox, and posts a report your team reads - instead of a dashboard nobody opens.](/use-cases/database-reporting/)[Billing operationsAn agent watches Stripe for failed charges and starts recovery, reconciles what you billed against what your own system recorded, and reports the revenue numbers every morning.](/use-cases/billing-ops/)[Weekly digestsAn agent reads a week of activity across the tools your team uses, separates decisions from chatter, and posts a digest people actually read.](/use-cases/weekly-digests/)
## Pick a task and hand it over.
Describe the work once. An agent runs it on your schedule, on your events, forever.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Billing operations - AI Agents That Run It | Helios
URL: https://www.heliosapp.com/use-cases/billing-ops
Description: An agent watches Stripe for failed charges and starts recovery, reconciles what you billed against what your own system recorded, and reports the revenue numbers every morning.
[← All use cases](/use-cases/)
Billing operations
# Failed payments, reconciled books, and no spreadsheet archaeology.
An agent watches Stripe for failed charges and starts recovery, reconciles what you billed against what your own system recorded, and reports the revenue numbers every morning.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
How it works
## Three steps to a standing task
1. Step 01
### Connect Stripe and your database
A restricted Stripe key covers reporting agents; add write scopes only where an agent 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 would need a hundred branches.
3. Step 03
### Let it run hourly and monthly
Recovery runs every hour. Reconciliation runs after the books close. Both post where your revenue team already reads.
The run
## What the agent actually does
Every step below is a real tool call: the agent reaches for the API it needs, reads what it finds, and acts.
⏰Hourly
Every hour, find failed charges, 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
* Follow-up scheduled if unpaid in 48h
Reach
## The tools this agent touches
Each one connects once, and the agent gets its complete API.
* [Stripe](/integrations/stripe/)
* [Attio](/integrations/attio/)
* [Resend](/integrations/resend/)
* [Databases](/integrations/databases/)
* [Google Sheets](/integrations/google-sheets/)
This task belongs to [Operations](/solutions/operations/). See the rest of what that team hands off.
Templates
## Start from a working agent
Each template carries the prompt, the trigger, and the integrations it needs.
[Sales & RevOpsFailed payment recoveryFinds failed charges every hour, emails the billing contact a working update link, and escalates the accounts that matter.⏰Hourly](/templates/stripe-failed-payment-recovery/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.⏰Mondays at 7:00amP](/templates/churn-risk-watchlist/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)
FAQ
## Questions, answered
### Can the agent move money?
### Does it email customers automatically?
### How does reconciliation work?
### What about disputes and refunds?
## Put an agent on billing operations.
Describe the task, attach a trigger, and let it run around the clock.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Community monitoring - AI Agents That Run It | Helios
URL: https://www.heliosapp.com/use-cases/community-monitoring
Description: An agent sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space, judges which threads deserve an answer, and brings them to your team.
[← All use cases](/use-cases/)
Community monitoring
# Someone is always reading the threads about you.
An agent sweeps Reddit and Discord for mentions of your product, your competitors, and your problem space, judges which threads deserve an answer, and brings them to your team.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
How it works
## Three steps to a standing task
1. Step 01
### Name what to watch
Subreddits, Discord channels, brand terms, competitor names, category language. The agent reads full comment trees rather than matching keywords.
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 sentiment and intent, and ignores the rest.
3. Step 03
### Get a shortlist, not a firehose
Every few hours the agent posts the threads worth a reply, with a suggested response and a link. Feature requests get filed where product will see them.
The run
## What the agent actually does
Every step below is a real tool call: the agent reaches for the API it needs, reads what it finds, and acts.
⏰Every 4 hours
Every few 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-worthiness
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
Reach
## The tools this agent touches
Each one connects once, and the agent gets its complete API.
* [Reddit](/integrations/reddit/)
* [Discord](/integrations/discord/)
* [Slack](/integrations/slack/)
* [Notion](/integrations/notion/)
* [GitHub](/integrations/github/)
This task belongs to [Marketing](/solutions/marketing/). See the rest of what that team hands off.
Templates
## Start from a working agent
Each template carries the prompt, the trigger, and the integrations it needs.
[MarketingReddit brand monitorSweeps the subreddits where your customers gather, judges which threads deserve a reply, and brings you a shortlist.⏰Every 4 hours](/templates/reddit-brand-monitor/)[MarketingDiscord community digestReads every channel each evening, surfaces unanswered questions, and files real bug reports as GitHub issues.⏰Daily at 7:00pm](/templates/discord-community-digest/)[MarketingCompetitor pricing & changelog watchScrapes competitor pricing pages and changelogs every week and reports only what actually changed.⏰Mondays at 6:00am](/templates/apify-competitor-scraper/)
FAQ
## Questions, answered
### Will the agent post replies itself?
### How does it avoid flooding the channel?
### Can it file bugs it finds?
### How often should it run?
## Put an agent on community monitoring.
Describe the task, attach a trigger, and let it run around the clock.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Content pipeline - AI Agents That Run It | Helios
URL: https://www.heliosapp.com/use-cases/content-pipeline
Description: An agent searches the web, reads what it finds, and writes a sourced draft into a real document. Give it your voice and your prior work, and the first draft already sounds like you.
[← All use cases](/use-cases/)
Content pipeline
# Research, draft, and file - while you sleep.
An agent searches the web, reads what it finds, and writes a sourced draft into a real document. Give it your voice and your prior work, and the first draft already sounds like you.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
How it works
## Three steps to a standing task
1. Step 01
### Give it a topic and your voice
Point the agent at your existing docs so it learns how you write. Then hand it a topic, an outline, or a keyword to build a brief around.
2. Step 02
### Let it research with a real computer
The agent searches the web, reads pages, and can run an Apify actor when it needs structured collection at scale. It clusters what it finds before it writes a word.
3. Step 03
### Get a draft with sources
The draft lands in Google Docs or Notion with every claim linked to where it came from, and open questions left as inline notes for you.
The run
## What the agent actually does
Every step below is a real tool call: the agent reaches for the API it needs, reads what it finds, and acts.
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. google-docs·read 3 prior briefs for voice
4. code·outline and cluster the findings
5. google-docs·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
Reach
## The tools this agent touches
Each one connects once, and the agent gets its complete API.
* [Google Docs](/integrations/google-docs/)
* [Apify](/integrations/apify/)
* [Notion](/integrations/notion/)
* [Slack](/integrations/slack/)
* [Google Drive](/integrations/google-drive/)
This task belongs to [Marketing](/solutions/marketing/). See the rest of what that team hands off.
Templates
## Start from a working agent
Each template carries the prompt, the trigger, and the integrations it needs.
[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](/templates/google-docs-brief-writer/)[MarketingSEO keyword briefReads what already ranks for a keyword, finds what everyone missed, and writes a brief your writer can work from.▶Run on demand](/templates/seo-keyword-brief/)[MarketingCompetitor pricing & changelog watchScrapes competitor pricing pages and changelogs every week and reports only what actually changed.⏰Mondays at 6:00am](/templates/apify-competitor-scraper/)
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 an agent on content pipeline.
Describe the task, attach a trigger, and let it run around the clock.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# CRM data sync - AI Agents That Run It | Helios
URL: https://www.heliosapp.com/use-cases/crm-data-sync
Description: An agent computes usage from your database, joins it with billing health and support volume, and writes the result onto the account record every night.
[← All use cases](/use-cases/)
CRM data sync
# A CRM that reflects what customers actually do.
An agent computes usage from your database, joins it with billing health and support volume, and writes the result onto the account record every night.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
How it works
## Three steps to a standing task
1. Step 01
### Connect the systems
Your database holds usage. Stripe holds billing. Your support tool holds sentiment. One agent holds all three connections at once.
2. Step 02
### Define health in plain English
Describe what an at-risk account looks like and what expansion looks like. The agent computes the scores in its sandbox and explains its reasoning in a note.
3. Step 03
### Write it back every night
Fields update on the account record, owners see the change, and every write is traceable to the run that made it.
The run
## What the agent actually does
Every step below is a real tool call: the agent reaches for the API it needs, reads what it finds, and acts.
⏰Nightly at 1:00am
Nightly, sync product usage, billing health, and support volume into the CRM as account health fields.
1. postgres·compute 30-day usage per account
2. stripe·read subscription and payment health
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
Reach
## The tools this agent touches
Each one connects once, and the agent gets its complete API.
* [Databases](/integrations/databases/)
* [Attio](/integrations/attio/)
* [Stripe](/integrations/stripe/)
* [PPlain](/integrations/plain/)
* [Apollo](/integrations/apollo/)
This task belongs to [Sales & RevOps](/solutions/sales-and-revops/). See the rest of what that team hands off.
Templates
## Start from a working agent
Each template carries the prompt, the trigger, and the integrations it needs.
[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing firmographics, and flags deals that have gone quiet - every night, without anyone remembering.⏰Nightly at 2:00am](/templates/attio-crm-hygiene/)[Sales & RevOpsChurn risk watchlistJoins billing signals with product usage and support volume to surface the accounts quietly drifting toward the exit.⏰Mondays at 7:00amP](/templates/churn-risk-watchlist/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)
FAQ
## Questions, answered
### Does it overwrite fields a rep edited?
### How do I audit a change?
### How large a sync can it handle?
### What if the score looks wrong?
## Put an agent on crm data sync.
Describe the task, attach a trigger, and let it run around the clock.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Database reporting - AI Agents That Run It | Helios
URL: https://www.heliosapp.com/use-cases/database-reporting
Description: An agent introspects your schema, writes the SQL, runs it, analyzes the results in its own sandbox, and posts a report your team reads - instead of a dashboard nobody opens.
[← All use cases](/use-cases/)
Database reporting
# Ask your database a question. Get an answer, every morning.
An agent introspects your schema, writes the SQL, runs it, analyzes the results in its own sandbox, and posts a report your team reads - instead of a dashboard nobody opens.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
How it works
## Three steps to a standing task
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 introspects the schema, writes the queries, and shows the SQL it ran alongside the answer.
3. Step 03
### Put it on a schedule
Describe the cadence in plain English and Helios turns it into a cron trigger. The report shows up before standup, every day, without anyone maintaining it.
The run
## What the agent actually does
Every step below is a real tool call: the agent reaches for the API it needs, reads what it finds, and acts.
⏰Weekdays at 7:00am
Each morning, post yesterday's metrics with anything unusual called out.
1. clickhouse·introspect schema and query 24h of events
2. postgres·join account metadata
3. code·compute trends and flag anomalies
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
* Query and assumptions attached to the run
Reach
## The tools this agent touches
Each one connects once, and the agent gets its complete API.
* [Databases](/integrations/databases/)
* [Slack](/integrations/slack/)
* [Google Sheets](/integrations/google-sheets/)
* [Resend](/integrations/resend/)
This task belongs to [Operations](/solutions/operations/). See the rest of what that team hands off.
Templates
## Start from a working agent
Each template carries the prompt, the trigger, and the integrations it needs.
[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)[OperationsNightly data quality checksRuns your invariants against production every night and tells the on-call analyst which rows broke and since when.⏰Nightly at 3:00am](/templates/database-health-check/)[OperationsKPI sheet refreshPulls from the warehouse every morning and writes the finished tables into the sheet leadership already opens.⏰Daily at 6:00am](/templates/google-sheets-kpi-sync/)
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 an agent on database reporting.
Describe the task, attach a trigger, and let it run around the clock.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Email outreach - AI Agents That Run It | Helios
URL: https://www.heliosapp.com/use-cases/email-outreach
Description: An agent finds the threads that went quiet, reads the conversation, and drafts a follow-up grounded in the last real next step. Onboarding sequences read the account before they send.
[← All use cases](/use-cases/)
Email outreach
# Follow-ups that reference what was actually said.
An agent finds the threads that went quiet, reads the conversation, and drafts a follow-up grounded in the last real next step. Onboarding sequences read the account before they send.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
How it works
## Three steps to a standing task
1. Step 01
### Connect your inbox and sending domain
Gmail for the conversations you already have; Resend for lifecycle mail from your own verified domain. The agent uses whichever the task calls for.
2. Step 02
### Give it the account context
Connect your CRM and your database so each message reflects what the account has actually done, rather than which day of the sequence they landed on.
3. Step 03
### Review drafts, then let it send
Start with drafts waiting in your inbox. Once the writing holds up, move the send step into the agent and it goes out on schedule.
The run
## What the agent actually does
Every step below is a real tool call: the agent reaches for the API it needs, reads what it finds, and acts.
⏰Tuesdays at 9:00am
Find threads where I sent the last message 5+ days ago and draft a follow-up referencing what we discussed.
1. gmail·search sent threads with no reply
2. gmail·read each thread for the last next step
3. attio·check deal stage and prior touches
4. 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
* 1 skipped: the deal closed last week
* All waiting in Drafts for your review
Reach
## The tools this agent touches
Each one connects once, and the agent gets its complete API.
* [Gmail](/integrations/gmail/)
* [Resend](/integrations/resend/)
* [Attio](/integrations/attio/)
* [Apollo](/integrations/apollo/)
* [Databases](/integrations/databases/)
This task belongs to [Sales & RevOps](/solutions/sales-and-revops/). See the rest of what that team hands off.
Templates
## Start from a working agent
Each template carries the prompt, the trigger, and the integrations it needs.
[Sales & RevOpsOnboarding email that reads the accountChecks what each new account has actually set up and sends the message that helps them next, rather than the next message in a sequence.⏰Daily at 9:00am](/templates/resend-onboarding-sequence/)[SupportMorning inbox triageReads what arrived overnight, labels it, drafts the easy replies, and hands you a ranked list of what needs a human.⏰Weekdays at 7:30am](/templates/gmail-inbox-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](/templates/apollo-lead-enrichment/)
FAQ
## Questions, answered
### Will it send email without me?
### How does it avoid sounding like a template?
### Gmail or Resend?
### Can it handle a whole onboarding sequence?
## Put an agent on email outreach.
Describe the task, attach a trigger, and let it run around the clock.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Form routing - AI Agents That Run It | Helios
URL: https://www.heliosapp.com/use-cases/form-routing
Description: A response arrives and an agent reads what the person wrote, enriches their company, decides where it belongs, and files it - as a deal, a support thread, or a reply within minutes.
[← All use cases](/use-cases/)
Form routing
# Every submission enriched, understood, and sent to the right place.
A response arrives and an agent reads what the person wrote, enriches their company, decides where it belongs, and files it - as a deal, a support thread, or a reply within minutes.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
How it works
## Three steps to a standing task
1. Step 01
### Point your form webhook at Helios
Helios webhook triggers are signed with a secret you control and rotate. Each response starts a run the moment it is submitted.
2. Step 02
### Describe the routing
Say which submissions are sales, which are support, and who owns which territory. The agent reads the open-text answers, so routing reflects intent rather than a dropdown.
3. Step 03
### Land it where the work happens
Deals go to the CRM with an owner. Support requests become threads with a priority. Everyone gets a reply that references what they wrote.
The run
## What the agent actually does
Every step below is a real tool call: the agent reaches for the API it needs, reads what it finds, and acts.
⇄Typeform response webhook
For each demo request, enrich the company, score fit, route it, and reply within five minutes.
1. typeform·read the response and hidden fields
2. apollo·enrich the company and person
3. attio·create the deal and assign an owner
4. resend·send a tailored reply
5. slack·notify @dana in #inbound
✓Routed and answered in 3 minutes
* Northwind · 240 employees · Series B
* Fit score 87 · assigned to @dana by territory
* Reply referenced their goal of consolidating tools
* Deal created with the use case summarized
Reach
## The tools this agent touches
Each one connects once, and the agent gets its complete API.
* [Typeform](/integrations/typeform/)
* [Apollo](/integrations/apollo/)
* [Attio](/integrations/attio/)
* [Resend](/integrations/resend/)
* [PPlain](/integrations/plain/)
* [Slack](/integrations/slack/)
This task belongs to [Marketing](/solutions/marketing/). See the rest of what that team hands off.
Templates
## Start from a working agent
Each template carries the prompt, the trigger, and the integrations it needs.
[Sales & RevOpsTypeform lead routerReads each form response, enriches the company, routes it to sales or support, and replies while the person still has your tab open.⇄Typeform response webhookP+1](/templates/typeform-lead-router/)[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](/templates/apollo-lead-enrichment/)[SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.◆slack · new message in #supportP](/templates/slack-support-triage/)
FAQ
## Questions, answered
### How do I know the webhook is really from my form?
### Can it route to support instead of sales?
### What if a required field is empty?
### How fast is the reply?
## Put an agent on form routing.
Describe the task, attach a trigger, and let it run around the clock.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Incident summaries - AI Agents That Run It | Helios
URL: https://www.heliosapp.com/use-cases/incident-summaries
Description: An agent reconstructs the timeline from your incident channel and the deploys around it, identifies the triggering change, and drafts the write-up with the facts already assembled.
[← All use cases](/use-cases/)
Incident summaries
# The postmortem writes its own first draft.
An agent reconstructs the timeline from your incident channel and the deploys around it, identifies the triggering change, and drafts the write-up with the facts already assembled.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
How it works
## Three steps to a standing task
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
### Hand it the task
Run it manually when the incident closes, or on a schedule that sweeps for channels created since the last run. It builds the timeline and names the triggering change.
3. Step 03
### Edit a draft instead of a blank page
The postmortem lands in Notion with the timeline, the contributing factors, and the action items people already agreed to in the channel.
The run
## What the agent actually does
Every step below is a real tool call: the agent reaches for the API it needs, reads what it finds, and acts.
Draft a postmortem from the #incident channel and the deploys around it.
1. slack·read #incident-2025-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 reconstructed
* Triggering deploy identified as #2833
* Detection took 12 minutes; alerting gap noted
* 5 action items pulled from the discussion
Reach
## The tools this agent touches
Each one connects once, and the agent gets its complete API.
* [Slack](/integrations/slack/)
* [GitHub](/integrations/github/)
* [Notion](/integrations/notion/)
* [WarpBuild](/integrations/warpbuild/)
This task belongs to [Engineering](/solutions/engineering/). See the rest of what that team hands off.
Templates
## Start from a working agent
Each template carries the prompt, the trigger, and the integrations it needs.
[EngineeringIncident postmortem drafterReconstructs the incident timeline from Slack and GitHub, names the triggering change, and drafts the write-up in Notion.▶Run on demand](/templates/incident-postmortem-drafter/)[EngineeringPull request reviewerReviews every pull request against your conventions, leaves inline comments, and posts a weekly digest of review load and CI health.◆github · pull\_request.opened](/templates/pr-review-digest/)[EngineeringCI cost & speed reportAttributes build spend to the workflows driving it, finds the jobs that got slower, and names the change responsible.⏰Mondays at 7:00am](/templates/warpbuild-ci-cost-report/)
FAQ
## Questions, answered
### How does it know when the incident started?
### Can it identify the cause?
### Where does the draft land?
### Can it run automatically?
## Put an agent on incident summaries.
Describe the task, attach a trigger, and let it run around the clock.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Lead enrichment - AI Agents That Run It | Helios
URL: https://www.heliosapp.com/use-cases/lead-enrichment
Description: When someone signs up or fills a form, an agent enriches the person and their company, scores fit against your definition of a good customer, creates the CRM record, and tells the right rep.
[← All use cases](/use-cases/)
Lead enrichment
# Every lead enriched, scored, and routed within the minute.
When someone signs up or fills a form, an agent enriches the person and their company, scores fit against your definition of a good customer, creates the CRM record, and tells the right rep.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
How it works
## Three steps to a standing task
1. Step 01
### Define a good customer
Write your ICP in plain English - size, stage, industry, the signals that matter. The agent uses that definition to score rather than a rigid rule table you have to maintain.
2. Step 02
### Trigger on the moment of interest
Point your signup or form webhook at a Helios webhook trigger. Signed with a secret you control, it starts a run the instant someone raises their hand.
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 to the channel where your reps live.
The run
## What the agent actually does
Every step below is a real tool call: the agent reaches for the API it needs, reads what it finds, and acts.
⇄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
Reach
## The tools this agent touches
Each one connects once, and the agent gets its complete API.
* [Apollo](/integrations/apollo/)
* [Attio](/integrations/attio/)
* [Slack](/integrations/slack/)
* [Typeform](/integrations/typeform/)
* [Gmail](/integrations/gmail/)
This task belongs to [Sales & RevOps](/solutions/sales-and-revops/). See the rest of what that team hands off.
Templates
## Start from a working agent
Each template carries the prompt, the trigger, and the integrations it needs.
[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](/templates/apollo-lead-enrichment/)[Sales & RevOpsTypeform lead routerReads each form response, enriches the company, routes it to sales or support, and replies while the person still has your tab open.⇄Typeform response webhookP+1](/templates/typeform-lead-router/)[Sales & RevOpsNightly CRM hygieneMerges duplicates, fills missing firmographics, and flags deals that have gone quiet - every night, without anyone remembering.⏰Nightly at 2:00am](/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?
## Put an agent on lead enrichment.
Describe the task, attach a trigger, and let it run around the clock.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# PR review & digest - AI Agents That Run It | Helios
URL: https://www.heliosapp.com/use-cases/pr-review-digest
Description: An agent reads each diff against your conventions and leaves a real review. A second agent summarizes the week: what merged, what is waiting, and how CI is holding up.
[← All use cases](/use-cases/)
PR review & digest
# A reviewer on every pull request, and a digest on Friday.
An agent reads each diff against your conventions and leaves a real review. A second agent summarizes the week: what merged, what is waiting, and how CI is holding up.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
How it works
## Three steps to a standing task
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 actually comments on rather than generic style advice.
2. Step 02
### Attach a GitHub trigger
Run the reviewer on \`pull\_request.opened\` and \`pull\_request.synchronize\`, filtered to the base branches you care about. Add a label filter if you want to opt PRs in one at a time.
3. Step 03
### Read the review, and the weekly digest
The agent posts inline comments where they belong. A scheduled sibling posts the Friday digest to your engineering channel.
The run
## What the agent actually does
Every step below is a real tool call: the agent reaches for the API it needs, reads what it finds, and acts.
◆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 analysis 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
Reach
## The tools this agent touches
Each one connects once, and the agent gets its complete API.
* [GitHub](/integrations/github/)
* [Slack](/integrations/slack/)
* [Notion](/integrations/notion/)
This task belongs to [Engineering](/solutions/engineering/). See the rest of what that team hands off.
Templates
## Start from a working agent
Each template carries the prompt, the trigger, and the integrations it needs.
[EngineeringPull request reviewerReviews every pull request against your conventions, leaves inline comments, and posts a weekly digest of review load and CI health.◆github · pull\_request.opened](/templates/pr-review-digest/)[EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup so nobody has to attend one.⏰Weekdays at 9:00am](/templates/daily-standup-digest/)[EngineeringRelease notes writerTurns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.◆github · tag.created](/templates/github-release-notes/)
FAQ
## Questions, answered
### Will it comment on every pull request?
### Can it run tests or analysis?
### Does it re-review when new commits land?
### Who can change what the reviewer says?
## Put an agent on pr review & digest.
Describe the task, attach a trigger, and let it run around the clock.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Support triage - AI Agents That Run It | Helios
URL: https://www.heliosapp.com/use-cases/support-triage
Description: An agent reads each incoming thread the moment it arrives, identifies the customer, checks their plan and history, labels and prioritizes it, and drafts a reply grounded in your documentation.
[← All use cases](/use-cases/)
Support triage
# Every ticket triaged before your team opens the queue.
An agent reads each incoming thread the moment it arrives, identifies the customer, checks their plan and history, labels and prioritizes it, and drafts a reply grounded in your documentation.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
How it works
## Three steps to a standing task
1. Step 01
### Describe the triage you want
Write the task in plain English: which labels exist, how priority maps to plan tier, when to escalate, and what a good draft reply looks like. Name your help center so the agent knows where answers live.
2. Step 02
### Put it on your support events
Attach a Plain \`thread.created\` trigger, or watch a Slack support channel for new messages. The agent starts working within seconds of a customer writing in.
3. Step 03
### Let it work the queue
The agent labels, prioritizes, drafts, and escalates. Your team arrives to a sorted queue with the context already assembled, and spends the day on the threads that need a person.
The run
## What the agent actually does
Every step below is a real tool call: the agent reaches for the API it needs, reads what it finds, and acts.
◆plain · thread.created
On each new thread: identify the customer, label, set priority, draft a reply, and escalate Enterprise accounts.
1. plain·read thread and customer record
2. stripe·check plan and payment health
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 paged with the thread link
Reach
## The tools this agent touches
Each one connects once, and the agent gets its complete API.
* [PPlain](/integrations/plain/)
* [Slack](/integrations/slack/)
* [Notion](/integrations/notion/)
* [Stripe](/integrations/stripe/)
* [Attio](/integrations/attio/)
This task belongs to [Support](/solutions/support/). See the rest of what that team hands off.
Templates
## Start from a working agent
Each template carries the prompt, the trigger, and the integrations it needs.
[SupportSlack support triageWatches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.◆slack · new message in #supportP](/templates/slack-support-triage/)[SupportPlain thread triage & weekly themesTriages every incoming Plain thread on arrival, then clusters the week into the themes product should hear about.◆plain · thread.createdP](/templates/plain-thread-summarizer/)[SupportMorning inbox triageReads what arrived overnight, labels it, drafts the easy replies, and hands you a ranked list of what needs a human.⏰Weekdays at 7:30am](/templates/gmail-inbox-triage/)
FAQ
## Questions, answered
### Will the agent reply to customers on its own?
### How does the agent know our answers?
### How fast does it pick up a new thread?
### What happens with a question it has never seen?
## Put an agent on support triage.
Describe the task, attach a trigger, and let it run around the clock.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Weekly digests - AI Agents That Run It | Helios
URL: https://www.heliosapp.com/use-cases/weekly-digests
Description: An agent reads a week of activity across the tools your team uses, separates decisions from chatter, and posts a digest people actually read.
[← All use cases](/use-cases/)
Weekly digests
# The status update writes itself.
An agent reads a week of activity across the tools your team uses, separates decisions from chatter, and posts a digest people actually read.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
How it works
## Three steps to a standing task
1. Step 01
### Name the sources
Point the agent at the channels, repositories, and databases that hold the week's activity. Pin the ones it should always carry as context.
2. Step 02
### Say what matters
Decisions, blockers, and owners - or shipped work, review load, and CI health. The agent filters to what your audience needs rather than repeating everything.
3. Step 03
### Schedule it for Friday afternoon
Describe the cadence in plain English. The digest posts to the channel where the team already reads, every week, without anyone owning the task.
The run
## What the agent actually does
Every step below is a real tool call: the agent reaches for the API it needs, reads what it finds, and acts.
⏰Fridays at 4:00pm
Every Friday, summarize merged work, review backlog, CI health, and the decisions made this week.
1. github·list PRs merged in the last 7 days
2. github·list open PRs awaiting review
3. slack·read #product and #eng threads
4. code·separate decisions from discussion
5. slack·post the 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%
* 3 decisions recorded, including the export beta
Reach
## The tools this agent touches
Each one connects once, and the agent gets its complete API.
* [Slack](/integrations/slack/)
* [GitHub](/integrations/github/)
* [Notion](/integrations/notion/)
* [Databases](/integrations/databases/)
* [WarpBuild](/integrations/warpbuild/)
This task belongs to [Operations](/solutions/operations/). See the rest of what that team hands off.
Templates
## Start from a working agent
Each template carries the prompt, the trigger, and the integrations it needs.
[EngineeringStandup without the meetingReads yesterday's commits, merges, and review queue, then posts a standup so nobody has to attend one.⏰Weekdays at 9:00am](/templates/daily-standup-digest/)[EngineeringPull request reviewerReviews every pull request against your conventions, leaves inline comments, and posts a weekly digest of review load and CI health.◆github · pull\_request.opened](/templates/pr-review-digest/)[OperationsWeekly metrics reportQueries your warehouse, computes the metrics your team argues about, and posts a report with the anomalies called out.⏰Mondays at 7:00am](/templates/weekly-metrics-report/)
FAQ
## Questions, answered
### How does it tell a decision from chatter?
### Can one digest span several tools?
### How do I set the schedule?
### Does it remember what it said last week?
## Put an agent on weekly digests.
Describe the task, attach a trigger, and let it run around the clock.
[Get started free](https://app.heliosapp.com/)[Book a demo](https://cal.com/suryao/helios)
---
# Helios Documentation
Base URL: https://www.heliosapp.com/docs
# 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"
updatedAt: "2026-07-09"
---
# Advanced
## 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 rather than assume
Agents are instructed to gather context with tools and to stop with a clear error rather than guess.
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).
## Persisting state between runs
Every workflow has a durable workspace at `~/workspace`, shared by all of its runs. Use it to carry
state forward:
```
Keep a file at ~/workspace/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 `~/workspace` - under `$TMPDIR`, for instance - disappears when the run
ends. See [sandboxes](/docs/basics/sandboxes).
## 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 rather than a model that was wrong.
## 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"
updatedAt: "2026-07-09"
---
# Quickstart
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 **cron 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 rather than waiting for Monday. 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 GitHub,
Slack, and Plain.
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@warpbuild.com, or reach out through the in-app chat.
---
# 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 memory that carries between runs - 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 memory that carries between runs - with SSO, roles, and encrypted secrets around it."
icon: Sun
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
# What is Helios?
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 GitHub, Slack, or Plain.
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 keep a persistent workspace that survives between runs.
### 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.
Seventeen services are available today - GitHub, Slack, Plain, Discord, Notion, Attio, Apollo,
Stripe, Resend, Reddit, Typeform, Apify, WarpBuild, and Google Docs, Drive, Gmail, and Sheets - plus
direct access to your [Postgres, MySQL, and ClickHouse databases](/docs/integrations/databases) and
any external [MCP server](/docs/basics/mcp-servers) you attach.
### Context that persists
Pin a [repository or other integration resource](/docs/basics/integration-resources) so an agent
always knows which one you mean. Files an agent writes to its workspace are still there on the next
run. And when an agent works out how to drive an unfamiliar API, it
[remembers that](/docs/basics/memory) for next time.
### 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 [cron trigger](/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
Helios is SOC 2 Type II compliant. For detailed security documentation, visit our
[trust center](https://trust.warpbuild.com) or contact support@warpbuild.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.
---
# 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"
updatedAt: "2026-07-09"
---
# Chat
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 under `~/workspace/uploads/`. 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 live in the chat's persistent workspace, so they survive across messages and across sandbox
restarts. 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 **and** the
chat's workspace files, so the new agent starts with everything the original had. 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 workspace 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"
updatedAt: "2026-07-09"
---
# Key concepts
## 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. |
| **Cron** | A schedule matches. Cron runs in UTC. |
| **Webhook** | A signed HTTP request arrives at the trigger's URL. |
| **Integration** | An event arrives from GitHub, Slack, or Plain. |
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 `~/workspace` directory persists between runs;
everything else is discarded. 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 authenticated connection to an external service. 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 - today, a GitHub repository.
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`. Your **resource role** on a
given project or workflow is `admin`, `editor`, or `user`. Organization admins are resource admins
everywhere; everyone else starts at `user`. See
[roles and permissions](/docs/basics/roles-permissions).
## Visibility
Whether a resource is **restricted** (explicit grants only) or **organization** (everyone gets a
role). Managed for projects and integrations; workflows and chats 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 - today, 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 - today, a GitHub repository - to a chat or workflow as scoped, authenticated context."
icon: Pin
createdAt: "2026-07-09"
updatedAt: "2026-07-09"
---
# Integration resources
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
Today, **GitHub repositories**. You can pin more than one.
Other integrations are reachable from any chat or workflow through their full API - they just don't
have a pinnable object type yet.
## 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, CI, and settings.
---
title: "Keyboard shortcuts"
excerpt: "Move around Helios without touching the mouse"
description: "Global shortcuts and two-key navigation sequences for Helios, CI, and settings."
icon: Keyboard
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
# Keyboard shortcuts
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 `c` | Go to CI |
| `g` then `i` | Go to Insights |
| `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 |
### Within CI
| Shortcut | Action |
| --- | --- |
| `c` then `r` | Runners |
| `c` then `c` | Cache |
| `c` then `b` | BYOC |
| `c` then `d` | Docker builders |
### 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"
updatedAt: "2026-07-09"
---
# MCP servers
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: rather than a fixed set of
actions, 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.
---
# Memory
URL: https://www.heliosapp.com/docs/basics/memory
Description: Helios agents carry two kinds of memory across runs: a persistent workspace, and a record of how they successfully used an integration's API before.
---
title: "Memory"
excerpt: "Agents remember how they drove an API last time"
description: "Helios agents carry two kinds of memory across runs: a persistent workspace, and a record of how they successfully used an integration's API before."
icon: Brain
createdAt: "2026-07-09"
updatedAt: "2026-07-09"
---
# Memory
An agent that starts from zero every time is slow and expensive. Helios agents carry context forward
in two ways.
## The persistent workspace
Files an agent writes under `~/workspace` survive between runs. For a workflow, every run shares the
same workspace, so an agent can leave itself notes, cached data, or state:
```
Keep a file at ~/workspace/processed.json listing the issue numbers you've
already handled. Skip any issue already in that list.
```
This is the memory you control directly. See [sandboxes](/docs/basics/sandboxes).
## API memory
When an agent works out how to accomplish a task against an
[integration's API](/docs/integrations) - which endpoints to search for, which calls to make in what
order - Helios records that procedure. The next time an agent takes on a similar task against the
same integration, it starts with that record instead of rediscovering the API.
This memory is:
- **Scoped to your organization and the specific integration.** It is never shared across
organizations.
- **Written automatically** after a task completes successfully, and read automatically before a
similar one begins.
- **Procedural, not data.** It records how an API was called, not the contents of your records.
There is nothing to configure and nothing to manage. It makes repeat tasks faster and more reliable.
API memory is managed by Helios and is not currently exposed for viewing or editing. If you need an
agent to behave differently, change the prompt - instructions in the prompt always take precedence.
## What is *not* memory
A chat's message history is part of that chat, not shared with other chats or with workflows.
[Forking a chat](/docs/basics/chat) copies its history and workspace into a new one; that is the only
way conversation context moves between sessions.
---
# 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"
updatedAt: "2026-07-09"
---
# Pricing and credits
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 cron trigger that runs hourly costs a twelfth of one that runs
every five minutes.
- **Persist state.** Keeping a record in `~/workspace` of what's 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.
---
# 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"
updatedAt: "2026-07-09"
---
# Projects and sharing
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 rather than the team - "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.
**Per-user roles** grant specific people a specific [role](/docs/basics/roles-permissions) on the
project: `user`, `editor`, or `admin`. An explicit grant beats the baseline.
The common shape is an organization-visible project at the `user` role - 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, rather than making each team
connect their own.
Credentials are never exposed by sharing an integration. Users of a shared integration can have
agents act through it; they cannot read the token 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, not to collaborate.
## What sharing does not cover
Database connections cannot be shared per-resource today. They are reachable by agents in the
organization that created them.
## 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 that every member carries, and per-resource roles that grant access to specific projects, workflows, chats, and integrations.
---
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 that every member carries, and per-resource roles that grant access to specific projects, workflows, chats, and integrations."
icon: Shield
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
# Roles and permissions
Access in Helios has two layers, and it helps to keep them apart.
1. **Organization role** - what you are in the company's account.
2. **Resource role** - what you can do to a specific project, workflow, chat, integration, database
connection, or MCP server.
## Organization roles
Every member of an organization carries exactly one organization role.
| Role | What it means |
| --- | --- |
| `admin` | Full control of the organization: members, billing, SSO, SCIM, API keys. |
| `member` | A normal user of the product. |
| `viewer` | Read-only at the account layer. |
Administrators are protected from lockout: the last admin in an organization cannot be demoted or
removed.
## Resource roles
Inside Helios, access to each resource is granted by a resource role.
| Role | Typically allows |
| --- | --- |
| `user` | Read the resource, list its runs, and trigger it. |
| `editor` | Everything `user` can do, plus create, update, and delete. |
| `admin` | Everything `editor` can do, plus view and change who has access. |
Concretely, for a [workflow](/docs/workflows): a `user` can read it, see its runs, and trigger it; an
`editor` can also edit the prompt, cancel runs, and delete it; an `admin` can also manage its
permissions.
### How the layers connect
When you access a resource, Helios resolves your role by walking from that resource outward: an
explicit grant on the resource itself, then a grant inherited from its project, and finally your
organization role.
Your organization role maps in as the baseline:
- Organization `admin` → resource `admin`.
- Organization `member` or `viewer` → resource `user`.
The organization `viewer` role is read-only at the account layer, but inside Helios it resolves to
the `user` resource role - which permits **triggering** a workflow. If a person must not be able to
run agents, don't grant them access to those workflows.
Nobody is an `editor` by default. The `editor` role is only ever obtained by an explicit grant on a
project or an individual resource.
## Visibility
Every resource is either:
- **Restricted** - reachable only by users with an explicit grant, or through the project it belongs
to. A restricted resource must always have at least one explicit admin.
- **Organization** - everyone in the organization gets a role on it. You choose which role.
Making a resource organization-visible is how you share it; see
[projects and sharing](/docs/basics/projects-and-sharing).
Visibility is managed today for **projects** and **integrations**. Workflows and chats inherit access
from the project they live in.
## Inheritance through projects
Resources belong to a [project](/docs/basics/projects-and-sharing), and by default they inherit their
access from it. Grant someone `editor` on a project and they can edit every workflow in it, without a
per-workflow grant.
This is why the project is the right unit to think about when granting access.
## API keys
API keys authenticate machines rather than people. Create them in your account settings, scoped to a
product - `helios`, `ci`, or `cache`. 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 admin of its organization,
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 E2B cloud sandboxes with a shell, a filesystem, code execution, web access, and a persistent workspace.
---
title: "Sandboxes"
excerpt: "Every agent gets its own isolated cloud computer"
description: "Helios agents run in isolated E2B cloud sandboxes with a shell, a filesystem, code execution, web access, and a persistent workspace."
icon: Box
createdAt: "2026-07-09"
updatedAt: "2026-07-09"
---
# Sandboxes
Every Helios agent runs inside its own **sandbox** - an isolated cloud computer, provisioned per
chat or per workflow run, powered by [E2B](https://e2b.dev). 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 image is Debian with a build toolchain, `git`, `jq`, and a JavaScript /
TypeScript runtime. The agent installs what else it needs.
**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).
## The workspace
Each sandbox mounts a persistent workspace at `~/workspace`, backed by durable object storage.
- For a **chat**, the workspace belongs to that chat. Uploaded files land in `~/workspace/uploads/`.
- For a **workflow**, the workspace belongs to the workflow and is shared by every run of it. Files
one run writes are there for the next.
Agents are instructed to write anything worth keeping under `~/workspace`, and to use `$TMPDIR` for
scratch work that should disappear when the run ends.
Deleting a chat or a workflow deletes its workspace.
## Lifetime
A sandbox stays alive while the agent is active and shuts down after a period of inactivity, roughly
fifteen minutes. Because the workspace lives in durable storage rather than in the sandbox, nothing
is lost - the next message or the next run gets a fresh sandbox with the same files.
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, not through raw credentials. 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"
updatedAt: "2026-07-09"
---
# SSO and SCIM
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 rather than integrating per-vendor, so any SAML 2.0 or OIDC identity
provider will connect. JumpCloud is the provider running in production today; if you're setting up
another and something doesn't line up, tell us and we'll work through it with you.
Contact support@warpbuild.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 today
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 when accepting an invitation, not on every sign-in.
- **No user-visible audit log.**
## 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.
---
# 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"
updatedAt: "2026-07-09"
---
# Variables and secrets
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.
Because they arrive as context rather than as text substitution, 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 `user`. 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.
---
# Authentication
URL: https://www.heliosapp.com/docs/integrations/auth
Description: Connect a service with a Helios-managed OAuth app, your own OAuth app, or an API key. Credentials are envelope-encrypted and never reach the agent.
---
title: "Authentication"
excerpt: "How Helios connects to your tools, and where credentials live"
description: "Connect a service with a Helios-managed OAuth app, your own OAuth app, or an API key. Credentials are envelope-encrypted and never reach the agent."
icon: Key
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
# Authentication
Each [integration](/docs/integrations) offers one or more ways to authenticate. Whichever you choose,
the credential is [envelope-encrypted](/docs/basics/variables-and-secrets) at rest and applied
server-side when an agent makes a call.
**Agents never hold your credentials.** When an agent calls an API, Helios attaches the credential to
the outbound request outside the agent's sandbox. There is nothing inside the sandbox for a prompt
injection to read. See [sandboxes](/docs/basics/sandboxes).
## Helios app (OAuth)
The fastest path, available for most OAuth services. Click connect, authorize in the provider's
consent screen, and you're done. Helios stores the access and refresh tokens and refreshes them
automatically.
Helios apps request broad scopes, so agents can use the full API rather than a slice of it. If that's
more than you want to grant, bring your own app.
## Bring your own OAuth app
Register an OAuth application with the provider and give Helios its client ID, client secret, and
tokens. Use this when you want to:
- request **fewer scopes** than the Helios app does,
- request **more** - a beta scope Helios doesn't ask for,
- show **your own branding** on the consent screen.
Setup is per-provider; each integration's page lists the exact fields it needs.
## API key
For services that authenticate with a long-lived key - Stripe, Resend, Apify, Plain, WarpBuild -
generate a key in the provider's dashboard and paste it into Helios.
Give the key the narrowest permissions the task requires. A read-only key is the simplest way to
guarantee an agent can't mutate anything.
### Rotating a key
1. Generate a **new** key at the provider.
2. Edit the integration in Helios, paste the new key, and save.
3. Revoke the **old** key at the provider.
Runs already in flight continue with the credential they started with.
## Per-user authorization
Some connections need two steps: the workspace or organization installs the app, and then each person
authorizes it individually. This is how an agent acts with the right identity rather than a shared
one.
This applies to:
- **[Slack](/docs/integrations/apps/slack)** - always.
- **[GitHub](/docs/integrations/apps/github)** - when the app is installed on an organization or
enterprise.
If an agent reports it can't reach one of these services, an unauthorized user is the usual cause.
## Who can connect and use an integration
Creating, editing, or deleting an integration requires the `editor` role on it; using one requires
`user`. Integrations have their own visibility, so you can connect GitHub once at organization
visibility and let every project's agents use it.
Sharing an integration never exposes its credential. Users of a shared integration can have agents
act *through* it; they cannot read the token behind it.
See [roles and permissions](/docs/basics/roles-permissions) and
[projects and sharing](/docs/basics/projects-and-sharing).
## Databases
Database connections authenticate differently - with a connection string, and optionally an SSH
tunnel keypair. Both are envelope-encrypted. See [databases](/docs/integrations/databases).
---
# Database Security Best Practices
URL: https://www.heliosapp.com/docs/integrations/databases-security
Description: How to safely expose databases to Helios agents via SSH bastions, scoped credentials, and read replicas
---
title: "Database Security Best Practices"
excerpt: "Recommended hardening for database connections used by Helios agents and workflows"
description: "How to safely expose databases to Helios agents via SSH bastions, scoped credentials, and read replicas"
icon: ShieldCheck
createdAt: "2026-05-10"
updatedAt: "2026-07-09"
---
These are recommendations for customers connecting [databases](/docs/integrations/databases) to Helios. The goal is to bound what an agent running in a sandboxed environment can do with the credentials you provide.
## Threat model
When you connect a database to Helios, an LLM-driven agent running inside an isolated sandbox is granted enough access to authenticate to that database. The sandbox holds your SSH key (if you use a bastion) and your database credentials for as long as the session lives. While the sandbox is isolated from the public internet on the inbound side, the agent code running inside it is, by design, untrusted: prompt injection, jailbreaks, or hostile tool output could cause it to use those credentials in ways you didn't intend.
The mitigations below are about **bounding the blast radius** of that access. None of them are required for the connection to work, but each one limits what an agent can do if it goes off-script.
## Use a read-only database role
The simplest and highest-leverage mitigation. Create a role on your database that only has `SELECT` on the tables you want the agent to introspect, and use that role's credentials in the Helios connection.
- The agent cannot write, update, delete, drop, or grant anything.
- SQL injection in the agent's prompt cannot mutate data.
- Schema introspection still works.
For Postgres:
```sql
CREATE ROLE helios_readonly LOGIN PASSWORD '...';
GRANT CONNECT ON DATABASE mydb TO helios_readonly;
GRANT USAGE ON SCHEMA public TO helios_readonly;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO helios_readonly;
ALTER DEFAULT PRIVILEGES IN SCHEMA public
GRANT SELECT ON TABLES TO helios_readonly;
```
## Point Helios at a read replica
Even better than a read-only role on the primary. Most managed Postgres services (RDS, Aurora, Supabase, Neon branches, Cloud SQL) let you create a read replica with a click.
- Production writes are physically impossible from the replica's endpoint.
- Expensive queries from the agent hit the replica, not your primary.
- If the agent ever escalates beyond read-only (e.g. a database CVE), the damage is contained to the replica.
Use the replica's host in the Helios connection string and a read-only role on that replica.
## Lock down your SSH bastion's `authorized_keys`
If you connect via an SSH tunnel, the SSH key you give Helios works for anything the bastion can reach by default: other databases, internal HTTP services, shell access on the bastion itself. To limit that key to forwarding only to the configured database, prepend restriction options to the key's line in `~/.ssh/authorized_keys` on your bastion:
```
no-pty,no-agent-forwarding,permitopen="db.internal:5432" ssh-ed25519 AAAA... helios
```
Replace `db.internal:5432` with your database host and port. Now the bastion refuses any forward request to a different target, so even if an agent had its own SSH client it could not pivot to other hosts.
Additional flags you may want depending on your bastion configuration:
- `no-X11-forwarding` - disables X11 forwarding.
- `no-port-forwarding` - too strict for our case; the tunnel relies on local-forward.
- `command="/bin/false"` - refuses interactive shell commands.
## Use a dedicated SSH key
Generate a fresh SSH keypair specifically for Helios, rather than reusing one of your developer keys. This makes auditing and revocation simple: rotate or remove the helios key on the bastion any time without affecting other access.
```
ssh-keygen -t ed25519 -f ~/.ssh/helios -C helios
```
Add the public key (`~/.ssh/helios.pub`) to your bastion's `authorized_keys` with the `permitopen` restriction above, and paste the private key into the Helios connection form.
## Restrict network reachability
If your bastion sits behind a firewall and you can reach it from the public internet, consider also restricting which source IPs are allowed to dial port 22. Helios connects from a stable egress range; contact support for the current IP list.
## Audit logs
All queries the agent runs are visible to you:
- Database side: enable query logging on your database (`pg_stat_statements`, etc.) to record what was actually executed against your data.
- Helios side: the agent session transcripts capture every tool call, including SQL strings.
We recommend keeping database-side logging on for any production-data connection.
## Summary
| Mitigation | Bounds |
|---|---|
| Read-only role | What the agent can do _at the database_ |
| Read replica | Where the agent's writes (if any) can land |
| `permitopen` on bastion | What the agent can reach _through_ the SSH key |
| Dedicated SSH key | How quickly you can rotate / revoke |
Layered together, the residual exposure is exactly what you chose to grant: read access to specific tables via a tunnel that can't pivot anywhere else.
---
# Databases
URL: https://www.heliosapp.com/docs/integrations/databases
Description: Connect a database and agents can discover its schema and run read-only queries, optionally through an SSH tunnel.
---
title: "Databases"
excerpt: "Let agents introspect and query Postgres, MySQL, and ClickHouse"
description: "Connect a database and agents can discover its schema and run read-only queries, optionally through an SSH tunnel."
icon: Database
createdAt: "2026-07-09"
updatedAt: "2026-07-09"
---
# Databases
Connect a database and your agents can explore it and answer questions from it - no ETL, no
pre-built reports.
Three engines are supported: **PostgreSQL**, **MySQL**, and **ClickHouse**.
## What an agent can do
An agent reaches your database through a dedicated tool with exactly three operations:
| Operation | What it does |
| --- | --- |
| List | See which database connections are available. |
| Introspect schema | Read tables, columns, types, primary keys, and foreign keys. |
| Run query | Execute a `SELECT` and read the rows back. |
Introspection is what makes this work without configuration. The agent discovers your schema, works
out which tables answer the question, and writes the query itself.
```
Every Monday, query the production database for signups in the last 7 days
grouped by plan, compare against the prior week, and post the numbers to
#growth.
```
## Queries are read-only
This is enforced by Helios, not merely requested of the agent:
- Queries run inside a **read-only transaction**.
- A **statement timeout** (60 seconds by default) bounds how long any one query can run.
- A **row limit** (100 by default) bounds how much comes back.
An agent cannot write, update, delete, or drop through this tool.
Enforcement on the Helios side is a backstop, not your whole defence. Point Helios at a read-only
role or a read replica - see [database security](/docs/integrations/databases-security).
## Connecting
1. Go to **Integrations → Databases** and add a connection.
2. Give it an **alias** you'll recognize; agents see this name.
3. Choose the engine and paste a **connection string**. Anything the driver understands - including
SSL parameters - belongs in the string.
4. Optionally configure an **SSH tunnel**.
The connection string, and any tunnel password or private key, are
[envelope-encrypted](/docs/basics/variables-and-secrets) with AWS KMS. They are decrypted only when a
query runs, and are never exposed to the agent.
Helios tests the connection on save, so you'll know immediately whether it works.
## SSH tunnels
If your database isn't reachable from the internet, connect through a bastion host. Supply the
tunnel's **host** and **user**, plus either a **password** or a **private key**. Helios opens a local
port forward for the duration of the query.
Default ports are assumed when the connection string omits them: 5432 for PostgreSQL, 3306 for MySQL,
8443 for ClickHouse.
An SSH key that can reach your bastion can, by default, reach anything else the bastion can. Restrict
it with `permitopen` - see [database security](/docs/integrations/databases-security).
## Access
Database connections belong to the organization that created them and are usable by its agents. They
cannot be shared per-resource or restricted to a single project today, so connect only databases the
organization as a whole should be able to query.
## Next
- **[Database security](/docs/integrations/databases-security)** - read-only roles, read replicas,
bastion hardening.
- **[Sandboxes](/docs/basics/sandboxes)** - how agents are isolated.
---
# Integrations
URL: https://www.heliosapp.com/docs/integrations
Description: Connect a service once and Helios agents can call any endpoint of its API - not a curated list of actions.
---
title: "Integrations"
excerpt: "Give your agents the full API of every tool you use"
description: "Connect a service once and Helios agents can call any endpoint of its API - not a curated list of actions."
icon: Puzzle
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
import { IntegrationsExplorer } from '@/components/docs/IntegrationsExplorer';
# Integrations
Connect a service once, and your agents can use **all of it**.
Most automation tools ship a fixed list of actions per service - "create issue", "post message" - and
you're stuck when the task needs the hundred-and-first. Helios indexes each service's **entire API
surface**. When an agent needs to do something, it searches that index for the right endpoint and
calls it, with authentication applied server-side.
The practical consequence: if the service's API can do it, your agent can do it.
## Browse
## How it works
1. **You connect the service.** Helios stores the credential
[envelope-encrypted](/docs/basics/variables-and-secrets).
2. **An agent needs something.** It searches the service's indexed API - Helios keeps a semantic
index of every endpoint, its parameters, and its docs.
3. **It calls the endpoint.** Helios attaches your credential to the outbound request. The agent
never sees it. See [sandboxes](/docs/basics/sandboxes).
Agents can also reason across services in one task: read a Typeform response, enrich the contact in
Apollo, create the record in Attio, and post to Slack - because each one is just another API it can
reach.
## Triggers
Three services can also *start* an agent when something happens in them:
| Service | Events |
| --- | --- |
| [GitHub](/docs/integrations/apps/github) | Pull requests, issues, pushes, tags, releases, workflow runs, issue comments |
| [Slack](/docs/integrations/apps/slack) | Messages in public and private channels |
| [Plain](/docs/integrations/apps/plain) | New customer threads and chats |
Every other integration is reachable *from* an agent - you just start the agent some other way, with
a [schedule, a webhook, or manually](/docs/workflows/triggers).
## Beyond the catalog
- **[Databases](/docs/integrations/databases)** - query Postgres, MySQL, and ClickHouse directly,
through an SSH tunnel if you need one.
- **[MCP servers](/docs/basics/mcp-servers)** - attach any remote MCP server to bring your own tools.
- **The web** - every agent can search the web and scrape a page without any integration at all.
## Authentication
Most services offer several ways to connect: a Helios-managed OAuth app for one-click setup, your own
OAuth app when you want to control scopes and branding, or a plain API key. See
[authentication](/docs/integrations/auth) for the general model, and each service's page for its
specific setup.
## Getting help
Something not connected that you need? Email
[integrations@heliosapp.com](mailto:integrations@heliosapp.com).
Trouble with an integration you've set up? Check that service's page, or reach us through the in-app
chat or [support@heliosapp.com](mailto:support@heliosapp.com).
---
# Workflows
URL: https://www.heliosapp.com/docs/workflows
Description: A Helios workflow is an agent prompt attached to one or more triggers. Describe the task in plain English and choose when it should run.
---
title: "Workflows"
excerpt: "Put an agent on a task permanently - a prompt plus its triggers"
description: "A Helios workflow is an agent prompt attached to one or more triggers. Describe the task in plain English and choose when it should run."
icon: Workflow
createdAt: "2026-07-09"
updatedAt: "2026-07-09"
---
# Workflows
A workflow is an agent you've put on a task permanently. It has two essential parts:
1. A **prompt** - the task, written in plain English.
2. One or more **[triggers](/docs/workflows/triggers)** - when the agent should pick it up.
That's the whole model. Each time a trigger fires, Helios starts an agent in a fresh
[sandbox](/docs/basics/sandboxes), hands it your prompt and the trigger's payload, and records the
result as a [run](/docs/workflows/runs-and-outputs).
## Creating a workflow
Workflows live inside a [project](/docs/basics/projects-and-sharing). From your project, choose
**Create Workflow**, give it a name, and write the prompt.
A workflow won't run until it has a prompt. Triggering an empty workflow returns an error.
## Writing the prompt
The prompt is a standing instruction, not a one-off question. Two things make a large difference:
**Be explicit about when to act.** The agent runs unattended and sees the trigger payload alongside
your prompt. Tell it what to do when the event doesn't apply.
```
When a pull request is opened in acme/api:
- If it only touches files under docs/, add the "documentation" label and stop.
- Otherwise, review the diff for changes to authentication or billing code.
If you find any, comment on the PR listing the specific files and why they
need a second reviewer.
- If nothing is risky, do nothing. Don't comment.
```
**Ask it to verify, not assume.** Agents are told to gather context with tools and to stop with a
clear error rather than guess. Prompts that say "check the current state of X before deciding" get
better results than prompts that assume state.
## What the agent can reach
Every workflow run has the full agent toolkit: a shell and filesystem, code execution, web search
and scraping, your connected [integrations](/docs/integrations), your
[databases](/docs/integrations/databases), and any [MCP servers](/docs/basics/mcp-servers) attached
to the project.
Two things are configured per workflow:
- **[Integration resources](/docs/basics/integration-resources)** - pin specific GitHub repositories
so the agent has authenticated access to them and knows which repo "the repo" means.
- **[Variables](/docs/basics/variables-and-secrets)** - variables visible to the workflow's project
are passed into every run as context the agent may use.
Workflow runs use Helios's frontier agent model. There is no per-workflow model setting today.
## Persisting work between runs
Each workflow has its own persistent workspace at `~/workspace`, backed by durable storage and
scoped to that workflow. Files written there are available to every subsequent run - useful for
state an agent needs to carry forward, like "the last issue number I processed."
Anything written outside `~/workspace` (for example under `$TMPDIR`) disappears when the run ends.
## Running a workflow by hand
Any workflow can be dispatched manually, whatever triggers it has. Manual runs can carry an
arbitrary JSON input payload, which the agent receives as trigger context - handy for testing a
prompt before you attach a schedule to it.
## Next
- **[Triggers](/docs/workflows/triggers)** - manual, cron, webhook, and integration events.
- **[Runs and outputs](/docs/workflows/runs-and-outputs)** - statuses, transcripts, output formats,
and cancellation.
---
# Runs and outputs
URL: https://www.heliosapp.com/docs/workflows/runs-and-outputs
Description: Every workflow execution is a run: a full agent transcript, a structured result, and a status you can act on.
---
title: "Runs and outputs"
excerpt: "Statuses, transcripts, results, and cancellation"
description: "Every workflow execution is a run: a full agent transcript, a structured result, and a status you can act on."
icon: ListChecks
createdAt: "2026-07-09"
updatedAt: "2026-07-09"
---
# Runs and outputs
Every time a [trigger](/docs/workflows/triggers) fires, Helios creates a **run**. A run records the
trigger context that started it, the agent's full transcript, the final result, and - if something
went wrong - the error.
## Statuses
| Status | Meaning |
| --- | --- |
| `queued` | The run is created and waiting for an agent to pick it up. |
| `running` | An agent is working the task in its sandbox. |
| `succeeded` | The agent finished and produced a result. |
| `failed` | The agent reported a failure, errored, or timed out. |
| `pending_cancel` | You asked to cancel; Helios is stopping the agent. |
| `cancelled` | The run stopped before finishing. |
Statuses only move forward. A run that has already succeeded, failed, or been cancelled will not be
overwritten by a later transition.
## The transcript
A run stores every message in the agent's session - its reasoning, each tool call it made, and each
result that came back. This is the ground truth for debugging a prompt: you can see exactly which
API the agent chose, what it sent, and what it got.
## Outputs
When an agent finishes, Helios extracts a final result from the transcript and stores it in one of
three formats:
| Format | When it's used |
| --- | --- |
| `markdown` | The result is a formatted report, digest, or summary. |
| `plainText` | The result is short and simple. |
| `json` | The result is structured data. |
The format is chosen automatically from the shape of the agent's answer - there is no output schema
to configure. If you need structured data, say so in the prompt ("return the results as a JSON array
of `{repo, prCount}` objects") and the result will be stored as `json`.
If the agent determines it could not complete the task, it reports a failure. The run ends as
`failed` and the reason is stored on the run rather than as an output.
## Cancelling a run
Cancel a `queued` or `running` run at any time. The run moves to `pending_cancel`, and the agent is
signalled to stop; Helios checks for the signal every few seconds, so a running agent stops within
moments rather than instantly. Once it stops, the run becomes `cancelled`.
A run that was still `queued` when you cancelled it goes straight to `cancelled` without ever
starting an agent.
Deleting a workflow cancels any of its runs that are still queued or running.
## Timeouts and failures
A run has a **30-minute execution limit**. An agent that is still working when the limit is reached
is stopped and the run is marked `failed` with a timeout error.
Runs also fail before they start if the workflow has no prompt, or if your organization has exhausted
its Helios credits. See [pricing](/docs/basics/pricing).
## Retention
Runs, their transcripts, and their outputs are kept for as long as the workflow exists - there is no
automatic expiry. Deleting a workflow deletes its runs, and clears the workflow's persistent
`~/workspace` storage.
---
# Triggers
URL: https://www.heliosapp.com/docs/workflows/triggers
Description: Decide when your agent picks up the task: run it by hand, on a schedule, from a signed webhook, or on an event from GitHub, Slack, or Plain.
---
title: "Triggers"
excerpt: "Manual, cron, webhook, and integration event triggers"
description: "Decide when your agent picks up the task: run it by hand, on a schedule, from a signed webhook, or on an event from GitHub, Slack, or Plain."
icon: Play
createdAt: "2026-07-09"
updatedAt: "2026-07-09"
---
# Triggers
A trigger decides when a [workflow](/docs/workflows) runs. A workflow can have any number of
triggers, of any mix of types, each with its own label. Whichever one fires, the agent receives your
prompt plus that trigger's payload as context.
There are four types: **manual**, **cron**, **webhook**, and **integration events**.
## Manual
Run the workflow yourself, on demand. Every workflow can be dispatched manually regardless of which
other triggers it has, which makes this the easiest way to test a prompt.
A manual run can carry an arbitrary JSON input payload. The agent sees it as trigger context, so you
can rehearse an event-driven prompt by handing it a sample event.
## Cron
Run the workflow on a schedule, using a standard cron expression with either five fields
(minute, hour, day-of-month, month, day-of-week) or six (a leading seconds field). Ranges (`-`),
lists (`,`), steps (`/`), and wildcards (`*`) all work.
```
0 9 * * 1-5 # 9:00 every weekday
*/15 * * * * # every 15 minutes
0 0 1 * * # midnight on the 1st of each month
```
**Cron schedules run in UTC.** Convert your local time before entering an expression, or describe
the schedule in plain English and let Helios do it (below).
### Natural language schedules
Instead of a cron expression you can describe the schedule - "every weekday at 9am Eastern", "the
first Monday of the month" - and Helios converts it to a cron expression, handling the timezone
conversion to UTC for you. You'll see the generated expression before you save it, and a plain-English
readback of what it means.
If a description is too ambiguous to convert, Helios says so rather than guessing.
### Default input
A cron trigger can carry a default JSON input passed to the agent on every scheduled run.
## Webhook
A webhook trigger exposes a public URL that any HTTP client can `POST` to:
```
https:///webhooks/agent-trigger//
```
The request body is parsed as JSON and handed to the agent as trigger context. An empty body is
treated as `{}`. A successful request returns the id of the run it started.
### Signing
Because the URL is public, every request must carry a valid HMAC-SHA256 signature derived from a
per-trigger signing secret. Helios generates the secret when you add the trigger; you can reveal it
from the workflow's trigger panel.
| Header | Value |
| --- | --- |
| `X-Helios-Timestamp` | Unix seconds at the moment of signing |
| `X-Helios-Signature` | `sha256=` |
To sign a request:
1. Capture the raw request body as bytes.
2. Compute `HMAC-SHA256(secret, ".")` and hex-encode it.
3. Send both headers above.
```ts
import crypto from "node:crypto";
const url = "";
const secret = "";
const ts = Math.floor(Date.now() / 1000);
const body = JSON.stringify({ hello: "world" });
const sig = crypto
.createHmac("sha256", secret)
.update(`${ts}.${body}`)
.digest("hex");
await fetch(url, {
method: "POST",
headers: {
"Content-Type": "application/json",
"X-Helios-Timestamp": String(ts),
"X-Helios-Signature": `sha256=${sig}`,
},
body,
});
```
```bash
ts=$(date +%s)
body='{"hello":"world"}'
sig=$(printf '%s.%s' "$ts" "$body" \
| openssl dgst -sha256 -hmac "$SECRET" -hex \
| awk '{print $2}')
curl -X POST "$URL" \
-H "X-Helios-Timestamp: $ts" \
-H "X-Helios-Signature: sha256=$sig" \
-H 'Content-Type: application/json' \
--data "$body"
```
Helios rejects a request with `401` when the signature header is missing or doesn't begin with
`sha256=`, when the timestamp is more than **5 minutes** away from server time, or when the digest
doesn't match. The response body is deliberately generic; the precise reason is in your workflow's
server-side logs.
Three details that cause most signing bugs:
- The secret is signed as a **UTF-8 string**, not decoded from hex. Don't `Buffer.from(secret, "hex")`
on one side only.
- The body is signed **exactly as transmitted**. A proxy that reformats JSON or changes whitespace
will break the signature.
- An empty body signs as the empty string - sign over `"."` with nothing after the dot.
### Rotating the secret
Rotate a webhook trigger's signing secret from the workflow's trigger panel. **Rotation takes effect
immediately and there is no overlap window** - every existing sender gets `401` until it is
reconfigured with the new secret.
## Integration events
Run the workflow when something happens in a connected service. Three services emit events into
Helios today: **GitHub**, **Slack**, and **Plain**.
Choose the integration, the event, and any filters. The agent receives the full event payload as
trigger context.
### Filters
Each event exposes a set of filter fields. Within one field, multiple values are **OR**'d; across
different fields they are **AND**'d. Leaving a field empty means "match anything".
Fields marked as patterns accept glob syntax: `*` (any characters within a segment), `?` (one
character), `**` (across segments), `[abc]` / `[a-z]` (character classes), and `{a,b}` (alternation).
### GitHub
Every GitHub event requires a repository filter.
| Event | Filters |
| --- | --- |
| `pull_request.opened` | repository |
| `pull_request.closed` | repository |
| `pull_request.synchronize` | repository |
| `pull_request.labeled` | repository, label (pattern) |
| `issues.opened` | repository |
| `issues.closed` | repository |
| `issues.labeled` | repository, label (pattern) |
| `push` | repository, branch (pattern, **required**) |
| `tag.created` | repository, tag name (pattern) |
| `release.published` | repository |
| `workflow_run.completed` | repository, workflow name (pattern), conclusion |
| `issue_comment.created` | repository |
### Slack
| Event | Filters |
| --- | --- |
| `message.channel` - a message in a public channel | channel |
| `message.group` - a message in a private channel | channel |
Omit the channel filter to match every channel the Helios bot can see.
### Plain
| Event | Filters |
| --- | --- |
| `thread.thread_created` - a customer opens a new thread | none |
| `thread.chat_received` - a new chat message from a customer | none |
Plain requires manual webhook configuration. After connecting the integration, paste the webhook URL
Helios shows you into Plain's settings so events reach Helios.
## Guarding against events you don't want
Filters narrow which events reach your agent, but they can't express everything. The agent sees the
event payload and your prompt together, so the prompt is the second filter - say plainly what should
happen when the event doesn't warrant action:
```
When a pull request is opened in acme/api, review the diff.
If it only touches files under docs/, do nothing and stop.
```
Agents are instructed to stop as soon as they determine no action is required, so a run that decides
to do nothing still succeeds - it just has no side effects.
## Next
- **[Runs and outputs](/docs/workflows/runs-and-outputs)** - what happens after a trigger fires.
- **[Integrations](/docs/integrations)** - connecting GitHub, Slack, and Plain.
---
# Apify
URL: https://www.heliosapp.com/docs/integrations/apps/apify
Description: The Apify integration lets Helios agents run actors, extract web data, manage datasets, and work with Apify's platform directly.
---
title: "Apify"
excerpt: "Run Apify actors, extract web data, and manage datasets with Helios agents."
description: "The Apify integration lets Helios agents run actors, extract web data, manage datasets, and work with Apify's platform directly."
icon: /static/img/assets/apify.svg
createdAt: "2025-09-26"
updatedAt: "2026-07-09"
---
## What your agents can do
Helios agents don't work from a preset list of actions. They semantically search the entire Apify API and call any endpoint directly, with authentication handled server-side. Anything you can do with your Apify Personal Access Token, an agent can do on your behalf.
- Run any Apify actor and wait for its results
- Pull items from a dataset and summarize them into Slack or Notion
- Start a scraping run and monitor it to completion
- Read and write key-value stores and request queues
- List actors, runs, and schedules across your account
- Inspect run logs, usage, and billing details
## Authentication
| Method | Type | Description |
| --------------------- | ----------- | ------------------------------------------------- |
| Personal Access Token | Token-based | Server-to-server access with your Apify API token |
### Personal Access Token
Connect Apify with a Personal Access Token (PAT) for server-to-server authentication.
#### Setup Steps
1. Go to your [Apify Console](https://console.apify.com/)
2. Navigate to **Settings → Integrations → Personal Access Tokens**
3. Click **Create new token**
4. Provide a descriptive name for your token
5. Select the appropriate scopes for your use case
6. Click **Create token**
7. Copy the generated token and paste it into Helios
8. Save your integration
Store your Personal Access Token securely. It provides access to your Apify account and cannot be recovered once lost.
## Triggers
Apify does not currently emit event triggers into Helios. Use it from Chat, or from a Workflow driven by a [schedule, webhook, or manual run](/docs/workflows/triggers).
---
# Apollo
URL: https://www.heliosapp.com/docs/integrations/apps/apollo
Description: The Apollo.io integration lets Helios agents search for prospects, enrich contact data, manage sequences, and run sales outreach directly.
---
title: "Apollo"
excerpt: "Automate lead generation, prospecting, and sales outreach with Apollo.io from your Helios agents."
description: "The Apollo.io integration lets Helios agents search for prospects, enrich contact data, manage sequences, and run sales outreach directly."
icon: /static/img/assets/apollo-light.svg
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
## What your agents can do
Helios agents don't work from a preset list of actions. They semantically search the entire Apollo.io API and call any endpoint directly, with authentication handled server-side. Anything you can do in Apollo, an agent can do on your behalf.
- Search for people and companies matching a target profile
- Enrich a contact or account with emails, phone numbers, and firmographics
- Create and update contacts and accounts
- Enroll prospects in sequences and manage outreach
- Pull sequence and engagement stats to report on outreach
- Look up your account, users, and saved lists
## Authentication
| Method | Type | Description |
| ------------------------------ | ---------------- | ----------------------------------------------- |
| Helios Apollo App (Recommended) | OAuth 2.0 | User-specific access via a redirect OAuth flow |
| API Key | Server-to-Server | Simple authentication with your account API key |
| BYO Apollo App | OAuth 2.0 | Custom OAuth app for enterprise requirements |
### Helios Apollo App (Recommended)
The Helios Apollo App connects through a standard OAuth redirect flow and is the recommended way to connect. Choose it in Helios, authorize access to your Apollo account, and Helios handles token management for you.
### API Key
Connect Apollo.io using your account API key if you already have one.
#### Setup Steps
1. Go to your [Apollo.io account](https://app.apollo.io/)
2. Go to **Settings → Integrations & API → API**
3. Copy your API key
4. Paste the API key into Helios and save your integration
### BYO Apollo App
Bring your own Apollo.io OAuth application for enterprise requirements or custom control. You supply the client ID, client secret, access token, and refresh token.
> Learn more about creating Apollo.io apps in the [Apollo.io documentation](https://apolloio.github.io/apollo-api-docs/).
## Triggers
Apollo does not currently emit event triggers into Helios. Use it from Chat, or from a Workflow driven by a [schedule, webhook, or manual run](/docs/workflows/triggers).
---
# Attio
URL: https://www.heliosapp.com/docs/integrations/apps/attio
Description: The Attio integration lets Helios agents manage CRM records, run sales processes, track interactions, and sync data with Attio's customizable platform directly.
---
title: "Attio"
excerpt: "Manage contacts, companies, deals, and CRM data with Attio from your Helios agents."
description: "The Attio integration lets Helios agents manage CRM records, run sales processes, track interactions, and sync data with Attio's customizable platform directly."
icon: /static/img/assets/attio-light.svg
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
## What your agents can do
Helios agents don't work from a preset list of actions. They semantically search the entire Attio API and call any endpoint directly, with authentication handled server-side. Anything you can do in your Attio workspace, an agent can do on your behalf.
- Look up a person, company, or deal and summarize their recent activity
- Create and update records across standard and custom objects
- Add records to lists and manage list entries
- Read and write notes, tasks, and comments on records
- Pull records matching a filter and report on your pipeline
- Read workspace members and object configuration
## Authentication
| Method | Type | Description |
| ------------------------------ | --------- | ----------------------------------------------- |
| Helios Attio App (Recommended) | OAuth 2.0 | Pre-configured scopes for common CRM operations |
| BYO Attio App | OAuth 2.0 | Custom OAuth app for enterprise requirements |
### Helios Attio App (Recommended)
The Helios Attio App connects through a standard OAuth redirect flow with pre-configured permissions covering most CRM use cases. Choose it in Helios, authorize access to your Attio workspace, and Helios handles token management for you.
The app requests read and read-write access to: user management, record permissions, object configuration, list entries, list configuration, and public and private collections.
### BYO Attio App
Bring your own Attio OAuth application for custom control over scopes and branding. You supply the client ID, client secret, and access token.
#### Setup Steps
1. Go to [Attio Developer Settings](https://app.attio.com)
2. Create a new OAuth application
3. Configure the required scopes for your use case
4. Copy the client ID and client secret into Helios
> Learn more about creating Attio apps in the [Attio API documentation](https://developers.attio.com).
## Triggers
Attio does not currently emit event triggers into Helios. Use it from Chat, or from a Workflow driven by a [schedule, webhook, or manual run](/docs/workflows/triggers).
---
# Discord
URL: https://www.heliosapp.com/docs/integrations/apps/discord
Description: The Discord integration lets Helios agents interact with Discord to read/send messages, manage channels, automate community interactions and much more.
---
title: "Discord"
excerpt: "Send messages, manage channels, and automate community interactions with Discord from your Helios agents."
description: "The Discord integration lets Helios agents interact with Discord to read/send messages, manage channels, automate community interactions and much more."
icon: Si-Discord
createdAt: "2025-09-29"
updatedAt: "2026-07-09"
---
## What your agents can do
Helios agents don't work from a preset list of actions. They semantically search the entire Discord API and call any endpoint directly, with authentication handled server-side. Anything your Discord bot has permission to do, an agent can do on your behalf.
- Post a message or rich embed to a channel
- Read recent messages from a channel and summarize them
- Create and manage channels, threads, and roles
- Add reactions, mention users, and pin messages
- Look up server members and their roles
- Manage the server on behalf of your bot
## Authentication
| Method | Type | Description |
| --------------- | --------- | --------------------------------------------------------------------- |
| BYO Discord Bot | Bot Token | Your own Discord bot, with full control over its permission set and branding |
Helios bot is not supported for Discord due to permissions limitations.
#### BYO Discord Bot
Create your own Discord bot application for interacting with Discord
through Helios. You supply the client ID, client secret, and bot token.
##### Setup Steps
Go to [Discord Developer Portal](https://discord.com/developers/applications).
Click **New Application** and give it a name.
Navigate to the 'Installation' section and
scroll to the bottom of the page to the 'Default Install Settings'.
Click on the Guild Install scope dropdown > Select 'bot' from the scope list.
A new permissions section will show up for the Guild Install. Click on the dropdown
and select the appropriate permissions for your bot. You can either give the bot exact
permission set or you can give it 'Administrator' permission. 'Administrator' permission
has complete access to the Discord API. Finally, click 'Save Changes'.
Discord should give you a confirmation at the top of the page.
Copy and paste the install link in your browser.
Click on 'Add to Server'. Select your server. Click on 'Continue'.
Click on 'Authorize' on the next screen.
Discord should redirect you to a success screen here.
Close the tab and go back to your application settings. Navigate to the
OAuth2 section. Copy the 'Client ID' from this page.
Navigate to the [create Discord integration](http://localhost:3000/helios/integrations/discord?modal=true&mode=create) page.
Give the integration a name. Paste your client ID.
Navigate back to your Discord application page and click on 'Reset Secret'
under the 'Client Secret' section. This will open a verification popup.
Click on 'Yes, do it!'. Discord may ask you to perform additional steps
for verification like password verification. It should show a newly generated
secret in the 'Client Secret' section. Please copy it.
The client secret here is sensitive information, do not share this with anyone. We show
the token here for simplicity; the token shown here is revoked and is no longer in use.
Navigate back to the 'Create Discord Integration' tab on Helios and paste
the token in the Client Secret section.
Navigate back to the Discord applications tab > Go to the Bot section. Generate
and copy the 'Token'. You'll need to follow steps similar to the 'Client Secret' generation.
Copy the token and navigate back to the 'Create Discord Integration' tab on Helios. Paste the
Bot Token and click on 'Test Connection' to validate.
Click on 'Create Integration'.
Learn more about creating Discord bots in the [Discord documentation](https://discord.com/developers/docs/quick-start/overview-of-apps).
## Triggers
Discord does not currently emit event triggers into Helios. Use it from Chat, or from a Workflow driven by a [schedule, webhook, or manual run](/docs/workflows/triggers).
---
# GitHub
URL: https://www.heliosapp.com/docs/integrations/apps/github
Description: The GitHub integration lets Helios agents search and call the entire GitHub REST API to manage repositories, automate pull requests and issues, drive GitHub Actions, and run automatically on repository events.
---
title: "GitHub"
excerpt: "Give your agents access to GitHub - manage repositories, pull requests, issues, and CI/CD by calling any GitHub API endpoint."
description: "The GitHub integration lets Helios agents search and call the entire GitHub REST API to manage repositories, automate pull requests and issues, drive GitHub Actions, and run automatically on repository events."
icon: Si-Github
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
## What your agents can do
Helios agents don't choose from a fixed menu of GitHub actions. They semantically search GitHub's entire REST API and call any endpoint directly, with authentication injected server-side - so anything the GitHub API can do, an agent can do on your behalf.
- Open, review, comment on, and merge pull requests
- Triage issues - label, assign, close, and reply
- Read and write repository contents, branches, tags, and releases
- Kick off and inspect GitHub Actions runs, check runs, and workflow status
- Manage collaborators, teams, and repository settings
- Clone a repo and work directly in its code (see [Pinned resources](#pinned-resources))
## Authentication
| Method | Type | Description |
| ------------------------------- | ----------- | ------------------------------------------------------ |
| Helios GitHub App (Recommended) | GitHub App | Install with a single redirect; Helios manages tokens |
| Personal Access Token | Token-based | You supply a PAT with the scopes your agents need |
| BYO GitHub App | GitHub App | You supply your own App's ID, private key, and install |
See [Integration authentication](/docs/integrations/auth) for how credentials are stored and injected.
### Helios GitHub App (Recommended)
Connecting through the Helios GitHub App is the fastest path. When you create the integration, Helios redirects you to GitHub to install the app and pick the repositories or organization it can access. Tokens are minted and refreshed for you - you never handle a credential.
For an organization or enterprise install, each user who wants their agents to act must also complete a one-time **per-user authorization** before those agents can use the integration.
### Personal Access Token
You can also connect with a Personal Access Token (PAT) scoped to your use case.
1. Go to [GitHub Settings → Developer settings → Personal access tokens](https://github.com/settings/tokens).
2. Click **Generate new token → Generate new token (classic)**.
3. Select the scopes your agents need (e.g. `repo`, `workflow`, `read:org`).
4. Copy the generated token and paste it into Helios.
5. Save the integration.
### BYO GitHub App
Bring your own GitHub App when you need custom branding or your own permission model.
1. Go to [GitHub Settings → Developer settings → GitHub Apps](https://github.com/settings/apps).
2. Click **New GitHub App** and configure its permissions and events.
3. Generate and download a private key.
4. Install the app on your repositories and note the **installation ID**.
5. In Helios, provide the **App ID**, **private key**, and **installation ID**.
### Supported deployments
The integration works across GitHub deployments. Select the matching API version when you connect:
| Deployment | API version | Notes |
| ------------------------- | ------------- | ------------------------------------------------ |
| GitHub.com | `2022-11-28` | Default for github.com |
| GitHub Enterprise Cloud | `ghec` | Enterprise-hosted cloud |
| GitHub Enterprise Server | `ghes-3.17` | Self-hosted - you must supply your GHES base URL |
## Triggers
GitHub is one of only three integrations that emit **event triggers** into Helios, so a [Workflow](/docs/workflows) can run an agent automatically when something happens in a repository. Every event requires a **repository** (`repoId`) filter; some events support additional filters.
| Event | Filters |
| ------------------------- | ------------------------------------------------ |
| `pull_request.opened` | repository |
| `pull_request.closed` | repository |
| `pull_request.synchronize`| repository |
| `pull_request.labeled` | repository, label (glob) |
| `issues.opened` | repository |
| `issues.closed` | repository |
| `issues.labeled` | repository, label (glob) |
| `push` | repository, branch (glob, **required**) |
| `tag.created` | repository, tag name (glob) |
| `release.published` | repository |
| `workflow_run.completed` | repository, workflow name (glob), conclusion |
| `issue_comment.created` | repository |
**Filter semantics:** multiple values for the same field are OR'd; different fields are AND'd. Glob patterns support `*`, `?`, `**`, `[abc]`, and `{a,b}`.
See [Triggers](/docs/workflows/triggers) for how to attach these to a Workflow.
## Pinned resources
GitHub is the only integration that supports **pinned resources**. You can attach specific **repositories** to a [chat](/docs/basics/chat) or a [Workflow](/docs/workflows). Helios then mints a short-lived, repo-scoped installation token and injects it at the network layer, so the agent can `git clone` and work in the repo without ever seeing a credential.
Learn more in [Integration resources](/docs/basics/integration-resources).
---
# Google Docs
URL: https://www.heliosapp.com/docs/integrations/apps/google-docs
Description: The Google Docs integration lets Helios agents search the Google Docs API and call any endpoint to create documents, edit content, and manage formatting.
---
title: "Google Docs"
excerpt: "Let Helios agents create, edit, and manage documents in Google Docs."
description: "The Google Docs integration lets Helios agents search the Google Docs API and call any endpoint to create documents, edit content, and manage formatting."
icon: /static/img/assets/google-docs-light.svg
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
## What your agents can do
Agents don't pick from a preset list of actions. They semantically search the entire Google Docs API and call whatever endpoint a task needs, using your connected credentials. Because the Docs integration can also reach the Google Drive API, an agent can locate a file in Drive and then open and edit it in Docs.
- Create new documents from a prompt, outline, or template
- Read and extract text, structure, and formatting from an existing document
- Insert, replace, or restyle content in place
- Apply headings, named styles, and text formatting
- Find a document in Drive and edit it in Docs
## Authentication
| Method | Type | Description |
| ------------------------------- | --------- | --------------------------------------------------- |
| Helios Google app (recommended) | OAuth 2.0 | Per-user consent with pre-configured document scopes |
| BYO Google app | OAuth 2.0 | Bring your own Google OAuth app and credentials |
### Helios Google app (recommended)
Connect in one click. Helios runs the Google OAuth redirect flow and asks each user for consent (`access_type=offline`, `prompt=consent`) so agents can act on your behalf, including when you're offline.
The Helios Google app requests scopes to:
- Read and write Google Docs documents (`documents`, `documents.readonly`)
- Discover documents in Google Drive, read-only (`drive.readonly`)
- Access the specific Drive files you open with Helios (`drive.file`)
### BYO Google app
Bring your own Google OAuth application when you need custom scopes or branding.
1. Go to [Google Cloud Console](https://console.cloud.google.com/)
2. Create a new project or select an existing one
3. Enable the Google Docs API (and the Google Drive API)
4. Configure the OAuth consent screen
5. Create OAuth 2.0 credentials (client ID and client secret)
6. Add the Helios redirect URI to your OAuth client
7. In Helios, supply your client ID, client secret, an access token, a refresh token, and the Google account email
> Learn more in the [Google Docs API documentation](https://developers.google.com/docs/api).
## Triggers
Google Docs does not currently emit event triggers into Helios. Use it from Chat, or from a Workflow driven by a [schedule, webhook, or manual run](/docs/workflows/triggers).
---
# Google Drive
URL: https://www.heliosapp.com/docs/integrations/apps/google-drive
Description: The Google Drive integration lets Helios agents search the Google Drive API and call any endpoint to upload, organize, and manage files and folders.
---
title: "Google Drive"
excerpt: "Let Helios agents store, search, and manage files and folders in Google Drive."
description: "The Google Drive integration lets Helios agents search the Google Drive API and call any endpoint to upload, organize, and manage files and folders."
icon: Si-Googledrive
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
## What your agents can do
Agents don't pick from a preset list of actions. They semantically search the entire Google Drive API and call whatever endpoint a task needs, using your connected credentials. There is no fixed set of file operations to choose from.
- Search and list files and folders across your Drive
- Read file content and metadata
- Create and upload new files and folders
- Organize, copy, and update files the agent created or you opened with Helios
- Read Google Meet recordings and photos (read-only)
- Manage the hidden app-data folder
## Authentication
| Method | Type | Description |
| ------------------------------- | --------- | ------------------------------------------------- |
| Helios Google app (recommended) | OAuth 2.0 | Per-user consent with pre-configured Drive scopes |
| BYO Google app | OAuth 2.0 | Bring your own Google OAuth app and credentials |
### Helios Google app (recommended)
Connect in one click. Helios runs the Google OAuth redirect flow and asks each user for consent (`access_type=offline`, `prompt=consent`) so agents can act on your behalf, including when you're offline.
The Helios Google app requests scopes to:
- Read files and file metadata (`drive.readonly`, `drive.metadata`, `drive.metadata.readonly`)
- Create and manage files it opens with Helios (`drive.file`)
- Read Google Meet recordings and photos, read-only (`drive.meet.readonly`, `drive.photos.readonly`)
- Manage the hidden app-data folder and read installed-app metadata (`drive.appdata`, `drive.apps.readonly`)
### BYO Google app
Bring your own Google OAuth application when you need custom scopes or branding.
1. Go to [Google Cloud Console](https://console.cloud.google.com/)
2. Create a new project or select an existing one
3. Enable the Google Drive API
4. Configure the OAuth consent screen
5. Create OAuth 2.0 credentials (client ID and client secret)
6. Add the Helios redirect URI to your OAuth client
7. In Helios, supply your client ID, client secret, an access token, a refresh token, and the Google account email
> Learn more in the [Google Drive API documentation](https://developers.google.com/drive/api).
## Triggers
Google Drive does not currently emit event triggers into Helios. Use it from Chat, or from a Workflow driven by a [schedule, webhook, or manual run](/docs/workflows/triggers).
## Notes
Helios requests read access to your Drive plus write access to files it creates or you explicitly open with it (`drive.file`). It deliberately does not request the full `drive` or `drive.scripts` scopes, so agents cannot modify arbitrary existing files they did not create.
---
# Gmail
URL: https://www.heliosapp.com/docs/integrations/apps/google-gmail
Description: The Gmail integration lets Helios agents search the Gmail API and call any endpoint to send email, read and organize messages, and manage labels and settings.
---
title: "Gmail"
excerpt: "Let Helios agents send, read, and organize email in Gmail."
description: "The Gmail integration lets Helios agents search the Gmail API and call any endpoint to send email, read and organize messages, and manage labels and settings."
icon: /static/img/assets/gmail-light.svg
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
## What your agents can do
Agents don't pick from a preset list of actions. They semantically search the entire Gmail API and call whatever endpoint a task needs, using your connected credentials. There is no fixed set of email operations to choose from.
- Draft, send, reply to, and forward email
- Read and search messages and threads
- Organize your inbox with labels
- Modify messages (mark read, archive, move between labels)
- Manage signatures, forwarding, filters, and other basic settings
## Authentication
| Method | Type | Description |
| ------------------------------- | --------- | ------------------------------------------------- |
| Helios Google app (recommended) | OAuth 2.0 | Per-user consent with pre-configured Gmail scopes |
| BYO Google app | OAuth 2.0 | Bring your own Google OAuth app and credentials |
### Helios Google app (recommended)
Connect in one click. Helios runs the Google OAuth redirect flow and asks each user for consent (`access_type=offline`, `prompt=consent`) so agents can act on your behalf, including when you're offline.
The Helios Google app requests scopes to:
- Compose, send, and insert email (`gmail.compose`, `gmail.send`, `gmail.insert`)
- Read and modify messages and threads (`gmail.readonly`, `gmail.modify`)
- Manage labels (`gmail.labels`)
- Read and update basic settings and sharing (`gmail.settings.basic`, `gmail.settings.sharing`)
### BYO Google app
Bring your own Google OAuth application when you need custom scopes or branding.
1. Go to [Google Cloud Console](https://console.cloud.google.com/)
2. Create a new project or select an existing one
3. Enable the Gmail API
4. Configure the OAuth consent screen
5. Create OAuth 2.0 credentials (client ID and client secret)
6. Add the Helios redirect URI to your OAuth client
7. In Helios, supply your client ID, client secret, an access token, a refresh token, and the Google account email
> Learn more in the [Gmail API documentation](https://developers.google.com/gmail/api).
## Triggers
Gmail does not currently emit event triggers into Helios. Use it from Chat, or from a Workflow driven by a [schedule, webhook, or manual run](/docs/workflows/triggers).
## Notes
Helios requests granular Gmail scopes for composing, reading, modifying, and labeling mail, but deliberately does not request the full-mailbox `mail.google.com` scope.
---
# Google Sheets
URL: https://www.heliosapp.com/docs/integrations/apps/google-sheets
Description: The Google Sheets integration lets Helios agents search the Google Sheets API and call any endpoint to create spreadsheets, read and write data, and manage formatting.
---
title: "Google Sheets"
excerpt: "Let Helios agents create, edit, and analyze spreadsheet data in Google Sheets."
description: "The Google Sheets integration lets Helios agents search the Google Sheets API and call any endpoint to create spreadsheets, read and write data, and manage formatting."
icon: /static/img/assets/google-sheets-light.svg
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
## What your agents can do
Agents don't pick from a preset list of actions. They semantically search the entire Google Sheets API and call whatever endpoint a task needs, using your connected credentials. Because the Sheets integration can also reach the Google Drive API, an agent can locate a spreadsheet in Drive and then open and edit it in Sheets.
- Create new spreadsheets from a prompt or template
- Read, write, append, and clear cell ranges
- Add, rename, and reorganize sheets and tabs
- Apply formatting, formulas, and data validation
- Find a spreadsheet in Drive and edit it in Sheets
## Authentication
| Method | Type | Description |
| ------------------------------- | --------- | ------------------------------------------------------ |
| Helios Google app (recommended) | OAuth 2.0 | Per-user consent with pre-configured spreadsheet scopes |
| BYO Google app | OAuth 2.0 | Bring your own Google OAuth app and credentials |
### Helios Google app (recommended)
Connect in one click. Helios runs the Google OAuth redirect flow and asks each user for consent (`access_type=offline`, `prompt=consent`) so agents can act on your behalf, including when you're offline.
The Helios Google app requests scopes to:
- Read and write spreadsheet data (`spreadsheets`, `spreadsheets.readonly`)
- Discover spreadsheets in Google Drive, read-only (`drive.readonly`)
- Access the specific Drive files you open with Helios (`drive.file`)
### BYO Google app
Bring your own Google OAuth application when you need custom scopes or branding.
1. Go to [Google Cloud Console](https://console.cloud.google.com/)
2. Create a new project or select an existing one
3. Enable the Google Sheets API (and the Google Drive API)
4. Configure the OAuth consent screen
5. Create OAuth 2.0 credentials (client ID and client secret)
6. Add the Helios redirect URI to your OAuth client
7. In Helios, supply your client ID, client secret, an access token, a refresh token, and the Google account email
> Learn more in the [Google Sheets API documentation](https://developers.google.com/sheets/api).
## Triggers
Google Sheets does not currently emit event triggers into Helios. Use it from Chat, or from a Workflow driven by a [schedule, webhook, or manual run](/docs/workflows/triggers).
---
# Notion
URL: https://www.heliosapp.com/docs/integrations/apps/notion
Description: The Notion integration lets Helios agents search the Notion API and call any endpoint to create pages, update database entries, query data, search content, and comment.
---
title: "Notion"
excerpt: "Let Helios agents create, update, and query pages and databases in Notion."
description: "The Notion integration lets Helios agents search the Notion API and call any endpoint to create pages, update database entries, query data, search content, and comment."
icon: Si-Notion
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
## What your agents can do
Agents don't pick from a preset list of actions. They semantically search the entire Notion API and call whatever endpoint a task needs, using your connected credentials. There is no fixed set of operations to choose from.
- Create pages and add rows to databases
- Update page properties and content
- Query databases with complex filters and sorts
- Read and append blocks (text, headings, to-dos, images, code, and more)
- Search the workspace to locate pages or databases
- Read and add comments on pages
## Authentication
| Method | Type | Description |
| ------------------------------ | ------------ | ---------------------------------------------- |
| Helios Notion app (recommended) | OAuth 2.0 | Full-featured integration for all workspaces |
| Internal integration | Secret Token | Workspace-specific integration with a token |
| BYO Notion app | OAuth 2.0 | Custom public integration for advanced control |
### Helios Notion app (recommended)
The Helios Notion app is a full-featured integration that can access any Notion workspace. Connecting runs the Notion OAuth redirect flow.
It requests permission to:
- Read, update, and insert content
- Read and insert comments
- Read user information, including email addresses
### Internal integration
An internal integration only has access to the workspace it is created in, and can be used with a token instead of the OAuth flow.
1. Go to [notion.so/my-integrations](https://www.notion.so/my-integrations) and create a new internal integration
2. Copy the integration's Internal Integration Token
3. Paste the token into the Notion credential in Helios
4. In Notion, share each page or database you want Helios to access with the integration
> Learn more about internal integrations in the [Notion documentation](https://developers.notion.com/docs/authorization#what-is-an-internal-integration).
### BYO Notion app
If you want more granular control, create your own public OAuth app in Notion and supply its client ID, client secret, access token, and refresh token to Helios. This requires additional setup and is not recommended for most users.
> Learn more about public integrations in the [Notion documentation](https://developers.notion.com/docs/authorization#what-is-a-public-integration).
## Triggers
Notion does not currently emit event triggers into Helios. Use it from Chat, or from a Workflow driven by a [schedule, webhook, or manual run](/docs/workflows/triggers).
## Notes
An agent can only reach pages and databases that have been explicitly shared with the integration. If
an agent reports that it cannot find a page, share that page with the integration in Notion and try
again.
See the full endpoint list in the [Notion API reference](https://developers.notion.com/reference/intro).
---
# Plain
URL: https://www.heliosapp.com/docs/integrations/apps/plain
Description: The Plain integration lets Helios agents query and mutate your Plain workspace through its GraphQL API, and run agents automatically when customer threads are created.
---
title: "Plain"
excerpt: "Give your agents access to Plain - read threads, reply to customers, and trigger agents on new conversations."
description: "The Plain integration lets Helios agents query and mutate your Plain workspace through its GraphQL API, and run agents automatically when customer threads are created."
icon: LifeBuoy
createdAt: "2026-07-09"
updatedAt: "2026-07-09"
---
## What your agents can do
Plain exposes a **GraphQL API**, not REST. Helios agents don't pick from a preset list of actions - they run GraphQL queries and mutations against Plain's full schema, with your API key injected server-side, so anything the Plain API can express, an agent can do in your workspace.
- Triage incoming support threads
- Draft or post replies to customers
- Label and assign threads
- Pull thread history for reporting
- Escalate a thread to another tool
## Authentication
| Method | Type | Description |
| ------- | ------- | ------------------------------------------------ |
| API key | API Key | Server-to-server authentication with a Plain key |
See [Integration authentication](/docs/integrations/auth) for how credentials are stored and injected.
### API key
1. In Plain, create a **machine user** for Helios.
2. Generate the machine user's **API key**.
3. Paste the key into Helios and save.
Plain's API is served from its UK region endpoint.
## Triggers
Plain is one of only three integrations that emit **event triggers** into Helios, so a [Workflow](/docs/workflows) can run an agent automatically when a customer conversation starts.
| Event | Description |
| ------------------------ | -------------------------------------------- |
| `thread.thread_created` | A customer starts a new thread |
| `thread.chat_received` | A new chat message arrives from a customer |
These events have no filter fields today.
Plain requires **manual webhook configuration**: after connecting, paste the webhook URL Helios shows you into Plain's settings so events reach Helios. Inbound webhooks are verified with HMAC-SHA256 signatures. See [Triggers](/docs/workflows/triggers) for how to attach these to a Workflow.
---
# Reddit
URL: https://www.heliosapp.com/docs/integrations/apps/reddit
Description: The Reddit integration lets Helios agents manage subreddits, post content, moderate communities, track submissions and comments, and work with Reddit's platform directly.
---
title: "Reddit"
excerpt: "Automate subreddit management, content posting, moderation, and community engagement with Reddit from your Helios agents."
description: "The Reddit integration lets Helios agents manage subreddits, post content, moderate communities, track submissions and comments, and work with Reddit's platform directly."
icon: Si-Reddit
createdAt: "2025-09-26"
updatedAt: "2026-07-09"
---
## What your agents can do
Helios agents don't work from a preset list of actions. They semantically search the entire Reddit API and call any endpoint directly, with authentication handled server-side. Anything your Reddit account and app scopes allow, an agent can do on your behalf.
- Search subreddits and posts and summarize what's trending
- Submit a post or comment to a subreddit
- Pull a user's or subreddit's recent activity
- Vote, save, and manage flair on content
- Run moderation actions (approve, remove, ban) in subreddits you moderate
- Read and send private messages
## Authentication
| Method | Type | Description |
| ------------------------------- | ---------- | ----------------------------------------------- |
| Helios Reddit App (Recommended) | OAuth 2.0 | Seamless integration with automatic permissions |
| BYO Reddit App | OAuth 2.0 | Custom Reddit App for enterprise requirements |
### Helios Reddit App (Recommended)
The Helios Reddit App connects through a standard OAuth redirect flow with automatic permission management. Choose it in Helios, authorize access to your Reddit account, and Helios handles token refresh for you.
### BYO Reddit App
Bring your own Reddit application for enterprise requirements or custom permission management.
#### Setup Steps
1. **Create the Reddit App**
- Go to [Reddit App Preferences](https://www.reddit.com/prefs/apps)
- Click **Create App** or **Create Another App**
- **Important**: Choose **web app** (this is required for OAuth flow)
- Fill in the app details:
- **Name**: Your app name (e.g., "MyHeliosApp")
- **Description**: Brief description of your app
- **About URL**: Optional URL with information about your app
- **Redirect URI**: Set to your OAuth callback URL (e.g., `https://your-app.com/auth/reddit/callback`)
- Click **Create app**
- Copy the **Client ID** (displayed under the app name) and **Client Secret**
2. **Generate Access and Refresh Tokens**
- Direct users to the authorization URL:
```
https://www.reddit.com/api/v1/authorize?client_id=YOUR_CLIENT_ID&response_type=code&state=RANDOM_STRING&redirect_uri=YOUR_REDIRECT_URI&duration=permanent&scope=REQUIRED_SCOPES
```
- After user authorization, Reddit will redirect to your callback URL with an authorization code
- Exchange the authorization code for access and refresh tokens:
```
POST https://www.reddit.com/api/v1/access_token
```
- Include the authorization code, client ID, client secret, and redirect URI in the request
- Save both the access token (short-lived) and refresh token (for token renewal)
3. **Configure in Helios**
- **Client ID**: The client ID from your Reddit app
- **Client Secret**: The client secret from your Reddit app
- **Access Token**: The access token obtained from the OAuth flow
- **Refresh Token**: The refresh token for automatic token renewal
- **App Name**: Your app identifier in format `MyHeliosApp:v1.0.0` (used for Reddit API requests)
- **Username**: Your Reddit username in format `/u/heliosuser` (the account associated with the app)
- Helios will automatically handle token refresh when needed
The **App Name** and **Username** fields are required by Reddit's API for the User-Agent header. Make sure the username matches the account that created the Reddit app.
#### Common OAuth Scopes
- `identity` - Access to account information
- `read` - Read posts and comments
- `submit` - Submit posts and comments
- `edit` - Edit and delete posts and comments
- `vote` - Submit and change votes on posts and comments
- `save` - Save and unsave posts and comments
- `history` - Access to post and comment history
- `flair` - Manage user and link flair
- `subscribe` - Subscribe/unsubscribe from subreddits
- `mysubreddits` - Access to subscribed and moderated subreddits
- `privatemessages` - Access to private messages
- `report` - Report posts and comments
- `account` - Access to account settings
- `modposts` - Approve/remove posts and comments
- `modflair` - Manage user and link flair in moderated subreddits
- `modmail` - Access moderator mail
- `modconfig` - Manage subreddit configuration and rules
Learn more about creating Reddit apps in the [Reddit API documentation](https://reddit.com/dev/api/).
## Triggers
Reddit does not currently emit event triggers into Helios. Use it from Chat, or from a Workflow driven by a [schedule, webhook, or manual run](/docs/workflows/triggers).
---
# Resend
URL: https://www.heliosapp.com/docs/integrations/apps/resend
Description: The Resend integration lets Helios agents search the Resend API and call any endpoint to send email, check delivery status, and manage domains and contacts.
---
title: "Resend"
excerpt: "Let Helios agents send transactional email and manage domains and contacts with Resend."
description: "The Resend integration lets Helios agents search the Resend API and call any endpoint to send email, check delivery status, and manage domains and contacts."
icon: /static/img/assets/resend-light.svg
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
## What your agents can do
Agents don't pick from a preset list of actions. They semantically search the entire Resend API and call whatever endpoint a task needs, using your connected API key. There is no fixed set of operations to choose from.
- Send single or batch transactional emails
- Retrieve the delivery status of a sent email
- Add and verify sending domains
- Manage audiences and contacts
- Send broadcasts to an audience
## Authentication
| Method | Type | Description |
| -------------- | ------- | ----------------------------------------------- |
| Resend API key | API Key | Server-to-server authentication with the Resend API |
### Resend API key
Generate an API key in your Resend dashboard (resend.com → **API Keys**) and paste it into the Resend credential in Helios. This key authenticates every request Helios sends to the Resend API. OAuth is not supported by this integration.
## Triggers
Resend does not currently emit event triggers into Helios. Use it from Chat, or from a Workflow driven by a [schedule, webhook, or manual run](/docs/workflows/triggers).
## Notes
An agent can only do what your API key allows. Create a Resend API key with the permissions you need (for example, full access or sending-only); any operation beyond those permissions is rejected by Resend.
See the full endpoint list in the [Resend API reference](https://resend.com/docs/api-reference).
---
# Slack
URL: https://www.heliosapp.com/docs/integrations/apps/slack
Description: The Slack integration lets Helios agents search and call the entire Slack API to post messages, manage channels, work with files and canvases, and run automatically on new messages.
---
title: "Slack"
excerpt: "Give your agents access to Slack - post messages, manage channels, and run automatically when messages arrive."
description: "The Slack integration lets Helios agents search and call the entire Slack API to post messages, manage channels, work with files and canvases, and run automatically on new messages."
icon: /static/img/assets/slack-light.svg
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
## What your agents can do
Helios agents don't pick from a preset list of Slack actions. They semantically search Slack's entire API and call any method directly, with authentication injected server-side - so anything the Slack API exposes, an agent can do in your workspace.
- Post, update, and thread messages in channels and DMs
- Read channel history and search across the workspace
- Create, join, and manage channels
- Upload, read, and share files
- Create and update canvases
- Add reactions and read who reacted
## Authentication
| Method | Type | Description |
| ----------------------------- | --------- | --------------------------------------------------- |
| Helios Slack app (Recommended)| OAuth 2.0 | Install with a single redirect; Helios manages tokens |
| BYO Slack app | OAuth 2.0 | You supply your app's client ID, secret, and bot token |
See [Integration authentication](/docs/integrations/auth) for how credentials are stored and injected.
### Helios Slack app (Recommended)
The default and recommended path. When you create the integration, Helios redirects you to Slack to approve the workspace install, then stores and refreshes the tokens for you.
On top of the workspace install, each user completes a one-time **per-user authorization** so their agents act with the right Slack identity.
### BYO Slack app
Bring your own Slack app when you need custom branding or your own scopes.
1. Go to [Slack App Management](https://api.slack.com/apps).
2. Click **Create New App → From scratch** and configure OAuth scopes and event subscriptions.
3. Install the app to your workspace.
4. In Helios, provide the **client ID**, **client secret**, and a **bot token** (`xoxb-…`).
Token rotation is **not** supported for BYO bot tokens - Helios uses the `xoxb-…` token you provide as-is.
### Scopes
The Helios Slack app requests the scopes agents commonly need.
- **Bot scopes:** `app_mentions:read`, `channels:history`, `channels:join`, `channels:manage`, `channels:read`, `chat:write`, `chat:write.public`, `commands`, `files:read`, `files:write`, `groups:history`, `canvases:*`, `emoji:read`
- **User scopes:** `channels:read`, `channels:history`, `channels:write`, `chat:write`, `files:read`, `groups:history`, `groups:read`, `im:write`, `search:read`
## Triggers
Slack is one of only three integrations that emit **event triggers** into Helios, so a [Workflow](/docs/workflows) can run an agent automatically when a message is posted.
| Event | Description | Filters |
| ----------------- | ------------------------------------------ | ---------------- |
| `message.channel` | A message posted in a public channel | channel (optional) |
| `message.group` | A message posted in a private channel | channel (optional) |
Omitting the channel filter matches all channels the bot can see. See [Triggers](/docs/workflows/triggers) for how to attach these to a Workflow.
---
# Stripe
URL: https://www.heliosapp.com/docs/integrations/apps/stripe
Description: The Stripe integration lets Helios agents search and call the entire Stripe API to manage payments, customers, subscriptions, and reporting with a server-side secret key.
---
title: "Stripe"
excerpt: "Give your agents access to Stripe - reconcile payments, manage customers and subscriptions, and report over the full Stripe API."
description: "The Stripe integration lets Helios agents search and call the entire Stripe API to manage payments, customers, subscriptions, and reporting with a server-side secret key."
icon: Si-Stripe
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
## What your agents can do
Helios agents don't work from a fixed list of Stripe actions. They semantically search Stripe's entire API and call any endpoint directly, with your secret key injected server-side - so a single Stripe key lets an agent reconcile and report across your whole account.
- Reconcile payments, charges, payouts, and balance transactions
- Look up and update customers, subscriptions, and invoices
- Create, confirm, or refund payments and payment intents
- Pull financial summaries and reports over any date range
- Investigate disputes, failed payments, and past-due invoices
## Authentication
| Method | Type | Description |
| ------- | ------- | ------------------------------------------------ |
| API key | API Key | Server-to-server authentication with a secret key |
See [Integration authentication](/docs/integrations/auth) for how credentials are stored and injected.
### API key
The Stripe integration authenticates with a secret key. Obtain it from **Stripe → Developers → API keys** and paste it into Helios. Both _test_ and _live_ keys are supported.
An agent can only perform the actions your key's permissions allow. Generate a key with the minimum scopes you need - any call outside those scopes is rejected by Stripe. Test and live data are fully isolated per environment.
## Triggers
Stripe does not currently emit event triggers into Helios. Use it from [Chat](/docs/basics/chat), or from a [Workflow](/docs/workflows) driven by a [schedule, webhook, or manual run](/docs/workflows/triggers).
---
# Typeform
URL: https://www.heliosapp.com/docs/integrations/apps/typeform
Description: The Typeform integration lets Helios agents create forms, manage surveys, collect responses, and work with Typeform's platform directly.
---
title: "Typeform"
excerpt: "Create and manage forms, surveys, and collect responses with Typeform from your Helios agents."
description: "The Typeform integration lets Helios agents create forms, manage surveys, collect responses, and work with Typeform's platform directly."
icon: /static/img/assets/typeform-light.svg
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
## What your agents can do
Helios agents don't work from a preset list of actions. They semantically search the entire Typeform API and call any endpoint directly, with authentication handled server-side. Anything you can do in Typeform, an agent can do on your behalf.
- Create and update forms and surveys
- Retrieve responses and summarize them into Slack or Notion
- Manage workspaces and themes
- Upload images for use in forms
- List and inspect forms across your account
- Configure form settings programmatically
## Authentication
| Method | Type | Description |
| ------------------------------ | ----------- | ---------------------------------------------- |
| Helios Typeform App (Recommended) | OAuth 2.0 | Seamless setup with automated token management |
| Personal Access Token | Token-based | Simple token-based authentication |
| BYO Typeform App | OAuth 2.0 | Custom OAuth app for advanced control |
### Helios Typeform App (Recommended)
The Helios Typeform App connects through a standard OAuth redirect flow and is the recommended way to connect. Choose it in Helios, authorize access to your Typeform account, and Helios handles token management for you.
The app requests these scopes: `accounts:read forms:write images:write themes:write responses:write webhooks:write workspaces:write offline`.
### Personal Access Token
Connect Typeform with a Personal Access Token if you already have one. Generate a token in your Typeform account under **Settings → Personal tokens**, then paste it into Helios and save your integration.
### BYO Typeform App
Bring your own Typeform OAuth application for advanced control over scopes and branding. You supply the client ID, client secret, access token, and refresh token.
## Triggers
Typeform does not currently emit event triggers into Helios. Use it from Chat, or from a Workflow driven by a [schedule, webhook, or manual run](/docs/workflows/triggers).
---
# WarpBuild
URL: https://www.heliosapp.com/docs/integrations/apps/warpbuild
Description: The WarpBuild integration lets Helios agents search and call the entire WarpBuild API to manage runners, builders, cloud connections, and monitor build infrastructure.
---
title: "WarpBuild"
excerpt: "Give your agents access to WarpBuild - manage runners, builders, and build infrastructure across the full WarpBuild API."
description: "The WarpBuild integration lets Helios agents search and call the entire WarpBuild API to manage runners, builders, cloud connections, and monitor build infrastructure."
icon: /static/img/assets/warpbuild-light.svg
createdAt: "2025-07-31"
updatedAt: "2026-07-09"
---
## What your agents can do
Helios agents don't work from a fixed list of WarpBuild actions. They semantically search WarpBuild's entire API and call any endpoint directly, with your access token injected server-side - so anything the WarpBuild API exposes, an agent can do for you.
- Manage runner images, instances, and pools
- Configure builders, builder profiles, and build sessions
- Connect and manage GCP, AWS, and Azure cloud providers
- Track jobs, usage, and daily cost snapshots
- Manage stacks, snapshots, and VCS integrations
## Authentication
| Method | Type | Description |
| --------------------- | ---- | ------------------------------------------------------ |
| Personal Access Token | PAT | Authenticate with a WarpBuild Personal Access Token |
See [Integration authentication](/docs/integrations/auth) for how credentials are stored and injected.
### Personal Access Token
Authenticate with a WarpBuild Personal Access Token (`wb_pat_…`), supplied as the `accessToken`.
1. Go to your [WarpBuild dashboard](https://app.warpbuild.com).
2. Open your account settings.
3. Generate a Personal Access Token (format: `wb_pat_xxxxxxxxxxxxxxxxx`).
4. Paste the token into Helios as the **access token** and save.
## Triggers
WarpBuild does not currently emit event triggers into Helios. Use it from [Chat](/docs/basics/chat), or from a [Workflow](/docs/workflows) driven by a [schedule, webhook, or manual run](/docs/workflows/triggers).
---