--- title: "Pipeliner CRM Integration" description: "Connect AI agents to Pipeliner CRM. Agents get full create, read, update, and delete access to accounts, contacts, leads, opportunities, and tasks, plus a generic entity request that reaches appointments, notes, and custom records." url: https://flowrunner.ai/integrations/pipelinercrm date_modified: 2026-08-07T17:20:23-07:00 --- # Pipeliner CRM [CRM](https://flowrunner.ai/integrations/category/crm-sales) Connect AI agents to Pipeliner CRM. Agents get full create, read, update, and delete access to accounts, contacts, leads, opportunities, and tasks, plus a generic entity request that reaches appointments, notes, and custom records. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 26 actions · Basic auth · available [Pipeliner CRM website](https://pipelinersales.com/) · [Platform Documentation](https://developers.pipelinersales.com/) · Capability data verified 2026-07-27 1. A new order fires from the storefront 2. Company, order value, and expected close pulled from the order 3. List Accounts looks for the company before creating anything 4. Create Account and Create Opportunity open the deal in the pipeline 5. Create Task schedules the welcome call for the assigned rep 6. The team channel gets the new deal with its pipeline step 7. A rep confirms step and value before the deal enters the forecast ## What This Integration Enables Pipeliner CRM sells sales managers one thing above all: a visual pipeline they can read at a glance. But the glance is only worth something if the data underneath moves when the deal does. A board full of deals in stale steps is not a pipeline, it is a mural. FlowRunner agents keep the picture honest by writing the events into the CRM as they happen: orders open opportunities, payments advance steps and record values, and follow-up tasks land on the records they belong to. The connector gives agents full create, read, update, and delete access to accounts, contacts, leads, opportunities, and tasks, with cursor pagination and related-entity expansion for reads. Beyond the typed operations, Entity Request is the escape hatch: raw access to any Pipeliner entity, including Appointments, Activities, Notes, and the custom records your admin built. Two design facts matter for governance. Pipeliner's typed deletes are soft, moving records to the recycle bin where they can be restored. And the raw escape hatch carries no typed guardrails, which is exactly why FlowRunner wraps it in [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) checkpoints. ### Without FlowRunner **The board lies**: The visual pipeline shows deals in steps they left weeks ago **Manual order entry**: New business gets retyped from the store into the CRM **Side entities untouched**: Appointments, notes, and custom records sit outside every automation ### With FlowRunner **The board matches reality**: Steps, values, and close dates update as the events happen **Deals open themselves**: Orders become accounts and opportunities on arrival **Everything reachable**: Entity Request reaches appointments, notes, and custom records too ## Use Case Scenarios ### Orders walk onto the board by themselves A new order fires from [Shopify](https://flowrunner.ai/integrations/shopify). The agent checks List Accounts for the company, creates it with Create Account only if it is genuinely new, and opens the deal with Create Opportunity carrying the order value and expected close date. Create Task puts the welcome call on the rep's list, and the team channel in [Slack](https://flowrunner.ai/integrations/slack) gets the new deal with its pipeline step. The rep confirms step and value in the thread before the deal rolls into the forecast, so the board gains a deal and stays trustworthy at the same time. ### Payments move deals, and the forecast follows A payment confirms in [Stripe](https://flowrunner.ai/integrations/stripe). The agent finds the opportunity, and Update Opportunity advances the pipeline step and records the closed value. On a weekly schedule, a reporting agent pulls active deals with List Opportunities, expands owners and accounts, writes the pipeline to [Google Sheets](https://flowrunner.ai/integrations/google-sheets), and posts the summary to the sales channel. The manager's glance at the board and the finance team's spreadsheet finally describe the same pipeline. ### The records the typed actions do not cover A field sales team logs appointments and custom visit-report records in Pipeliner. The agent uses Entity Request to read the week's appointments, cross-references them against open opportunities, and creates note records against accounts that had visits but no logged outcome. Reads and single-record writes run automatically. When the flow calls for a bulk write through the raw interface, the agent stages it and waits for approval, because an escape hatch with no guardrails should not fire unattended. ## Human-in-Loop Highlight The risk profile of this connector is unusual, and the gate sits where the risk actually is. Pipeliner's typed deletes are soft: Delete Opportunity and its siblings move records to the recycle bin, where an admin can restore them. The operation that deserves a pause is Entity Request, the raw CRUD interface that reaches any entity with whatever payload the agent assembled and no typed field validation to catch a mistake. A malformed bulk update through it can overwrite live field values across hundreds of records in one call, and there is no recycle bin for an overwrite. So before an agent executes a bulk Entity Request write, it stops and posts the plan to the CRM admin in Slack: "Ready to update 340 custom visit-report records via Entity Request. Target entity, field list, and the exact payload are attached. Approve or hold?" The agent runs it only on approval. Raw power stays available, and it stays supervised. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 26 actions ### Contacts 5 - **List Contacts** Lists people with cursor pagination, filters, ordering, and related-entity expansion. Used for match checks and sweeps. - **Get Contact** Retrieves a contact with optional expansion of owner and linked accounts. Used to load context before updates. - **Create Contact** Creates a person with contact and ownership fields, plus custom fields via additional fields. Used when new people arrive from any channel. - **Update Contact** Partially updates a contact; only supplied fields change. Used for enrichment and corrections. - **Delete Contact** Soft-deletes a contact to the recycle bin, where it can be restored. Used in cleanup flows with recovery available. ### Accounts 5 - **List Accounts** Lists companies with pagination, filters, and expansion. Used as the match check before creating accounts. - **Get Account** Retrieves a company with optional related-entity expansion. Used before updates and merges. - **Create Account** Creates a company with contact and ownership details. Used when orders introduce new companies. - **Update Account** Partially updates a company, including custom fields. Used for enrichment. - **Delete Account** Soft-deletes a company to the recycle bin. Restorable by an admin. ### Leads 5 - **List Leads** Lists early-stage prospects with pagination and filters. Used for routing and follow-up sweeps. - **Get Lead** Retrieves a lead with optional expansion. Used before qualification moves. - **Create Lead** Creates a lead with name, company, and contact details. Used to capture inbound interest. - **Update Lead** Partially updates a lead. Used as qualification progresses. - **Delete Lead** Soft-deletes a lead to the recycle bin. Restorable. ### Opportunities 5 - **List Opportunities** Lists deals with pagination, filters, and expansion of owner, account, and contacts. The backbone of pipeline reporting. - **Get Opportunity** Retrieves a deal with its step, value, and relations. Used to confirm state before a move. - **Create Opportunity** Opens a deal with pipeline step, value, close date, and ownership. Used when orders or qualified leads become business. - **Update Opportunity** Advances the step, adjusts value, or moves the close date. The action that keeps the visual board honest. - **Delete Opportunity** Soft-deletes a deal to the recycle bin. Restorable. ### Tasks 5 - **List Tasks** Lists to-dos linked to accounts, contacts, leads, and opportunities. Used to audit follow-ups. - **Get Task** Retrieves a task with optional expansion. Used before completion or reassignment. - **Create Task** Creates a task with subject, description, and due date, linkable to any core record. Used to put follow-ups on the record. - **Update Task** Partially updates a task's subject, dates, or details. Used as work completes. - **Delete Task** Soft-deletes a task to the recycle bin. Restorable. ### Everything Else 1 - **Entity Request** Performs raw CRUD against any Pipeliner entity, reaching Appointments, Activities, Notes, and custom records that have no dedicated actions. The most powerful operation in the connector and the one FlowRunner gates: bulk writes through it wait for human approval. ## Frequently Asked Questions ### What can FlowRunner do with Pipeliner CRM? FlowRunner agents can run List Contacts, Get Contact, and Create Contact in Pipeliner CRM, plus 23 more actions. ### Does connecting Pipeliner CRM to FlowRunner require OAuth? No. Pipeliner CRM connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can Pipeliner CRM trigger a FlowRunner workflow automatically? Pipeliner CRM doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Pipeliner CRM?** This integration exposes Pipeliner CRM to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/pipelinercrm. Site index: https://flowrunner.ai/llms.txt