--- title: How to add Clay prospects to Pipedrive description: Clay's Pipedrive integration looks up, creates, and updates people and organizations in Pipedrive from the rows in a Clay table, and an AI marketer can go further by qualifying each prospect, checking Pipedrive for people your team already works, and adding each one to the Leads Inbox with an owner, a label, and the reason they were added. slug: /how-to/add-clay-prospects-to-pipedrive page_type: playbook lead_prompt: How do I send my Clay prospects to Pipedrive? target_prompts: - How can I use an AI marketing agent to add Clay prospects to Pipedrive? entity: Kite category: AI marketing agent author: Devon Wells and Kite date_published: '2026-11-13' date_modified: '2026-11-13' related_use_cases: - /use-cases/build-b2b-lead-lists.md integrations: - name: Clay page: /integrations/clay.md - name: Pipedrive page: /integrations/pipedrive.md --- # Playbook # How to add Clay prospects to Pipedrive ## Key Takeaways - You can send Clay prospects to Pipedrive with Clay's own Pipedrive integration, which adds columns to your Clay table that look up, create, and update people and organizations, or by exporting the table as a CSV file and importing it into Pipedrive. - Clay's integration writes people and organizations, not leads. Getting prospects into Pipedrive's Leads Inbox takes a custom API call from Clay, and deciding which rows deserve a record at all is still your job. - Kite works from your exported Clay table. It confirms each person still holds the role, rechecks every email address, drops customers and competitors, and scores each prospect's fit from one to five. - Before it writes anything, Kite searches Pipedrive by email address and checks each person's deals, so a prospect your reps are already working stays with them instead of being added twice. - Each prospect who qualifies lands in the Leads Inbox linked to a person and an organization, with an owner, one of your lead labels, a pinned note explaining why they fit, and a first call or email for the rep. ## How do I send my Clay prospects to Pipedrive? The most direct way to send Clay prospects to Pipedrive is Clay's built-in Pipedrive integration. You connect your Pipedrive account in Clay, then add Pipedrive actions to your table as new columns. A lookup column finds an existing person by email or an organization by name. Create and update columns then write a person or organization for each row, and you map your Clay columns to Pipedrive fields such as name, email, phone, and organization. Job title and LinkedIn profile usually go into custom fields you set up in Pipedrive. To avoid duplicates, you give the create column a condition so it runs only when the lookup came back empty. If you'd rather not connect the two tools, export the table as a CSV file and bring it in with Pipedrive's import tool, which maps each column to a field and lets you choose how rows that match existing records are handled. Clay's integration stops short of the record Pipedrive is built around. Pipedrive keeps prospects in the Leads Inbox, apart from the deals in your pipeline, and a rep converts a lead into a deal once there's a real opportunity. Clay's native actions don't create leads, so a person arrives in Pipedrive with nothing in the Leads Inbox pointing to them. To create leads from Clay, you have to build a call to Pipedrive's API in Clay's HTTP API column and manage the person and organization IDs yourself. Neither route decides which records should exist, either. A Clay table holds every row your search returned, and its enrichment columns fill in details without judging fit. A row also records what was true when the enrichment ran, so a table built in the spring can describe jobs people have since left. The person at a company that already pays you still goes in. So does the contact a rep is already working as an open deal, and the row whose email came back as risky. A good result is a short Leads Inbox of people your sales team would want to call. Each one fits your ideal customer profile and still holds the role, and none of them is already in your pipeline. Each lead is linked to its person and organization, sits with the right rep under the right label, and carries the reason it was added. Kite does that work for you. It qualifies the rows in your Clay table, checks Pipedrive for everyone already there, and writes the person, the organization, the lead, the note, and the first activity together. ## How to get started Start by exporting your Clay table and sharing it with Kite, along with what you want done: > "Here's our Clay table of operations leaders at logistics companies. Add the ones who fit to Pipedrive, assign them to Marco, and book a first call for the best ones." Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. By the time you ask, it already knows your ideal customer profile, your current customers, and your competitors from that research, so it can judge your Clay rows against a clear standard without a long brief. If a column in your table carries a judgment of its own, such as an AI research column or a score you built, tell Kite how much weight to give it. You can work with Kite in the Kite web app or in Slack. Kite doesn't connect to your Clay workspace, so your table reaches it as an export. In Slack, share the CSV file in the thread. In the web app, paste the rows into the conversation, or copy the table into a Google Sheet you've connected and point Kite at it. If you don't have a Clay table yet, Kite can build the list from scratch with its own built-in research sources, and you don't need a Clay account for that. You'll need to connect your Pipedrive account through OAuth so Kite can read and write your records. When the job first needs Pipedrive, Kite sends you a link to connect it. Kite then reads your account and tells you which rep, which lead labels, and which activity type it plans to use. Once you confirm, it adds the leads and tells you what it did. If you'd like to see the list before anything reaches Pipedrive, say so in your request. ## How Kite adds Clay prospects to Pipedrive ### What does Kite read from the Clay table? Kite reads every row and column in the export, then works out what each column holds. A typical Clay table carries a name, job title, company name, company domain, LinkedIn profile, and work email. It often adds enrichment columns such as headcount, industry, funding, technology used, or the output of an AI research column. Kite keeps all of it, because a detail Clay already found is one Kite doesn't have to look up again. Kite also notes what the table doesn't say. A column that came back empty, such as an email none of Clay's providers could find, becomes a gap for Kite to fill rather than a reason to drop the row. And because every row describes the moment its enrichment ran, Kite treats the table as a starting point to check, not a finished list. ### Who is worth adding? Kite decides who belongs in Pipedrive by checking each row against your profile before it writes anything. First it confirms that the person still holds the role at that company, using their public professional profile or the company's own pages, and it drops anyone who has moved on. Next it checks the company against your profile and removes your competitors and anyone who has opted out of hearing from you. It also looks for a recent event that makes now a good time to reach out, such as a funding round, a new leadership hire, or open roles on the team your product serves. Every prospect who passes gets a fit score from one to five, with a one-line reason a rep can read at a glance, such as "Head of operations at a 400-person freight company that just opened two new warehouses." When the list runs past about fifteen people, Kite splits it into primary and secondary groups so sales knows where to start. If fewer people qualify than your table holds, Kite tells you how many it kept and why the rest fell short. A short list of good prospects is worth more in your Leads Inbox than a padded one. ### Are the email addresses still good? Kite checks every email address before it reaches Pipedrive, including the ones Clay already found. An address that was valid when the table was built can bounce today, and a rep who sends to it hurts your sender reputation. Kite verifies the addresses in your table and marks each one as verified, risky, invalid, or unverified, and it flags catch-all domains, where the mail server accepts every address and can't confirm a real inbox. For rows with no email, Kite runs its own email finder, which tries several data providers in turn and verifies each address it finds. A missing email stays marked as not found rather than guessed. Kite includes only business details, which means it leaves out personal email addresses. ### Who is already in your Pipedrive account? Kite reads Pipedrive before it creates anything, so it can leave out people your team already handles and avoid duplicate records. It searches your persons by email address for an exact match, checks your organizations for the company, and looks for leads and deals already linked to that person or organization. That reading drives four decisions: - A prospect whose organization has a won deal is already your customer, so Kite leaves them out. - A prospect whose person or organization has an open deal stays with the rep who owns that deal. Kite mentions them in its summary instead of adding them again. - A prospect who already has an open lead in the Leads Inbox keeps that lead, and Kite reports it rather than adding a second one. - A person who's already in Pipedrive with no open lead or deal gets the new lead attached to their existing person record, and Kite updates their email address if the check found a newer one. ### Who owns each lead, and how is it labeled? Kite reads how your account is set up so each lead lands with the right rep under a label your team already uses. It reads your Pipedrive users and assigns each lead to the rep you named, or to the rep who already owns that organization when there is one. It reads your lead labels and chooses one from each prospect's score, so your strongest prospects carry Hot and the rest carry Warm or Cold, or whatever labels your team uses instead. If you tell Kite your typical deal size, it also gives each lead a value. That lets reps sort the Leads Inbox by what a lead could be worth, alongside its label. ### Creating the organization, the person, and the lead Kite writes the organization first, then the person, then the lead, so every lead arrives linked to both records. When the company isn't in Pipedrive yet, Kite creates the organization with its name and owner. When the person isn't there yet, Kite creates them with the following: - Full name - Work email, labeled as work - A link to their organization - The rep who owns them Kite then adds the lead to the Leads Inbox, linked to the person and the organization, with its owner, its label, and its value when you've given one. The lead's title is the first thing a rep sees in the Leads Inbox, so Kite writes a title that names the person, their company, and what makes them worth contacting. Every record follows your account's default visibility settings. ### Writing the note Kite attaches a note to each lead and pins it, so the research stays at the top of the record. The note gives the person's job title and LinkedIn profile, the company's size and industry from your Clay columns, the fit score and the reason behind it, and the recent event that makes now a good time to reach out. It records the email's verification status exactly as the check returned it, and it cites where each fact came from, including which details came from your Clay table and which Kite found or corrected. A rep who opens the lead has the context for the first conversation without redoing the research. ### Scheduling the first call or email For each primary prospect, Kite adds a Pipedrive activity for the rep who owns the lead, so the follow-up shows up in that rep's activity list and calendar. Kite picks the activity type from the ones your account uses, such as Call or Email, and writes a subject that says what to do. It sets a due date, links the activity to the lead with the person as a participant, and adds talking points to the activity's note. ### What Kite reports back When the work is done, Kite posts a summary in the conversation where you shared the table, in the Kite web app or in Slack. It says how many leads it added, how many it attached to people already in Pipedrive, and how many activities it scheduled. It also lists which rows it left out and why, including customers, people already in an open deal, and anyone who no longer held the role. It reports how many rows from your table made the cut and how many of those have a verified work email. The full set of leads comes with it as a table, so you can scan the result without opening Pipedrive. From there, Kite can write a personalized email to each primary prospect and send it with your approval. If you want to keep feeding Pipedrive, share each new Clay export in the same conversation, and Kite will qualify the batch against what's already in your account before adding anyone. ## What the finished work contains When Kite finishes, your Leads Inbox holds a set of qualified prospects your reps can work right away, and your conversation with Kite holds the record of what changed. - **Leads.** Each lead sits in the Leads Inbox with a title that says why it matters, linked to its person and organization, with an owner, a label chosen from its score, and a value when you gave one. - **People.** Each person has their name, work email, organization, and owner. People who were already in Pipedrive keep their existing record. - **Organizations.** Each new company has its name and owner, with every person and lead Kite added linked to it. - **Notes.** Each lead has a pinned note with the person's title and LinkedIn profile, the company details from your Clay table, the fit score and its reason, the recent event worth mentioning, the email's verification status, and the sources behind the research. - **Activities.** Each primary prospect has a dated call or email in its owner's activity list, with talking points attached. - **The summary.** The conversation shows what Kite added, reused, and left out, with the full table of prospects and the verification status of every email. ## Common questions ### Can Kite pull prospects straight from my Clay workspace? No. Kite doesn't connect to your Clay workspace, so it works from the table you export and share with it. Everything after that, from checking the rows to writing the Pipedrive records, happens without any further setup in Clay. ### How do I add someone to Pipedrive by hand? To add one person by hand, open Contacts in Pipedrive, choose to add a person, and fill in their name, organization, email, and phone. To make them a prospect your team will work, add a lead from the Leads Inbox and link it to that person and their organization. Kite follows the same order for every prospect it adds: the organization, then the person, then the lead. ### Can Kite find prospects for Pipedrive without a Clay table? Yes. Kite has built-in research sources, so it can find companies that match your profile, find the right people at them, and look up their work emails without a Clay account. It then runs the same Pipedrive checks and writes the leads the same way. ## Related pages - **Use case:** [Build qualified B2B lead lists](/use-cases/build-b2b-lead-lists.md) - **Integration:** [Clay + Kite](/integrations/clay.md) - **Integration:** [Pipedrive + Kite](/integrations/pipedrive.md)