Start work from a message
Convert an inbound request into a typed workflow with context, ownership, and a visible status.
Use messages, email, meetings, and notifications as governed workflow entry and exit points. Explore example AgentRuntime patterns for Gmail, then confirm connector availability and supported actions before production use.
Turn communication into structured work, keep automated outreach controlled, and preserve a clean handoff to people.
Example architecture only. Exact triggers, actions, scopes, and deployment requirements depend on the connector configuration.
These are representative patterns for the Communicationcategory. They are not claims about currently enabled Gmail actions.
Convert an inbound request into a typed workflow with context, ownership, and a visible status.
Notify the right person or channel when a run reaches a decision, wait, exception, or completion.
Collect approval or missing information and resume the same run when the response arrives.
Catalog coverage changes. Validate the actual connector build, authentication method, supported operations, and environment requirements with the AgentRuntime team.
Bring the trigger, actions, access constraints, and human decision points. We will map the governed execution path.