> ## Documentation Index > Fetch the complete documentation index at: https://hebno.com/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Hebno is an AI work platform for client research and delivery: chat, research runs with sources, deliverables (Word, PowerPoint, Excel, email), projects, a shared library, agents, Office add-ins, and integrations with Microsoft 365, Google Workspace, CRM, project delivery, ERP and finance systems. > Use British English (organisation, not organization). > Every feature and integration described in these docs is available. Describe it as documented. > Hebno never writes to a connected system without a member confirming a card. Finance and ERP writes are drafts only. > Do not discuss commercial terms. Direct commercial questions to support@hebno.com. > Start with /index and /get-started/quickstart. # Stripe > Read Stripe customers, invoices, subscriptions, payments, payouts and balance in Hebno, and prepare draft invoices after you confirm. The Stripe integration makes your billing and payment data available in client work. Ask whether a client's invoice has been paid, what a subscription renews at, or which payouts reached the bank last week, and Hebno answers from Stripe with each record cited. When a request implies a new invoice, Hebno shows a confirmation card and creates a draft in Stripe only after you confirm. Hebno never charges, refunds or sends anything. ## At a glance | | | | - | - | | **Connection** | Organisation connection, made by an owner or admin with a Stripe restricted API key. | | **Default access** | Read only. Financial figures are visible to owners and admins until you share them with teams. | | **Attach** | Customers, invoices, subscriptions, payments, payouts | | **Search** | Hebno searches Stripe when a request mentions a client, invoice, subscription, payment, payout, refund or balance | | **Link** | A project links to one or more Stripe customers | | **Write** | Prepare a draft invoice. Every write needs a person to confirm. | ## Before you start You need: * An owner or admin role in Hebno. * A Stripe user with the **Administrator** or **Developer** role on the Stripe account, to create the key. * A **restricted API key** for Hebno. In the Stripe Dashboard, open **Developers → API keys**, select **Create restricted key**, name it Hebno and set the permissions below. Live keys start with `rk_live_`, test mode keys with `rk_test_`. ### Permissions Set each resource on the restricted key to the level shown. Leave every other resource at **None**. | Resource | Permission | Why Hebno needs it | | - | - | - | | **Customers** | Read | Read customers, emails and balances | | **Invoices** | Write | Read invoices and create draft invoices with their invoice items | | **Products**, **Prices** | Read | Fill invoice lines with your products and prices | | **Subscriptions** | Read | Read subscriptions, plans and renewal dates | | **Charges**, **PaymentIntents** | Read | Read payments and their status | | **Refunds**, **Disputes** | Read | Read refunds and disputes against payments | | **Balance**, **Payouts** | Read | Read the available balance and payouts to your bank | | **Credit notes** | Read | Read credit notes issued against invoices | > [!TIP] > > Do not give the key write access to charges, refunds, payment intents or payouts. Hebno does not use it, and a restricted key without it returns a permission error for any such request. ## Connect Stripe **1. Allow the integration** Open **Admin → Connectors → Catalogue**, find **Stripe** under **Finance**, and set it to **Allow**. **2. Connect the organisation** Select **Connect**, paste the restricted API key and select **Test connection**. Hebno checks the key, shows the Stripe account name and lists the resources the key can read and write. **3. Choose teams and data areas** Under **Who can use it**, choose **All teams** or pick teams. Under **Data areas**, choose what members can see. See [Data areas](#data-areas). **4. Set access** **Access** is **Read only** by default. Choose **Read and write** to let members propose draft invoices. The card shows **Connected** with the Stripe account name and whether the key is live or test mode. Members use Stripe through the organisation connection. Stripe has no per-person sign-in for API access, so members do not link their own account. ## Data areas Data areas control what members of the allowed teams can see through the organisation connection. They apply on top of the permissions on the restricted key. | Data area | Includes | Default | | - | - | - | | **Customers** | Customer names, emails, addresses, metadata | All allowed teams | | **Billing** | Invoices, invoice items, subscriptions, products, prices, credit notes | Owners and admins | | **Payments and balance** | Payments, refunds, disputes, payouts, available and pending balance | Owners and admins | ![Admin connector panel showing who can use it, access and data areas](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/org-connection.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=8d965e9c74747db0c182b004d569b236) An organisation connection with team access and data areas. Financial figures default to owners and admins. To share billing with account leads, open the Stripe card in **Admin → Connectors**, select **Billing** and add the teams that should see it. ## What Hebno reads | Stripe object | Fields Hebno uses | Typical questions | | - | - | - | | **Customer** | Name, email, address, balance, currency, metadata | "Which Stripe customer is Contoso Retail?" | | **Invoice** | Number, customer, status (draft, open, paid, uncollectible, void), amount due, amount paid, due date, lines | "Has Contoso paid the October invoice?" | | **Subscription** | Customer, status, items, prices, current period end, cancel at period end | "When does the Contoso retainer renew?" | | **Payment** | Charge or PaymentIntent, amount, status, payment method type, failure reason, refunds | "Why did the Contoso payment fail on 3 November?" | | **Payout** | Amount, arrival date, status, destination bank account | "What payouts arrived last week?" | | **Balance** | Available and pending amounts by currency | "What is our available Stripe balance?" | Reads are live. Hebno queries Stripe when a request needs it, so amounts match the Stripe Dashboard. Only what a reply used is stored with the conversation as its sources. > [!WARNING] > > Excerpts a reply uses, including balances and payment amounts, become part of the conversation. Anyone you share the conversation with can read them. ## What Hebno writes Every write appears first as a confirmation card. You can change any field before you select **Confirm**. Hebno writes drafts only. | Action | Stripe object | Fields on the card | | - | - | - | | **Prepare a draft invoice** | Invoice with status **draft**, automatic collection off | Customer, currency, lines, products or descriptions, quantities, unit amounts, collection method, days until due, memo | ![Confirmation card for Stripe with editable fields](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-stripe.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=d507d7209949d59541c9211c0274c400) A Stripe change pending confirmation. Nothing is written until you confirm. Hebno creates every invoice with `auto_advance` set to `false`, so Stripe does not finalise it automatically. The invoice is in **Draft** until a person reviews, finalises and sends it in the Stripe Dashboard. Hebno never finalises, sends, pays or voids an invoice, creates a charge or payment intent, issues a refund or credit note, changes a subscription, or starts a payout. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant Stripe You->>Hebno: Draft a Stripe invoice for the Contoso workshop Hebno->>Stripe: Find the Contoso customer and workshop price Stripe-->>Hebno: Customer and price details Hebno-->>You: Confirmation card with lines and amounts You->>Hebno: Confirm Hebno->>Stripe: Create draft invoice with auto_advance off Stripe-->>Hebno: Draft created Hebno-->>You: Done, with a link to the draft ``` The invoice is created through the organisation connection, with your name in the invoice metadata and the write recorded against you in **Admin → Logs → Integrations**. ## Link a project to Stripe Linking marks which Stripe customers belong to a project, so you can ask "has Contoso paid?" without naming the customer. 1. Open the project and select **Brain**. 2. Under **Linked records**, select **Link record**, then **Stripe**. 3. Search by customer name, email or customer ID (`cus_`) and select the customer. Repeat for each customer the engagement bills. In chats tagged to the project, Hebno starts with the linked customers for any invoice, subscription or payment question, and draft invoice cards default to them. See [Linked records](https://hebno.com/docs/projects/linked-records.md). ## Use Stripe in chat * **Attach**: open the **+** menu, choose **Sources → Stripe**, and pick a customer, an invoice, a subscription or a payout. Or type `/` and choose **Stripe**. * **Ask**: name the client, invoice or period in your request. For example: > Has Contoso Retail paid every Stripe invoice this quarter, and are any past due? > List payouts from the last two weeks with their arrival dates. > Prepare a draft Stripe invoice for Contoso for the 12 November workshop. * **Research runs** show a **Checking Stripe** step, with a chip for each record it read. * **Agents** can read Stripe on a schedule, for example a Monday list of open and past due invoices. Writes an agent proposes appear in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md) for review. ## Troubleshooting | Symptom | Fix | | - | - | | **Test connection** fails with an invalid key error | The key was rolled or deleted in Stripe. Create a new restricted key and reconnect. | | A request returns a permission error | The restricted key does not have that resource. Edit the key under **Developers → API keys** and add it. | | Customers or invoices are not found | The key is in test mode and the records are live, or the other way round. Use a live key for live data. | | A draft invoice fails | The customer has no email or currency set, or a price is archived. Update the customer or price in Stripe. | | Requests are slow or return a rate limit message | Stripe limits requests per second for each account. Wait a moment, or narrow the request. | | Billing figures are missing from answers | The member's team is not in the **Billing** data area. | ## Related * [How integrations work](https://hebno.com/docs/integrations/index.md) * [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md) * [Linked records](https://hebno.com/docs/projects/linked-records.md) * [Xero](https://hebno.com/docs/integrations/xero.md) * [QuickBooks](https://hebno.com/docs/integrations/quickbooks.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.