Skip to main content

Prerequisites

Before continuing, you should have already completed the following for this connector:
1

Configure the Connector

Enable the connector and set up its connector profile in your project. See Managing Connectors.

Connector Profile

Close - OAuth 2.0

Connector Profile

Close - API Key
2

Link an Account

Connect an account using StackOne Hub or Auth Link.

Link Account

Close - OAuth 2.0

Link Account

Close - API Key

How webhooks are set up

Close delivers events through a webhook subscription, and StackOne provisions it for you on connection. When you connect your account, StackOne creates one Close webhook subscription (POST /webhook/) pointing at a StackOne callback URL, covering every supported event type. When you disconnect, StackOne deletes that subscription (DELETE /webhook/{id}/). There is nothing to set up in Close and no URL to paste.

1

Connect with OAuth 2.0 or an API key

Authorize the connection with either OAuth 2.0 or an API key — both work the same way for webhooks — so StackOne can create and delete the subscription on your behalf. No further setup is needed in Close.

2

Enable the events you need

Enable the Close events you want in StackOne. StackOne registers one consolidated subscription that already covers every event type; only the events you enable in StackOne are dispatched onward.

How events are delivered

Close signs each delivery with two headers, close-sig-hash and close-sig-timestamp, which together let Close’s own systems verify authenticity. Because the signing key is only handed back once — at the moment the subscription is created — StackOne cannot store it for later use, so it does not recompute the full signature on incoming requests. As a safeguard, StackOne still rejects (with a 401 response) any request that is missing either signature header, so unsigned or malformed requests are never processed.

Available webhook events

The events below can be enabled for this connection, grouped by the entity they apply to.

1

Lead events

Fired for leads.

  • Lead Created (lead.created) — Fired when a lead is created.
  • Lead Updated (lead.updated) — Fired when a lead’s fields change.
  • Lead Deleted (lead.deleted) — Fired when a lead is deleted.
  • Lead Merged (lead.merged) — Fired when two leads are merged.
2

Contact events

Fired for contacts.

  • Contact Created (contact.created) — Fired when a contact is created.
  • Contact Updated (contact.updated) — Fired when a contact’s fields change.
  • Contact Deleted (contact.deleted) — Fired when a contact is deleted.
3

Opportunity events

Fired for opportunities.

  • Opportunity Created (opportunity.created) — Fired when an opportunity is created.
  • Opportunity Updated (opportunity.updated) — Fired when an opportunity’s fields change.
  • Opportunity Deleted (opportunity.deleted) — Fired when an opportunity is deleted.
4

Call activity events

Fired for logged call activities.

  • Call Created (activity.call.created) — Fired when a call activity is logged.
  • Call Completed (activity.call.completed) — Fired when a call activity’s status changes to completed.
5

Email activity events

Fired for email activities.

  • Email Created (activity.email.created) — Fired when an email activity is created.
  • Email Sent (activity.email.sent) — Fired when an email activity is sent.
6

SMS activity events

Fired for SMS activities.

  • SMS Created (activity.sms.created) — Fired when an SMS activity is created.
  • SMS Sent (activity.sms.sent) — Fired when an SMS activity is sent.
7

Note activity events

Fired for note activities.

  • Note Created (activity.note.created) — Fired when a note activity is created.
  • Note Updated (activity.note.updated) — Fired when a note activity is updated.
8

Meeting activity events

Fired for meeting activities.

  • Meeting Scheduled (activity.meeting.scheduled) — Fired when a meeting activity is scheduled.
  • Meeting Completed (activity.meeting.completed) — Fired when a meeting activity is completed.
9

Status change activity events

Fired when a lead’s or opportunity’s status changes.

  • Lead Status Change (activity.lead_status_change.created) — Fired when a lead’s status changes.
  • Opportunity Status Change (activity.opportunity_status_change.created) — Fired when an opportunity’s status changes.
10

Task events

Fired for lead-scoped tasks.

  • Task Created (task.lead.created) — Fired when a task is created on a lead.
  • Task Completed (task.lead.completed) — Fired when a task on a lead is marked complete.
11

Sequence subscription events

Fired when a contact’s sequence subscription changes.

  • Sequence Subscription Created (sequence_subscription.created) — Fired when a contact is subscribed to a sequence.
  • Sequence Subscription Updated (sequence_subscription.updated) — Fired when a sequence subscription is updated (e.g. paused, resumed).
12

Membership events

Fired for organization membership changes.

  • Membership Activated (membership.activated) — Fired when a user’s membership in the organization is activated.
  • Membership Deactivated (membership.deactivated) — Fired when a user’s membership in the organization is deactivated.

Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.