Works with the tools your team already runs on
Import knowledge from where it lives, route conversation events to where your team works, and extend helpo with a typed API. Every entry below says plainly whether it exists yet.
The whole list, honestly labelled
Open a row to see how it connects, what it can reach, and what it can't. Nothing here is marked live unless it ships today.
The file goes to storage, is split into overlapping chunks, embedded, and written into the vector store against your project. Ingestion runs as a background job, so a long PDF does not hold up the upload — the source appears immediately with a pending status and flips to ready when its chunks land.
- Formats
- .pdf, .txt, .md
- Connects by
- Direct upload
- Ingestion
- Background job, status per source
helpo reads sitemap_index.xml, sitemap.xml or robots.txt to discover what a site actually publishes, then shows you the list so you choose what gets indexed rather than hoovering up the whole domain. Sites without a sitemap fall back to entering URLs directly. Selected pages can re-crawl on a schedule so the answers move when your docs do.
- Discovery
- sitemap, then robots.txt
- Re-crawl
- manual, daily or weekly
- Connects by
- Public read
An article written in helpo is both the page your customers read and a source the AI answers from. There is no export step and no drift between the published version and the indexed one, because they are the same record — editing the article re-indexes it.
- Source type
- article, linked to the page
- Sync
- None needed — same record
- Connects by
- Internal
Some things your team knows are not in any document — the real refund window, which plan actually includes the thing, what to say when someone asks about the outage. A Q&A pair is a first-class source, so those answers get retrieved and cited exactly like a page of docs.
- Shape
- One question, one answer
- Retrieval
- Same ranking as any source
- Connects by
- Internal
The connector is not finished. The source type is already reserved in the schema, so the pages will land through the same ingestion path a crawl uses and nothing has to migrate when it ships. Until then, exporting a Notion page as Markdown and uploading it works today.
- Status
- Connector in progress
- Planned scope
- Pages and databases
- Today
- Export to .md and upload
Two halves that work independently. The import reads your storefront's public products.json — no install, no token, nothing helpo can write — and indexes titles, descriptions, prices and stock beside your docs. The app is a separate, approved install: once it is connected the store pushes order updates to helpo, so helpo never holds credentials that could read your shop.
- Catalog
- Public /products.json
- Orders
- Pushed by the app, not pulled
- Connects by
- Public read + approved install
helpo probes the site, detects WooCommerce, reports roughly how many products it found, and shows you a preview before anything is written. The read is against the public Store API that your storefront already serves to browsers, so there are no API keys to generate and nothing to install.
- Catalog
- Public Store API
- Detection
- Automatic, with a preview first
- Connects by
- Public read
Install the plugin, click connect, approve the request from your helpo dashboard, and the widget is live on the site. The plugin holds a scoped bearer token of its own rather than your login, and revoking it from helpo takes the site offline immediately without touching WordPress.
- Setup
- Install, connect, approve
- Token
- Scoped to the site, revocable
- Connects by
- Approved install
What you paste is a loader, not the chat app — it waits on the page costing almost nothing and only pulls the conversation UI when somebody opens it. It runs on static sites, Next.js, Rails, Webflow, anything that can serve a script tag, and needs no build step.
- Setup
- One tag before </body>
- Cost on the page
- A loader until it is opened
- Connects by
- Public script
Create an incoming webhook in Slack, paste the URL into helpo, and pick which of the seven events should reach it. Messages arrive as coloured attachments with the visitor, the text that triggered them and a deep link back into the thread, so an alert is something you can act on rather than something you have to go look up.
- Setup
- Paste an incoming webhook URL
- Events
- All seven triggers
- Connects by
- Outgoing webhook
A Discord channel webhook works exactly like the Slack one — same rules, same filters, same seven triggers. Events arrive as embeds coloured by what happened, so takeovers and new tickets are distinguishable at a glance in a busy channel.
- Setup
- Paste a channel webhook URL
- Format
- Embeds, coloured per trigger
- Connects by
- Outgoing webhook
Lark custom-bot webhooks take the same treatment, rendered as interactive cards with a coloured header per trigger. Worth knowing: Lark answers with HTTP 200 even when it rejects a message, so helpo reads the response body rather than the status code and records a real failure in the delivery log instead of a silent success.
- Setup
- Paste a custom-bot webhook URL
- Format
- Interactive cards
- Connects by
- Outgoing webhook
Point a rule at any URL you control and helpo POSTs a JSON body describing what happened — the trigger, the person, the text, and a link back. Every attempt is recorded with its response status, the number of tries and how long it took, so a broken endpoint is visible in helpo rather than discovered a week later.
- Payload
- JSON, one POST per event
- Delivery log
- Status, attempts, duration
- Connects by
- Outgoing webhook
The API is not a bolted-on subset — the dashboard is built on it, so anything you can do in the UI has an endpoint behind it. Every route declares its request and response schema, which means the OpenAPI document is generated from the code that actually runs rather than maintained beside it, and the browsable reference cannot drift from the implementation.
- Spec
- OpenAPI, generated from the routes
- Reference
- Browsable, always current
- Connects by
- Authenticated request
Not built. Exporting a help center and uploading the articles works today and gets you the same retrieval — the value a connector would add is keeping it in step afterwards. Tell us you need it and it moves up.
- Status
- Not started
- Today
- Export articles, upload as files
- Connects by
- Would be an approved install
Not built. Email as a channel is a bigger piece than an alert destination — it needs addresses, threading and identity matching against existing visitors — so it is scoped as its own thing rather than a connector.
- Status
- Not started
- Scope
- A channel, not a notification
- Today
- Alerts out, not mail in
Not built as a first-party connector. A webhook rule on ticket.created can already POST to a function that opens the issue for you — which is most of the value — and a native version would mainly save you writing that function.
- Status
- Not started
- Today
- Webhook on ticket.created
- Connects by
- Would be an approved install
Not built. Public docs hosted from a repository are usually reachable by crawling the site they are published to, which works today; the gap is private repositories and raw Markdown that never becomes a page.
- Status
- Not started
- Today
- Crawl the published docs site
- Gap
- Private repos and raw Markdown
Three ways in, and that's the list
Which shape an integration uses tells you what it can reach and what happens when you switch it off.
helpo fetches what your site already serves.
Crawling a docs site and importing a store catalog both read endpoints your visitors' browsers can already hit. There is nothing to install, no key to generate, and no credential for helpo to lose — and because the access is read-only by construction, there is no version of this that writes to your site.
Website crawl · Shopify catalog · WooCommerce catalog
You approve the connection from inside helpo.
The app asks for a short code, you approve it while signed in to the workspace it should land in, and the app trades the code for a bearer token scoped to that one install. helpo never holds your store or site login — the token belongs to the app, and revoking it from helpo cuts the connection without touching the other system.
Shopify app · WordPress plugin
helpo POSTs JSON. What happens next is yours.
Slack, Discord, Lark and your own endpoint are the same mechanism with four body shapes: one unauthenticated POST to a URL, where the URL is the secret. Nothing is installed on either side, every attempt is logged with its response, and deleting the connection stops it instantly.
Slack · Discord · Lark · Your endpoint
Seven events, four destinations
Every trigger reaches every destination — a rule is one event, one place to send it, and the filters that decide whether it's worth sending.
conversation.createdSomebody opens the widget and sends a first message.message.receivedAny message arrives on a thread. The noisiest one — filter it.conversation.takeoverAn agent claims a live thread from the AI.conversation.closedA conversation ends, with its CSAT score if one was given.lead.capturedThe agent gets a name and an email out of a conversation.ticket.createdSomething outlives the chat and gets filed.form.submittedA visitor completes a form inside the chat.A rule can require a keyword — case-insensitive, matched against the message or the ticket body — or a triage priority. Both are lists, and any hit passes, so one rule covers “refund, chargeback, dispute” without three copies of itself.
Every real attempt is recorded with its response status, how many tries it took and how long it ran. A rule whose filters simply didn't match is not logged, so a busy project's log stays a list of things that actually went wrong.
Turn support chats into checkouts
Connect Shopify or WooCommerce in one click. helpo indexes your catalog right alongside your docs, then the AI suggests the right products mid-conversation — with live price and stock awareness.
- One-click catalog sync
- Product cards in chat
- Intent-aware suggestions
- Price & stock aware answers
Catalog re-syncs automatically
Missing something?
Tell us which tool you need and what you'd do with it. The ones people actually ask for are the ones that get built.
Put your support on autopilot
Train helpo on your product today. Your customers get answers in seconds — your team gets their time back.