Skip to main content

Close Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a Close location.
close_com_api.png

Close

  1. Click the + icon on the Nexset that will be sent to the Close destination, and select the Send to Destination option from the menu.

  2. Select the Close connector from the list of available destination connectors. Then, select the credential that will be used to connect to the Close organization, and click Next; or, create a new Close credential for use in this flow.

  3. Close destinations can be manually configured to send data to any valid Close API endpoint. You can also configure Nexla to automatically send the response received from the Close API after each call to a new Nexla webhook data source.

    First, select the API method that will be used for calls to the Close API from the Method pulldown menu. The Close API supports the following HTTP methods for write operations:

    • POST: For creating new records (for example, creating a new lead, contact, or activity)
    • PUT: For fully replacing an existing record
    • PATCH: For partially updating an existing record (for example, updating specific fields on a lead or opportunity)
    • DELETE: For removing records

The Close REST API base URL is https://api.close.com/api/v1. All destination endpoint URLs should include this base URL followed by the specific resource path. For creating records, use POST requests to the resource collection (for example, https://api.close.com/api/v1/lead/). For updating or deleting records, append the record ID to the URL (for example, https://api.close.com/api/v1/lead/lead_abc123/). Refer to the Close API Reference for full endpoint documentation.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Close API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call.

    The Close API accepts data in JSON format for all write operations. Select JSON as the content format to ensure compatibility.

API Endpoint URL​

  1. Enter the URL of the Close API endpoint to which you want to send the Nexset data in the URL field. For update or upsert operations, include the ID of the record to be updated at the end of the URL.

    Common Close destination endpoints include:

    • Create Lead: https://api.close.com/api/v1/lead/ (POST)
    • Update Lead: https://api.close.com/api/v1/lead/{'{lead_id}'}/ (PUT or PATCH)
    • Create Contact: https://api.close.com/api/v1/contact/ (POST)
    • Update Contact: https://api.close.com/api/v1/contact/{'{contact_id}'}/ (PUT or PATCH)
    • Create Opportunity: https://api.close.com/api/v1/opportunity/ (POST)
    • Update Opportunity: https://api.close.com/api/v1/opportunity/{'{opportunity_id}'}/ (PUT or PATCH)
    • Create Activity (Note): https://api.close.com/api/v1/activity/note/ (POST)
    • Create Activity (Email): https://api.close.com/api/v1/activity/email/ (POST)
    • Create Activity (Call): https://api.close.com/api/v1/activity/call/ (POST)

When sending records that need to be associated with an existing Close lead, include the lead_id field in your Nexset data. Contacts, opportunities, and activities all require a valid lead_id to be linked to the correct lead in Close. For a complete list of required and optional fields for each resource type, refer to the Close API Reference.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers and corresponding values as comma-separated pairs in the Request Headers field (for example, header1:value1,header2:value2).

    You do not need to include any headers already present in the credentials. The Close API's Authorization header and Content-Type header are handled automatically by Nexla based on your credential and content format configuration.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Close destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Use Exclude Attributes to remove internal Nexla metadata fields or any fields that are not accepted by the Close API for the target resource type. For example, system-generated fields like record timestamps or internal IDs that conflict with Close's expected payload structure can be excluded here.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings. Some algorithms require additional settings — click on an algorithm listed below to view instructions for configuring these settings.

The Close API does not have a native bulk import endpoint for most resource types — individual records are typically created or updated via separate API calls. When using record batching, verify that the target Close endpoint supports batch payloads. For high-volume imports, consider using Nexla's rate-limiting settings to stay within Close's default limit of 60 requests per minute per organization.

Response Webhook​

Optional

Nexla can automatically send the response received from the Close API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call — for example, the newly created record's Close ID, timestamps, or error messages.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Close API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.

  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing​

After all endpoint settings have been configured, Nexla can send a test payload to the Close API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Close API using the current settings.

Important

Sending test data will create or modify actual records in your Close CRM account. Use a test lead or sandbox environment when possible to avoid unintended changes to production data.

Save & Activate the Destination​

  • Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to the configured Close endpoint, open the destination resource menu, and select Activate.

    The Nexset data will not be sent to Close until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.