> ## 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. # Pipedrive > Read Pipedrive organisations, people, deals and activities in Hebno, and add notes, activities and deal updates after you confirm. The Pipedrive integration shows your pipeline next to your client work. Ask what is open with an organisation, who the contacts are, or what was agreed on the last call, and Hebno answers from Pipedrive with each record cited. When a request implies a change, such as adding a note or moving a deal to a new stage, Hebno shows a confirmation card and writes to Pipedrive only after you confirm. ## At a glance | | | | - | - | | **Connection** | Personal connection. Each member connects their own Pipedrive user. | | **Default access** | Read and write | | **Attach** | Organisations, people, deals | | **Search** | Hebno searches Pipedrive when a request mentions a client, contact, deal, stage, close date or past activity | | **Link** | A project links to a Pipedrive organisation and to one or more deals | | **Write** | Add a note, create a task, log a call or meeting, update a deal, create a person. Every write needs a person to confirm. | ## Before you start You need: * A Pipedrive user in your company account. * Permission in Pipedrive to install apps. If your administrator restricts app installs, ask them to approve Hebno first. * An allowed integration. An owner or admin sets **Pipedrive** to **Allow** under **Admin → Connectors → Catalogue**. Hebno requests these OAuth scopes: | Scope | Why Hebno needs it | | - | - | | `base` | Identify the connected user and company account | | `deals:full` | Read deals, stages and deal notes, and update deals after you confirm | | `contacts:full` | Read organisations, people and their notes, and create or update them after you confirm | | `activities:full` | Read activities such as calls, meetings and tasks, and create them after you confirm | | `users:read` | Show who owns a deal, person or organisation | ## Connect Pipedrive **1. Start the connection** Open **Settings → Connections**, find **Pipedrive** and select **Connect**. You can also select **Connect** from the prompt in a chat. **2. Sign in to Pipedrive** Sign in, choose your company account if you belong to more than one, and approve the access Hebno requests. **3. Return to Hebno** The card shows **Connected** with your Pipedrive company name. Hebno reads and writes with your own permissions, so you see only the deals, people and organisations that your Pipedrive visibility settings allow. 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 | Pipedrive object | Fields Hebno uses | Typical questions | | - | - | - | | **Organisation** | Name, address, owner | "What do we know about Contoso Retail?" | | **Person** | Name, email, phone, job title, organisation | "Who are our contacts at Contoso?" | | **Deal** | Title, value, currency, pipeline, stage, status, expected close date, owner, organisation, person | "Which Contoso deals are open and when do they close?" | | **Activity** | Subject, type, due date, done status, related deal, person or organisation | "What was the last call we logged with Priya?" | | **Note** | Content, related deal, person or organisation | "What did we note after the discovery meeting?" | | **Pipeline and stages** | Pipeline name, stage names and order | "Where does the Contoso deal sit in the pipeline?" | Reads are live. Hebno queries Pipedrive when a request needs it. Only what a reply used is stored with the conversation as its sources. > [!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 Pipedrive. ## What Hebno writes Every write appears first as a confirmation card. You can change any field before you select **Confirm**. | Action | Pipedrive object | Fields on the card | | - | - | - | | **Add a note** | Note | Related deal, person or organisation, note text | | **Create a task** | Activity of type task | Subject, related record, due date, assigned user | | **Log a call or meeting** | Activity | Subject, type, date and time, related records, notes, done | | **Update a deal** | Deal | Stage, value, expected close date | | **Create a person** | Person | Name, email, phone, organisation | ![Confirmation card for Pipedrive with editable fields](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/card-pipedrive.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=8f9200f291c0e4250f6df2356d1136e4) A Pipedrive change pending confirmation. Nothing is written until you confirm. Hebno never deletes records, changes pipelines or stages, or sends email from Pipedrive. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant Pipedrive You->>Hebno: Log today's call with Priya on the Contoso deal Hebno->>Pipedrive: Find the Contoso deal and Priya Pipedrive-->>Hebno: Deal Contoso Phase 2, person Priya Hebno-->>You: Confirmation card with subject, time, related records You->>Hebno: Confirm Hebno->>Pipedrive: Create the activity as you Pipedrive-->>Hebno: Activity created Hebno-->>You: Done, with a link to the activity ``` ## Link a project to an organisation and a deal Linking marks which Pipedrive records belong to a project, so you can ask "where does the deal stand?" without naming it. 1. Open the project and select **Brain**. 2. Under **Linked records**, select **Link record**, then **Pipedrive**. 3. Search for the organisation and select it. Repeat to add the deals that belong to the engagement. In chats tagged to the project, Hebno starts with the linked organisation and deals for any client or pipeline question, and cards for notes and activities default to them. See [Linked records](https://hebno.com/docs/projects/linked-records.md). ## Use Pipedrive in chat * **Attach**: open the **+** menu, choose **Sources → Pipedrive**, and pick an organisation, person or deal. Or type `/` and choose **Pipedrive**. * **Ask**: name the client, contact or deal in your request. For example: > Prep me for the pitch meeting with Contoso Retail on Thursday: open deals, who we have met, and what we proposed last time. > Summarise the history with Contoso and flag any deal with no activity in the last month. > Move the Contoso Phase 2 deal to Negotiation, set the expected close date to 30 November and add a note that Priya wants fixed-fee pricing. * **Research runs** show a **Reviewing Pipedrive** step, with a chip for each organisation, deal and activity it read. * **Agents** can read Pipedrive on a schedule, for example a Monday brief on deals due to close this month. Writes an agent proposes appear in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md) for review. ## Troubleshooting | Symptom | Fix | | - | - | | Pipedrive blocks the install | Ask your Pipedrive administrator to allow app installs for your user, then select **Connect** again. | | Hebno cannot find a deal you can open in Pipedrive | Check that you connected the right company account. Disconnect and reconnect, choosing the correct one. | | A deal or person is missing from answers | Pipedrive visibility settings hide it from your user. Hebno reads only what you can read. | | A write fails with a Pipedrive message | Fix the field the message names on the card and select **Confirm** again. | | **Reconnect Pipedrive** appears | The authorisation was revoked in Pipedrive. Select **Connect** to authorise again. | | Requests fail with a rate limit message | Pipedrive limits requests per company account. Wait 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) * [Salesforce](https://hebno.com/docs/integrations/salesforce.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.