Carry a Drive sharing change into agent settings
When access changes, Notis can update the Agenty agent settings you specify as part of your process.
Trigger
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.
Action
Update Agent by ID
Tool to update an agent's configuration and settings by agent id. use when you need to modify an existing agent after retrieving its current settings. example: "update agent 123 with new name and tags."
Why this helps
Sharing changes can prompt follow-up configuration work that is easy to forget when it lives in another app.
- Tie a permission event to a configured follow-up.
- Reduce manual settings changes when the same process repeats.
- Keep the target agent explicit in the instruction.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Agenty once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name the workflow.
- 3Tell Notis which Agenty agent to update and which specific settings should change after the relevant permission event.
- 4Pick File Shared as the trigger and choose where run reports go.
- 5Test with one real permission change and review the updated settings.
Questions about this workflow
Will this infer which settings to change from the permission event?
No. State the intended settings update in your instruction and verify it with a test.
Is this suitable for every share?
Use a clear instruction describing the relevant case. The trigger fires on new sharing permissions, so confirm the behavior with a representative event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Agenty. A trigger fires from one place; an action lands in another.
Google Drive triggers
Agenty actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Clone Agent by ID
Tool to clone an existing agent by its id. use when you need to duplicate an agent's configuration and optionally start the clone immediately.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Agent
Tool to create a new agent. use when you need to add an agent with configuration and optional auto-start.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Get Agent Templates
Tool to fetch all public agent templates and sample agents. use when listing available templates for users to select.
File Created
Triggers when a new file is created in Google Drive.
Delete Agent by ID
Tool to delete a single agent by its id. use when you need to permanently remove an agent after confirming it exists.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Fetch all agents
Tool to fetch all active agents under an account. use after authenticating when you need to list agents with pagination and sorting.
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.
Get Agent by ID
Tool to fetch details of a specific agent by its id. use when you need full agent configuration before taking further actions.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Update Agent by ID
Tool to update an agent's configuration and settings by agent id. use when you need to modify an existing agent after retrieving its current settings. example: "update agent 123 with new name and tags."
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Create API Key
Tool to create a new api key. use when you need to provision access credentials for the api.
Connect any two apps with Notis in the middle.
Google Drive and Agenty, 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 Agenty.