Zendesk Sell

Connect AI agents to Zendesk Sell, the sales CRM formerly known as Base. Agents run full CRUD across leads, contacts, deals, tasks, and notes, advance deals through pipeline stages, attach catalog products as line items, and read pipelines, sources, tags, and users to route work correctly.

38 actions API key available

Zendesk Sell website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

Stripe confirms payment against an open quote

Agent reads the purchased products and quantities from the order

Get Product confirms the catalog price for each SKU

Add Deal Line Item attaches each product to the deal

Update Deal moves the deal to the won stage

Create Note logs the payment details and the team channel gets a summary

A rep signs off when the paid amount disagrees with the line-item total

What This Integration Enables

Zendesk Sell has a product catalog and deal line items for a reason: so the pipeline number is built, not guessed. Most CRM automation stops at creating a deal with a value someone typed. This connector goes further, attaching real catalog products to deals as line items so the value on the board reconciles with what the customer actually bought. When the pipeline rolls up, it rolls up from SKUs and quantities, not optimism. FlowRunner agents run full create, read, update, and delete across leads, contacts, deals, tasks, and notes. They advance deals through real pipeline stages and read pipelines, stages, sources, tags, and users so every write routes correctly on the first try. The decisions that cannot be walked back, deleting records that carry history, stay with a person through FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop/) steps.

Without FlowRunner

Deal values are guesses Reps type a round number instead of building it from the catalog

Won deals updated late Payment clears but the pipeline still shows the deal open

Follow-ups tracked in heads Next steps live in memory, not on the record

With FlowRunner

Line-item accuracy Deal values assemble from catalog products, quantities, and prices

Stage moves follow the money Payment confirmation advances the deal the same hour

Every step on the record Tasks and notes attach to the lead, contact, or deal they belong to

Use Case Scenarios

Payment closes the deal, line items make it honest

A payment settles in [Stripe](/integrations/stripe). The agent finds the matching deal, reads the purchased products, and verifies each price against the catalog with Get Product. It attaches the products with Add Deal Line Item, moves the deal to the won stage with Update Deal, and logs the payment details on the record with Create Note. If the paid amount and the line-item total disagree, the agent does not force the close. It posts the discrepancy to the sales channel in [Slack](/integrations/slack) and waits for a rep to resolve it. The won column stays a number finance can trust.

Booked meetings become owned leads

A prospect books through [Calendly](/integrations/calendly). The agent creates the lead with Create Lead, sets the source so attribution survives, resolves the right owner from List Users, and opens a preparation task with Create Task, due before the meeting starts. When a new customer appears in [Shopify](/integrations/shopify), the same pattern runs with Create Contact and Create Deal, opening a follow-up opportunity tied to the buyer. Inbound interest stops depending on who happened to see the notification.

The daily pipeline digest

On a schedule, the agent pulls the pipeline with List Deals, resolves stage names from List Stages, and writes the export to [Google Sheets](/integrations/google-sheets). A short digest posts to the sales channel: new deals, stage moves, deals gone quiet. The sales lead reads thirty seconds of exceptions instead of paging through the board, and the spreadsheet the leadership meeting runs on is never a week old.

Human-in-Loop Highlight

Zendesk Sell's Delete Deal cannot be undone, and a deleted deal takes its attached context with it: the notes reps wrote, the tasks that tracked the close, the line items that record what was actually sold. So when a cleanup agent finds two deals for the same purchase, the artifact of a double-fired webhook, it does not guess which one is real. It retrieves both with Get Deal, compares their line items with List Deal Line Items, and puts the pair in front of the deal owner in Slack: "Two deals exist for the Meridian order. Deal 8102 has three line items and the pricing note. Deal 8117 is empty. Delete 8117?" Only after the rep confirms does Delete Deal run. An agent can spot a duplicate; deciding which version of the truth survives is a person's call.

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

38 actions

Contacts

List Contacts Lists people and organizations with pagination, sorting, and filters by name, email, or organization. Used as the match check before creating anyone.
Get Contact Retrieves a contact with address, tags, and custom fields. Used to load context before updates.
Create Contact Creates a person or an organization record. Used when orders and signups introduce new customers.
Update Contact Changes only the supplied fields. Used for enrichment without clobbering existing data.
Delete Contact Permanently deletes a contact and its associations. Cannot be undone; gated behind approval.

Leads

List Leads Lists leads with filters by name, organization, or status. Used for routing sweeps.
Get Lead Retrieves a lead with status, source, and custom fields. Used before qualification moves.
Create Lead Creates a company or person lead with ownership and source. Used to capture inbound interest with attribution intact.
Update Lead Advances status or reassigns the owner. Used as qualification progresses.
Delete Lead Permanently deletes a lead. Cannot be undone; kept behind sign-off.

Deals

List Deals Lists deals with filters by name, stage, or hot flag. The backbone of pipeline reporting.
Get Deal Retrieves a deal with value, stage, and associations. Used to confirm state before moves.
Create Deal Opens a deal with a name and primary contact, plus value, stage, and source. Used when interest becomes real business.
Update Deal Moves a deal between stages, updates value, or flags it hot. The workhorse for keeping the board true.
Delete Deal Permanently deletes a deal. Cannot be undone; reserved for human-approved cleanup.

Tasks and Notes

List Tasks Lists tasks with filters by completion or linked resource. Used to audit open follow-ups.
Get Task Retrieves a task with content, due date, and its resource. Used before completion or reassignment.
Create Task Creates a task attached to a lead, contact, or deal, with a due date and reminder. Used to turn events into follow-ups on the record.
Update Task Marks tasks complete or shifts dates and owners. Used as work gets done.
Delete Task Permanently deletes a task. Cannot be undone.
List Notes Lists notes by attached resource. Used to gather history before decisions.
Get Note Retrieves a note with its content. Used to load specific context.
Create Note Attaches commentary to a lead, contact, or deal. Used to log payments, decisions, and agent actions where reps read.
Update Note Updates a note's content. Used for corrections.
Delete Note Permanently deletes a note. Cannot be undone.

Products and Line Items

List Products Lists the catalog with pagination. Used to resolve what can be sold.
Get Product Retrieves a product with SKU, cost, and prices. Used to verify pricing before attaching line items.
List Deal Line Items Lists the products attached to a deal with quantity and value. Used to reconcile deal value against reality.
Add Deal Line Item Attaches a catalog product to a deal with quantity and optional price override. Used to build deal values from real SKUs.
Delete Deal Line Item Removes a line item from a deal without touching the catalog. Used to correct order changes.

Pipeline Reference

List Pipelines Lists the configured pipelines. Used to target the right stage sequence.
List Stages Lists deal stages, optionally per pipeline. Used so every stage move is valid before it runs.
List Sources Lists deal and lead sources. Used to keep attribution consistent.
List Lead Sources Lists lead-specific sources. Used when lead attribution differs from deal attribution.
List Tags Lists tags by resource type. Used for segmentation checks before writes.

Users

List Users Lists account users with pagination. Used to resolve owners for routing.
Get User Retrieves a user with role and status. Used before assignment decisions.
Get Current User Retrieves the authenticated user. Used as a connection check.

Frequently Asked Questions

What can FlowRunner do with Zendesk Sell?

FlowRunner agents can run List Contacts, Get Contact, and Create Contact in Zendesk Sell, plus 35 more actions.

Does connecting Zendesk Sell to FlowRunner require OAuth?

No. Zendesk Sell connects to FlowRunner with an API key, no OAuth flow required.

Can Zendesk Sell trigger a FlowRunner workflow automatically?

Zendesk Sell doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Zendesk Sell

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us