
Sign in, add OKSign in Apps, then choose the account your AI can use.
Get started with OKSign
- Add OKSign to your Weavz workspace and connect the account you want to use.
- Review the available tools below and enable the actions your task needs. Check the account permissions before allowing changes.
- Connect a compatible AI client to your workspace, or use the actions API from your application.
Tools
| Name | Description |
|---|---|
Get Credits get_creditsGet remaining credits and account storage usage. | Get remaining credits and account storage usage. |
List Active Documents list_active_documentsList active signing documents. The provider permits one request every three minutes. | List active signing documents. The provider permits one request every three minutes. |
Create or Update Contact upsert_contactInsert or update one contact identified by name and email; the existing contact list is retained. | Insert or update one contact identified by name and email; the existing contact list is retained. |
Quick Start
import { WeavzClient } from '@weavz-io/sdk'
const weavz = new WeavzClient({ apiKey: 'wvz_...' })
const result = await weavz.actions.execute('oksign', 'get_credits', {
workspaceId: '550e8400-e29b-41d4-a716-446655440000',
integrationAlias: 'oksign',
input: { /* ... */ },
})Related Integrations
Explore integrations in other categories
Frequently Asked Questions
Is there a OKSign MCP server through Weavz?
Yes. Add the OKSign integration to a Weavz workspace, enable the actions you need and connect any required account. Weavz provides the workspace MCP endpoint in Tool Mode or Code Mode. The catalog currently lists 3 OKSign actions.
What can an AI agent do with OKSign?
Available actions include Get Credits, List Active Documents, Create or Update Contact. Your workspace exposes only the actions you enable. The agent also needs the intended account access and any required input values.
How do I connect OKSign to Claude or ChatGPT?
Use a compatible remote MCP client, add the Weavz connector and choose a workspace. Add OKSign, connect the required account and review the enabled actions. Client availability and account requirements vary; adding the connector does not authorize every app automatically.
Can I use OKSign through an API or SDK?
Yes, supported actions can run through the Weavz REST API, TypeScript SDK or Python SDK. Configure a workspace and the required connections, use scoped access, and pass the intended end-user context when acting for a customer.
What authentication does OKSign require?
The catalog lists custom credentials for OKSign. Use Hosted Connect to authorize the intended account. Required permissions, provider app access and available connection methods depend on the integration.
How do I review sensitive OKSign actions?
Limit enabled actions, scope credentials to the intended user and configure Human Gates for the operations that need review. A matching policy can pause a send, record change or other sensitive action for an approver before execution.
What limits or costs apply to OKSign?
Weavz plan limits apply to the actions and resources you use. The external provider may also require an account, a paid plan, API credits or specific permissions, and may enforce its own rate limits. Check current Weavz pricing and the provider’s terms before rollout.
Connect OKSign in minutes
Get 20,000 free action executions every month. No credit card required.