Put lead research in Drive when a request comes in
Start focused lead research from an HTTP request and keep the result with your sales materials.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Upload File
Uploads a file (max 5mb) to google drive, moving it to a specified folder if a valid folder id is provided, otherwise uploads to root.
Why this helps
When lead research starts in one place and notes end up elsewhere, it takes extra effort to find the context before outreach.
- Start research from an HTTP request in an existing process.
- Collect relevant lead context in a Drive file.
- Make research easier to locate when preparing sales outreach.
Setup
Build it in a few focused steps.
- 1Connect Autobound and Google Drive once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to use the lead details supplied with the request to gather available Autobound context and upload a concise research file to Google Drive.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real example and confirm the uploaded file contains the expected context.
Questions about this workflow
What starts this workflow?
An HTTP request starts the Notis webhook. Include the lead details Notis needs to identify the relevant Autobound context.
What file does it create?
It uploads the research content Notis prepares as a file to Google Drive. Keep the request and instruction clear about the lead and information you need.
Does Autobound send a trigger event?
No. This workflow starts from a Notis webhook, then asks Notis to work with Autobound and Google Drive.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Autobound to Google Drive. A trigger fires from one place; an action lands in another.
Autobound triggers
Google Drive actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add file sharing preference
Modifies sharing permissions for an existing google drive file, granting a specified role to a user, group, domain, or 'anyone'.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Copy file
Duplicates an existing file in google drive, identified by its `file id`.
Create Comment
Tool to create a comment on a file. use when you need to add a new comment to a specific file in google drive.
Create Shared Drive
Tool to create a new shared drive. use when you need to programmatically create a new shared drive for collaboration or storage.
Create File or Folder
Creates a new file or folder with metadata. use to create empty files or folders, or files with content by providing it in the request body (though this action primarily focuses on metadata creation).
Create a File from Text
Creates a new file in google drive from provided text content (up to 10mb), supporting various formats including automatic conversion to google workspace types.
Create a folder
Creates a new folder in google drive, optionally within a parent folder specified by its id or name; if a parent name is provided but not found, the action will fail.
Create Reply
Tool to create a reply to a comment in google drive. use when you need to respond to an existing comment on a file.
Connect any two apps with Notis in the middle.
Autobound and Google Drive, 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 Google Drive.