> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Pipedrive on Vortex IQ > Monitor Pipedrive pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn. Monitor Pipedrive pipeline, responsiveness and customer-satisfaction signals, and catch stalls before they become churn. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=pipedrive) performance signals automated checks automated fixes workflows API operations ### What you can achieve Capabilities are grouped around merchant outcomes, not API terminology. Monitor orders, fulfilment, delivery and settlement. Improve discovery, conversion, campaigns and repeat purchase. Find failures, leaks and risks before they cost sales. Find storefront, speed, accessibility and journey problems. Identify missing, inconsistent or outdated product data. ### From connection to verified outcome The controlled sequence every capability follows. Nothing changes a connected system without the approval step. Authorise the source. Scopes are shown before access is granted. Watch the signals against your own baselines, not universal defaults. Run checks and gather evidence specific to your store. Explain what happened, why it matters and the proposed action. You review scope, risk and reversibility before anything changes. Apply through governed connector operations. Confirm the intended result and keep the receipt. No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls. ### Monitor performance 32 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system. | Signal | Alert behaviour | What it tracks | | ----------------------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Active Subscribers (Est.)** | Merchant rule | Estimated count of active persons/contacts in the CRM over the trailing window. | | **CRM Data Hygiene Score** | Alert band 95 / 80 | Composite of confirmed-real Pipedrive fields: share of persons with an email on file (GET /persons email\[]) and share of persons assigned an owner\_id. | | **Click-to-Open Rate** | Alert band 10 / 3 | Clicks divided by opens on outbound email to persons. Higher is better. | | **Email Click Rate** | Alert band 2 / 0.5 | Unique clicks divided by delivered emails to persons. Higher is better. | | **Email Open Rate** | Alert band 20 / 10 | Opens divided by delivered emails to persons. Higher is better. | | **Flow Count Summary** | Merchant rule | Count of active automation flows / scheduled activity sequences. | | **Flow Status Breakdown** | Merchant rule | Automation flows grouped by status (done vs pending activities). | | **Flow Trigger Types** | Merchant rule | Distribution of activity/flow trigger types (call, email, task, meeting). | | **Flows List** | Merchant rule | Tabular list of automation flows / activity sequences with status and counts. | | **Lead Response Time** | Alert band 60 / 480 | Median minutes from a person's add\_time to their first logged Activity (GET /activities carries person\_id + add\_time for every call/email/meeting/task | | **List Count** | Merchant rule | Number of CRM lists / saved filters (organizations grouping). | | **Lists Overview** | Merchant rule | Tabular overview of CRM lists with member counts and last-update times. | | **Placed Orders Total** | Merchant rule | Total orders placed by CRM-tracked persons. Needs an ecommerce sibling. | | **Segments Overview** | Merchant rule | Tabular overview of CRM segments / person filters with member counts. | | **Stalled Deal %** | Alert band 10 / 30 | Open deals with no logged activity in 14 days, as a share of all open deals. GET /deals returns last\_activity\_date per deal (confirmed real Pipedrive | | **Top Lists by Name** | Merchant rule | Largest CRM lists ranked by member count, labelled by name. | | **Total Sends** | Merchant rule | Total outbound emails sent to persons over the window. | | Signal | Alert behaviour | What it tracks | | ----------------------------- | --------------- | ----------------------------------------------------------------------------------------------------- | | **Campaign Status Breakdown** | Merchant rule | Distribution of campaign/deal records by status (open/won/lost). | | **Checkout-to-Order Rate** | Merchant rule | Of attributed checkouts, the share that converted to a placed ecom order. Needs an ecommerce sibling. | | **Conversion Rate** | Merchant rule | Won deals divided by total deals over the window. Higher is better. | | **Email Health KPIs** | Merchant rule | Rolled-up email engagement health summary across persons (sends/opens/clicks). | | **Engagement Funnel** | Merchant rule | Sent → delivered → opened → clicked funnel for outbound email to persons. | | **List Health Summary** | Merchant rule | Aggregate list-health summary across CRM lists (size, freshness, engagement). | | **Revenue per Recipient** | Merchant rule | Attributed revenue divided by recipients reached. Needs an ecommerce sibling. | | **Revenue per Send** | Merchant rule | Attributed revenue divided by emails sent. Needs an ecommerce sibling. | | **Total Revenue** | Merchant rule | Total won-deal value over the window - top-level CRM revenue pulse. | | Signal | Alert behaviour | What it tracks | | ----------------------- | -------------------- | ----------------------------------------------------------------------------- | | **Bounce Rate** | Alert band 2 / 5 | Share of outbound emails to persons that hard/soft bounced. Higher is worse. | | **Delivery Rate** | Alert band 98 / 95 | Share of outbound emails to persons successfully delivered. Higher is better. | | **Refund Rate** | Merchant rule | Refund rate on orders attributed to CRM persons. Needs an ecommerce sibling. | | **Spam Complaint Rate** | Alert band 0.1 / 0.3 | Share of delivered emails marked as spam by recipients. Lower is better. | | **Unsubscribe Rate** | Alert band 0.5 / 2 | Share of delivered emails that resulted in an unsubscribe. Lower is better. | | Signal | Alert behaviour | What it tracks | | --------------------- | --------------- | ------------------------------------------------------------------------------ | | **Checkouts Started** | Merchant rule | Checkouts initiated by persons tracked in the CRM. Needs an ecommerce sibling. | ### Audit risks and opportunities A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail. **Severity** critical · **Outcome** Catalogue quality · **Fix status** Report only Once this credential fails, VortexIQ stops seeing deals, contacts and pipeline activity from this CRM entirely, and every pipeline and data-quality finding here goes stale from that moment, silently, until someone notices the numbers stopped updating. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `CRM-AUTH-001` **Severity** high · **Outcome** Grow revenue · **Fix status** Report only Leads answered after 8 hours convert at a fraction of the rate of leads answered in minutes; speed-to-lead is the cheapest conversion lever in the pipeline. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `CRM-LEAD-001` **Severity** high · **Outcome** Run operations · **Fix status** Report only Deals with no activity for two weeks are quietly dying; a nudge list ordered by value recovers some before they close-lose themselves. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `CRM-PIPE-001` **Severity** medium · **Outcome** Run operations · **Fix status** Report only More than 1 in 5 records is missing a required field. Incomplete records make segmentation, reporting and any automation keyed off those fields (routing, scoring, follow-up sequences) unreliable, so the gap compounds into every process built on top of this data, not just the records themselves. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `CRM-DATA-001` #### Build your own automated fixes Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change. ### Automate approved work Vortex IQ is integrated with **6 read** and **2 write** operations across activitys, deals, organizations, persons, stages, usermes on Pipedrive. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words. Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=pipedrive) #### Ready to build your first Pipedrive workflow Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build. | Resource | Read operations | Write operations | | ------------- | --------------- | ---------------- | | activitys | 1 | 1 | | deals | 1 | 1 | | organizations | 1 | 0 | | persons | 1 | 0 | | stages | 1 | 0 | | usermes | 1 | 0 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.