This page is part of the Customer.io documentation. For the complete documentation index, see llms.txt.

10

Close Destination

About this integration

Close is the CRM platform of choice for startups and SMBs engaged in inside sales. This integration uses your source data to identify enrich leads in Close, helping you identify your prospects, better understand their needs, and close more sales.

Use cases

• Keep your CRM up to date automatically. When people sign up or update their profile in your app, send identify calls to create or update their contact and lead records in Close—no manual data entry required.
• Enrich leads with product usage data. Pass traits like plan type, company size, or last login date to Close so your sales team can prioritize outreach based on real activity.
• Sync company information to leads. Map company traits from your identify calls—like company name, industry, or employee count—to lead records in Close, giving your reps context before they reach out.
• Route prospects to the right pipeline stage. Use lead status IDs to automatically set the pipeline stage for new leads based on their behavior in your product.

Getting started

1. Go to Data & Integrations > Integrations and select the Close entry in the Directory tab.

2. (Optional) Select the data sources that you want to connect to your outbound integration. You can always connect data sources later. We’ll only show you data sources that work with your integration.

3. Configure your integration.

   1. API key: Your Close API key.

   2. Lead Custom Field ID for Company ID: Enter the ID of a Lead Custom Field that'll be used to store Company ID. You'll need to create this Lead Custom Field in Close first, and then the integration will use this field to store the Company ID when creating new contacts, and/or will be used as a lookup key when updating existing Lead. The Custom Field type must be a text. If this field is not filled out, it will only lookup and de-dupe based on Contact's email.

   3. Contact Custom Field ID for User ID: Enter the ID of a Contact Custom Field that'll be used to store User ID. You'll need to create this Contact Custom Field in Close first, and then the integration will use this field to store the User ID when creating new contacts, and/or will be used as a lookup key when updating existing Contacts. The Custom Field type must be a text. If this field is not filled out, it will only look up and de-dupe based on email.

4. Click Enable Destination.

Actions

When you’re done setting things up, you can go to the Actions tab to see how we map incoming data to your integration.

Create or update contact and lead

This is the only action for the Close destination, and it fires on identify calls by default. It handles both contacts and leads in a single operation:

1. Close searches for an existing lead using the Lead Company ID (if you set a Lead Custom Field ID in your integration settings).
2. If Close doesn’t find a matching lead, it searches for an existing contact using Contact User ID or Contact Email.
3. If Close doesn’t find a matching contact, it creates a new lead and contact.
4. If Close finds a contact that belongs to a lead with a different Company ID, it creates a new lead and contact, duplicating the contact under the new lead.

You can control this behavior with the boolean fields in the action: Allow creating new Leads, Allow updating existing Leads, Allow creating new Contacts, Allow updating existing Contacts, and Allow creating duplicate Contacts under different Lead.

Custom field IDs for matching

To match contacts and leads reliably, set up custom fields in Close and provide their IDs in your integration settings:

• Lead Custom Field ID for Company ID—create a text-type custom field on leads in Close, then enter its ID (for example, cf_xxxx) in the integration settings. Close uses this field to match incoming identify calls to existing leads.
• Contact Custom Field ID for User ID—create a text-type custom field on contacts in Close, then enter its ID in the integration settings. Close uses this field to match contacts by your internal user ID.

If you don’t set these fields, Close falls back to matching contacts by email only. This works for basic setups, but can cause issues if people change their email address.

Default data mapping

The action maps your identify call traits to Close fields automatically:

Set custom fields

You can pass custom field values for both leads and contacts. Use the Lead Custom Fields and Contact Custom Fields objects, where each key is the custom field ID from Close (for example, cf_xxxx) and the value comes from your identify call.

For example, to store a person’s plan trait as a custom field on their contact:

{
    "type": "identify",
    "userId": "user-123",
    "traits": {
        "email": "jane@example.com",
        "name": "Jane Smith",
        "plan": "enterprise",
        "company": {
            "id": "company-456",
            "name": "Acme Corp"
        }
    }
}

Then add a key/value pair in Contact Custom Fields: set the key to your custom field ID in Close (like cf_abc123) and the value to $.traits.plan.

Handle multiple matches

If Close finds multiple contacts with the same email or User ID, it updates up to 10 contacts, ordered by creation date. This can happen if you have duplicate contacts across different leads. Check your Close data for duplicates if you see unexpected behavior.

Things to know

• This integration only supports identify calls. You can’t send track or group events to Close. All contact and lead data flows through identify.
• The matching custom fields must exist in Close first. Create the lead and contact custom fields you reference for matching (Company ID and User ID) in Close before you enter their IDs in your integration settings.
• New email, phone, and URL values append, not replace. If a contact already has a different email, phone number, or URL, Close adds the new value rather than overwriting the existing one.
• Lead status IDs follow the stat_xxxx format. Find your status IDs in Close under Settings > Statuses & Pipelines > Lead Statuses. You can use these to assign leads to specific pipeline stages automatically.
• Custom field IDs follow the cf_xxxx format. Find these in Close under Settings > Customization > Custom Fields. Click a field to see its ID.