Extend an existing automation
Start or continue a governed workflow when a current automation reaches work that needs context or judgment.
Connect existing automation systems to durable workflows with state, decisions, and ownership. Explore example AgentRuntime patterns for Zapier, then confirm connector availability and supported actions before production use.
Use automation services for triggers and actions while AgentRuntime coordinates exceptions, long waits, and human responsibility.
Example architecture only. Exact triggers, actions, scopes, and deployment requirements depend on the connector configuration.
These are representative patterns for the Automation & Operationscategory. They are not claims about currently enabled Zapier actions.
Start or continue a governed workflow when a current automation reaches work that needs context or judgment.
Keep several tools and owners aligned inside one run instead of chaining opaque one-off jobs.
Route failed actions and missing inputs into a visible recovery path without losing process state.
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.