Skip to main content

Close integration

Sync leads, contacts, opportunities, and call activity on behalf of your clients' Close CRM workspaces.

What it does

The Close integration lets you run CRM automations on behalf of any client whose Close workspace you manage. Connect a Close account once, then create and look up leads, attach contacts, open opportunities, log call and note activity, and route live Close events (leads created, opportunities updated) into the rest of your workflow without writing any code.

Connect a Close account

  1. In TaskJuice, open Settings -> Connections and choose Add connection -> Close.
  2. In Close, open Settings -> Developer -> API Keys on the workspace TaskJuice should act on, click Add API Key, copy the generated key, and paste it into the Close API Key field.
  3. Enter the literal letter X as the password. Close ignores the password when an API key is supplied as the username; X is the documented placeholder.

The connection is read- and write-capable across leads, contacts, opportunities, and activities scoped to the workspace the key was issued from. Rotate or revoke the API key from the same Settings -> Developer -> API Keys page at any time.

Triggers

  • close/lead-created. Fires when a new lead is created in the connected Close workspace.
  • close/opportunity-updated. Fires when an existing opportunity is updated (status, value, confidence, period, or currency).

Both triggers verify the inbound POST against an HMAC-SHA256 signature. In Close, create a webhook subscription via the Webhook Subscription API, copy the signature_key returned at creation time, and paste it into the trigger's signing-key field when you wire the trigger in TaskJuice. Close signs timestamp + body with the key and delivers the hex digest in the close-sig-hash header alongside close-sig-timestamp.

Actions

  • close/list-leads. List leads in the workspace using a Close advanced filter query, cursor-paginated.
  • close/get-lead. Look up a single lead by ID, optionally requesting specific fields.
  • close/create-lead. Create a new lead with a name, URL, description, status, contacts, and custom fields.
  • close/create-contact. Attach a new contact (name, title, emails, phones, URLs) to an existing lead.
  • close/create-opportunity. Open an opportunity on an existing lead with a value, period, currency, confidence, and note.
  • close/create-note-activity. Log a rich-text or plaintext note activity on a lead.
  • close/log-call-activity. Log a call activity on a lead with direction, disposition, duration, phone number, and notes.

Known limitations

  • Rate limits follow Close's per-endpoint policy documented at https://developer.close.com/api/overview/rate-limits.md. TaskJuice retries on 429 responses honoring the Retry-After header.
  • List endpoints use cursor-based pagination via the _cursor query parameter. TaskJuice stops paginating after 100 pages by default; raise the ceiling on the action if you need a deeper sweep.
  • The note and note_html fields on notes and call activities overwrite each other. When both are provided, note_html takes precedence and the plaintext note is regenerated from the HTML.
  • Each Close organization can hold up to 40 webhook subscriptions (500 for approved automation partners). Reuse a single subscription across triggers where possible.
  • API key authentication is scoped to the user the key was issued from. Switching users requires rotating the connection's API key.
Was this helpful?
Close integration | TaskJuice Docs