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.
https://stackone-logos.com/api/capsule/filled/png

Connector Profile

Capsule CRM - API Key
https://stackone-logos.com/api/capsule/filled/png

Connector Profile

Capsule CRM - OAuth 2.0
2

Link an Account

Connect an account using StackOne Hub or Auth Link.
https://stackone-logos.com/api/capsule/filled/png

Link Account

Capsule CRM - API Key
https://stackone-logos.com/api/capsule/filled/png

Link Account

Capsule CRM - OAuth 2.0

How webhooks are set up

Capsule delivers events through REST Hooks, and StackOne provisions them for you — there is no webhook screen to configure inside Capsule and no URL to paste.

1

Connect with OAuth 2.0 as an Administrator

Capsule only allows registered OAuth applications, authorized by an account Administrator, to create REST Hook subscriptions. Connect the account using the OAuth 2.0 authentication method — API Key connections cannot provision webhooks and will not receive any events.

2

Enable the events you need

When the connection is established, StackOne generates a unique callback URL for it and automatically subscribes a Capsule REST Hook for each webhook event you enable in StackOne. Only the events you enable are subscribed. Capsule allows a maximum of 20 active REST Hook subscriptions per account, so enable only the events you intend to consume.

Available webhook events

The events below can be enabled for this connection. Only the events you select in StackOne are subscribed in Capsule and delivered.

1

Review contact events

Fired for people and organisations (Capsule “parties”).

  • Party Created (party/created) — Fired when a new contact (person or organisation) is created.
  • Party Updated (party/updated) — Fired when a contact’s details are changed.
  • Party Deleted (party/deleted) — Fired when a contact is deleted.
2

Review project events

Fired for projects (referred to as “cases” in the API, event code kase/*).

  • Project Created (kase/created) — Fired when a new project is created.
  • Project Updated (kase/updated) — Fired when a project’s details are changed.
  • Project Deleted (kase/deleted) — Fired when a project is deleted.
  • Project Closed (kase/closed) — Fired when a project is closed.
  • Project Moved (kase/moved) — Fired when a project is moved to a different stage.
3

Review opportunity events

Fired for sales opportunities.

  • Opportunity Created (opportunity/created) — Fired when a new opportunity is created.
  • Opportunity Updated (opportunity/updated) — Fired when an opportunity’s details are changed.
  • Opportunity Deleted (opportunity/deleted) — Fired when an opportunity is deleted.
  • Opportunity Closed (opportunity/closed) — Fired when an opportunity is closed (won or lost).
  • Opportunity Moved (opportunity/moved) — Fired when an opportunity is moved to a different pipeline stage.
4

Review task events

Fired for tasks.

  • Task Created (task/created) — Fired when a new task is created.
  • Task Updated (task/updated) — Fired when a task’s details are changed.
  • Task Completed (task/completed) — Fired when a task is marked as completed.
5

Review user events

Fired for user accounts on the Capsule account.

  • User Created (user/created) — Fired when a new user is added to the account.
  • User Updated (user/updated) — Fired when a user’s details are changed.
  • User Deleted (user/deleted) — Fired when a user is removed from the account.

Delivery format

How Capsule delivers events to StackOne.

1

Inspect event payloads

Capsule sends each event as an HTTP POST with a JSON body containing the trigger name in an event field (for example party/updated) and a payload field holding an array of the affected records.

2

Handle batched deliveries

Capsule may batch several records affected by the same event into a single delivery, so the payload array can contain more than one record. StackOne forwards the full payload array in a single emitted event.

3

Verify deliveries

Capsule REST Hook deliveries are not signed. StackOne verifies each delivery through the unique, unguessable callback URL generated for the connection.

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.