Skip to content
Start in the sandbox
All connectors
Close logo

Close

CRM, sales & customer success

Keep Close up to date with every customer, deal and order, without copy and paste.

47 ways to read, 18 ways to write, each write switched on by you.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Close with Nexra

Connected, approved, proven.

The things teams do most with Close, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Log callcalls.createApproval by rule
  • Create commentcomments.createApproval by rule
  • List activitiesactivities.listRead

Example flow

  1. Close · List activitiesactivities.listDone
  2. Close · Log callcalls.createMaker-checker
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Close.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Close
  • Close's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Read and write Close leads, contacts, opportunities, tasks, notes, logged calls, comments, custom activities and custom objects; read emails, SMS, status changes, form submissions and the event log.

Elastic Inc. (Close) API docs
Source actions
47
Destination actions
18
Data types
31

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

activities1
  • List activitiesSourceIncremental

    Activities for the organization, a lead, contact or user, newest first.

calls4
  • Log callDestinationNot retried automaticallyApproval before production

    Logs a call made outside Close as a call activity on a lead. It does not place a call.

  • Get callSource

    One call.

  • List callsSourceIncremental

    Calls for the organization, a lead, contact or user, newest first.

  • Update callDestinationProvider duplicate protectionApproval before production

    Updates a logged call's note, outcome, status or duration.

comments4
  • Create commentDestinationNot retried automaticallyApproval before production

    Adds an internal comment to an object's thread (Close creates the thread if needed).

  • Get commentSource

    One comment.

  • List commentsSource

    Comments on one object (for example a lead, opportunity or activity).

  • Update commentDestinationProvider duplicate protectionApproval before production

    Replaces the body of a comment.

contacts5
  • Create contactDestinationNot retried automaticallyApproval before production

    Creates a contact.

  • Get contactSource

    One contact with custom fields.

  • List contactsSource

    Contacts, optionally for one lead.

  • Search contactsSource

    Advanced filtering over contacts by text (names, titles, email addresses and other text fields) and title, sent in the JSON body.

  • Update contactDestinationProvider duplicate protectionApproval before production

    Updates only the mapped contact fields.

custom activities4
  • Create custom activityDestinationNot retried automaticallyApproval before production

    Records a custom activity of a defined type on a lead.

  • Get custom activitySource

    One custom activity instance with its custom fields.

  • List custom activitiesSourceIncremental

    Custom activity instances; filtering by type also needs a lead (Close requirement).

  • Update custom activityDestinationProvider duplicate protectionApproval before production

    Updates custom fields, status, pin or contact of a custom activity.

custom activity types1
  • List custom activity typesSource

    Custom activity types with their field definitions.

custom fields1
  • List custom fieldsSource

    Lead, contact or opportunity custom field definitions with type, choices and multi-value flag.

custom object types1
  • List custom object typesSource

    Custom object types with field and back-reference definitions.

custom objects4
  • Create custom objectDestinationNot retried automaticallyApproval before production

    Creates a custom object instance of a defined type on a lead.

  • Get custom objectSource

    One custom object instance with its custom fields.

  • List custom objectsSource

    Custom object instances on one lead, optionally of one type.

  • Update custom objectDestinationProvider duplicate protectionApproval before production

    Updates a custom object's name or custom fields.

email templates1
  • List email templatesSource

    Email templates (read-only; Nexra does not send email).

emails2
  • Get emailSource

    One email.

  • List emailsSourceIncremental

    Emails for the organization, a lead, contact or user, newest first.

events1
  • List eventsSourceIncremental

    Event log of creates, updates and deletes over the last 30 days, newest first. Use it to sync leads and contacts incrementally.

form submissions2
  • Get form submissionSource

    One form submission.

  • List form submissionsSourceIncremental

    Form submissions for the organization, a lead, contact or user, newest first.

forms1
  • List formsSource

    Close forms with their field definitions.

groups1
  • List groupsSource

    User groups with members.

lead status changes1
  • List lead status changesSourceIncremental

    Lead status changes for the organization, a lead, contact or user, newest first.

lead statuses1
  • List lead statusesSource

    Lead statuses.

leads5
  • Create leadDestinationNot retried automaticallyApproval before production

    Creates a lead.

  • Get leadSource

    One lead with custom fields.

  • List leadsSource

    Leads (companies) with status, addresses and custom fields.

  • Search leads or contactsSource

    Advanced filtering by object type with optional full-word text; returns IDs and core fields, most recently updated first.

  • Update leadDestinationProvider duplicate protectionApproval before production

    Updates only the mapped lead fields.

me1
  • Get current userSource

    The user the API key belongs to, with organization memberships.

meetings2
  • Get meetingSource

    One meeting.

  • List meetingsSourceIncremental

    Meetings for the organization, a lead, contact or user, newest first.

notes4
  • Create noteDestinationNot retried automaticallyApproval before production

    Adds a note activity to a lead.

  • Get noteSource

    One note.

  • List notesSourceIncremental

    Notes for the organization, a lead, contact or user, newest first.

  • Update noteDestinationProvider duplicate protectionApproval before production

    Updates a note's text, title, contact or pin.

opportunities4
  • Create opportunityDestinationNot retried automaticallyApproval before production

    Creates a opportunity.

  • Get opportunitySource

    One opportunity with custom fields.

  • List opportunitiesSourceIncremental

    Opportunities filtered by lead, owner, status type or update time.

  • Update opportunityDestinationProvider duplicate protectionApproval before production

    Updates only the mapped opportunity fields.

opportunity status changes1
  • List opportunity status changesSourceIncremental

    Opportunity status changes for the organization, a lead, contact or user, newest first.

opportunity statuses1
  • List opportunity statusesSource

    Opportunity statuses with type (active, won, lost) and pipeline.

outcomes1
  • List outcomesSource

    Call and meeting outcomes.

pipelines1
  • List pipelinesSource

    Opportunity pipelines with their statuses.

sequences1
  • List sequencesSource

    Sequences with their status and steps (read-only; enrolment is not automated).

smart views1
  • List smart viewsSource

    Saved searches (Smart Views) for leads or contacts.

sms2
  • Get SMS messageSource

    One SMS message.

  • List SMS messagesSourceIncremental

    SMS messages for the organization, a lead, contact or user, newest first.

tasks4
  • Create taskDestinationNot retried automaticallyApproval before production

    Creates a task.

  • Get taskSource

    One task with custom fields.

  • List tasksSourceIncremental

    Tasks filtered by lead, assignee, completion, view or update time.

  • Update taskDestinationProvider duplicate protectionApproval before production

    Updates only the mapped task fields.

users2
  • Get userSource

    One user.

  • List usersSource

    Users in the organization.

Access and limits

Authentication
Close API key (HTTP Basic username, empty password)
Plans and access
All Close plans include the API. An API key acts as the user and organization it was created for.
Test environment
Use a Close trial organization or a separate test organization.
Rate limits
Per endpoint group, per API key and per organization (organization limit is 3x the key limit); on HTTP 429 wait rate_reset seconds (Retry-After is also sent).
Pagination
_skip and _limit with has_more; advanced search uses a cursor that expires after 30 seconds.
Provider events
Webhook subscriptions for lead, contact, opportunity, task and activity events. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Close leads double as companies; contacts belong to exactly one lead.
  • Lead and contact lists have no update-time filter; use List events (date_updated__gte, last 30 days) or the opportunity and task date_updated filters for incremental syncs.
  • The event log keeps 30 days, accepts only Close's documented filter combinations (checked before the call) and returns at most 50 events per page; data and previous_data are visible to non-admins only for one hour.
  • Contact search sends its text in the JSON body of POST /data/search/, so email addresses never appear in the URL. Matching on a specific email-address record (contact_email) is not built because its condition shape is not documented.
  • Custom activities filtered by type and custom objects both require a lead ID, as Close documents.
  • Advanced-search cursors expire after 30 seconds and searches stop at 10,000 results.
  • Email unsubscribe state and sequence subscriptions are returned read-only and never written.
  • Custom fields are written by field ID (custom.cf_...); fetch definitions with List custom fields.
  • Calls can be logged (source External) and updated but never placed; emails and SMS are read-only. Sending email or SMS, sequence enrolment, bulk actions, merges, exports, deletes, and user, role, membership or group changes are not automated.
  • Email templates and sequences are listed read-only.
  • Close has no idempotency key; uncertain creates are not repeated automatically.

Developer reference

  1. Create the Elastic Inc. (Close) credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Close, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Elastic Inc. (Close) docsAPI referenceElastic Inc. (Close) docsAuthenticationElastic Inc. (Close) docsRate limitsElastic Inc. (Close) docsWebhooks

Machine-readable detail: GET /api/public/connect/connectors/close and the Connections API.