Yes, this can be automated. You don't need someone to open Power Automate and press Run after every solution deployment.
If the purpose of the flow is to initialize/update an environment-specific value after the solution is imported, I would use a solution-aware cloud flow with a Dataverse trigger rather than an HTTP-triggered flow that has to be manually invoked.
Microsoft specifically documents this scenario: if you want a flow to start automatically after a solution is imported, use the Microsoft Dataverse connector when creating the flow.
A typical pattern would be:
Solution import → Dataverse trigger → Update environment/configuration → Flow completes
For example, you could use a Dataverse trigger such as When a row is added, modified or deleted on a small configuration/control table. The deployment process can create/update the appropriate configuration row, which causes the flow to execute automatically.
Also, if the value you're updating is genuinely environment-specific, consider whether you need a separate HTTP flow at all. Environment variables are designed for values that change between environments, and their values can be supplied during solution import or through a deployment pipeline.
If you're using Power Platform Pipelines/ALM, an even cleaner architecture is:
Dev → Solution → Pipeline → Target Environment → Environment Variable value
Then your JavaScript and scheduled flow can consume the environment variable directly, without requiring a post-deployment manual run. Pipelines support providing/validating environment variables and connection references during deployment.
One thing to keep in mind: if you change an environment variable value directly in the target environment, an existing flow may continue using its previous value until the flow is saved or turned off/on. ALM-based updates are preferable for deployment scenarios.
So I would first look at replacing the "HTTP flow + manually run after import" pattern with either:
- Dataverse-triggered initialization flow, if something actually needs to execute after deployment, or
- Environment variable + solution/pipeline deployment, if you're simply setting environment-specific configuration.
The second option is usually cleaner if the value is just configuration rather than something that needs processing.