Close CRM

​

Prerequisites

• A Close CRM account
• Permission to create an API key in Close CRM (Settings → Developer → API Keys)

​

What This Integration Does

Close CRM has two independent flows:

1. Send positive replies to Close CRM. Always on. RevyOps automatically creates and updates contacts, companies, and activities in Close CRM when qualified engagement is detected from your connected outbound systems.
2. Import CRM data into RevyOps. Optional. Brings your Close CRM contacts, companies, opportunities, and activity history into RevyOps, then keeps syncing hourly.

​

Setup

​

Contact Fields

The integration creates and fills two custom contact fields in Close CRM:

• Cold Email Accepted
• Cold Email Reply Type

RevyOps finds these fields in your Close CRM account if they already exist, or creates them automatically the first time it needs to write to them.

​

Custom Field Handling

• When importing, custom fields on your Close CRM contacts and companies are brought into RevyOps.
• When pushing Do Not Contact status (see below), RevyOps looks for a Close CRM custom field named Outbound Status (type: choices). If it doesn’t exist, RevyOps creates it.

​

Sync Behavior

• Sending replies to Close CRM happens automatically whenever a reply matches one of your chosen interested statuses. Sending itself can’t be turned off, only the statuses that trigger it can be changed from Edit statuses.
• Importing from Close CRM runs an initial full import, then keeps checking for changes every hour as long as import stays enabled. Turning import off stops the hourly updates but leaves Flow 1 (sending replies) running.
• If the import stops reporting progress, the panel shows it as stalled and lets you retry.
• Turning import off shows a warning that this removes reporting, unified records, attribution, full activity history, and AI context that depend on your Close CRM data.

​

How Close Leads Become Companies

Each imported Close lead becomes a company keyed on the domain in the lead’s URL field, so https://www.acme.com/about becomes acme.com. A lead stays without a company when its URL is empty or doesn’t name the business’s own website:

• a personal email provider or relay, such as gmail.com or privaterelay.appleid.com
• a social profile, such as a LinkedIn or Facebook page
• a registry lookup, such as an FMCSA SAFER page

When the URL gives no company, RevyOps looks at the work emails of the lead’s contacts. If they all share one domain, leaving out personal email providers and your own team’s domain, the lead becomes the company with that domain. A lead whose contacts use two or more work domains stays without a company. When the URL is a LinkedIn company page, the lead joins the company whose LinkedIn URL is that page, if exactly one company in your workspace has it. The page alone never creates a company. When the lead’s company is already known and has no LinkedIn URL yet, the page is saved on it. Several Close leads can become one company: every lead whose URL names the same website joins that company, and contacts, deals and activities that arrive later on any of those leads get it too. The company’s name and status come from the lead imported or updated last. Deleting a lead in Close CRM removes it from its company. When no other Close lead is on that company, RevyOps sets its CRM Deleted Date and leaves its Status as it was. When two leads are merged in Close CRM, the merged lead moves to the surviving lead’s company. The lead’s contacts are still imported. A contact whose email domain matches a company in your workspace is linked to it, as described in How contacts get a company.

​

How Close Contacts Become People

Close keeps a separate contact under every lead, so one human on two leads is two Close contacts. RevyOps makes them one person: a Close contact whose email or LinkedIn URL already belongs to another Close contact joins that person, and the person keeps both. Calls, emails, tasks and deals of either Close contact appear on the person. A person has one name, title, owner and set of fields: when its Close contacts differ, the one imported or changed last in Close sets them for all its contacts. A phone number never joins people, because everyone behind an office line shares it. When Ann Lee and Bob Ray are both listed in Close with the front desk number +1 281 871 2699, they stay two people, each with their own name, title and owner. The front desk number becomes a contact of its own, named after the name most of its Close contacts have, and calls to that number appear on it. Deleting a contact in Close CRM sets CRM Deleted Date on its RevyOps contact only when no other Close contact still has it. The contact’s Status stays as it was. Importing the lead from Close again clears the date. See Deleted in your CRM.

​

How Close Emails Find Their Person

An email from Close CRM joins the contact Close filed it under. When Close names no contact, or names one that RevyOps didn’t import, RevyOps looks at the other side of the email: the recipients of an email your team sent, or the sender of one you received. Your team’s own addresses and automated senders such as mailer-daemon or no-reply don’t count.

• If a contact in your workspace has one of those addresses, the email joins that contact.
• If none does and there is exactly one such address, RevyOps creates a contact for it, in the lead’s company when the lead has one.
• Otherwise the email isn’t imported.

Calls, texts and WhatsApp messages work the same way by phone number. When Close names no contact, or one RevyOps didn’t import, the record joins the contact whose phone is the other party’s number. Your team’s own Close lines never count. RevyOps doesn’t create contacts from a number alone, so a call from a number no contact has stays without a contact. Close keeps a separate copy of an email under every lead that has a contact with the address. RevyOps stores such a message once per person. Drafts, scheduled emails, emails waiting in the outbox and emails that failed to send aren’t imported. An email already in RevyOps is removed when Close reports it as one of them again. A note in Close belongs to the lead, not to a contact. On a lead with one contact, the note appears on that person’s timeline as well as on the company. On a lead with several contacts it stays on the company, because Close doesn’t say which of them it is about. A meeting appears on every attendee who is a contact in RevyOps. Lead status changes, deal status changes and the record of a lead’s creation stay on the company. Each call, email and deal keeps the Close user it belongs to as its owner. A user who has left your Close organization keeps the name shown on their activities. Every email, call, text and WhatsApp message imported from Close CRM keeps its Close activity id as Close ID, so you can filter by it to find the record that matches one in Close. Calls also bring in when they were answered, the call method, the Close sequence, whether there is a recording, the recording and voicemail transcripts, the voicemail link and length, and where the call was forwarded or transferred. Emails and texts keep the name of the Close sequence that sent them, and a lead’s description is saved on its company. A Close export lists only open tasks. Each task completed in Close is still recorded, so RevyOps creates it as a completed task from that record, with its text and assignee, or marks the task complete if it is already there. When an email, call, text, note, meeting or other activity is deleted in Close CRM, RevyOps deletes it too and rescores the people it belonged to.

​

Sending People From Workflows

The Send to step in a workflow sends each person who enters a saved view to Close CRM: it updates the matching Close contact, or creates the lead and contact, fills the Close fields you map, and can subscribe the person to a Close workflow. It uses the same Close CRM API key as the rest of this integration, and the workflow can’t be turned on for a workspace without one. It works on People and Contacts workflows, not company workflows, and a Close user field or choices field is filled from a dropdown of the workspace’s Close users or the field’s options. A person with Close contacts on several leads is sent to the one on their company’s lead, and a person new to Close is added to their company’s lead when the company has one.

​

Undoing an Import

The Imports tab in the Close CRM panel lists every import from Close CRM with how many records it created and updated. Import history in the import card opens the same tab. Choose Undo import from an import’s menu to delete the companies, people, and activities it created and put back the values it changed on records that already existed. Records edited in RevyOps after the import keep their current values, and a contact with other activity since then, such as an email from your sequencer, is kept too. The confirmation says how many records each case covers, and the Contacts page describes the rules in full. Undoing a Close CRM import turns Import CRM data into RevyOps off, so later changes in Close CRM don’t bring the deleted records back. Turning it back on starts a new import of your Close CRM data, which brings them back. Undo changes nothing in Close CRM.

​

Do Not Contact Sync

When enabled, contacts marked Do Not Contact anywhere in RevyOps get Close CRM’s Outbound Status custom field set, so nobody reaches out to them again from Close CRM. You can also trigger a one-time push of your current Do Not Contact list from the integration settings. The same field works in the other direction once a day. A Close CRM contact whose Outbound Status is Do Not Contact is marked Do Not Contact in RevyOps, and any other value is ignored. If Close CRM stops accepting your API key, this daily pull finds nothing and still shows as synced. See Do Not Contact Sync.

​

Settings

From Sync setup in the Close CRM panel you can:

• View and edit which statuses sync to Close CRM
• Turn CRM data import on or off, retry a failed or stalled import, or view its progress
• Turn Do Not Contact sync on or off and push the current Do Not Contact list
• View the Activity tab for push volume and the Sync log for individual sync events and errors