Send matching Drive contracts for signature
Already organize incoming agreements with a Drive query? Use matching files to start a signature workflow with the instructions and recipients you provide.
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
Send Signature Request
Tool to create and send a new signature request with documents. Use when you need to send documents for electronic signature. The action sends emails to all specified signers with links to view and sign the documents. Supports multiple signers, CC recipients, custom fields, form fields, and various signing options. Documents can be uploaded directly or provided via publicly accessible URLs.
Why this helps
Contracts that meet a filing rule can still wait for someone to find them and send them for signing.
- Start from newly matched files in an existing Drive query.
- Keep eligibility criteria aligned with the files you intend to send.
- Report each run so exceptions are easier to follow up.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Dropbox Sign once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis which matched files are ready to sign and provide signer details and a message.
- 4Pick the Google Drive New File Matching Query trigger and choose where run reports should go.
- 5Test with one real matching contract and verify the selected document and signer details.
Questions about this workflow
Does this create or edit the Drive query?
No. Configure or select the query as part of the available Drive trigger setup. The automation acts when a new file matches it.
How does Notis know the document is a contract?
Use a query that matches the intended documents and describe any additional readiness checks in your instruction.
What if recipient information is not in the file?
Supply the signer names and email addresses in the automation prompt or ensure they are available in the document context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Dropbox sign. A trigger fires from one place; an action lands in another.
Google Drive triggers
Dropbox sign actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Invite User to Team
Tool to invite a user to your Team. Use when you need to add a member by email or account ID.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add User to Template
Tool to grant a specified account access to a template. Use when you need to share a template with another user after confirming template and account identifiers.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Bulk create embedded signature request with template
Tool to create a BulkSendJob for embedded templated signature requests. Use when you need to send up to 250 embedded signature requests at once via one or more templates for iFrame signing.
File Created
Triggers when a new file is created in Google Drive.
Bulk send with template
Tool to create a BulkSendJob for templated signature requests. Use when you need to send up to 250 signature requests at once via one or more templates.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Cancel Signature Request
Cancels an incomplete signature request. Use when you need to cancel a pending signature request that has not been completed. The operation is asynchronous and not reversible - once canceled, the signature request cannot be restored.
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.
Create Dropbox Sign Account
Tool to create a new Dropbox Sign account associated with a specified email address. Use when you need to programmatically register new users in the Dropbox Sign platform.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Create API App
Tool to create a new Dropbox Sign API App. Use when you need to register a new application for API integration. The app will have a client_id for authentication and can be configured with OAuth, callbacks, and white labeling.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Create Embedded Signature Request
Tool to create an embedded signature request for signing in an iFrame. Use when you need to initiate a signature request that will be signed within your application rather than via email links.
Connect any two apps with Notis in the middle.
Google Drive and Dropbox sign, 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 Dropbox sign.