ClocknextHelp
DocumentationAPI ReferenceMCP Tools
Dashboard
What is Clocknext?Getting started

Customers

CustomersCustomer detail

Billing

PurchasesInvoicesPayments

Tracking

SignalsRevenue dashboardCustomer Portal

Settings

Profile settingsOrganisation settingsTeam MembersModelsIntegrationsAPI Keys

Documentation

Integrations

Connect third-party services like Stripe to your workspace so Customers can settle Invoices.

Integrations connects third-party services to your workspace. The main page is a grid of available providers with their connection status; each provider has its own detail page with a guided, three-step setup and a credentials panel. Today the catalog centres on Stripe for accepting card payments on Invoices. Credentials you enter are stored encrypted per Organisation. Integrations — the grid of provider cards split into Connected and Available with their status badges. (Authenticated screen — sign in at payments.clocknext.com to view.)

What you can do here

  • Browse available integrations and see which are connected.
  • Open a provider to connect it by pasting its credentials.
  • Update the stored keys for a connected provider.
  • Copy the webhook endpoint a provider needs to post events back to.
  • Disconnect a provider.

Owner or admin only

Connecting, updating keys, and disconnecting are available to owners and admins. Members can view a provider's page but not change it.

On this page

Integrations grid

Providers are split into two groups — Connected and Available (or All integrations when nothing is connected yet). Each card shows the brand logo, a short tagline, and a status badge (Connected with the date, or Not connected). The card footer links to the provider's setup page — Manage when connected, Connect otherwise.

Provider detail (/settings/integrations/[provider])

A branded hero with the provider name, status, and description sits above a two-column layout:

  • Setup guide (left) — numbered steps: get your API keys (with a link to the provider's dashboard), paste the keys, and — for providers that receive events — add the webhook endpoint. The endpoint URL has a copy button.
  • Credentials (right) — one field per secret the provider needs. Each field has a show/hide toggle. Once connected, saved keys are hidden; re-enter all values to update them.

Connecting a provider

  1. From the grid, open the provider (e.g. Stripe).

  2. Follow step 1 to fetch your keys from the provider's dashboard.

  3. Paste each credential into the Credentials panel. For Stripe these are:

    FieldNotes
    Secret keyStarts with sk_. Stripe Dashboard → Developers → API keys.
    Webhook signing secretStarts with whsec_. Shown when you add the webhook endpoint.
    Publishable keyStarts with pk_. Optional — needed for embedded portal checkout.
  4. If the provider receives events, add the shown webhook endpoint in the provider and subscribe to the required event (for Stripe, checkout.session.completed), then paste the signing secret it gives you.

  5. Press Connect. The fields are validated (a friendly prefix check first, then re-validated on the server) and stored encrypted.

To change keys later, re-enter every value and press Update keys. Disconnect removes the stored keys after a confirmation — payments through that provider stop working until you reconnect.

Related

  • API Keys — programmatic access to the workspace.
  • Organisation settings — the workspace these integrations belong to.

Models

Build your Model catalog with per-token pricing so Credits and Outcomes can be tracked and costed.

API Keys

Create, regenerate, and delete the single secret key that authenticates the Clocknext API and SDK for your workspace.

On this page

What you can do hereOn this pageIntegrations gridProvider detail (/settings/integrations/[provider])Connecting a providerRelated