Close
Two-way sync Close leads, contacts, opportunities, tasks, and notes with Airtable, Notion, Google Sheets, and more.
Close Connector Guide
Section titled “Close Connector Guide”This guide covers how to connect Whalesync to Close, which tables and fields sync, and a few things to know before you start.
In Whalesync terms, a Close organization is the base you pick. Each Close object Whalesync supports is a table, and each lead, contact, opportunity, task, or note is a row. Leads, Contacts, Opportunities, Tasks, and Notes sync in both directions. Pipelines sync both ways too, but only the pipeline name is writable. Users, Lead Statuses, and Opportunity Statuses are your organization's configuration and are read only.
Connecting to Close
Section titled “Connecting to Close”Whalesync connects with a Close API key you paste in. An API key reaches one Close organization, and that organization is the base. See Authorize Close.
- In Whalesync, choose Close and paste a Close API key.
- Pick the organization to sync.
- Pick the tables to sync.
Supported Tables
Section titled “Supported Tables”| Table | Status | Notes |
|---|---|---|
| 👥 Leads | ✅ Supported | The companies and accounts in Close. Contacts, opportunities, tasks, and notes all hang off a lead. |
| 👤 Contacts | ✅ Supported | Each contact belongs to one lead. |
| 🤝 Opportunities | ✅ Supported | |
| ☑️ Tasks | ✅ Supported | Whalesync creates lead tasks, and Close's own task types can appear in the table. See Things to Keep in Mind. |
| 🗒️ Notes | ✅ Supported | |
| 🎛️ Pipelines | ✅ Supported | Name is the only field that writes back to Close; the rest, including the list of statuses, are read only. Creating a row creates a pipeline in Close, and deleting one deletes the pipeline along with its statuses. |
| 📊 Lead Statuses | ➡️ Supported (1-Way) | Read only. Organization configuration. |
| 🎲 Opportunity Statuses | ➡️ Supported (1-Way) | Read only. Organization configuration. |
| 🧑💻 Users | ➡️ Supported (1-Way) | Read only. Your Close teammates. |
| ✉️ Emails, 📞 Calls, 📅 Meetings, 🏃 other activities | ✖️ Not supported | Notes are the only Close activity type that syncs. Tasks have their own table above. |
Supported Fields
Section titled “Supported Fields”| Close field | Status | Notes |
|---|---|---|
| Name | ✅ Supported | Required to create a lead. |
| Description | ✅ Supported | |
| Url | ✅ Supported | The lead's website. |
| Status id | ✅ Supported | Links to the Lead Statuses table. |
| Addresses | ✅ Supported | Multi-value. Each entry is a JSON object with label, address_1, address_2, city, state, zipcode, and country. |
| Html url | ➡️ Supported (1-Way) | Read only. The lead's page in Close. |
| Created by, Updated by | ➡️ Supported (1-Way) | Read only. Links to the Users table. |
| Date created, Date updated | ➡️ Supported (1-Way) | Read only. |
Contacts
Section titled “Contacts”| Close field | Status | Notes |
|---|---|---|
| Name, Title | ✅ Supported | |
| Emails | ✅ Supported | Multi-value. The addresses sync; their office or home labels do not. |
| Phones | ✅ Supported | Multi-value. The numbers sync; their labels do not. |
| Urls | ✅ Supported | Multi-value. Each entry is a JSON object with url and type, unlike Emails and Phones, which sync the bare value. |
| Lead | ✅ Supported | Required. Set when the contact is created. Close does not allow moving a contact to another lead afterwards. |
| ➡️ Supported (1-Way) | Read only. The contact's first email address. Write through Emails. | |
| Organization id | ➡️ Supported (1-Way) | Read only. |
| Created by, Updated by, Date created, Date updated | ➡️ Supported (1-Way) | Read only. |
Opportunities
Section titled “Opportunities”| Close field | Status | Notes |
|---|---|---|
| Lead | ✅ Supported | Required. Set when the opportunity is created, and fixed after that. |
| Contact | ✅ Supported | The contact has to belong to the same lead. |
| Status id | ✅ Supported | Links to the Opportunity Statuses table. |
| Value | ✅ Supported | In cents. $1,500 is 150000. |
| Value period | ✅ Supported | How often the value recurs, for example one_time or monthly. |
| Confidence | ✅ Supported | Close's percentage, 0 to 100. |
| Note | ✅ Supported | |
| Lead name, Status label, Status type, Value formatted, Value currency | ➡️ Supported (1-Way) | Read only. Close works these out from the fields above. |
| Expected value, Annualized value, Annualized expected value, Date won | ➡️ Supported (1-Way) | Read only. Calculated by Close. |
| User, User name | ➡️ Supported (1-Way) | Read only. The opportunity's owner in Close. |
| Organization id, Created by, Updated by, Date created, Date updated | ➡️ Supported (1-Way) | Read only. |
| Close field | Status | Notes |
|---|---|---|
| Text | ✅ Supported | The task itself. |
| Date | ✅ Supported | The date the task is due. |
| Is complete | ✅ Supported | |
| Assigned to | ✅ Supported | Links to the Users table. |
| Lead | ✅ Supported | Required. Set when the task is created, and fixed after that. |
| Type | ✅ Supported | Set when the task is created. Whalesync creates lead tasks. |
| Contact, Object Type, Object ID, View, Is dateless, Due date | ➡️ Supported (1-Way) | Read only. Close fills these in itself. |
| Organization | ➡️ Supported (1-Way) | Read only. Named Organization id on the other tables. |
| Created by, Updated by, Date created, Date updated | ➡️ Supported (1-Way) | Read only. |
| Close field | Status | Notes |
|---|---|---|
| Note | ✅ Supported | The text of the note. Required to create a note. |
| Contact | ✅ Supported | Links to the Contacts table. |
| Lead | ✅ Supported | Required. Set when the note is created, and fixed after that. |
| User | ✅ Supported | Who the note is from. Set when the note is created, and fixed after that. |
| Activity at, Type | ➡️ Supported (1-Way) | Read only. |
| Organization id, Created by, Updated by, Date created, Date updated | ➡️ Supported (1-Way) | Read only. |
Custom fields
Section titled “Custom fields”Close custom fields sync on Leads, Contacts, and Opportunities. Each one is a column named after the field.
| Close custom field type | Status | Notes |
|---|---|---|
| Text, Hidden | ✅ Supported | A text column. |
| Number | ✅ Supported | |
| Date, Date and time | ✅ Supported | |
| Choices | ✅ Supported | Synced by the choice's label, not an ID. Add new choices in Close first. |
| User | ✅ Supported | Links to the Users table. |
| Contact | ✅ Supported | Links to the Contacts table. The contact has to belong to the same lead. |
| Custom object | ✖️ Not supported | The field still appears, as a text column holding Close's raw object ID. Whalesync does not resolve it to the object it points at. |
A custom field that accepts multiple values in Close becomes a multi-value column in Whalesync, whatever its type: a multiple-choice dropdown, but equally a User or Contact field set to accept several.
Adding a custom field in Close brings it in the next time you refresh the schema in Whalesync.
Reference tables
Section titled “Reference tables”Users, Lead Statuses, and Opportunity Statuses are read only. They are here so the fields that point at them, like a lead's status or a task's assignee, have something to link to. Pipelines is listed for a different reason: nothing links to it, and its name is the only organization configuration Whalesync can write. Pipeline id on Opportunity Statuses is plain text rather than a link to it.
| Table | Fields |
|---|---|
| Users | First name, Last name, Email, Image, Organizations, Last used timezone, Email verified at, Email verification token generated at, Date created, Date updated. All read only. |
| Lead Statuses | Label, Organization id. Read only. |
| Opportunity Statuses | Label, Type, Pipeline id, Organization id. Read only. |
| Pipelines | Name syncs both ways. Statuses, Organization id, Created by, Updated by, Date created, and Date updated are read only. |
To add a lead status, an opportunity status, or a pipeline stage, add it in Close. It arrives as a new row in the matching table on the next scheduled poll.
Things to Keep in Mind
Section titled “Things to Keep in Mind”- Most changes in Close arrive within a minute. Whalesync uses Close webhooks for leads, contacts, opportunities, notes, and lead tasks. Everything else is picked up on the next scheduled poll.
- Delete leads in Close, not from your other app. Close deletes a lead's contacts, opportunities, tasks, and notes along with it, and your other app has no way to know that happened, so those rows turn into sync issues. Deleting the lead in Close deletes the matching rows cleanly.
- A record cannot be moved to another lead. Close fixes the lead on a contact, opportunity, task, or note when it is created. Changing it in your other app is ignored rather than synced. Create a new record under the right lead instead.
- A contact on an opportunity has to belong to the same lead. Close refuses a contact from another lead, and the change is reported as a sync issue.
- Opportunity values are in cents. Close stores $1,500 as
150000. Use a formula in your other app if you want to show dollars. - Email and phone labels are not synced. The addresses and numbers on a contact sync, but Close's office, home, and mobile labels do not, and writing to those columns resets the label to Close's default.
- Whalesync creates lead tasks. Close also generates its own tasks for calls, emails, and opportunities. Close only notifies Whalesync about lead tasks, so any of the others that show up in the table are only refreshed on the next scheduled poll.
- A task created in Close takes a few seconds to appear. Close does not return a new task immediately, so it arrives in the following sync.
- Statuses and pipelines are organization configuration. Whalesync never creates a lead status, an opportunity status, or a pipeline stage for you. Pipelines are the exception: a new row in the Pipelines table creates a pipeline in Close, renaming a row renames it, and deleting a row deletes that pipeline in Close along with the statuses on it. Delete a pipeline in Close, where you can see what is attached to it, rather than from your other app.
- Close refuses to delete the last pipeline in an organization, and some Close plans limit how many pipelines you can have. Both come back as sync issues carrying Close's own message.