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

Oneflow - API Token
2

Link an Account

Connect an account using StackOne Hub or Auth Link.

Link Account

Oneflow - API Token

​
How webhooks are set up

Oneflow delivers events through a webhook subscription, and StackOne provisions it for you on connection. When you connect your account, StackOne creates one Oneflow webhook (POST /webhooks) pointing at a StackOne callback URL, with an EVENT_TYPE filter covering the events you enable. When you disconnect, StackOne deletes that webhook (DELETE /webhooks/{id}). There is nothing to set up in Oneflow and no URL to paste.

1

Connect with your API token

Authorize the connection with your Oneflow API token and user email so StackOne can create and delete the webhook subscription on your behalf. No further setup is needed in Oneflow.

2

Enable the events you need

Enable the Oneflow events you want in StackOne. StackOne registers exactly those event types on the Oneflow webhook (via the EVENT_TYPE filter rule) and dispatches them onward.

​
How events are delivered

Each delivery is a JSON body of the shape { "contract": { "id": … }, "callback_id": …, "events": [ { "id": …, "type": …, "created_time": … } ], "signature": … }. The event type is carried in events[0].type and the affected contract in contract.id. Oneflow signs each delivery with signature = sha1(callback_id + sign_key) inside the body; StackOne forwards deliveries without enforcing this signature.

​
Available webhook events

The events below can be enabled for this connection, grouped by subject.

1

Contract events

Fired for contracts.

  • Contract Create (contract:create) — A new contract was created.
  • Contract Publish (contract:publish) — A contract moved from draft to pending (sent out).
  • Contract Sign (contract:sign) — A contract became fully signed.
  • Contract Decline (contract:decline) — A contract was declined.
  • Contract Delete (contract:delete) — A contract was deleted.
  • Contract Restore (contract:restore) — A deleted contract was restored.
  • Contract Content Update (contract:content_update) — Contract content changed after sending.
  • Contract Signature Reset (contract:signature_reset) — Signatures were cleared after a change.
  • Contract Signing Period Expire (contract:signing_period_expire) — The signing deadline passed.
  • Contract Signing Period Revive (contract:signing_period_revive) — A new signing period began.
  • Contract Workspace Update (contract:workspace_update) — The contract’s workspace changed.
  • Contract AI Extract Complete (contract:ai_extract:complete) — AI data extraction finished.
  • Draft Approval Flow Start (contract:draft_approval_flow:start) — Draft approval flow started.
  • Draft Approval Flow Complete (contract:draft_approval_flow:complete) — Draft approval flow completed.
  • Draft Approval Flow Reset (contract:draft_approval_flow:reset) — Draft approval flow was reset.
  • Lifecycle Settings Update (contract:lifecycle_settings:update) — Lifecycle settings changed.
  • Lifecycle State Start (contract:lifecycle_state:start) — The contract began its first period.
  • Lifecycle State New Period (contract:lifecycle_state:new_period) — The contract entered a new period.
  • Lifecycle State Cancel (contract:lifecycle_state:cancel) — A recurring contract was cancelled.
  • Lifecycle State Terminate (contract:lifecycle_state:terminate) — The contract was terminated.
  • Lifecycle State End (contract:lifecycle_state:end) — The contract expired naturally.
  • Lifecycle Reminder New (contract:lifecycle_reminder:new) — A new lifecycle reminder fired.
  • Lifecycle Reminder End (contract:lifecycle_reminder:end) — A lifecycle reminder ended.
2

Participant events

Fired for participants on a contract.

  • Participant Create (participant:create) — A participant was added.
  • Participant Publish (participant:publish) — A participant gained contract access.
  • Participant Sign (participant:sign) — A participant signed.
  • Participant Decline (participant:decline) — A participant declined.
  • Participant Signature Reset (participant:signature_reset) — A participant’s signature was cleared.
  • Participant Update (participant:update) — A participant’s attributes changed.
  • Participant Delegate (participant:delegate) — A participant delegated to someone else.
  • Participant Delete (participant:delete) — A participant was removed.
  • Participant Delivery Failure (participant:delivery_failure) — Invitation delivery failed.
  • Participant First Visit (participant:first_visit) — A participant opened the contract for the first time.
  • Participant Draft Approval Approve (participant:draft_approval_flow:approve) — A participant approved in the draft flow.
  • Participant Draft Approval Reset (participant:draft_approval_flow:reset) — A participant’s draft approval was reset.
3

Party events

Fired for parties on a contract.

  • Party Create (party:create) — A party was added.
  • Party Update (party:update) — A party’s attributes changed.
  • Party Delete (party:delete) — A party was removed.
4

Product events

Fired for products on a contract.

  • Product Create (product:create) — A product was added.
  • Product Update (product:update) — A product’s attributes changed.
  • Product Delete (product:delete) — A product was removed.
5

Other events

Data field, comment, and reminder events.

  • Data Field Update (data_field:update) — A contract data field changed.
  • Comment Create (comment:create) — A comment was added to a contract.
  • Reminder Expire (reminder:expire) — A reminder expired.

​
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.