Skip to content
Notis

Give complex emailed tasks an execution path

For involved requests, ask the Composio agent to reason across tool calls, handle errors, and retry where appropriate.

Trigger

New Email Received

Trigger for new emails in an AgentMail inbox

Action

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.

Why this helps

Coordinating several app actions by hand creates context switching and leaves more chances for a step to fail unnoticed.

  • Delegate complex multi-step tool work to agent reasoning.
  • Handle errors and retry logic within the execution flow.
  • Keep execution tied to the request that triggered it.

Setup

Build it in a few focused steps.

  • 1Connect AgentMail and Composio once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a clear name.
  • 3In one instruction, ask Notis to use Composio agent execution for complex multi-step requests and report actions and errors.
  • 4Pick AgentMail New Email Received as the trigger and choose where run reports go.
  • 5Test with one real request whose steps and desired outcome are clear.

Questions about this workflow

Should every email use agent execution?

No. This is intended for complex multi-step tasks that need reasoning, error handling, or retries.

Will the agent know the intended outcome?

It can use the email and your instruction. Include relevant constraints and success criteria that are not stated in the request.

Does this guarantee every action succeeds?

No. The execution can handle errors and retries, and the run report should be reviewed for outcome and failures.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Agent mail to Composio. A trigger fires from one place; an action lands in another.

Agent mail triggers

Composio actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

New Email Received

Trigger for new emails in an AgentMail inbox

TriggerPolling

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.

ActionInstant

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.

ActionInstant

Enable trigger

Enable a specific trigger for the authenticated user.

ActionInstant

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.

ActionInstant

Execute Composio Tool

Execute a tool using the composio api.

ActionInstant

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.

ActionInstant

Connect any two apps with Notis in the middle.

Agent mail 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.