Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Close Destination


Close(link takes you to an external page) is the inside sales CRM of choice for startups and small and midsize businesses (SMBs.)


Getting started

getting-started page anchor
  1. Go to your Close app and select the Organization you want to use.
  2. Click Settings in the bottom left, then click API Keys in the left menu. Create a new API Key.
  3. From the Segment web app, click Catalog, then click Destinations.
  4. Find the Destinations Actions item in the left navigation, and click it.
  5. Click the "Close" item to select it and click Configure.
  6. Choose which of your sources to connect the destination to. (You can connect more sources to the destination later.)

Property nameTypeRequiredDescription
API keypassword
required

Your Close API key.


Contact Custom Field ID for User IDstring

Optional

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.


Lead Custom Field ID for Company IDstring

Optional

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.


Build your own Mappings. Combine supported triggers with the following Close-supported actions:

(information)

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Create or Update Contact and Lead

create-or-update-contact-and-lead page anchor

Create or Update Contact and/or Lead. At first, Close will try to find Lead via Lead Company ID. If Lead is not found, Close will try to find a Contact either via Contact User ID or via Contact Email. If Contact is not found, Close will create a new Lead and Contact. It will also create a new Lead and Contact if Contact is found but exists under a Lead with different Lead Company ID. If the Action does not specify Lead Company ID, Close will update the Contact and also the Contact’s Lead. It might happen that Close will find multiple Contacts with the same Contact User ID or Contact Email. In such case, Close will update up to 10 Contacts, ordered by creation date.

Create or Update Contact and Lead is a Cloud action. The default Trigger is type = "identify"

Property nameTypeRequiredDescription
Lead NameSTRING

Optional

The name of the Lead.


Lead Company IDSTRING

Optional

Your ID that identifies the Lead. Lead Custom Field ID for Company must be defined in the global integration settings.


Lead DescriptionSTRING

Optional

Description of the Lead.


Lead Status IDSTRING

Optional

ID of the Lead Status (stat_xxxx). You can get it in Close in the Statuses & Pipelines page.


Lead Custom FieldsOBJECT

Optional

Custom Fields to set on the Lead. Key should be Custom Field ID (cf_xxxx).


Contact NameSTRING

Optional

The name of the Contact.


Contact EmailSTRING

Optional

Used to lookup Contact if Contact User ID is not set. If the Contact already has different email address, this value will be appended.


Contact PhoneSTRING

Optional

If the Contact already has different phone number, this value will be appended.


Contact URLSTRING

Optional

If the Contact already has different URL, this value will be appended.


Contact TitleSTRING

Optional

The title of the Contact.


Contact User IDSTRING

Optional

Your ID that identifies the Contact. Contact Custom Field ID for User ID must be defined in the global integration settings.


Contact Custom FieldsOBJECT

Optional

Custom Fields to set on the Contact. Key should be Custom Field ID (cf_xxxx).


Allow creating new LeadsBOOLEAN

Optional

Whether the integration is allowed to create new Leads.


Allow updating existing LeadsBOOLEAN

Optional

Whether the integration is allowed to update existing Leads.


Allow creating new ContactsBOOLEAN

Optional

Whether the integration is allowed to create new Contacts.


Allow updating existing ContactsBOOLEAN

Optional

Whether the integration is allowed to update existing Contacts.


Allow creating duplicate Contacts under different LeadBOOLEAN

Optional

Whether the integration is allowed to create duplicate Contact (same email or Contact User ID) under a different Lead (different Lead Company ID).