Hey @nilsen and @Ronnie_Kilsbo, I reopened the Automations API thread Automations API, so feel free to write up detailed API use cases there. The cases from the latest post daily or weekly data aggregation, changelog generation, and especially a meta-agent that reads run logs and updates prompts for future runs are exactly what’s worth describing in detail. What are the absolute blockers for you, and what’s just nice to have? That’s the best way to boost the signal.
We’ll keep discussing config-as-code here and in the related threads:
For now, here’s what you can already use:
- Each Automation has a Webhook trigger. After you save it, Cursor generates a private HTTP endpoint and an API key. You can POST to it from your own systems to start runs programmatically.
- The Cloud Agents API Cloud Agents API | Cursor Docs lets you create, list, and monitor individual agent runs.
Listing automations themselves and exporting their run history via API isn’t available yet. That’s exactly the direction worth describing in detail in 166898. I can’t share a specific timeline, but there’s interest in it. If there’s an update, we’ll post it in those threads.