> ## Documentation Index
> Fetch the complete documentation index at: https://docs.1eye.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Close

> Connect Close CRM to 1eye, map buyers to Contacts and companies to Leads, then run your workflow and verify delivery in the Console.

Push buyers and companies from your 1eye target lists into Close CRM. Companies become **Leads** and buyers become **Contacts**. Each Contact belongs to the Lead for its company.

### Before you begin

* Admin or Marketer access to your 1eye workspace.
* A Close account with permission to authorize the integration and create or update Leads and Contacts in the organization you want to use.
* At least one [Target List](https://docs.1eye.ai/target-lists/overview.md). For your first run, use a small list with verified work emails, buyer names, company names, and company websites.

### Connect Close

1. In 1eye, open **Destinations** and select **Add Destination**.
2. Enter a name, such as **Push to Close**, select **Close**, then select **Add**.
3. In the workflow, open the **Destination** node labeled **Close** and select **Connect**. Confirm that you want to continue.

![Close destination node with the Connect button highlighted](https://mintcdn.com/1eye/qA2kmlExZIF53g_f/images/close-connect.png?fit=max\&auto=format\&n=qA2kmlExZIF53g_f\&q=85\&s=7717ab9f0a28e1e717cecf2704c69a41)

4. Sign in to Close if prompted. Under **Grant access to**, choose the organization that should receive your records.
5. Review the permissions on the Close screen and select **Allow**. Back in 1eye, check that the node shows **Connected**.

![Close authorization screen with the organization selector and Allow button highlighted](https://mintcdn.com/1eye/qA2kmlExZIF53g_f/images/close-authorize.png?fit=max\&auto=format\&n=qA2kmlExZIF53g_f\&q=85\&s=1f8ca45e67e7c08d6cd89ac5a87d06d0)

### Target Lists node

1. Open **Target Lists** in the workflow and select one or more lists.
2. Under **Delivery behavior**, choose which buyers to include.

| Option | What it pushes |
| - | - |
| **Going forward** | New buyers as 1eye identifies them in the selected lists. |
| **Push retroactively** | Existing eligible buyers in the selected lists, followed by new buyers while the workflow is running. |

3. Select **Apply** to save your changes. Return to the **Close** destination node to choose the fields to send.

![Target Lists node showing selected lists and the two delivery behavior options](https://mintcdn.com/1eye/qA2kmlExZIF53g_f/images/close-target-lists.png?fit=max\&auto=format\&n=qA2kmlExZIF53g_f\&q=85\&s=3a1063a702cf1e9dc22a58030425c8b0)

![Selected Target Lists feeding a connected Close destination](https://mintcdn.com/1eye/qA2kmlExZIF53g_f/images/close-select-buyers.png?fit=max\&auto=format\&n=qA2kmlExZIF53g_f\&q=85\&s=05729db62d63a842ea8ce95224063d7f)

### Field mapping

In the **Close** node, use the **Push** column to select the standard fields to send. Use custom mappings for additional data.

**Standard Buyer Fields**

| 1eye field | Close Contact field |
| - | - |
| Work Email | Emails |
| First Name | Name |
| Last Name | Name |
| Phone | Phones |
| Title | Title |
| LinkedIn | URLs |

1eye combines first and last name into the Close Contact's **Name**. Keep a verified work email on each buyer record so 1eye can match the buyer to an existing Contact or create one.

**Custom Buyer Fields**

Select a **1eye Field** and an existing, compatible **Close Custom Property** on the Contact. Select **Add more** to add another mapping. For example, map Persona Name to a text field you created in Close.

![Standard Buyer Fields and Custom Buyer Fields in the Close node](https://mintcdn.com/1eye/qA2kmlExZIF53g_f/images/close-buyer-fields.png?fit=max\&auto=format\&n=qA2kmlExZIF53g_f\&q=85\&s=ab58a16c829d9ff89f78dca256c6d911)

**Standard Company Fields**

| 1eye field | Close Lead field |
| - | - |
| Company Name | Name |
| Company Website | Website |

**Custom Company Fields**

Select a company field and a compatible custom property on the Lead. For example, map Employee Count to a number field. Create any custom fields you need in Close before mapping them, then reopen the destination to load the available fields.

**Push behavior**

Choose **Once per Target Buyer** to push a buyer when first identified. The **New Signal** and **Every Signal** options trigger pushes based on incoming signals. Select **Apply** to save your mappings and push behavior.

![Company field mapping and the Once per Target Buyer, New Signal, and Every Signal options](https://mintcdn.com/1eye/qA2kmlExZIF53g_f/images/close-company-fields.png?fit=max\&auto=format\&n=qA2kmlExZIF53g_f\&q=85\&s=1a2e5d9009cab02591ae26188b3b934b)

### Run the workflow

1. Open **Start**. Set the workflow name and choose **Runs continuously until stopped**, **Runs until a selected date**, or **Runs once only**. If you select an end date, enter it before applying your changes.
2. Apply any pending changes and check that the **Target Lists** and **Close** nodes show **Ready**.
3. Select **Run** at the top of the workflow.

![Start node showing the workflow name and three scheduling options](https://mintcdn.com/1eye/qA2kmlExZIF53g_f/images/close-start.png?fit=max\&auto=format\&n=qA2kmlExZIF53g_f\&q=85\&s=1ca2283c3a1f8cacda880a1e583363cc)

> [!TIP]
>
> To verify delivery with existing buyers, choose a small Target List, set **Push retroactively**, and choose **Runs once only**. After the run, check one buyer in the Console and confirm the Contact and its parent Lead in Close.

### Monitor pushed records

Select **View console** from the workflow. Use **All** to review delivery activity, **Pushed** to confirm successful records, **Pending** to check records waiting to be sent, and **Failed** to investigate errors.

For a successful push, find the Contact in the selected Close organization by work email. Open its parent Lead and verify that the company and mapped values are correct. 1eye uses the company website domain and the buyer's verified work email to help match existing records.

### Disconnect Close

Open the **Close** destination node, select the menu next to **Connected**, and choose **Disconnect**. Existing Leads and Contacts stay in Close. To send records again, reconnect and verify the organization before running the workflow.

### Troubleshooting

| Issue | What to check |
| - | - |
| **Close is Not Connected** | Open the Close node and complete authorization. Check that you selected the intended organization. |
| **Run is unavailable** | Select a Target List, confirm that Close is connected, and apply pending changes. Check any node marked **Not Ready**. |
| **Existing buyers did not push** | Check that **Push retroactively** is selected and that the buyers are eligible in the selected lists. Check **Pending** and **Failed** in the Console. |
| **A Lead exists but its Contact is missing** | Check the buyer's verified work email and the Console. An eligible company can be sent even when its buyer lacks a verified work email. |
| **Multiple matches or a Contact belongs to a different Lead** | Review the existing records in Close. Resolve duplicate domains or emails, or correct the Contact's Lead association in Close before trying again. |
| **A custom field is missing** | Verify that it exists in the connected organization on the correct record type, has a compatible type, and is editable by the connected account. |

### Next step

See how to pause, resume, or update your workflow in [Managing Destinations](https://docs.1eye.ai/destinations/managing-destinations.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.