Connect Oksign to Truvera
When something happens in Oksign, Notis takes the next step in Truvera. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Oksign to Truvera
Keep signed agreement credentials in view
When Oksign reports a completed agreement, retrieve Truvera credential metadata so the founder can see whether a related credential exists.
Verify credentials linked to signed agreements
When a signed Oksign agreement arrives through a Notis webhook, verify the related credential or presentation in Truvera.
Review credentials for recently signed documents
On a weekly schedule, review recent Oksign completions and retrieve Truvera credential metadata for a compact follow-up list.
Run a scheduled credential verification review
At a recurring interval, ask Notis to verify credential or presentation material available from the Oksign-connected workflow.
Review Truvera API keys monthly
On a monthly schedule, retrieve the Truvera API key inventory and report it alongside current Oksign integration operations.
Review Truvera webhooks monthly
Retrieve the configured Truvera webhook endpoints each month and report them for a quick review of Oksign-related operations.
Open credential details from an agreement request
When an Oksign-connected service sends a document reference, retrieve the matching Truvera credential details for the founder.
Review credential revocation registries quarterly
On a quarterly schedule, retrieve Truvera revocation registries for a lightweight credential operations review connected to Oksign work.
Check a Truvera API key for a document workflow
When an Oksign-connected process flags a key for review, retrieve its Truvera details for the founder to inspect.
Supported Triggers and Actions
Notis builds workflows that link Oksign to Truvera. A trigger fires from one place; an action lands in another.
Oksign triggers
Truvera actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create API Key
Tool to create an API key. Use when you need to generate a new API key with optional alias and IP allowlist.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Webhook
Tool to create a webhook endpoint. Use when you need Dock.io to push event notifications to your service.
Delete API Key
Tool to delete a specific API key. Use after confirming the API key's ID via list_api_keys.
Delete Credential
Tool to delete a verifiable credential. Use after confirming the credential is no longer needed.
Delete Tag
Tool to delete a specific tag. Use when you have a tag ID and want to permanently remove it.
Delete Webhook
Tool to delete a specific webhook. Use after confirming the webhook's ID via list_webhooks.
Retrieve API Key
Tool to retrieve details of an API key. Tries single-key endpoint first, then falls back to listing and filtering.
Retrieve API Keys
Tool to list all API keys. Use when you need to retrieve all API keys for the authenticated account.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Connect any two apps with Notis in the middle.
Oksign and Truvera, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Truvera.