> ## 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. # Copper > Read Copper companies, people, opportunities and activities in Hebno, and add notes, tasks and opportunity stage changes after you confirm. The Copper integration shows your relationships and pipeline next to your client work. Ask what is open with a company, who the contacts are, or what was logged after the last meeting, and Hebno answers from Copper with each record cited. When a request implies a change, such as adding a note or moving an opportunity to a new stage, Hebno shows a confirmation card and writes to Copper only after you confirm. ## At a glance | | | | - | - | | **Connection** | Personal connection. Each member connects their own Copper user. | | **Default access** | Read and write | | **Attach** | Companies, people, opportunities | | **Search** | Hebno searches Copper when a request mentions a client, contact, opportunity, pipeline stage, close date or past activity | | **Link** | A project links to a Copper company and to one or more opportunities | | **Write** | Add a note, create a task, update an opportunity stage. Every write needs a person to confirm. | ## Before you start You need: * A Copper user in the account that contains your CRM data. Copper users sign in with their Google account. * Access in Copper to the records you want to use. Your Copper admin sets record visibility for teams and users. * An allowed integration. An owner or admin sets **Copper** to **Allow** under **Admin → Connectors → Catalogue**. Hebno requests this OAuth scope: | Scope | Why Hebno needs it | | - | - | | `developer/v1/all` | Read companies, people, opportunities, activities, tasks and pipelines through the Copper API as you, and write the confirmed changes on this page. Copper offers one scope for its API. | Your Copper visibility settings still apply. Hebno cannot read or change a record you cannot open in Copper. ## Connect Copper **1. Start the connection** Open **Settings → Connections**, find **Copper** and select **Connect**. You can also select **Connect** from the prompt in a chat. **2. Sign in to Copper** Sign in with the Google account you use for Copper and select **Authorize** to approve the access Hebno requests. **3. Return to Hebno** The card shows **Connected** with your Copper account name. Hebno reads and writes with your own permissions, so you see only the records Copper shows you. Tokens are encrypted at rest. Select **Disconnect** at any time, or ask an admin to revoke the connection under **Admin → Connectors → Connections**. ## What Hebno reads | Copper object | Fields Hebno uses | Typical questions | | - | - | - | | **Company** | Name, email domain, industry, address, owner, tags, custom fields | "What do we know about Contoso Retail?" | | **Person** | Name, title, emails, phone numbers, company, owner, tags | "Who are our contacts at Contoso?" | | **Opportunity** | Name, pipeline, stage, status, monetary value, win probability, close date, company, primary contact, owner | "Which Contoso opportunities are open and when do they close?" | | **Activity** | Type such as note, phone call or meeting, details, date, user, related record | "What did we log after the meeting with Priya Nair?" | | **Task** | Name, due date, status, priority, assignee, related record | "What follow-ups are open on Contoso?" | | **Pipeline and stages** | Pipeline name, stage names, order and win probability | "What is the stage after Proposal in the Advisory pipeline?" | Reads are live. Hebno queries Copper when a request needs it. Only what a reply used is stored with the conversation as its sources. Copper also records Gmail threads and Google Calendar events on a record. Hebno reads those from your own [Gmail](https://hebno.com/docs/integrations/gmail.md) and [Google Calendar](https://hebno.com/docs/integrations/google-calendar.md) connections, not from Copper. > [!WARNING] > > Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, including notes and contact details from Copper. ## What Hebno writes Every write appears first as a confirmation card. You can change any field before you select **Confirm**. | Action | Copper object | Fields on the card | | - | - | - | | **Add a note** | Activity of type note | Related company, person or opportunity, note details, date | | **Create a task** | Task | Name, related record, due date, priority, assignee | | **Update an opportunity stage** | Opportunity | Opportunity, pipeline stage, monetary value, close date | ![Confirmation card for Copper with editable fields](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-copper.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=16c75e8ae994228edf8e63ecaedbb91c) A Copper change pending confirmation. Nothing is written until you confirm. Hebno never deletes or merges records, marks opportunities won or lost without a stage change you confirm, changes pipelines or custom fields, or sends email from Copper. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant Copper You->>Hebno: Move the Contoso Phase 2 opportunity to Negotiation Hebno->>Copper: Find the Contoso Phase 2 opportunity Copper-->>Hebno: Opportunity Contoso Phase 2, stage Proposal Hebno-->>You: Confirmation card with stage, value, close date You->>Hebno: Confirm Hebno->>Copper: Update the opportunity as you Copper-->>Hebno: Opportunity updated Hebno-->>You: Done, with a link to the opportunity ``` Writes are made as your Copper user, so Copper shows you in the record's activity. ## Link a project to a company and an opportunity Linking marks which Copper records belong to a project, so you can ask "how is the opportunity progressing?" without naming it. 1. Open the project and select **Brain**. 2. Under **Linked records**, select **Link record**, then **Copper**. 3. Search for the company and select it. Repeat to add the opportunities that belong to the engagement. In chats tagged to the project, Hebno starts with the linked company and opportunities for any client or pipeline question, and cards for notes and tasks default to them. See [Linked records](https://hebno.com/docs/projects/linked-records.md). ## Use Copper in chat * **Attach**: open the **+** menu, choose **Sources → Copper**, and pick a company, person or opportunity. Or type `/` and choose **Copper**. * **Ask**: name the client, contact or opportunity in your request. For example: > Prep me for Thursday's meeting with Contoso Retail: open opportunities, the people we have met and the last three activities. > Which opportunities in the Advisory pipeline have a close date in November 2026 and no activity in 21 days? > Move Contoso Phase 2 to Negotiation and create a task for Sarah Chen to send the revised fee proposal by 10 November. * **Research runs** show a **Reviewing Copper** step, with a chip for each company, opportunity and activity it read. * **Agents** can read Copper on a schedule, for example a Monday brief on opportunities closing this month. Writes an agent proposes appear in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md) for review. ## Troubleshooting | Symptom | Fix | | - | - | | Sign-in fails with a Google account error | Sign in with the Google account your Copper user belongs to, not a personal Gmail account. | | Hebno cannot find a record you can open in Copper | Check that you connected the right Copper account. Disconnect and reconnect, choosing the correct one. | | A record is missing from answers | Copper visibility settings hide it from your user. Hebno reads only what you can read. | | A stage update fails with **422 Unprocessable Entity** | The stage belongs to a different pipeline from the opportunity. Pick a stage from the opportunity's pipeline on the card and select **Confirm** again. | | **Reconnect Copper** appears | The authorisation was revoked or your Copper user was deactivated. Select **Connect** to authorise again. | | Requests fail with **429 Too Many Requests** | Copper limits API requests per minute for each user. Wait a minute and retry. | ## 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) * [HubSpot](https://hebno.com/docs/integrations/hubspot.md) * [Gmail](https://hebno.com/docs/integrations/gmail.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.