Create an embedded signing link from a matching Drive file
When a file that meets your Drive query appears, prepare an embedded BoldSign request link for the signing flow you describe.
Trigger
New File Matching Query
Triggers when a new Google Drive file matches a provided query. This is the legacy query-centric trigger: it preserves Drive API query config such as ``corpora`` / ``driveId`` aliases and emits the historical ``file_matching_query`` event type. ``FileCreatedTrigger`` covers the broader "new file" case and emits ``file_created``.
Action
Create Embedded Request Link
Tool to create an embedded request link. Use after specifying title and signers to generate an embeddable URL for in-app document preparation and sending.
Why this helps
Turning a prepared contract into an in-app signing link can add a manual step between document preparation and the customer experience.
- Start link preparation when a relevant new file matches your Drive query.
- Give Notis one instruction for the title and signer details to use.
- Reduce manual handoffs for embedded signature experiences.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and BoldSign once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name and prompt.
- 3Tell Notis which matching file should be used and specify the request title and signer details.
- 4Pick the Google Drive New File Matching Query trigger and choose where run reports go.
- 5Test with one real matching file and verify the returned embedded request link.
Questions about this workflow
Does this send the document for signing?
The action creates an embedded request link for in-app document preparation and sending. Confirm the returned link and complete the preparation and sending steps in the intended experience.
Where do the title and signer details come from?
Specify them in your instruction or ensure they are available from the matched file and event. The workflow cannot invent signer identities.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Boldsign. A trigger fires from one place; an action lands in another.
Google Drive triggers
Boldsign actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Brand Details
Tool to get brand details by brand ID. Use after obtaining the brand identifier.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Brands
Tool to list all brands in the account. Use after confirming account is authenticated.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Create Custom Field
Tool to create a brand-scoped custom field. Use when you need to define and register a new custom field for a specific brand.
File Created
Triggers when a new file is created in Google Drive.
Edit Custom Field
Tool to edit an existing custom field. Use when you need to update a custom field's properties after creation.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
List Behalf Documents
Tool to list documents sent on behalf of users. Use when fetching and filtering documents you've sent or on behalf of others.
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
Edit Document (Beta)
Tool to edit a draft or sent document. Use when updating files, recipients, or document settings before finalizing the document.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Extend Document Expiry
Tool to extend a document's expiry date. Use before signing to prolong a document's deadline.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
List Documents
Tool to list documents in My Documents with filters. Use when you need to fetch and filter documents based on various criteria.
Connect any two apps with Notis in the middle.
Google Drive and Boldsign, 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 Boldsign.