Reference · built on requestConnectorCRM & sales

Close

Leads, contacts, opportunities, and the calls, emails, and SMS logged in Close, with signed webhooks on every change.

Request accessPricing ↗

About

Close is a CRM built around outreach: calling, email, and SMS sit inside the lead record rather than in separate tools. Its REST API at https://api.close.com/api/v1/ exposes leads, contacts, opportunities, tasks, and each activity type, and webhook subscriptions post created, updated, and deleted events with a signed header.

Fibric reads lead and activity records and receives those webhooks. An operator proposes an opportunity status change, a task, or a note; a person approves it, and the write lands once, with a record of who approved what.

This is a reference listing. It documents what Fibric would read from Close and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Leads through GET /api/v1/lead/ with status_id, addresses, contact_ids, and custom fields, paged with _skip and _limit
  • Opportunities with status_id, value, value_period, confidence, and date_won
  • Call, Email, and SMS activities through their list endpoints, filtered to a lead
  • Tasks assigned to users, with a bulk-update endpoint
  • Webhook events for lead, contact, opportunity, activity.call, activity.email, activity.sms, activity.note, and task, with actions created, updated, and deleted
  • Headroom from the RateLimit response header: limit, remaining, and reset per endpoint group

Proposed actions

  • Target capability: propose an opportunity status, value, or confidence change through PUT /api/v1/opportunity/{id}/
  • Target capability: propose a lead status change, or a merge of two duplicate leads, for a person to confirm
  • Target capability: propose a task for a user with a due date
  • Target capability: propose a note activity on a lead summarizing what the operator found and why

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Answer inbound leads inside the hour

    A lead created event arrives with the contact and source. The operator drafts the first email or call script and a task for the rep, who approves and sends.

    With Lead Response

  • Keep opportunity statuses honest

    Opportunities whose status has not moved since a date you choose are listed with the last call or email. The operator drafts the next touch and a task.

    With Stale Pipeline

  • Summarize a call into the lead

    After an activity.call created event, the operator drafts a note with the outcome and next step. The rep edits it before it is saved to the lead.

    With Call Summary

  • Merge duplicate leads

    Leads sharing an email domain or phone number are paired for review. The operator proposes which record survives, and a person runs the merge.

    With Duplicate Lead

Requirements

  • A Close organization and an API key scoped to a user in it
  • A webhook target URL and a place to keep the signature_key each subscription returns
  • Headroom under the organization's cap of 40 webhook subscriptions
  • Retry logic that sleeps for the rate_reset value on a 429
Authentication
An API key created under Settings → Developer → API Keys, sent as the HTTP Basic username with a blank password, or OAuth 2.0 for a user-facing app.

Limits

  • Rate limits apply per endpoint group and per API key; the organization-wide limit is 3 times the per-key limit
  • At most 40 webhook subscriptions per organization
  • Failed deliveries retry with exponential backoff for up to 72 hours; a subscription pauses at 100,000 backlogged events or after 3 days of failure
  • Lead lists return 100 results by default and page with _skip, so long histories are read in slices

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Close ↗

Questions and answers

How are Close webhooks secured?
Each POST carries close-sig-hash and close-sig-timestamp headers. The hash is a SHA256 HMAC of the timestamp and payload concatenated, keyed by the subscription's signature_key. The connector recomputes it and ignores any delivery that does not match.
What rate limits apply?
Close enforces limits per endpoint group, both per API key and per organization, with the organization limit at 3 times the key limit. Every response carries a RateLimit header. On a 429, the connector sleeps for the rate_reset value before retrying.
Can the connector read calls, emails, and SMS?
Yes. Each activity type has list, get, create, update, and delete endpoints, and webhook events exist for activity.call, activity.email, activity.sms, and activity.note, so a new call or message can trigger an operator.
Ask about Close

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Close through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy