Do Automations have webhooks associated with them, that is webhooks that trigger the automation on-demand?

Not sure if I understand, is there a specific use case you have in mind?

I would like to trigger an Automaton on-demand, potentially through a custom workflow I am building (such as a script)

🤔 I thought they’re supposed to trigger automatically, not on-demand

They do, but we dont have robust event-driven in Agent Canvas, so I might want to create my own triggers from various systems and kickoff the automation

we can support it, doesn't exist as of today the closest we have is on demand dispatch of schedule based automations which we use for testing

I think it would be amazing if users could easily get the webhook that triggers the Automation directly from within the canvas UI. Especially if they want to run those Automations in systems that support outbound webhooks

gotcha that part thats confusing me is webhook vs api seems like you want an explicit REST API to trigger an automation ?

Yes. For example some tools like Linear have Webhook functionality where Linear can send an HTTP POST to your endpoint to kickoff jobs

Right the automation server receives webhooks as of today (e.g from linear) I'm a bit confused about what is meant by > users could easily get the webhook that triggers the Automation The user should be able to identify which webhook triggers the automation (e.g linear)? > would like to trigger an Automaton on-demand, potentially through a custom workflow I am building (such as a script) This would mean we expose a separate endpoint like

/trigger <automation-id>

where the user can fire off a CURL command to dispatch the automation, as opposed to today where this is only possible if a webhook is received

I'm basically suggesting we do something like this: https://code.claude.com/docs/en/routines#add-an-api-trigger Claude Routines == OH Automations

An API trigger gives a routine a dedicated HTTP endpoint. POSTing to the endpoint with the routine’s bearer token starts a new session and returns a session URL. Use this to wire Claude Code into alerting systems, deploy pipelines, internal tools, or anywhere you can make an authenticated HTTP request.

API triggers are added to an existing routine from the web. The CLI cannot currently create or revoke tokens.