Check Ascora customers when a new Drive file arrives
A new customer document can trigger a quick customer record check in Ascora, helping you avoid opening apps and searching lists yourself.
Trigger
File Created
Triggers when a new file is created in Google Drive.
Action
Get Customers
Tool to retrieve a list of customers. use after authenticating with your api key.
Why this helps
Customer documents can sit unlinked because identifying the right record takes extra searching and context switching.
- Start customer checks as soon as a document is created.
- Use available file context to guide a customer list search.
- Surface ambiguous or missing references for a person to resolve.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Ascora once in the Notis portal.
- 2Create an automation and ask Notis to inspect new file context and retrieve relevant Ascora customers for a customer reference check.
- 3Pick the File Created trigger.
- 4Choose where run reports should go.
- 5Test with one real customer file and review the returned customer list.
Questions about this workflow
What starts the check?
Creation of a new file in Google Drive.
Does this create or update a customer record?
No. The available Ascora action retrieves customer records. It can help with a check, but it does not create or update them.
What if the file does not identify the customer?
Notis should report that it could not establish a reliable match and ask for a person to review the document.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Ascora. A trigger fires from one place; an action lands in another.
Google Drive triggers
Ascora actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Customer
Tool to delete a specific customer by id. use when you need to remove a customer after confirming its existence.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Quotation
Tool to create a new quotation. use when submitting a customer quote request via the ascora api.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Delete Customer
Tool to delete a specific customer by id. use after confirming the customer exists.
File Created
Triggers when a new file is created in Google Drive.
Get Customers
Tool to retrieve a list of customers. use after authenticating with your api key.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Get Jobs
Tool to retrieve jobs. use when you need to filter and paginate job listings from ascora.
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.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Connect any two apps with Notis in the middle.
Google Drive and Ascora, 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 Ascora.