Integrating Oneflow
Auth: OAuth 2.0 · Partner program: not required · Setup time: about 20 minutes · Last verified: 2026-05-21
Swedish contract-automation platform with native e-signature. Useful when operators want the contract drafting + negotiation surface alongside signing — Oneflow renders structured contracts to PDF for signing rather than uploading pre-rendered files.
Auth model
Section titled “Auth model”OAuth 2.0 Authorization Code grant.
Prerequisites
Section titled “Prerequisites”- Oneflow account at oneflow.com.
- Register an OAuth application via developers.oneflow.com.
- Add
<base-url>/auth/docsign/oneflow/callbackto the redirect URIs.
Set the client credentials as the adapter’s config — on the platform’s page in
the admin UI (/platforms/docsign/oneflow), or:
curl -X POST "$INTEGRATION_SERVER_URL/admin/platforms/docsign/oneflow/enable" \ -H "X-Admin-Secret: $ADMIN_SECRET" -H "Content-Type: application/json" \ -d '{"config":{"clientId":"...","clientSecret":"...","redirectUri":"<base-url>/auth/docsign/oneflow/callback"}}'These are adapter settings, not environment variables: nothing reads a
ONEFLOW_CLIENT_ID from .env. See
OAuth adapter credentials.
Contract-automation model
Section titled “Contract-automation model”Oneflow treats the contract as the envelope. The contract body (clauses, sections, fields) is structured data — but only metadata flows through the canonical schema. The rendered-PDF document is single-per-envelope.
Webhooks
Section titled “Webhooks”HMAC-SHA256 in X-Oneflow-Signature (hex).
Refused fields
Section titled “Refused fields”- Contract body content (the structured clause tree)
- Rendered PDF bytes
- Signature images
opensteward.dev ·Plans and free license ·Terms ·Privacy ·support@opensteward.dev
© 2026 Falco Consulting AB. Built from open-steward/opensteward@a3961d8. This site sets no cookies, runs no analytics and loads nothing from other sites, except platform logos from Brandfetch on the Platforms page.