Validate Composio inputs from document keywords
When a request becomes explicit, fetch the schema that makes the next tool call precise.
Trigger
Keyword Detected in Document
Triggers when a specific keyword or phrase first appears in a Google Doc. This trigger monitors a Google Doc and fires once when the specified keyword is detected. After the keyword is found, the trigger will not fire again until reset.
Action
Get Tool Schemas
Retrieve input schemas for tools by slug. Returns complete parameter definitions required to execute each tool. Only pass tool slugs returned by COMPOSIO_SEARCH_TOOLS — never guess or fabricate slugs. If unsure of the exact slug, call COMPOSIO_SEARCH_TOOLS first.
Why this helps
A clear request can still stall when nobody knows which inputs the connected tool requires.
- Clarify required inputs
- Improve execution accuracy
- Reduce failed tool calls
Setup
Build it in a few focused steps.
- 1Connect Google Docs and Composio in Notis once.
- 2Create an automation describing the keyword and the Composio tool whose schema should be retrieved.
- 3Pick Keyword Detected in Document and configure the document and phrase.
- 4Choose a report channel and test when the phrase appears.
Questions about this workflow
Does this call the tool?
No. It retrieves the input schema so the later call can be prepared correctly.
What if the tool slug is unknown?
Search for the tool first in a separate instruction or provide the exact slug in the automation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Docs to Composio. A trigger fires from one place; an action lands in another.
Google Docs triggers
Composio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Ask Oracle
Static helper that returns a comprehensive system prompt describing how to plan and execute tasks using the available composio tools and workflows. no inputs required; simply call to retrieve the prompt. always call this after the search tool is executed -- it will provide the best context on how to proceed, chain tools, and execute the task end-to-end. relevant tools referenced by the prompt: 1. composio search tools 2. composio multi execute tool 3. composio execute code 4. composio manage connections 5. composio bash tool
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Check active connection (deprecated)
Deprecated: use check active connections instead for bulk operations. check active connection status for a toolkit or specific connected account id. returns connection details if active, or required parameters for establishing connection if none exists. active connections enable agent actions on the toolkit.
New Document Created
Triggers when a new Google Doc is created. This trigger monitors Google Docs and fires when new documents are detected. Uses timestamp filtering to efficiently poll for new documents.
Check multiple active connections
Check active connection status for multiple toolkits or specific connected account ids. returns connection details if active, or required parameters for establishing connection if none exists. active connections enable agent actions on toolkits.
Document Deleted
Triggers when an existing Google Doc is deleted (moved to trash). This trigger monitors Google Docs and fires when documents are trashed.
Create Plan
This is a workflow builder that ensures the LLM produces a complete, step-by-step plan for any use case. WHEN TO CALL: - Call this tool based on COMPOSIO_SEARCH_TOOLS output. If search tools response indicates create_plan should be called and the usecase is not easy, call it. - Use this tool after COMPOSIO_SEARCH_TOOLS or COMPOSIO_MANAGE_CONNECTIONS to generate an execution plan for the user's use case. - USE for medium or hard tasks — skip it for easy ones. - If the user switches to a new use case in the same chat and COMPOSIO_SEARCH_TOOLS again instructs you to call the planner, you MUST call this tool again for that new use case. Memory Integration: - You can choose to add the memory received from the search tool into the known_fields parameter of the plan function to enhance planning with discovered relationships and information. Outputs a complete plan with sections such as "workflow_steps", "complexity_assessment", "decision_matrix", "failure_handling" "output_format", and more as needed. If you skip this step for non-easy tasks, workflows will likely be incomplete, or fail during execution for complex tasks. Calling it guarantees reliable, accurate, and end-to-end workflows aligned with the available tools and connections.
Document Placeholder Filled
Triggers when a Google Doc's plain text changes such that a configured placeholder token/pattern is no longer present (i.e., the document has been filled in). This trigger monitors a specific Google Doc and fires when a placeholder pattern that was previously present is no longer found in the document's plain text.
Enable trigger
Enable a specific trigger for the authenticated user.
Document Search Update
Triggers when a Google Doc matching a user-defined search query is newly created or updated since the last poll. This trigger uses timestamp filtering to efficiently monitor documents.
Execute agent
Execute complex workflows using ai agent reasoning between multiple tool calls. use this for: complex multi-step workflows requiring reasoning, error handling and retry logic. use composio multi execute tool instead for: simple parallel operations, batch operations on similar data (e.g., fetch 5 emails, get 10 sent messages, retrieve multiple user profiles), independent tool calls that don't need each other's results, or bulk operations where all parameters are known upfront. performance: agent calls add ~2-3 seconds overhead. use for workflows >3 tools or requiring conditional logic. avoid for simple parameter passing.
Document Structure Changed
Triggers when a Google Doc's structure changes (headers/footers added/removed, tables/images count changes). This trigger monitors a specific document for structural changes like: - Headers added or removed - Footers added or removed - Tables added or removed - Images (inline objects) added or removed - Positioned objects added or removed - Footnotes added or removed
Execute Composio Tool
Execute a tool using the composio api.
Document Updated
Triggers when an existing Google Doc is updated or modified. This trigger monitors Google Docs and fires when documents are updated.
Get Tool Dependency Graph
Get the dependency graph for a given tool, showing related parent tools that might be useful. this action calls the composio labs dependency graph api to retrieve tools that are commonly used together with or before the specified tool. this helps discover related tools and understand common workflows.
Connect any two apps with Notis in the middle.
Google Docs and Composio, 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 Composio.