Bring people and companies in from Clay, Apollo or any tool with an API key. Plum matches each one to who is already there, fills in only the fields you allow, and never changes what someone typed.
Owners, admins and revops. Sending rows in needs an API key with read and write access, which owners and admins create.
Go to Integrations and open Lead generation. The page has four parts: what each tool may change, Clay, Apollo, and segments.
What tools may change
For each tool, and for each field on contacts and accounts, choose one of three settings. Clay and Apollo have their own column. Every other tool that sends rows with an API key uses the column for other tools.
- Leave alone
- The tool can't set this field. What it sends is ignored.
- Fill in blanks
- The tool sets the field only when it is empty.
- Fill in and update
- The tool sets the field when it is empty, and replaces a value a tool set before.
Out of the box, every tool may fill in a contact's first and last name, job title and phone, and an account's domain, when they are blank. Your workspace's own fields are left alone until you choose otherwise for each one.
A value someone typed in Plum is never changed by a tool, whatever is set here. Plum records where each value came from: a person, an import, Clay, Apollo or another tool.
How Plum finds who a row is about
- A contact: by the tool's own id for the person if Plum has seen it before, then by email address, in any capitalization.
- An account: by the tool's own id, then by domain, then by the domain of the contact's email address, then by the company name with punctuation and endings like Inc or LLC set aside.
- A public mailbox domain, such as gmail.com, never matches an account. Two accounts with the same name don't match by name.
- When nothing matches, Plum creates the record, and links a new contact to its company. A new record gets the lead source named for the tool, if your Lead sources list has one with that name.
Sending the same rows again changes nothing. Each row comes back as created, updated, unchanged or skipped, with the fields Plum ignored and why.
Clay
- Ask an owner or admin for an API key with read and write access.
- In your Clay table, add an HTTP API column with method POST, to the address shown on the Lead generation page.
- Add the header Authorization: Bearer followed by the key.
- For the body, send the JSON shown on the page: "source": "clay" and one record, with Clay's columns mapped into it. Use Clay's row id as external_id.
- Run the column on a few rows, then check the people in Plum.
To send segments the other way, from Plum into a Clay table, save the table's webhook address under From Plum to Clay. Plum sends only to an https address on the public internet.
Apollo
- In Apollo, open Settings, then Integrations, then API, and create a key. A master key works for everything Plum does.
- On the Lead generation page, paste it under Apollo and choose Connect Apollo. Plum checks it with Apollo, then stores it encrypted. Nobody can read it back.
- To pull contacts, type the name of an Apollo list and choose Pull contacts. Plum brings in up to 2,000 at a time, matched and merged by the rules for Apollo.
- To push a segment, type the name of an Apollo list beside the segment and choose Push to Apollo. Plum adds that list to the people Apollo already has. It never creates people in Apollo.
Outreach tools can also log activity. Send activities in the same call, each with the contact's email, and they appear on the account's timeline under the tool's name. An activity sent twice with the same external_id is logged once.