Move approved contracts from Notion into Oksign
Keep the handoff to signing simple: mark the contract ready in Notion and let Notis upload its document to Oksign.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Upload Document
Tool to upload a PDF or Word document to OKSign platform for completion and/or signing. Use when you need to add a new document that requires signatures. Maximum file size is 10 MB. Supported formats: PDF, DOC, DOCX.
Why this helps
Copying contract files between tools adds a step that is easy to forget when several agreements are moving at once.
- Starts the signing handoff from the Notion status your team already updates.
- Reduces repeated file handling for each approved agreement.
- Keeps the workflow prompt readable and easy to adjust.
Setup
Build it in a few focused steps.
- 1Connect Notion and Oksign to Notis once in the portal.
- 2Create an automation in Automations -> New Automation, or ask Notis conversationally.
- 3In one plain-language prompt, tell Notis to upload the approved contract document from the Notion record to Oksign.
- 4Choose the Notion Page Properties Updated trigger and a channel for run reports.
- 5Test by marking one real contract record ready and review the Oksign upload.
Questions about this workflow
Does this trigger on every Notion property edit?
The event can fire on property changes. In the prompt, tell Notis to act only when the contract is marked ready, and test that condition with a real record.
Do I need to set up field mappings?
No. Describe the desired upload in the automation prompt; Notis interprets the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Oksign. A trigger fires from one place; an action lands in another.
Notion triggers
Oksign actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Remove Briefcase
Tool to remove a previously created briefcase from OKSign platform. Use when you need to delete a briefcase that is no longer needed. The briefcase is identified by the token received when it was created.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Retrieve Briefcase Information
Tool to retrieve a previously uploaded briefcase tokeninfo for consultation. Use when you need to examine bundled document properties and signer requirements without re-creating the briefcase.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Remove Contacts
Tool to remove specified contacts from the account's contact list. Use when you need to delete one or more contacts by providing their name and email.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Retrieve Contacts
Tool to retrieve the list of contacts stored in the account. Use when you need to access all contacts with their details including name, email, mobile number, and role.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Upload Contacts
Tool to insert or update contact information in the account's contact list. Use when you need to add new contacts or update existing ones with details like name, email, phone, mobile, address, company, or identifier.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Retrieve Account Credits
Tool to retrieve account credit balance and storage information. Use when you need to check available credits or storage capacity.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Check Document Exists
Tool to check if a signed or unsigned document still exists on the OKSign platform. Use when you need to verify document availability before performing operations.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Remove Document
Tool to remove a signed or unsigned document from the OKSign platform. Use when you need to delete a document and its signed copies from storage. Note: If document is removed immediately after signing while platform processes notifications, service may return FAILED status with retry message.
Connect any two apps with Notis in the middle.
Notion and Oksign, 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 Oksign.