HTTP and scheduled triggers

All of these can cause real actions and consume allowance after admission. Start with a manual test before enabling an automatic source.

1. Open the workflow editor and select its HTTP Trigger.
2. Set the method, route/path, and response behavior using the inspector’s controls.
3. Review who may invoke the workflow. Keep it private unless anonymous access is part of the intended product behavior.
4. Select Save to publish the intended graph version. Open More actions → API & schemas to copy the actual endpoint and inspect its input/output contract.
5. Send a harmless test request and verify both the response and the workflow run evidence.

Use HTTP Trigger to receive incoming requests and HTTP Request to send requests to another service.

1. Select Schedule Trigger and choose the supported interval or cron configuration.
2. Set the intended frequency and review any timezone field or scheduler interpretation before enabling it.
3. Publish and synchronize the schedule through the workflow’s available controls.
4. Inspect schedule status and confirm it is active rather than paused.
5. Verify a scheduled run and its result. Pause the schedule when it should stop generating work.

A synchronous request waits for the workflow result. An asynchronous request acknowledges that work was accepted and returns run information. An accepted response is not proof that the workflow completed successfully. Follow the run status to its final outcome.